It’s a request from a Logix driver to read the CIP identity object timing out. You can mute the log statement for now…
I think there might be a bug fix necessary here, either to figure out why this “rogue” request is happening (if that’s the case) or to just change the log level.
Thanks for the response.
A) Please excuse my ignorance here, but how do I “mute” the log statement?
B) What is the next step for a final resolution? How do I proceed with figuring out why this “rogue” request is happening?
On the log levels page you can set the level for the ReadIdentityObjectRequest logger to OFF.
If you’d like to send your logs to support that might help figure out what’s going on, but if all your Logix devices are currently connected there’s nothing else to do on your end - it’s just a bug on our end.
No. I haven’t heard back yet. I gave them lots of data to sort through. I feel like it will turn out to be a bug. Can anyone from Inductive Automation comment on the status of this?
It appears that we had a suspect switch in the network. The confusing part was that Rslinx and Studio5000 would happily connect to the PLC where Ignition would not.
Ignition must be a little more fussy when it comes to connectivity…