Hello all,
We have an implementation where our custom software and driver reads/writes configuration data from/to the PLC into normal tags. Some of these locations are remote so we use a cellular ethernet modem to connect remotely from administration. It seems that the communications drop out from time to time when we are performing a "sync". This dropout appears to be "holding" the port open on the PLC.
We hit the WAN IP address and establish our connection to the cell modem and everything appears to be working fine, port forwards are all intact. When we cycle power on the PLC everything comes back up.
Are there known firmware issues? Better yet, is there a way to perform a reboot of the PLC or the ethernet daughterboard with an internal tag? I could detect comm failure and reboot if there is no use at the station.
Thanks!
We have an implementation where our custom software and driver reads/writes configuration data from/to the PLC into normal tags. Some of these locations are remote so we use a cellular ethernet modem to connect remotely from administration. It seems that the communications drop out from time to time when we are performing a "sync". This dropout appears to be "holding" the port open on the PLC.
We hit the WAN IP address and establish our connection to the cell modem and everything appears to be working fine, port forwards are all intact. When we cycle power on the PLC everything comes back up.
Are there known firmware issues? Better yet, is there a way to perform a reboot of the PLC or the ethernet daughterboard with an internal tag? I could detect comm failure and reboot if there is no use at the station.
Thanks!