I think you have too many things. The 0.7 release introduced brief
support for OSGi runtimes. If you have PLC4J: OSGi installed then Aries
spi-fly is not necessary.
AFAIK osgi.core shouldn't be installed as it is rather a compile
artifact, and not runtime one.
Best,
Łukasz
On 12.06.2020 11:33,
Hello Cesar,
i think i've some kind of deeper misconfiguration on my side, cause i've
redone a karaf clean install and loaded your updated fixture and command,
but the "Unsopported transport tcp" still remains.
"org.apache.plc4x.java.api.exceptions.PlcConnectionException: Unsupported
transport
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
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
> 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
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
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
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
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
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
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,
Hello Alessio,
As I pointed out, with the new design of the drivers it is necessary to
make a few modifications so that the system allows communication with the
OSGi container.
In a default installation, the load of services in the SPI services are not
seen between the different bundles, and
Thank you Cesar,
thanks for your insight, but i think i'm still lost somewhere.
I've registered the driver inside my bundle context, at least i think so:
[org.apache.plc4x.java.api.PlcDriver]
-
org.apache.plc4x.driver.code = modbus
Hello Alessio,
Perform the test with the "feature" that you put online, and I can see that
the services associated with the drivers are active.
karaf@root()> service:list PlcDriver
[org.apache.plc4x.java.api.PlcDriver]
-
org.apache.plc4x.driver.code = modbus
Thank you Julian,
i've tried to install th Aries SPI Bundle:
176 │ Active │ 80 │ 1.3.0 │ Apache Aries SPI Fly Dynamic
Weaving Bundle
But i'm still unable to resolve the drivers.
Ale
On Mon, Jun 8, 2020 at 8:13 PM Julian Feinauer
wrote:
> Hi Alessio,
>
> if I remember
Hi Alessio,
if I remember correctly you need the Aries SPI Fly package loaded.
In Plain PLC4X we use ServiceLoader to discover drivers.
If you have nothing like Aries SPI Fly which mediates and "immitates" the
ServiceLoader then you dont get a wiring between the DriverManager and the
driver.
16 matches
Mail list logo
