"NDI" driver issue

Dave KC9EI

While installing some "NDI" software (not NDIS) on a local laptop on my network, my 6600M rebooted and failed to start. I started getting two "red" slow flashing power switch lights. After numerous attempts to power off, restart, on and on... I reset to factory and recovered. The radio is working fine now and seems to be fine even with the NDI protocol running on the network.

I do have an external GPS running and the power button does not go off completely unless I disconnect the actual power into the radio... which I tried as well.

I'm putting this out "just in case" someone else has seen this as well. NDI is a new(er) semi-protocol to allow screen sharing over IP, even KVM.

FYI

Dave KC9EI

Mike-VA3MW

The NDI software will not have any affect the radio rebooting since the radio is firewalled from all outside communication. It is impossible they are related in a failing sense you are seeing. This is supported by the fact they are both working together now at the same time.

Make sure, when powering on your radio from cold off, that you turn on the DC power supply and then wait up to 2 minutes before hitting the power button on the front of the radio.

https://helpdesk.flexradio.com/hc/en-us/articles/360034961172-The-Correct-Power-Up-and-Power-Down-Sequence-for-M-Model-Radios

Dave KC9EI

Mike,

Three questions:

What is your definition of "outside communication?"

Is SmartSDR considered "outside communications?"

Is Node-Red capable of rebooting a 6600M?

Inquiring minds would like to know. :)

See you on the webinar.

Dave KC9EI

Mike-VA3MW

The 6600M, which runs Windows embedded has its own Firewall that only allows communication to the radio in the same cabinet. It would not see any of your NDI packets.

Communication with the actual radio on port 4992 is possible and rebooting is possible with NodeRed or even FRStack.

There are 2 unique computer systems in the M models.

I hope that helps.

Dave KC9EI

This will be my last post on this subject since it is obviously going nowhere.

My point was simple. When installing the NDI software on another computer on the local network, it did indeed cause the radio (6600M) to reboot and would only recover after performing factory restore.

Further, this is not the first time this has happened on the network. I probably have more running than on this network that most people do, which may have some cause and effect.

The fact that NodeRed can actually reboot the radio indeed DOES prove something outside the actual radio can cause what I'm describing happened or similar.

I was only wishing to document what happened for future reference if needed.

Best Regards

Dave KC9EI