Hello,
I already tested with Karaf 4.2.8 and Karaf 4.2.9 and the behavior is the
same.
If there is an important observation it is that when the first deployment
of the app feature is carried out, the correct loading of the objects is
not guaranteed, it is difficult to solve it since you have to e
Hello,
Now from zero, with Karaf 4.2.8
1. I made a mistake when testing the libraries, I tested them in the
"deploy" and passed them to the "feature". Attached the modified feature. I
apologize for that.
${project.description}
Implementation of the protocol adapters for usag
> We are closer, jeje
^_^
There's still something strange, installing the aries-blueprint feature
there still a "Unsupported 'Bundle-ManifestVersion' value: 1"
Error executing command: Error:
Unable to create resource for bundle
mvn:org.apache.aries.spifly/org.apache.aries.spifly.weaver-internal/1
Hello,
You need install Blueprint feature, is not install by default.
1. karaf>feature:install aries-blueprint
I see yesterday that new version is out 4.2.9,
But I have not tried it. Still, it's a minor update. From what we said it
should work, the update of libraries are the same as those of t
Hello Cesar,
still no luck, i've redone a clean install and a clean installation of
Karaf (last version 4.2.9).
Which version of Karaf are you using? Cause installing your feature i have
those errors:
Error executing command: Error:
Unable to create resource for bundle
mvn:org.apache.aries.spifly
Bernhard Rupprecht created PLC4X-204:
Summary: S7 Connection: Subscribing not possible
Key: PLC4X-204
URL: https://issues.apache.org/jira/browse/PLC4X-204
Project: Apache PLC4X
Issue Type
Hi,
Your connection string looks something like
modbus: tcp: //192.168.1.69?unit-identifier=12
Take a look at this link,
https://plc4x.apache.org/users/protocols/modbus.html
Best regards,
El jue., 11 jun. 2020 a las 10:17, udeho () escribió:
> Hi all,
>
> I have a general question regarding
Hello Alessio,
If the problem is in Karaf, you probably aren't doing a clean boot, so you
should be using the unmodified version as noted in the previous post.
1. Make sure you compiled the PLC4X project with the modification in clean
form ("> mvn clean install -DskipTests").
2. Perform a clean b
Hi all,
I have a general question regarding the Modbus driver.
Is it possible to specify a specific SlaveID in the connection string (or
elsewhere)?
As far as I have experienced, the slave with ID 0 is always used for connection.
Cheers,
Tim
Hello Julian,
providing the complete connection string the error is still present:
karaf@root()> plc4x:read modbus modbus:tcp://192.168.70.73 coil:1
Find driver service: Modbus
Error executing command: Unsupported transport tcp
During the other test, for example running a local class, the stri
I guess its in your config. If I remember correctly you have to state the
transport layer.
So in your case:
Modbus:tcp://xxx
Does that help?
Am 11.06.20, 12:13 schrieb "Alessio Bernesco Làvore"
:
Thank you very much Cesar for your insight and your detailed explanation,
much appreciat
Thank you very much Cesar for your insight and your detailed explanation,
much appreciated.
I've used your feature to enable your example and my works, now they both
find the Modbus driver and all the flow seems clear to me.
Running your command, but also running my test using an activator, there'
12 matches
Mail list logo