Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
I am using an OpusA3 with version 3.5 SP17 Patch 3 as part of a project. I had no real problem before I encountered a problem that blocked me.
The detection of the OpusA3 from Codesys is done correctly. The gateway is well configured and if I ping the gateway or the OpusA3 I receive the response correctly.
The problem is that when I try to connect, the Opus screen freezes and a few moments later Codesys displays an error message ("connection to device closed").
I tried to change PC, to update the runtime, to change OpusA3 but the problem remains the same. I'm a little lost knowing that before it worked without problem.
I went back to a previous version of the project (where it worked correctly) but the message still appears.
Do you have any clues to solve the problem?
Sincerely,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
I am using an OpusA3 with version 3.5 SP17 Patch 3 as part of a project. I had no real problem before I encountered a problem that blocked me.
The detection of the OpusA3 from Codesys is done correctly. The gateway is well configured and if I ping the gateway or the OpusA3 I receive the response correctly.
The problem is that when I try to connect, the Opus screen freezes and a few moments later Codesys displays an error message ("connection to device closed").
I tried to change PC, to update the runtime, to change OpusA3 but the problem remains the same. I'm a little lost knowing that before it worked without problem.
I went back to a previous version of the project (where it worked correctly) but the message still appears.
Do you have any clues to solve the problem?
Sincerely,
is there a way to check the plclog on Opus A3 by using cmd line under Linux? This log is what you need to check for the disconnection problem
Hello,
Exulting the command /opt/CoDeSysControl/Files/run restart debug I get this response from the linux terminal:(ScreenShot1 to ScreenShot7)
When I try to reconnect via codesys this line appears at the linux terminal level:(ScreenShot8)
A few seconds later, the error window appears on Codesys.(ScreenShot9)
I see that following the command /opt/CoDeSysControl/Files/run restart debug there are errors, are they the problem?
Sincerely,
i found this error in /opt/CoDeSysControl/Files
Last edit: mozed 2023-08-25