Hi We delivered a system with a PFC100 using the CODESYS Control for PFC100 SL runtime a few years back. The system has once been decommissioned and are now to be commissioned again. Back then, there were only single licenses for the runtime. Can I now upgrade the firmware and runtime without purchasing a new license?
I just noticed in the audit log the following error message on each retry from HMI: CmpDevice: System, Device login from 01D3 failed. So I guess it has something to do with user management?
I just noticed in the audit log the following error message on each retry from HMI: CmpDevice: System, Device login from 01D3 failed. So I guess it has something to do with user management?
Hi I'm having problem accessing published variables from a PFC100 Symbol Configuration on a Exor JMobile HMI. The PFC100 is running FW19, device description version 4.7.0.0. Using compiler 3.5.18.40. I'm noticing the following in the PLC log when the HMI is trying to get data. This is repeating at every reconnection from the HMI. CmpDevice: Session not available anymore! CmpSrv: Invalid session ID. No other session on this channel, close it. The HMI is opening a channel, but this is closing and repoening...
Hi As Wago now has released all their libraries for Codesys 3.5, it should be possible to use modules such as 750-652 with Codesys Control for PFC100 SL device for example. However I have a problem with resolving a dependency in the WagoAppPlcModbus library. This library is dependent on WagoAppSocket, which again is dependent on WagoSysSocketInternal. The latter library is the issue. I'm able to add the missing library as a regular library to the project, but I'm not able to find it when trying to...
Shouldnt be any difference ... Are they running the same FW aswell? I'd expect it to be an configuration issue since the Port can behave as RS232, 422 or 485. Also verify that there is no owner assigned to the serial port on WBM.
yes udev is the way to go. wether config rule works you must test on the device.
You could also do symbolic link from /dev/ttyUSB0/1 to /dev/serial sudo ln -s /dev/ttyUSB0 /dev/serial2 sudo ln -s /dev/ttyUSB1 /dev/serial3 Presuming you keep original .cfg file with Linux.Devicefile=/dev/serial, ttyUSB0/1 will then be available as COM3 and COM4.