[
https://issues.apache.org/jira/browse/PLC4X-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984868#comment-16984868
]
Alvaro del Castillo commented on PLC4X-44:
------------------------------------------
Thanks for the info [~cdutz] . I have also opened an issue about the
deviceId/slaveId/uniqueId hard coded in the current driver. Do you plan to
manage this issue also in the refactor?
[https://issues.apache.org/jira/projects/PLC4X/issues/PLC4X-156]
In order to understand what is a generated driver, is there some doc, issue or
mail message that I could read?
The opc-ua driver, will it follow the same refactor?
In my company we are adopting PLC4x for our edge solutions and our plan is to
get closer to the project and to help.
Thanks!!
> [Modbus] Make the modbus driver support reading and writing of multiple values
> ------------------------------------------------------------------------------
>
> Key: PLC4X-44
> URL: https://issues.apache.org/jira/browse/PLC4X-44
> Project: Apache PLC4X
> Issue Type: Improvement
> Components: Driver-Modbus
> Reporter: Christofer Dutz
> Priority: Major
>
> Currently the modbus driver would throw an Exception when writing more than
> one item and/or value in one request
> Plc4XModbusProtocol.encodeWriteRequest
> This however has to be possible. If the protocol itself doesn't support it,
> we need to implement some automatic code similar to that of the S7 driver
> (See: DefaultS7MessageProcessor and the PendingWriteQueue in S7Protocol)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
