patrickboisclair commented on issue #1523: URL: https://github.com/apache/plc4x/issues/1523#issuecomment-2061289706
Hi Chris, I think requiring PlcValue is fine. That's what I use with 0.9.1. It's just that right now, in 0.12.0, not all the drivers do so. Best example, is the OPCUA one, which you cannot pass PLCValue. It throws an exception like: Exception in thread "main" org.apache.plc4x.java.api.exceptions.PlcRuntimeException: Expected PlcValue of type NULL but got INT In my use case, I can connect to any type of PLC (supported by PLC4X) via a configuration from a .yaml file. We connect to PLC "x", get the data and push it on different platformms (RabbitMQ, MQTT, Kafka, SignalR,...) depending on the needs. As of now, I can have a workaround using a "switch statement" on the "driver" and using the addTagAdress() method appropriatly, but it just feels inconsistent and "harder" for newcomers. Just my 0.2 cents on the subject :) As always, I really appreciate all the works you guys do on the project. I love PLC4X and just wish the best for it. Best regards -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
