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 ... 111 112 [113] 114 115 ... 126
Hard to say, Ed.

If you have a serial port or USB to serial cable, I would test COM2 on your RRC
to see if it works that way (turn USB CAT off first). That would at least indicate
where the problem lies and make it much easier to solve.

If you can't test it that way, then it will be more difficult to find. You can send me
a screen shot of your COM ports in Windows for a starter. Otherwise, maybe the
RemoteRig guys in Sweden or someone else has something I missed.

Mitch DJ0QN / K7DX

No problem, Alex.

On the back of the RRC is a reset button, see the manual, page 17.

Mitch DJ0QN / K7DX

Ed, did you:

1) Connect a cable to the K3's CAT port up to COM2 on the RRC?
2) The both RRC's COM2 mode set to mode 4 and the correct baud rate?
3) Downloaded and installed Setup Manager to get the drivers installed on your PC?
4) Looked under Windows to see which COM port the "Microbit RRC Virtual Comport" was assigned?
5) Enter that COM port in HRD with the correct baud rate?

Maybe this list will help find something you missed.

Mitch DJ0QN / K7DX


That doesn't always work with wireless networks, so that is why I said to reconnect to the
network afterward. It wouldn't hurt to restart the RRC after you are booked back in.

Mitch DJ0QN / K7DX


The next time that happens, call-up a DOS window and type: "ipconfig /release" into it. Then connect
to the wireless network again. I bet this solves your problem.

Mitch DJ0QN / K7DX

Just don't forget then to use the external IP number or dynamic DNS address with the
port number with the : in between, e.g.

Mitch DJ0QN / K7DX

In the case of a hardware problem, I will default back to RemoteRig support in Sweden.

You may wish to do a full hardware reset. Save your config file first and reload
afterward. It is a long shot, but maybe this will help.

Mitch DJ0QN / K7DX

Assuming you are within the same network, then always use the internal IP numbers
to access each RRC, e.g. and There is
no reason why this should not work. If you changed the port number, don't forget to
append the different port number, e.g.

To connect the two, use the radio's internal IP address in the "SIP contact" field of the
control RRC and enter the SIP password if you entered one in the radio RRC.

It should work just fine.

Mitch DJ0QN / K7DX

Is it green even if there is no ethernet cable connected? If so, then that is indeed
strange. If there is a cable connected, then that is how it should be (assuming the
cable is plugged into a switch).

Mitch DJ0QN / K7DX


I am not sure if you have a bad problem somewhere, but make sure that the internal
IP number was not changed by the router's DHCP server to something else. That happens
from time to time if you have a power outage or similar, and didn't bind the MAC address
in the router to a fixed internal IP number. Use the Setup Manager to call up the IP number
to make sure.

Mitch DJ0QN / K7DX

General discussion forum / Re: New Hum Problem with 2.41
« on: 2011-07-20, 11:36:52 »
I have managed to replicate the problem myself.

I am on vacation and set-up a portable RRC with TS-480 head that uses the USB COM port for CAT control.
When I connect to the same station that my other user does, after about 2 minutes I get a loud buzz (not
really a hum). When I pull the USB cable out, it goes away. Strangely, this problem does not occur with the
other station that I also use, only with this particular one, which has otherwise identical settings and hardware.

Mitch DJ0QN / K7DX

Hi Felix,

No, the RRC boxes have never accepted anything other than DynDNS addresses from

Mitch DJ0QN / K7DX

Hi John,

The short answer is NO.

The solution is to buy the PC Client dongle. It is very small, will give you a PTT button
and the virtual COM ports.

Mitch DJ0QN / K7DX

Hi John,

To bridge the two, you mark them with the control key and the right mouse click to
get the menu to bridge them. I have have very bad experience using XP in
this manner and have given up, since I get too many blue screens. Maybe you will
have better luck.

If you send me the type of bridge you are using, I can download the manual and see
if it is possible to switch to router mode.

That is why I always carry two different kinds of routers and bridges with me:

1) A Netgear WNCE2001: this is a pure bridge, like what you are describing. I use this
in the following manner:
  a) Access wireless networks with encryption, i.e. WPA or WEP. These networks generally
      are private and do not use a Radius server behind them.
  b) Access wireless networks with neither encryption, nor use a Radius server. This is somewhat
      rare here and usually is at private homes where the owner doesn't use encryption.

2) A Linksys WTR54GS: This is a router with ethernet and wireless "outputs", I use it for:
   a) Access wireless networks with no encryption, but do use a radius server. This covers
      most hot spots in the part of Europe I live in or in the case where you must "sign" an agreement.
      It allows you to pay once for the wireless connectivity, but use it among several users or devices.
   b) Access same as 1b above, but only when I want to offer my independent wireless network.

Mitch DJ0QN / K7DX


The problem is likely that the bridge is allowing the device it connects with to use DHCP
to receive an IP number from the wireless router (Radius server). This device's MAC
address is entered into the Radius server. Switching to the RRC, which has a different MAC
address, causes it not to work.

You need to see if you can change the bridge to work in a different (router) mode that in
turn has its own DHCP server and only shows pulls one IP address from the Radius server.

Mitch DJ0QN / K7DX

Pages: 1 ... 111 112 [113] 114 115 ... 126