Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - dj0qn

Pages: [1] 2 3 ... 136
Glad that you got it working, Jorge. I mistakenly assumed that your settings were set per the instructions
and that it was an interface problem. I will need to double-check from now on, thanks for the tip.

Mitch DJ0QN / K7DX

Hi Jorge,

You have done this correctly, but I have two tips:

1) Use the Windows audio settings to set the level of the sound card. Often one uses the wrong sound card or
the setting is too low or on mute.

2) I have often seen that there is a level issue between the RRC and computers which cause audio problems. To
solve this, either use a standard sound card interface between the two as if the RRC is a radio, or put isolation
transformers in between the two.

Mitch DJ0QN / K7DX

Hi Allen,

There is all the information you need already on this Forum if you use the search function. I will try to
summarize some of them:

- The problem is caused by your network somewhere and has nothing to do with RemoteRig. However, you can do
some optimization to minimize data transferred and compensate a little for minor network problems. To really solve
this problem, then you need to find the network problem. It may or may not be related to the actual internet connection.

- To determine which side the problem is located, move the control position to another location (e.g. friend's house). If the
problem continues, then you can focus on the radio site or visa-versa. Then it gets complicated, since it could be with the
router, provider or even network hardware such as a switch.

- Try some RRC tweaks to compensate somewhat:
   - set audio quality to 0 (half the bandwidth of codec 2 and more than adequate for SSB & CW)
   - set RTP to continuous. This increases data use, but often smooths out this type of problem
   - turn off the second receiver in the K3, since this doubles the bandwidth
   - increase rx jitter buffer to min 12+
   - increase rx jitter delay to min 10+
   - set audio packet size 20 or 40

I am not saying that any of these suggestions will work, but use them as a guideline to see if something helps or not. Since the true problem lies
somewhere else, these are possible "band aids" and nothing more.

Mitch DJ0QN / K7DX

Hi Chip,

Is that status page after the audio goes away? I assume that it is, so this one will be hard to find. The only thing I can tell you for sure is
that you are looking for the problem in the wrong place: it lies with the network and not with RemoteRig.

I would use a network sniffer like Wireshark to try to localize the problem, but that may too complex for you. In that case, I would try to
find the problem using the process of elimination:

- Try using the control side from a different location to see if you have the same problem. If you do, then the problem is at the station,
otherwise you know that you need to focus on the control side network. I also assume that you tried it out at the radio location using the
internal IP number as the SIP address first.
- The router needs to be checked to make sure that firewall settings, etc. are okay. For example, make sure that SIP ALG is not turned on
if offered in the router. Try turning its firewall completely off to see if that makes a difference.
- Sometimes other network components cause problems. I have even seen network switches causing this type of problem.

Mitch DJ0QN / K7DX

General discussion forum / Re: Error Tones
« on: 2019-08-12, 00:45:54 »
Hi Gus,

All I can say is the "not connected" tones means that the connection can not be made for some reason and that the "beep beep beep" tone means that the other side is already being used (busy). Maybe Mike can provide more details. I never really paid much attention all these years ;-)

Mitch DJ0QN / K7DX


Maybe you can answer this similar question while you are at it:

Mitch DJ0QN / K7DX

General discussion forum / Re: Error Tones
« on: 2019-08-11, 11:57:57 »

If the system was working before and all of a sudden stopped working, then the problem is 99% NOT with RemoteRig. Instead, something in the environment has changed. It would have helped had you told us what the status line says in the menus. Try the following:

- Reboot the router/modem on one side of the connection and then the other side if that didn't help.
- Restart the RRC's
- Check the cabling to make sure that nothing came loose or changed
- If that all didn't help, make the following check:

Mitch DJ0QN / K7DX

All it will show under Linux or iOS would be the generic FTDI drivers, which won't help all that much. Same
for Windows if you forget to install the Microbit Setup Manager first.

Mitch DJ0QN / K7DX

Yes, that was important missing information!

There are only Windows drivers available for the RRC USB port, which are installed when you install the
Microbit Setup Manager. It is not compatible with Linux and anyway wouldn't do what you want.

You can likely use the AUX/MIC port for PTT, depending upon how you have the red straps installed.

Mitch DJ0QN / K7DX

Often the Windows settings do strange things for USB to serial converters. Try doing the following:

Go to the presentation on serial interfaces at

Follow the instructions from pages 26-30.

I hope that this helps.

Mitch DJ0QN / K7DX


Moving to a dynamic external IP address is super easy. Just go to the dynamic DNS menu of
the radio RRC, change the drop-down to the RemoteRig service and enable it to check every
10 minutes. Put that address into the SIP contact field of the control RRC and you are ready to go.

More complicated is the move to a 4G service. Each provider and country is different, so I can't say
specifically about your area, but most of the time the 4G providers do not provide the users with a true
external (public)  IP address, instead using internal addressing. This causes a double-NAT situation
where the port forwards will not work.

If this is the case with your 4G provider, then you only have two work-arounds:
- Pay the provider for a public IP address ( a fixed IP address is not necessary, but a public one is)
- Or use a VPN

Mitch DJ0QN / K7DX

General discussion forum / Re: Internet parameters
« on: 2019-07-25, 23:11:08 »
Hi Kenny,

You are correct in your assumption that the issue is with your internet connection and not with
the RRC's. The problem is to locate where the problem lies. It could be a number of things:

- The modem at the radio side
- The modem at the control side
- The router at the radio side (if separate device)
- The router at the control side (if different device)
- The internet service provider at the radio side
- The internet service provider at the control side

The first thing to do is to use the process of elimination to locate at least on which side the problem occurs. The easiest
way to do that would be to move the control equipment to another location when the problem occurs, e.g. a neighbor's
house. If the problem still is occurring, then you narrowed the problem to the radio side, or visa-versa.

Once you locate which side it is on, then the problem solving gets more detailed. My suggestion would be to setup the router to
allow admin access from outside of your network. The router should have settings to allow this. Test it to make sure the access
works ok using your smartphone. Then the next time the problem occurs, try rebooting the router from the control location
to see if this solves your problem.

If this doesn't solve your problem, then the problem lies either with the provider, or with the modem if a separate device. To reboot
the modem is more complex: If at the remote site, I would suggest at least temporarily setting up a PC on the RRC's network and
install Teamviewer to answer. Then call up a browser on the remote PC and load the modem's web page at Then you
can go to its menu to reboot it. If that solves your problem, then the problem is with the modem, or perhaps with an unstable internet
connect with your provider (the same applies if a combo router/modem).

To see if the connection is unstable, look at the modem's status page. You will see the signal strength and error rate listed. Then you can
contact your provider to get it fixed. Use Google to figure out what is good and bad.

To directly answer your questions:
Question one - when this happens is there anything I can do to re-start radio?
you can restart the router and/or modem per my directions above. Maybe that fixes the problem

Question Two - is there anything I can do to avoid this?

Locate the problem and get it fixed per above

Question three - what kind of internet performance should be required for good sound operation of the RRC units?

Not worth going into detail, since any modern cable or DSL connection has way more than the required bandwidth
needed. Actually more important is latency, but that would require more explanation and is probably not important
at this point.

Question four - if the internet is the problem what specifics can I take to my provider to compare my internet service with requirements?

See above. The modem's status page is key, use if a separate device, or your router's page if not.

There are other methods using network sniffers, etc., but I believe you can solve your problem using this guide.

Good luck & 73,
Mitch DJ0QN / K7DX

General / Re: Nano + 480 (Radio on / off)
« on: 2019-07-17, 17:36:49 »
The radio always turns off when the SIP connection is cut. This occurs even if you lose
your internet connection, power or similar.

Mitch DJ0QN / K7DX

General discussion forum / Re: Audio Problems
« on: 2019-07-14, 19:47:32 »
Hi Gary,

Like I wrote yesterday, none of the other things you wrote would have any effect on the output
audio. The jumpers only affect the microphone audio, power has nothing to do with it, assuming
the control panel is otherwise working.

If that particular cable is okay, then I would contact Microbit about a possible repair requirement.
Try another audio cable between the TS-480 and RRC in the meantime if you haven't.

Mitch DJ0QN / K7DX

General discussion forum / Re: Audio Problems
« on: 2019-07-14, 02:58:58 »

You didn't give enough details to figure it out. However, I will make the following assumptions:
1) It worked before and all of a sudden stopped working
2) You didn't fiddle with any RRC settings
3) You are referring to the audio output and not microphone audio

If these assumptions are correct, then the only place the problem lies other than a defective RRC
would be the audio cable that goes between the radio RRC and the TS-480. Double check that cable
to make sure it is okay. Every device you listed before would have no effect on output audio.

Mitch DJ0QN / K7DX

Pages: [1] 2 3 ... 136