[
https://issues.apache.org/jira/browse/PLC4X-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894656#comment-16894656
]
Julian Feinauer commented on PLC4X-134:
---------------------------------------
[~generalkelly] I did not follow the whole discussion technically (as [~cdutz]
is definetly the expert here) but what about preparing a PR with your suggested
solution.
Then everybody can check against his PLCs (we have a 1500 here) and if its
good, we simply merge it.
I also proposed a solution for optional parameters on the list here:
https://lists.apache.org/thread.html/7ce5ef03aef5ef92e96be6afa8d57fb0de3d2e08193d6f8dc7f56881@%3Cdev.plc4x.apache.org%3E.
> S7 is terminating the connection during handshake
> -------------------------------------------------
>
> Key: PLC4X-134
> URL: https://issues.apache.org/jira/browse/PLC4X-134
> Project: Apache PLC4X
> Issue Type: Bug
> Components: Driver-S7
> Affects Versions: 0.5.0
> Reporter: Mirko Pohland
> Priority: Critical
> Attachments: stack_trace.txt
>
>
> When trying to connect to my S7-300 I get the following error (stack trace
> attached):
> {color:#FF0000} org.apache.plc4x.java.api.exceptions.PlcIoException:
> Connection terminated by remote{color}
> After some debugging I found out that I can fix this issue by doing a small
> change in S7PlcConnection.java
>
> From
> short calledTsapId = S7TsapIdEncoder.encodeS7TsapId(DeviceGroup.OS,
> 0, 0);
> short callingTsapId =
> S7TsapIdEncoder.encodeS7TsapId(DeviceGroup.PG_OR_PC, rack, slot);
> where calledTsapId does not contain rack and slot to
> short calledTsapId = S7TsapIdEncoder.encodeS7TsapId(DeviceGroup.OS,
> rack, slot);
> short callingTsapId =
> S7TsapIdEncoder.encodeS7TsapId(DeviceGroup.PG_OR_PC, 0, 0);
> Now I can connect to the S7.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
