Remote Rig
RRC 1258 Support in English => General discussion forum => Topic started by: oh2xx on 2020-10-03, 11:22:34
-
Hi,
We have encountered a new issue at OH0Z. We need to switch the power of the Radio-RRC off/on to get connected otherwise there is a SIP error as follows:
Name Value
P5.4 ON
Radio ON
Connection status Disconnected
SIP status Unknown(1)
Last SIP error SIP Error
RTP/UDP audio status Disconnected
UDP cmd status Disconnected
SIP command timeout 4
Rx Jitter buffer size 16
Rx Jitter delay 13
Dual Rx 0
SIP Out port 13000
SIP In port 13000
Audio Out port 13001
Audio In port 11000
Command Out port 13002
Command In port 12000
External SIP In port 13000
External Audio In port 11000
External Cmd In port 12000
Other party
Other party(mac)
Input 0 High
Input 1 High
Input 2 High
Output 0 Low
Output 1 Low
Output 2 Low
DNS status OK, .....
Active profile OH0Z
PTT status OFF
Common network settings No
System messages No
What could be the root cause for this one? We have not changed any settings in at least 2 years.
And as said power reboot helps but as we do it remotely the whole station is rebooted (PC, 4G modem, etc.) so and we are very reluctant to do that every time to run the station.
73 de Kari, OH2XX
-
Kari,
If you didn't change anything, then the problem is not with RemoteRig. Something in your
network environment has changed. Did your provider change something? New router? Is this
problem from multiple user locations, or only one?
A tip: you can just logon to your radio RRC over the internet and click on reboot. No need to
physically take power off of it until you find the problem.
73,
Mitch DJ0QN / K7DX
-
Hi Mitch,
Thank you for your reply and suggestions.
Yes, the problem is from multiple user locations. No known changes by the ISP/Mobile operator. Remote desktop, IP Cameras etc. work flawlessly as before. Public IP updates via DDNS ok.
The RRC WEB interface is not responsive - has never been. We can access it only right after the reboot (not tested that for a while though) but then lose it quite soon after. The web interface is not accessible even via the remote PC in the same LAN segment. Pinging the RRC fails too so could it be the aggressive robots/DoS type of behaviour causing the issue? We have not the latest FW installed that seems to have some WEB interface improvements.
73 de Kari, OH2XX
-
Hi Kari,
I have never heard of that problem with the web interface. I assume that you changed it from
80 to something else to prevent the normal and expected port conflicts with port 80.
You problem is obviously at the radio side. It could be anything, even a bad switch. I suggest
systematically trying to locate the problem. You are wasting your time if you look at the RRC as
the problem, I believe.
73,
Mitch DJ0QN / K7DX
-
Yes you have ;-)
http://www.remoterig.com/forum/index.php?topic=3818.0
And yes, the port number is changed from 80.
Trying to locate the problem but so far the SIP -error, unresponsive WEB-interface and no replies to PING requests point heavily to RRC. But we'll see.
73 de Kari
-
Hi
Remoterig cannot have a failiure which gives this type of problem it's typical ISP or Router problem
73 de mike
-
Ok,
Could be that or something else. Any ideas what to try next? Why does WebSwitch 1216H at OH0Z respond but RRC does not? Why does rebooting RRC help?
73 de Kari
-
Hi,
Checked today if Telnet debug gives any hints what is going on. Here are the results:
At remote site:
debug2 = 1
debug
=========================
+-:debuglevel
q: exit
0: com0-debug on/off
1: com1-debug on/off
2: com2-debug on/off
3: com3-debug on/off
4: com0-ascii on/off
5: com1-ascii on/off
6: com2-ascii on/off
7: com3-ascii on/off
8: debug2 on/off
i: icom-mic debug on/off
m: mode-10 debug on/off
t: comx time-stamp on/off
w: winkeyer on/off
CP-> Radio ON(Error)
SIP Timeout, state = ERROR
CP-> Radio ON(Error)
SIP Timeout, state = ERROR
CP-> Radio ON(Error)
SIP Timeout, state = ERROR
At radio site:
Not able to event connect via telnet to the RRC
"Connecting To 192.168.100.228...Could not open connection to the host, on port 23: Connect failed"
73 de Kari, OH2XX
-
There is nothing you can change in the RRC to make any difference. If it's not related to the Router it must be some hardware failure in the Ethernet PHY.
You can try to change IP and port number with the webswitch, maybe ethernet cable also. Does the router indicate ETH LINK when it's not working ? Can you ping the RRC from the router ?
73 de mike
-
Rebooted all and connected to RRC via WEB interface (it works for a while after reboot...)
Tried to upgrade the FW from current 2.90 to 2.95 to see if makes any difference.
Unfortunately the upgrade fails time after time. "Uploading at 33% ..." is the last message and after that there is a blank web frame with the following error message "The webpage at http://192.168.100.228:87/flash might be temporarily down or it may have moved permanently to a new web address."
Rebooted and tried again with the same result. Could this be related to these other symptoms we have encountered?
Tried yesterday also to ping the RRC (from the router) after radio failed to connect. It did not respond:
PING 192.168.100.228 (192.168.100.228): 32 data bytes
--- 192.168.100.228 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
Rebooting RRC helps and after that PING naturally works ok.
So it seems that it is not a configuration/cable/HW issue.
Cannot see the Ethernet LEDs via IP camera.
Just trying to analyze the case as much as possible to have a clear plan when we visit the station next time. Perhaps we need to get a spare RRC just in case.
Here is the Radio RRC Info page:
Name Value
Company Microbit
Product 1258
PID 4
Version 7
HW 8
Software 2.90
Bootloader 1.10
Compiler 4.6.2
Build Feb 17 2016 10:16:14
ROM/RAM 481192/44080
ETH-RAM 2944 (max 3kB)
USB-RAM 15352 (max 16kB)
Battery-RAM 4
ResetSrc 0 [3]
Last WD Reset 10
Uptime 0 Days, 0 Hours, 12 Mins, 32 Secs
73 de Kari, OH2XX
-
Tomi OH6EI decided to go on the island on Thrusday to run the SAC. We hope to have enough time to order a spare RRC unit with express delivery from Sweden to Tomi before his departure...
73 de Kari, OH2XX
-
Hi,
A new RRC is now in place. After 24 hours we encountered the same problem.
Tomi is on site testing. Ethernet LED blinks on both RRC and 4G router end. No Ethernet HUB in between. Changed the Ethernet cable too but it did not help. (the Ethernet cables are good quality CAT6 double shielded and only 3 meters long) Ping failed too as expected.
So we powered RRC off/on again and it helped.
I think this is an RFI problem - or any other ideas?
We will ground the RRC case and wire 12 VDC via WebSwitch to make rebooting easier in the future if needed.
73 de Kari, OH2XX
-
I doubt it's RFI. if so it should reboot when transmitting. But such problems are rare since people stopped using ADSL. Try to change router or at least try to put a switch in between to make any changes to the setup.
73 de mike
-
Mike,
He doesn't believe us that it is his network and not the RRC.
73,
Mitch DJ0QN / K7DX
-
Hi,
Thank you for your comments. And yes, I can admit I have trouble believing it is a network issue ;-) But perhaps we'll change the 4G router and put a switch there next time to see if it helps. It is still quite perplexing that the Webswitch stays alive and the RRC does not. I am also using another Radio-RRC in a different location here in Finland with the same 4G router model and the setup has been running flawlessly for many years.
73 de Kari, OH2XX
-
Karl,
I assume that the Webswitch and RRC web page are using different port numbers?
73,
Mitch DJ0QN / K7DX
-
Hi,
Just for the record.
I was running today for 1,5 hours from OH0Z on 15m. I kept the remote PC at OH0Z pinging the 4G router the whole time. I had one connection failure that time after working about an hour and noticed from the web interface that RRC had rebooted itself for some reason, while the PC ping statistics were as follows:
Ping statistics for 192.168.100.1:
Packets: Sent = 7717, Received = 7717, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 15ms, Average = 2ms
I had the RRC ping watchdog set to reboot - so perhaps that triggered it. I have now disabled it.
I am sure this (RRC/Network) issue will be figured out one day it is going to be something very simple, but for now it is just a mystery to me ;-)
And do not get me wrong - I really like the product and want all the best for it.
73 de Kari, OH2XX
-
Mitch,
Yes, 81 for RRC and 500 for webswitch.
- Kari
-
Karl,
Try changing port 81 to something else and forward that port.
73,
Mitch DJ0QN / K7DX
-
Hi,
Just a quick update on this. I changed the web port last weekend to over 500 (and changed the NAT setting respectively) and also disabled the ping watchdog. The RRC has been up and running since then and today I turned the radio on for the first time after the changes and made a few QSOs on 15m. It took just one or two QSOs after which the RRC's web interface stopped responding. Trying to reload it gave an error message saying "192.168.100.228 took too long to respond" (from the remote PC at OH0Z and my home PC). Anyway the radio worked ok for the 10 minutes I was running. But if we need to reboot the RRC the remote power switch is now the only option to do that.
73 de Kari, OH2XX
-
Kari,
If it only stops working after some QSO's, then it looks like RF is getting into the network.
73,
Mitch DJ0QN / K7DX
-
Yes,
Funny it affects only the WEB interface though. Everything else seems to work now. Been running FT8 on 160m for an hour now without any issues. The RRC's web interface is still unresponsive. That is not very critical as we can reboot the power remotely if needed. But to make things close to perfection it would be nice to resolve the web interface issues as well.
73 de Kari, OH2XX
-
Hi
As two units behave in the same way it's obvious that it's something outside the RRC which is causing the trouble. I have never heard RFI having that effect before, I doubt it's the reason probably it's more simple, but who knows.
73 de mike
-
Hi,
Well, my logic works the other way :-) if there are two (or three, see below) RRC units having similar issues and everything else in the network works fine (PCs, Webswitches, IPCameras, etc.) the problem must be inside the RRC.
As said there is a third RRC behaving the same way (at OH2U). The web interface is unresponsive but the radio connection works anyway. I just checked it again today and the issue is still there - radio works but the web interface does not. The Webswitch at OH2U has not had any web interface issues during these years.
Here is the link to my original post (in 2015 :-) http://www.remoterig.com/forum/index.php?topic=3818.0
If you read it through you will find out that I was not the only one who had experienced the web interface problem.
It would be nice to find a fix - be it anywhere. RFI is not the prime suspect for me either at the moment.
73 de Kari, OH2XX