News:

  • August 22, 2026, 09:20:01 PM

Login with username, password and session length

« previous next »
Pages: [1]

Author Topic: Loss of Communications  (Read 9137 times)

RBPLC

  • Hero Member
  • *****
  • Posts: 586
Loss of Communications
« on: February 14, 2020, 07:01:47 PM »
I have a BX-DM1E-18ED23 that I use for bench testing. After having had the unit powered on for 1-2 months at a time, on two different occasions I've cut power to the unit and when I turn power back on I've lost ability to communicate with it. By this I mean that after powering back up the unit is no longer seen under Links in DMD and the C-More micro that I have communicating with it also loses comms with it. NetEdit doesn't find it either after scanning. Has anyone else had this type of issue or could give me some troubleshooting pointers?
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6172
  • Yes Pinky, Do-more will control the world!
Re: Loss of Communications
« Reply #1 on: February 14, 2020, 11:29:34 PM »
Use a USB POM to connect to it, and check the IP settings. Barring that, I can show you how to clear the IP config.
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: Loss of Communications
« Reply #2 on: February 15, 2020, 08:34:49 AM »
I don't currently have a USB POM. I only have the Ethernet POM which is installed.

If I attempt to create a new link the unit will show up there with an IP Address of 255.255.255.255. I can reconfigure it to get it back online there which is what I did the first time this happened.
« Last Edit: February 15, 2020, 08:54:46 AM by RBPLC »
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6172
  • Yes Pinky, Do-more will control the world!
Re: Loss of Communications
« Reply #3 on: February 15, 2020, 10:27:34 AM »
Quote from: RBPLC on February 15, 2020, 08:34:49 AM
I don't currently have a USB POM. I only have the Ethernet POM which is installed.

If I attempt to create a new link the unit will show up there with an IP Address of 255.255.255.255. I can reconfigure it to get it back online there which is what I did the first time this happened.

If you did a clear all at some point, and added in the check box that cleared the IP setup (it?s off by default), the Ethernet port would continue working fine until the next power cycle.
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: Loss of Communications
« Reply #4 on: February 15, 2020, 10:43:16 AM »
That sounds like a likely candidate. I'll check into this. I've cleared it a couple of times as I'm using it for bench testing.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6172
  • Yes Pinky, Do-more will control the world!
Re: Loss of Communications
« Reply #5 on: February 15, 2020, 10:55:10 AM »
Quote from: RBPLC on February 15, 2020, 10:43:16 AM
That sounds like a likely candidate. I'll check into this. I've cleared it a couple of times as I'm using it for bench testing.

Did it many times during development...thinking it was broken when it lost the IP config days after being cleared. That is why we removed it from the default selection.
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: Loss of Communications
« Reply #6 on: February 16, 2020, 08:29:19 AM »
I'm pretty sure this is what happened. At other times I've powered off the unit and not lost the IP communications. It would be nice to immediately force the reconfiguration of the Ethernet port because (like you said) if you're connected through Ethernet while performing these actions there is no indication that you will have a communication problem after the next reboot. I bet that did cause problems during development when trying to track down an issue that was caused by something that happened at different times before the problem in question.
Logged
Pages: [1]
« previous next »