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 ... 125
Hi Harry,

Glad you found the problem, I had completely forgotten about that old problem.

I always recommend that even radio RRC's are set to DHCP and then fix the IP number in the router.
The reason is that many routers (such as the popular Fritz!Box in Germany) will not forward ports for
any device that it did not issue an IP address for and this prevents a number of other issues as well,
not to mention this DDNS bug.

Mitch DJ0QN / K7DX


Maybe I can help you with some ideas on your WiFi issue:

Basically, one must understand that WiFi is a shared medium and not switched like ethernet. This means that the WiFi
channel that is used to carry your traffic can have lots of QRM that will prevent the continuous stream you are expecting.
When you do have a packet collision, the packet will be resent until confirmed, which is what is causing your problem. This
is unlike UDP over the internet, which is not confirmed and packets are streamed without pause.

Now onto what can be causing this QRM:
- Neighbors sharing the same channel, especially on 2.4 GHz
- Multiple devices in your household using the WiFi at the same time. Worst offenders are streaming and teenagers.
- An older WiFi standard is being used that gives a smaller total bandwidth. Remember that net bandwidth is much less than the spec.
- Other devices such as microwave ovens, some surveillance cameras, etc. also operate on this band
- Etc.

What can be done to solve it, assuming there is no way to lay an ethernet cable:
- Move to a clear channel where no neighbors are operating their router
- Migrate to 5 GHz (you may need a new WiFi Bridge)
- Look for what in your household is causing the interference
- Operate as many devices in your household using ethernet as possible
- Etc.

Can the RRC settings be changed to compensate? The answer is to an extent, but this is a band-aid. Some examples:
- Reduce the audio quality to 0 (half the bandwidth of codec 2 and usually adequate for SSB & CW)
- Turn off dual-receive if used and not needed (halves bandwidth use)
- turn continuous RTP on or set RTP to continuous (depending upon firmware version)
- Play around with these 3 until you are satisfied:
    - increase rx jitter buffer to min 12+
    - increase rx jitter delay to min 10+
    - audio packet size 20 or 40
- Adjust CW settings (you may want to search this Forum for much discussion using the settings below as keywords):
    - Set Lf delay to a higher number
    - Set Key delay to a higher number

I hope this helps.

Mitch DJ0QN / K7DX

Hi Harry,

Probably best if Mike at Microbit takes a look, since he developed that function. However, I need
to point out that the DDNS will always show "unknown" for a few minutes after booting the RRC.
You need to be patient and check it after about 15 minutes or so. Perhaps you did that, but I just
wanted to make sure.

Otherwise, I can't see any reason why the update won't work. Of course, there is always the
alternative to load a DDNS from this service, which the RRC also accepts:
When they starting charging a few years ago, Microbit setup their own service, which is causing you problems.

Mitch DJ0QN / K7DX

General discussion forum / Re: K3/Twin Local and Remote
« on: 2018-11-12, 06:21:28 »
Hi Will,

Probably the Y-Box is the easiest way to manage that:

Mitch DJ0QN / K7DX

Here is the list of error codes:

How are you accessing the RRC's web page from outside, i.e. are you typing in its IP number or what exactly?

I would just turn the RRC's DDNS client off, reboot and then turn it on again. Maybe something got corrupted. There is no
reason whatsoever to use an external updater.

Mitch DJ0QN / K7DX

Hardware, Cabling, Installations / Re: Wifi Module Bad
« on: 2018-11-11, 17:16:10 »
There are two advantages of using an external WiFi Bridge:

1) 5 GHz band
2) You can use a public hotspot like a hotel to log into a web page to access the internet, the built-in card does not allow that

Otherwise, the internal card does not take up any more space if you can live with its limitations.

Mitch DJ0QN / K7DX

General discussion / Re: Audio feedback in K3/0 speaker
« on: 2018-11-06, 18:36:08 »
Hi Dennis,

Just turn off your monitor, you can not use it for remote operating due to the latency. Same goes for CW sidetone.

Mitch DJ0QN  / K7DX

Glad you found it, Will! I had assumed that you had the serial cable between the K3's RS232
port and the RRC's COM2, since it would not work without it. At least now you found it.

Mitch DJ0QN / K7DX

Hi Will,

TERM just means that it is in terminal mode and has no standing on it if is working or not. Normally,
the TERM shows-up on the screen for a few seconds and then the remote K3 display shows. You
didn't really say what was not working, so I am I correct to assume that you mean that the TERM does
not go away and the remote K3 display does not show?

If so, this could be due to a number of problems. First of all, check to make sure the remote K3's power
goes on when you hit the control power button. If not, then you need to concentrate of the cable going
to the K3's ACC port. If it does go on, then the problem lies with the CAT signal from the RS232 port.
That could be caused by a number of things, including wrong baud settings in one of the K3's.

Bottom line is we need more details. All of the cable wiring diagrams are in the RemoteRig manual.

Mitch DJ0QN / K7DX

Hi Marvin,

Thanks, but I have a question: were you running a second receiver? That would double data usage.

Mitch DJ0QN / K7DX

Hi Tom,

Using the Webswitch virtual serial port for a rotor works just fine, I used it for a long time.

I will try to answer your questions:

- You only have one external IP address, so just use the same host name that you do for your RRC. It will be found in your
network by the port number.
- The TCP port is any number you make it. This needs to be forwarded in your router to the Webswitch's internal IP number
- This should not be an issue with an outgoing connection with a firewall, only the Webswitch's router needs the port forwarded
- Once you create the serial port using Microbit Setup Manager, you don't need the program any more. Close it and move to the
client you use for rotor control. Once that program is started using the virtual port number, the connection will take place and
disconnect once you close the client again.
- Note that you can't use the Webswitch's web interface at the same time as the virtual serial port.

If you have any further questions, you can contact me at dj0qn (at) (natürlich auf Deutsch).

Mitch DJ0QN / K7DX

Glad to hear the good news!

Mitch DJ0QN / K7DX

General discussion forum / Re: Remote Use
« on: 2018-10-27, 19:05:24 »

Actually your question was covered quite a few times. If you search for "hotel", you will find quite a number of
tips on how to use the RRC in a hotel or hotspot situation.

The short answer is just attach a portable WiFi bridge that has an ethernet port to the RRC. You first book this into
the hotel network using a PC, then move it over to the RRC. There are a few on the market and most pocket routers
will also function in bridge mode.

To answer the question about DNS service; I think you are asking about a dynamic DNS service. The answer here is that
no extra service is required. The RRC has a free service from RemoteRig built-in under the  dynamic DNS settings.

Mitch DJ0QN / K7DX

Hi Dennis,

This is indeed covered in the manual, but a little hard to find. Look at the bottom of
page 94 (I/O Connector) and page 95. Also Appendix B.

Mitch DJ0QN / K7DX

Since no one else has responded, I will give you my tips.....

First of all, this problem is not caused by any settings in the RRC, it is hardware related. Don't waste your time
trying different settings.

Now on to what can be causing this. Like I said, it is hardware related. Some places to look:
- Most likely culprit is a power supply. Since you said you already replaced them, make sure also that any extension
plugs or whatever they are plugged into are also not the problem.
- remove or swap the microphone and see if that makes a difference
- Check all cabling to make sure they are tightly connected and that no wires became broken
- Make sure that the red straps inside of the RRC's are well placed and none came loose

Mitch DJ0QN / K7DX

Pages: [1] 2 3 ... 125