-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Do not throw PlcInvalidTagException exception during batched PlcReadRequest #1776
Comments
…o fail if one item address was wrong. #1776
Ok ... please test again with the latest SNAPSHOT version |
@chrisdutz |
Well the SNAPSHOTS are always automatically updated in apache's Nexus ... see here for how to use them: And regarding the arrays ... yes ... I will have to put a bit of work into that ... I also noticed that recently. This will most probably require a major refactoring of the driver. Especially if you have arrays of UDTs or even more complex tree and array structures such as:
Or even worse, when selecting array ranges ... |
Aaaaaa ... as SNAP (Like Ubuntu snap) ... unfortunately not that I know of ... I thought you were referring to SNAPSHOT. |
Actually you was right first time, thats my typo, i mean SNAPSHOT, already implemented your apache repo. thanks a lot for your help) And you are right about complexity and huge refactoring for Array index feature. |
Yeah ... will be working on that anyway as I need that for a private side-project ... but I think in general we really need to improve the array handling in almost every driver we have. Just with drivers supporting symbolic addressing it gets a lot more tricky :-/ |
What happened?
i am performing reading multiple tag addresses at once, and if one of tag not exist on PLC side, whole request will fail with exception. How can i get response for other tag addresses? Or is there any method that can help me filter out from my request invalid tags?
Exception:
org.apache.plc4x.java.api.exceptions.PlcInvalidTagException: Couldn't resolve symbolic address: GVL_HMI.Mod1Back_Unlck invalid
Version
v0.12.0
Programming Languages
Protocols
The text was updated successfully, but these errors were encountered: