[
https://issues.apache.org/jira/browse/PLC4X-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883771#comment-16883771
]
Christofer Dutz commented on PLC4X-134:
---------------------------------------
Ah ok ... so if you want rack 0 and slot 2 it should have been "/1/2" at the
end. However it seems as if Siemens uses rack and slot not directly, but
instead uses this to calculate the tsapId. I have never had access to a machine
that didn't accept a connection. So if you found a problem here, we should
investigate and correct the S7TsapIdEncoder classes. Could you perhaps send us
a packet capture of a connection (with TIA for example) with that device? That
would help us a lot ... I think the patch you suggested would completely make
"rack" and "slot" options obsolete and I think they do have a purpose.
> 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)
