Remote Rig
RRC 1258 Support in English => General discussion forum => Topic started by: VO1HP on 2016-02-02, 12:37:11
-
While remote K3 radio is ON and functioning the STATUS page at remote RR box show radio status OFF. Why does it show as OFF when radio is actually ON.? Is that the normal indication ??...STATUS will say OFF when radio is ON and also OFF...no change? I had not noticed this previously ...
Also what is the purpose of the DISCONNECT button? .. on this page when the radio is actually ON but status shows radio as OFF...
Same DISCONNECT button is not at CONTROL status page.
Status
Disconnect
Name Value
Radio OFF
Connection status OK
SIP status Connected/transfering
Last SIP error None
RTP status Excellent(60)
-
The on/off indication is connected to a input which is not used in a normal K3 setup, so it will always show OFF.
The disconnect button is there to be able to force a disconnect if you want to connect from an other control device.
Mainly used when you are more than user of a system or if you want to connect with the App but have forgot to disconnect the main Control.
73 de mike
-
OK Thanks for explanation..
.I am still having another issue that started yesterday after my home modem rebooted unexpectedly while I was using the remote. Now when I turn on the K3 remote from home it only will stay on for 5-10 mins and then shuts down...but K3 Mini is still on and gives audible alarm. The connection is being lost for some reason...but why does the K3 shut down...I have been at the remote site and reseated cable to the ACC and I/O jack....but no change in issue.
Any ideas?
FRank VO1HP
-
If the internet connection is lost and data is not comming in any more, the Radio-RRC will send a Power off command to the K3 to prevent it from being switched on for ever. When connecting next time the K3 will be powered up by activating the power on pin in the ACC connector
/mike
-
At present my K3 is OFF and will not turn on. I have powered the RCCRemote OFF and ON and also turn OFF and ON the K3 PS....turning on K3 Mini does not turn ON K3 can see in webcam.
-
If you have set Out0 = connect in the Radio-RRC, Out 0 will go low and start the K3 via the ACC connector at the same time as the yellow LED on the Mic/Aux connect turns on.
/mike
-
Mike Thank you for your reply again. Here is the I/O settings that exist. I have the correct settings according to your note. Still the K3 will not turn on.
Is it possible to use ON/OFF selection and then OFF/ON button to turn on the K3 manually? I tried to set selection to ON/OFF but it does not complete when APPLY CHANGES is clicked.
IO settings
OUT0 mode CONNECT
OUT0 on/off
OUT1 mode KEYER
OUT1 on/off
OUT2 mode KEYER
OUT2 on/off
Frank VO1HP
-
Why should you control it manually ?, if the radio is not starting with out 0 set to "Connected" then check the cable. You may also test that the input in the K3 is working by grounding the input at the ACC connector.
73 de mike
-
It is working again now ...resolved by itself....last night radio was shutting OFF after being on for 5-10 mins...this morning now working OK...radio has been on for over an hour. I reduced the audio BW to #6 maybe the setting I was using #11 too high for the link?......When it quits running the yellow light on Control box flashing ....I wait for 10-15mins and I restart both boxes and turn OFF/ON the K3 PS . Radio will turn on again...
Also wondering if my PS for K3 might be crapping out....old pre-used Astron 35 and I read posts from people who had issues with that unit.
-
Now have audio setting at #2 lowest 16bit setting....find that 12 bit settings too much hiss in background...but 16bit no hiss....will try #2 and see what happens.
-
Yes audio quality higher than 2 is not needed if you do not want to listen to music.
73 de mike
-
https://youtu.be/u2Ti-D0ploo
Mike: please look at this video. Any ideas on what may be causing errors on the K3 Mini display....this happening today for first time.
VO1HP
-
It's caused by packet loss on the internet connection.
/mike
-
Still struggling here with connection problems and K3 will sometimes not turn on....here is a STATUS from recent incident this morning when K3 did come on but shut down shortly there after:
Name Value
Radio OFF
Connection status Faulty(See below)
SIP status Connected/transfering
Last SIP error None
RTP/UDP audio status Stalled(11)
UDP cmd status Error(0)
SIP command timeout 0
Rx Jitter buffer size 12
Rx Jitter delay 8
Dual Rx 0
Current audio packet size 20
-
Yes you have problems with your internet connection. When the counters count down against 0 no data is comming in.
/mike
-
Yes I am beginning to understand what is happening and what the counters mean. RTP/UDP Stalled means that data is not getting transferred between the K3 twins and the line is dropped at the end of the count down to zero.
At the remote site the RR Remote is located in a workshop at the end of 50m of outdoor buried Ethernet cable which is connected to the router in a my cottage. From the logs and stats table for the router I cannot see any errors on the fibre line coming into the house from the FOTS network. Can only assume it is a good line. The modem is new having just been replaced.
In the workshop the ethernet feed enters a TP link SG1008 gigabit switch (cheap $30) and the RR box is on one of the ports of this switch. The interconnecting cable are all shielded Ethernet. Could be there is something gone wrong with the switch or the the patch cords....?
I also have an Afedri-NET SDR also running through the switch and monitoring it remotely at home do not have any issue logging on and tuning around using SDR Console...although intermittently I get some chopping of the audio for a second or so and sometimes will see alert "SYNCH LOST" but radio keeps working and the software keeps decoding.
Here are Speed test results today taken from PC in the remote workshop connected to one of the switch ports:
Download Speed: 130911 kbps (16363.9 KB/sec transfer rate)
Upload Speed: 23513 kbps (2939.1 KB/sec transfer rate)
Latency: 26 ms
Jitter: 10 ms
Packet Loss: -1%
2/6/2016, 5:47:44 PM
I was thinking of doing a reset of the RR Remote to factory settings on my next visit there but will check the switch port first . I didn't like the SG1008 switch in the beginning because it is in a plastic case...it was only switch available locally.
What ever is going on has rendered the K3 remote unusable.
-
Reseting the RRC will not help. it's not that kind of product where the functionality getting degraded over time like PCs, android devices etc. Every time you connect power, it start from 0. Try to use a progrem like ping plotter to find out if the problem is some where between the QTHs. If it's not you have to replace the network components until you found out which one is failing.
/mike
-
Frank,
I have helped over 300 people get their RemoteRig system running over the last few years. In at least 20 cases, it was
necessary to replace a router that was causing the problems that you describe. I would try it from a different location
to determine if the problem is on the radio or control side, then install a different router. Focusing on the RRC will not bring
you any success.
73,
Mitch DJ0QN / K7DX
-
OK Mitch...thanks for your note ...I am focussed now on the gigabit switch that I have at the remote and based on your input will look at moving the router from the cottage to the workshop. Last evening: the K3 would turn on 2 out of 5 times and if it did turn on there was RTP/UDP failure and the counter was started. Last evening the telco network would have been busy with lots of traffic...and heavily loaded but don't know if that is impacting my service at the location...which is at the end of the feed in a rural location.
The strange thing about this problem is this: Today at 6:30am local I turned on the K3 and it has been on for two hours or so...it is now past 0845 and still running....there was one "hit" where the word TERM appeared but the condition went away and the link was restored.
Yesterday I replaced the K3 power supply and I left all the eqpt turned off overnight...i'e K3; K3 power supply and RR unit. The temp in the garage is 5C. I also discovered a setting in the router that was giving QoS priority to IPTV...we do not have that service so I removed that setting.
This would be a non-busy time for the overall network as well.
From time to time I see under DNS status : Failure to resolve remoterig,com
Again
many thanks for your ongoing help and encouragement.
Frank VO1HP
-
Good luck, Frank.
Moving the router is not what I meant; I meant moving the control RRC to a different location and router to see
if the problem persist. If it does, then focus on the radio RRC's router as the cause. If it improves, focus on the
control location's router.
It is highly unlikely that a (non-managed) switch would cause this kind of problem, since they are relatively passive
devices and just pass the packets on. I have seen a couple go bad, but it is rare.
73,
Mitch DJ0QN / K7DX
-
I took the Mini and RR box to a friends FibreOp network location and total functionality was normal. The problem has been isolated to the CONTROL location. The CONTROL telco modem was replaced by the telco but the connection and RTP stalling problems persisted. The telco technician disconnected everything else from the router and K3 Mini performance was normal. IPTV set-top boxes were reconnected and still Mini OK. as well as IPTV PVR service OK
Another device connected to one of the router LAN ports was the issue. I had installed sometime ago a TP LINK SG1008D Ver5.0 8 port gigabit switch. When this switch and its connected devices was removed K3 Mini functionalty is normal. When connected the RTP and UDP packets stall out and eventually result in remote disconnection. I am not yet sure if its is the switch itself or something connected to it that is interfering with the data flow for the Mini....whatever is cauing the issue may have also been creating a problem for the IPTV service whole home PVR.
Further investigation of the switch and connected devices will give the answer. It would not have occurred to me to suspect that the switch would interfere with the flow of data but that is actually the case.
Finally a resolution.....now to further check out each device / feed attached to the now disconnected switch.
Thanks to all for ongoing help in isolating the problem here
-
:)