[ 
https://issues.apache.org/jira/browse/PLC4X-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012490#comment-17012490
 ] 

Alvaro del Castillo commented on PLC4X-159:
-------------------------------------------

It is open yet. I would like to find time also to fix it, and it is beating me 
because once you write several registers in different calls I experiment 
problems communicating with the modbus server (probably because the open 
futures not resolved already created).

> 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)

Reply via email to