News:

  • July 30, 2026, 11:52:01 PM

Login with username, password and session length

Author Topic: Error Message Time Stamp  (Read 8643 times)

RBPLC

  • Hero Member
  • *****
  • Posts: 586
Error Message Time Stamp
« on: September 30, 2022, 07:22:21 AM »
Is there a timestamp anywhere within DmD associated with error messages generated within System Information?

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6169
  • Yes Pinky, Do-more will control the world!
Re: Error Message Time Stamp
« Reply #1 on: September 30, 2022, 08:34:50 AM »
Is there a timestamp anywhere within DmD associated with error messages generated within System Information?

Only if they are also logged.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

RBPLC

  • Hero Member
  • *****
  • Posts: 586
Re: Error Message Time Stamp
« Reply #2 on: October 03, 2022, 08:25:15 AM »
I haven't looked through the documentation yet but is there an easy way to log these errors? I'm mainly getting a "random" EIPMSG failure.

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6169
  • Yes Pinky, Do-more will control the world!
Re: Error Message Time Stamp
« Reply #3 on: October 03, 2022, 09:56:45 AM »
I haven't looked through the documentation yet but is there an easy way to log these errors? I'm mainly getting a "random" EIPMSG failure.

Every time there is a comm failure, the "On Error" bit or stage will activate. Use that to trigger logic immediately after the EIPMSG instruction to store ERR and $LastError1 somewhere. At that moment, those should contain something useful. If you want a list of them with timestamps, store in a FIFO.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

RBPLC

  • Hero Member
  • *****
  • Posts: 586
Re: Error Message Time Stamp
« Reply #4 on: October 06, 2022, 08:03:16 AM »
I suspect there's still something in the comms stack that's not quite right (I'm referring to the same Modbus/EIP comms issue that was identified some time ago). I have 1 BRX master communicating with 2 BRX slaves over EIP. I started getting random/not persistent comms errors with one of the slaves. Then last week, I had full blown persistent comms failures with one slave. I power cycled both slaves and comms were not restored. I power cycled the master and comms came back immediately. I've got a process running and didn't have time to really troubleshoot.

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6169
  • Yes Pinky, Do-more will control the world!
Re: Error Message Time Stamp
« Reply #5 on: October 06, 2022, 11:36:27 AM »
I suspect there's still something in the comms stack that's not quite right (I'm referring to the same Modbus/EIP comms issue that was identified some time ago). I have 1 BRX master communicating with 2 BRX slaves over EIP. I started getting random/not persistent comms errors with one of the slaves. Then last week, I had full blown persistent comms failures with one slave. I power cycled both slaves and comms were not restored. I power cycled the master and comms came back immediately. I've got a process running and didn't have time to really troubleshoot.

I don't know of any issue with masters of any variety, at least not since 2.9.x. There was definitely an issue in TCP-based masters in 2.8.x.

The only outstanding issue we know about right now is two users have had issues with Modbus/TCP server (slave). Both use radios, and it appears to be a really narrow problem related to network instability.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO