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

Lukas Ott commented on PLC4X-338:
---------------------------------

This issue has been migrated to https://github.com/apache/plc4x/issues/639

> s7 could not write CHAR array
> -----------------------------
>
>                 Key: PLC4X-338
>                 URL: https://issues.apache.org/jira/browse/PLC4X-338
>             Project: Apache PLC4X
>          Issue Type: Bug
>          Components: Driver-S7
>    Affects Versions: 0.9.0, 0.10.0
>         Environment: Ubuntu 18.04
>            Reporter: Julian Zhang
>            Priority: Blocker
>
> h2. Use case
> Writing CHAR array to S7 PLc via plc4x sink kafka connector was throwing an 
> error, as is shown in the code snippet:
> {code:java}
> "sinks.CommonPlcSetup.fields.steelGradeCurrent": "%DB851:136:CHAR[12]" {code}
> h2. The error messages
> {code:java}
> [2022-03-01 03:22:16,673] INFO Configuring Bootstrap with 
> Configuration{local-rack=1, local-slot=1, remote-rack=0, remot-slot=5, 
> pduSize=1024, maxAmqCaller=8, maxAmqCallee=8, controllerType='null'} 
> (org.apache.plc4x.java.transport.tcp.TcpChannelFactory)
> [2022-03-01 03:22:16,680] INFO S7 Driver running in ACTIVE mode. 
> (org.apache.plc4x.java.s7.readwrite.protocol.S7ProtocolLogic)
> [2022-03-01 03:22:16,772] ERROR No DataTransportErrorCode for value 7 
> (org.apache.plc4x.java.s7.readwrite.DataTransportErrorCode)
> [2022-03-01 03:22:18,340] ERROR No DataTransportErrorCode for value 7 
> (org.apache.plc4x.java.s7.readwrite.DataTransportErrorCode)
> [2022-03-01 03:22:18,363] ERROR No DataTransportErrorCode for value 7 
> (org.apache.plc4x.java.s7.readwrite.DataTransportErrorCode)
> [2022-03-01 03:22:18,363] ERROR No DataTransportErrorCode for value 7 
> (org.apache.plc4x.java.s7.readwrite.DataTransportErrorCode) {code}
> h2. Context
> This was working with version 0.9.0-SNAPSHOT, but my customized version could 
> no longer be compiled on 0.9.0-SNAPSHOT, so I had to compile the the code 
> against 0.10.0-SNAPSHOT
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to