Licensed BBB No connection to device ^{CODESYS Forge talk (Thread)}
Licensed BBB No connection to device
Last updated: 2017-01-08

Connection to device closed ^{CODESYS Forge talk (Thread)}
Connection to device closed
Last updated: 2023-08-25

No connection to webvisu ^{CODESYS Forge talk (Thread)}
No connection to webvisu
Last updated: 2022-09-23

PFC200 Update to 4.9.0.0 - No Connection ^{CODESYS Forge talk (Thread)}
PFC200 Update to 4.9.0.0 - No Connection
Last updated: 2023-09-27

PFC200 Update to 4.9.0.0 - No Connection ^{CODESYS Forge talk (Thread)}
PFC200 Update to 4.9.0.0 - No Connection
Last updated: 2023-09-28

No connection to target: An existing connection was forcibly closed by the remote host ^{CODESYS Forge talk (Thread)}
No connection to target: An existing connection was forcibly closed by the remote host
Last updated: 2024-08-11

No device is responding to the scan request ^{CODESYS Forge talk (Thread)}
No device is responding to the scan request
Last updated: 2017-04-29

Add device to the device repository ^{CODESYS Forge talk (Thread)}
Add device to the device repository
Last updated: 2015-03-30

Profinet connection to Siemens CP343-1 Lean (IO-Device/Slave) ^{CODESYS Forge talk (Thread)}
Profinet connection to Siemens CP343-1 Lean (IO-Device/Slave)
Last updated: 2023-08-26

Only a limited connection to the device could be established. Therefore programming functions cannot be used. ^{CODESYS Forge talk (Thread)}
Only a limited connection to the device could be established. Therefore programming functions cannot be used.
Last updated: 2020-04-28

No Device Responding to Scan Request ^{CODESYS Forge talk (Thread)}
No Device Responding to Scan Request
Last updated: 2015-08-14

no connection to target (Raspberry not found) ^{CODESYS Forge talk (Thread)}
no connection to target (Raspberry not found)
Last updated: 2018-04-26

No connection to opc server from codesys opc client ^{CODESYS Forge talk (Thread)}
No connection to opc server from codesys opc client
Last updated: 2024-08-19

ERROR no connection With RPI ^{CODESYS Forge talk (Thread)}
ERROR no connection With RPI
Last updated: 2024-01-11

No device is responding... ^{CODESYS Forge talk (Thread)}
No device is responding...
Last updated: 2015-07-05

No device is responding to the scan request after password prompt ^{CODESYS Forge talk (Thread)}
No device is responding to the scan request after password prompt
Last updated: 2022-05-21

Codesys no device is responding to scan request ^{CODESYS Forge talk (Thread)}
Codesys no device is responding to scan request
Last updated: 2021-07-12

Post by docker on Canopen connection. Unknown node id. ^{CODESYS Forge talk (Post)}
hi, i am currently trying to adapt an i/o device for a project. the node id is unknown and there is no eds file available. no data is being emitted from the device as a giveaway, the baudrate is known but useless without the node id. is there an sdo request available to determine the id? i cannot get the device to leave pre op status even with a global nmt request. please help. no hair left.
Last updated: 2023-09-25

Profinet Device keeps abort connection with AR alarm.ind(err) ^{CODESYS Forge talk (Thread)}
Profinet Device keeps abort connection with AR alarm.ind(err)
Last updated: 2023-08-21

How to add an own device to the bus-master? ^{CODESYS Forge talk (Thread)}
How to add an own device to the bus-master?
Last updated: 2016-04-13

Post by mozed on Connection to device closed ^{CODESYS Forge talk (Post)}
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,
Last updated: 2023-08-23

Post by kuegerls on SysProcessExecuteCommand2 and CANopen Device ^{CODESYS Forge talk (Post)}
I am now executing the process in a separate task with lower priority, but unfortunately, the connection to the master is still interrupted.
Last updated: 2024-06-21

connection ^{CODESYS Forge talk (Thread)}
connection
Last updated: 2020-04-25

No route to the host error ^{CODESYS Forge talk (Thread)}
No route to the host error
Last updated: 2022-09-13

No Driver Found I2C Device ^{CODESYS Forge talk (Thread)}
No Driver Found I2C Device
Last updated: 2018-04-01

Sort by relevance or date