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 ... 148
Hi Jorge,

That would have to be addressed by Microbit. Is your status page showing an error message?

Mitch DJ0QN / K7DX


You are confusing me. Your first posting said that you needed to setup DDNS, now you are saying that
you didn't need that.

I really do not understand what you need, so I will just give general information that may help:

To setup DDNS on your radio RRC to report your public IP number:
 - Go to the Dynamic DNS settings tab (radio RRC only)
  - Change the check interval to i.e. 10 minutes
  - Make sure the drop-down is on RemoteRig's service
  - Click on apply changes

To use the DDNS address to access your station (after port forwarding):
- On the control RRC, place the information from the radio RRC's "own host name" on the Radio Settings tab under SIP contact.

This information was copied out of my Networking Checklist, in case you still have a copy.

Mitch DJ0QN / K7DX

Hi Jorge,

I am not sure if I understood you 100%, but I think you are saying that you replaced the router on the
radio side.

If so, then all you need to do is to reconfigure your new router to forward the ports to the radio RRC's internal
IP number. Nothing else is needed to be changed and nothing at all at the control RRC side.

The radio RRC already has the RemoteRig DDNS setup (I assume), which just tells the control side (in the SIP contact)
your current public IP address. This doesn't make any difference what router is being used.

If you are using a VPN, then you would use the internal IP address as the SIP contact instead.

Mitch DJ0QN / K7DX


I am not really sure if your problem is related to RemoteRig. It may instead be a setting inside of the K3 or K3/0.

You can set the K3's menu to use the rear or front microphone input, so make sure that you are using the correct input. In addition,
the K3 and K3/0 have separate settings. The way it works is that when you are connected to the remote K3, then changing the menu
with only change the remote K3. To change the control K3/0, you must make sure that there is no remote connect when turning it on.
You can temporarily disconnect the control RRC's network cable, for example.

Mitch DJ0QN / K7DX


For any low-bandwidth situation, I suggest the following from my low bandwidth checklist:

Try reducing your bandwidth to a minimum and changing some parameters to compensate for a poor line. Note that this is only for using 3G/4G on the control side. Running a RemoteRig system over 3G/4G with the router on the radio side will never work, unless you pay extra for a true external IPv4 address.

Here are some tips:

1) These are important:
- audio quality to 0 (half the bandwidth of codec 2 and more than adequate for SSB & CW)
- If using the K3 Twin or Yaesu with a second receiver, then turn off "audio dual-rx" on the radio RRC under the radio settings. This doubles the necessary bandwidth if on.

2) 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

Even though this increases data, I suggest setting RTP to continuous, since this forces a consistent data stream and may make the connection more stable.

Mitch DJ0QN / K7DX

Configuration, RRC 1258 / Re: Microbit Setup Manager
« on: 2021-08-16, 18:25:50 »
Hi Paul,

Yes, there some things that you need to do when moving the RRC. I have a checklist available that walks you
through the process, so no phone call should be necessary. Just drop me a short mail at dj0qn (at) darc (dot) de
and I will send it to you.

Mitch DJ0QN / K7DX

Configuration, RRC 1258 / Re: Microbit Setup Manager
« on: 2021-08-11, 21:53:19 »
Hi Paul,

Unfortunately, there is no way to recover a password if you forgot it. You will need to do a complete hardware reset on the RRC. If you saved your
config file before as a BIN, then you can reload it. Otherwise, use the control RRC as a guide to setting the radio RRC up again.

Mitch DJ0QN / K7DX


If Spectrum allows you to use your own router, then I would buy one and give theirs back. Any one one  the market will meet your needs.

Some providers like Comcast/Xfinity even charge you a monthly rental fee for the junk router and you save that by buying your own.

Mitch DJ0QN / K7DX


I currently like the GL.iNet series of pocket routers. They are switchable between modes, including bridge mode, but can be
used for other purposes as well. They have several models that have different features, e.g. WiFi bands, speed, external vs.
internal antenna, etc.

They can be found on Amazon and elsewhere.

Mitch DJ0QN / K7DX


Try using the Winkeyer emulation and see if that solves your problem. Just use COM3/COMEXTRA
on the RRC and set it to Winkeyer. Use the virtual COM port in Windows to key Winkeyer.

Maybe this won't work, but it is worth trying.

Mitch DJ0QN / K7DX

Hi Mike,

The data is only sent when a rig is connected, so that won't work how you are doing it, At
least make a connection between the RRC's first.

Mitch DJ0QN / K7DX

I don't think you ever requested my networking checklist and did this on your own. Taking a
quick look at it, it looks like you did a good job. That would point to the most likely problem being
your router. Instead of DMZ, forward ports 13000-13003 as UDP to and see if that
solves your problem. I have helped over 300 people get their system running and it always amazes
me how some routers just don't work correct for the DMZ.

If that doesn't help, I would be happy to take a look using Teamviewer. I am on EST. Just let me know.

Mitch DJ0QN / K7DX


Mike may wish to confirm, but I am very sure that it can not connect without a rig.

Mitch DJ0QN / K7DX

Configuration, RRC 1258 / Re: No connected
« on: 2021-01-21, 15:30:48 »

Offhand, I see two mistakes:

1) You don't have the same SIP password on the RRC's. They must be identical, including large/small letters

2) COM0 on the control RRC should be the same as on the radio RRC, i.e. 57600 in this case.

Mitch DJ0QN / K7DX

Maybe I missed wrote that they are five miles away, but no internet connection. Are you
saying that all RRC's are within the same LAN? If so, then no port forwarding is necessary at all. You address
the individual radio RRC's using their distinct internal IP number and the distinct set of ports if they changed. I
would think that you would not even have to change the port numbers either, since there is no need to separate
them for the purpose of port forwards.

If the radio RRC's indeed need to be reachable over the internet, then the above does not apply. Please clarify which
scenario is correct.

To answer your other question: since each radio RRC is addressable through its own internal IP number, there is no
difference from which control RRC connects to that particular radio RRC. they can alternate the connect without any
change being made at the radio side, but can not connect simultaneously.

I hope this helped clarify your questions. Some of your terminology confused me, since you were talking about ports
and static IP numbers. You meant static internal IP numbers, which are anyway necessary for radio RRC's. Port
changes are only necessary if you need to reach the radio RRCs over the internet.


Pages: [1] 2 3 ... 148