Florian Probst created PLC4X-179:
Summary: Initial connection terminated from PLC
Key: PLC4X-179
URL: https://issues.apache.org/jira/browse/PLC4X-179
Project: Apache PLC4X
Issue Type: Bug
Hi,
perhaps one minor thing... seems like you are missing a DB Number in your query
string.
But indeed a wireshark dump would help us to trace down the problem.
Could you open a Jira Issue for that (issues.apache.org) and attach the Dump
there (no attachements are allowed here).
Thank you!
Hi Chris,
thanks for your answer. I tried you suggestion, but then I got the following
message in the logs:
16:27:58.368 [main] DEBUG org.apache.plc4x.java.s7.connection.S7PlcConnection -
Unknown parameter controllerType with value S7_400
I assume you mean the parameter "controller-type"
Hi,
I managed to get BIT, BYTE, WORD and DWORD working, seems like there was a
problem in the generated source file DataItemIO.java. This file is generated
with a template and a .mspec file, so I don't know how to modify it really
well. I modified the generated sources locally (yikes) because
Hi Florian,
I just noticed that it's failing on sending the first message where the type
isn't requested.
So I guess you're correct that the problem is related to the tsap id and we did
have an issue with this as the connection string only configured the local
partner part and not the remote
Hey folks,
its release time again!
As discussed on multiple occasions, the 0.6 release branch will be a „LTS“
release of the „old fashioned“ or „hand written“ drivers.
The develop will be the 0.7.0 branch and will contain the generated drivers.
Please check the RELEASE_NOTES for all details.
Hi Florian,
from the log PLC4X is a little disappointed that the PLC just hangs up without
any notice.
I've had this problem with Siemens LOGO "PLC"s ... there the identification
step was causing problems.
Could you please append the following to your connection string?
?controllerType=S7_400
Hi,
The original version only handled the binary types correctly (BYTE, WORD,
DWORD), for the rest it generates the problems that you point out.
I am working on the writing of CHAR and TIME types, etc. I indicate when
you finish these modifications.
On my fork of GitHub and mount the
Hi,
The url is ok.
If you have a request that generates an internal exception in the drive, it
may cause the problem.
Try to just connect and generate a wait on the task.
Can you show the code?
Best regards,
El mié., 26 feb. 2020 a las 5:14, Probst, Florian (<
florian.pro...@de-gmbh.com>)
Hello all,
we're trying to replace our old style native INAT library by using a pure Java
PLC library.
I'm trying to connect to our S7-400 PLC but the PLC terminates the connection
after the first message sent.
As URL I've used the following:
s7://192.168.3.166/0/3
Earlier we used the TSAP
10 matches
Mail list logo