I have a customer system running a PR1 with a local I/O rack. Periodiacally, Groov View will losely lose connection to the I/O tags in groov view. When this happens I am no longer able to open the local I/O drop-down in the tag tree.
The I/O rack is configured in pac Control as local loopback and is the only I/O rack for this controller. The I/O rack shows good communication to the strategy when I open it in debug mode. This has happened a few times, a few months apart, with no obvious cause. The I/O rack will still be communicating to the controller, and any strategy tags in Groov View will still be connected, it’s only the Groov View local I/O tags that disconnect. So far the only way to make it restore is to restart the controller. I noticed the firmware on the controller is 3.5.1 and will be updating to 3.6.0 in hopes this will fix the issue.
When its disconnected, whats the yellow triangle show when you click on it?
Whats the local I/O show for device health, both now (when its Ok) and when its disconnected?.
Are you using ‘localhost’ or 127.0.0.1?
Have you tested connecting some groov View tags to the strategy and some to the local I/O?
When it disconnects next and after you have got the information, try just restarting groov View via its groov Manage menu rather than restarting the whole controller. If that works or not is a good data point.
When it next happens, view and grab the groov View logs.
I will have to respond to this more fully if it happens again. For now,
2.device health shows an average scan of 14ms with a max of 65ms
3.“localhost”
4.groov View tags connected to strategy work fine, while local I/O does not
Just to be clear, on point 4… Connect some tags to the I/O in the strategy. I understand there is a subtle difference between strategy tags and the I/O point tag names.
Hence trying both I/O tag names and the local I/O device.
Ok, I finally have all the data requested. It disconnected again today and I was able to get what I needed.
The yellow triangle says “Could not connect to the controller, groov will keep trying to connect. Details: Waiting 5.0 seconds until trying to reconnect to device OptoMMP@localhost:2001.”
The status of the Local I/O shows ERROR.
Response time: average-37.1ms, min-13.25ms, max-.14s, 75th percentile-44.51ms, 99th
percentile-0.14s.
Errors at 1.5 the last minute, 1.6 the last 5 minutes, 1.2 the last 15 minutes. No writes had been
attempted, and the read attempts were 0 as soon as the error showed up.
I’m using localhost for the address
groov View tags to the strategy I/O are unaffected, tags to Local I/O are disconnected
Restarting groov View via groov Manage does not fix the problem
Definitely contact product support (support@opto22.com), let them know what’s going on, and send the logs. It sounds like the I/O scanner on the system has gone offline, but if that happens then the strategy running should be having trouble at as well.
Download the logs both from within groov View (via the log viewer) and from within groov Manage. The groov View logs that Manage downloads are mostly meant for troubleshooting startup issues and don’t have a complete set of details in them.
