FUDforum
My FUDforum

Home »  » DeviceMaster RTS, Pro and Serial Hub » DeviceMaster RTS 1 port non responsive after reset
DeviceMaster RTS 1 port non responsive after reset [message #973] Sat, 26 May 2018 18:06 Go to next message
severach is currently offline  severach
Messages: 14
Registered: December 2016
Location: Michigan
Member
DeviceMaster RTS 1 port - NS-Link 11.23

From web interface, select System, Restore Defaults, [x] Everything

The DeviceMaster is non functional until power cycled.
Re: DeviceMaster RTS 1 port non responsive after reset [message #974 is a reply to message #973] Sat, 26 May 2018 19:07 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 290
Registered: July 2016
Location: Minnesota
Power User
Hi Severach,

After the reboot do you see the default settings in PortVision?

Is it still unresponsive after the reboot?

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 1 port non responsive after reset [message #975 is a reply to message #974] Sun, 27 May 2018 12:37 Go to previous messageGo to next message
severach is currently offline  severach
Messages: 14
Registered: December 2016
Location: Michigan
Member
On reboot after restore defaults no utility can see the DeviceMaster.

On reboot after power cycling the utilities can see the DeviceMaster with defaults. I can program the IP to show up on the network.
Re: DeviceMaster RTS 1 port non responsive after reset [message #976 is a reply to message #975] Tue, 29 May 2018 09:58 Go to previous messageGo to next message
Austin is currently offline  Austin
Messages: 9
Registered: March 2018
Location: Minnesota
Member
Severach:

After power cycling, do you need to reboot it every time to get it to work properly? Once you restore defaults, everything including IP address, ports, network settings are cleared. Then, once you change any of these settings again you need to power cycle to have them take effect. Afterwards, the device will retain the settings and work properly; but, once you restore defaults again you'll need to change all the settings to the way you had them.

Austin


Austin Wong-Parker | Technical Support
www.comtrol.com

Comtrol Corporation
100 5th Avenue NW
New Brighton, MN 55112

austin.wong-parker@comtrol.com
Main: 763-957-6000

[Updated on: Wed, 30 May 2018 10:44]

Report message to a moderator

Re: DeviceMaster RTS 1 port non responsive after reset [message #978 is a reply to message #976] Tue, 29 May 2018 12:44 Go to previous messageGo to next message
severach is currently offline  severach
Messages: 14
Registered: December 2016
Location: Michigan
Member
Only the first boot after reset requires a repower. Reboot after changed settings works fine.
Re: DeviceMaster RTS 1 port non responsive after reset [message #981 is a reply to message #978] Tue, 29 May 2018 16:38 Go to previous messageGo to next message
Austin is currently offline  Austin
Messages: 9
Registered: March 2018
Location: Minnesota
Member
Severach:

Okay, I see. I will need a bit of clarification on, "DeviceMaster is non functional until power cycle". Is the DM not able to be found on PortVision? Pinging it doesn't work?
Once you restore default and reboot it, does the DeviceMaster still not work?

Austin


Austin Wong-Parker | Technical Support
www.comtrol.com

Comtrol Corporation
100 5th Avenue NW
New Brighton, MN 55112

austin.wong-parker@comtrol.com
Main: 763-957-6000

[Updated on: Wed, 30 May 2018 10:44]

Report message to a moderator

Re: DeviceMaster RTS 1 port non responsive after reset [message #983 is a reply to message #981] Tue, 29 May 2018 21:02 Go to previous messageGo to next message
severach is currently offline  severach
Messages: 14
Registered: December 2016
Location: Michigan
Member
PortVision is Windows. I use the Linux tools. On the automatic reboot after the reset nslinkadmin does not see the DM as a Bootloader or a SocketServer.

I added 192.168.250.249/24 to my ethernet adapter and ping 192.168.250.250 gets no response.

After power cycling nslinkadmin finds the defaulted RP1 and ping works.

>Once you restore default and reboot it, does the DeviceMaster still not work?

This is what makes the DM stop responding.

Steps

RP1 with v4.28/v11.23

Web Interface, System, Restore Defaults, [x] Everything, (automatic reboot)

run nslinkadmin over and over. RP1 will not show up.

Power Cycle

nslinkadmin, (select RP1), ie, r, q

RP1 is fully functional on the network


Remotely resetting an RP1 forces a site visit.
Re: DeviceMaster RTS 1 port non responsive after reset [message #984 is a reply to message #983] Wed, 30 May 2018 11:52 Go to previous messageGo to next message
Austin is currently offline  Austin
Messages: 9
Registered: March 2018
Location: Minnesota
Member
Severach:

Thank you for the steps. I tested the restore defaults and tried responding to my DM. It appears this is normal behavior for our DeviceMaster; you will need to power cycle it unfortunately after restoring defaults. I will see if there is any alternatives to this; perhaps a work around. If I may ask, is restoring to default a necessary step for your system to function properly?

Thank you,

Austin


Austin Wong-Parker | Technical Support
www.comtrol.com

Comtrol Corporation
100 5th Avenue NW
New Brighton, MN 55112

austin.wong-parker@comtrol.com
Main: 763-957-6000
Re: DeviceMaster RTS 1 port non responsive after reset [message #985 is a reply to message #983] Wed, 30 May 2018 15:19 Go to previous message
Austin is currently offline  Austin
Messages: 9
Registered: March 2018
Location: Minnesota
Member
Severach:

After some testing on the DM RTS 1 port, it appears the Device sometimes opens the port and sometimes it does not. In the tests that opened the port, we would restore default and wait 30seconds - 1 minute. Then opened Wcom2 (Test Terminal) and had a successful and functional DM. In the tests that failed, we did the exact same thing, trying different intervals of when we opened the port. One thing is for certain: wait for the device to be in NS-Link before opening the port. We're still not 100% sure why the device is functioning like this, but those are our findings at this time. We did try in windows and linux as well.
For your system, I recommend waiting for the NS-Link, about 30seconds - 1minute, and try multiple tests. It seems pretty inconsistent whether the port will open or close.
I hope this clarifies some of the confusion; we'll get back to you if we find anything else.

Thank you,

Austin


Austin Wong-Parker | Technical Support
www.comtrol.com

Comtrol Corporation
100 5th Avenue NW
New Brighton, MN 55112

austin.wong-parker@comtrol.com
Main: 763-957-6000
Previous Topic: Cant open COM Ports
Next Topic: Invalid Digital Signature message
Goto Forum:
  


Current Time: Wed Jun 23 00:11:31 CDT 2021

Total time taken to generate the page: 0.01010 seconds