20 Apr
2018
20 Apr
'18
2:09 p.m.
EchoLink on our repeater is confused, and we are trying to reset. The EchoLink module has been in a “noload” state for over two days now, and the EchoLink website still shows our node as being a valid login. I’ve sent a service request in to EchoLink without response. My question is this, do I need to do more than “noload” the EchoLink module so the EchoLink server won’t see us as a login? Thanks, Bob K6ECM Sent from iPad