The alarm codes only sticks for up to 2 seconds, but these settings still seems to miss the values and catches when the errorcode has returned to “0000”.
I have had “Rate” set to 100 and it still seems to miss the data.
It kept recording “0000” when the alarm text for the mobus function reset the alarm code back to zero before initiating the next comm cycle., which happens 2s after the last device has been cycled thru. (7 devices, 2 reads each),
But now i have changed historical group to Direct and 100 ms
and on each tag i have, they are now get to Sample mode: Tag group, and now it catches each error code almost instantly, so i can fault trace, which is the desired outcome.
Im not sure most of the problem was/is because i sit in a craptop lenovo thinkpad.
Got a bunch of stuff running like brave browser, visual studio with a debugging session for a c# hmi, omron sysmac online against the plc in question, and mysql in the background with mysql workbench and ignition backend, designer and hmi/runtime.
I did some changes to the tags and historian group, but i think i wrote it in another of my threads, that seems to changed to work,but im not sure if its the optimal settings, but now it catches these non-“0000”-errorcodes tossed by the modbus calls.
