[
https://issues.apache.org/jira/browse/PLC4X-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990401#comment-16990401
]
Alvaro del Castillo edited comment on PLC4X-159 at 12/7/19 8:47 AM:
--------------------------------------------------------------------
!Screenshot from 2019-12-07 09-44-45.png! This is the data received from the
modbus server after writing the data. So it seems the communication flow is ok.
was (Author: acs):
!Screenshot from 2019-12-07 09-44-45.png!
> modbus: Future which writes data correctly in modbus does not return
> --------------------------------------------------------------------
>
> Key: PLC4X-159
> URL: https://issues.apache.org/jira/browse/PLC4X-159
> Project: Apache PLC4X
> Issue Type: Bug
> Components: Driver-Modbus
> Reporter: Alvaro del Castillo
> Assignee: Christofer Dutz
> Priority: Major
> Fix For: 0.6.0
>
> Attachments: Screenshot from 2019-12-07 09-44-45.png
>
>
> When writing data registers in modbus, the data is written correctly but the
> Future which does it does not return. The hack is just to not wait for the
> Future because you don't need the results. Just that the data is written. But
> if there are some error during the writing you don't know it. And probably
> the resources are not freed correctly.
> Some sample code:
> {code:java}
> PlcWriteRequest writeRequest = connection.writeRequestBuilder()
> .addItem(registerName, "register:" + offset + "[" + size + "]",
> writeRegister)
> .build();
> writeRequest.execute().whenComplete((writeResponse, error) -> {
> assertNotNull(writeResponse);
> });
> {code}
> The whenComplete is never called. I have follow the code and the "decode"
> method is called, so it is when processing the response from the modbus slave
> where the problem is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
