[Elecraft] K3 Mini Error question

Mon Nov 28 16:27:05 EST 2016

Hey Jim,

I'm late to the party, but just some words of advice:

- Make sure the station end is set up properly first.  As noted before,
there are three UDP ports that need to be set up in port forwarding.  You
don't have to use the ports RemoteRig recommends, but if you want to,
that's fine.  If you have VoIP phones at your QTH, use 5095 instead of
5060.    If your router support a DMZ, you can use that instead of port
forwarding.    Another port I like to forward is the RRC's Web server
port.  This allows you to view the rrc's configuration and status (station
end) while you are debugging a connection.  The default port is port 80.  I
would not use that; I'd make it 8080 or something along those lines.  You
still need to forward that port if you want to see it from the outside
world, and it is TCP.     The remoterig box also has a Telnet interface,
another tool for debugging, which is on TCP Port 23.   (If you port forward
that, make it a non-obvious port like 2300).

If you forward the web port and the telnet port on the station end, it's
pretty quick to find out if you can get to the RRC by trying to go to it's
web page.
(before you even attempt radio operation.)

As far as internet in far off lands, I've had no issues, except with
Wireless network providers.  Multipoint-to-Point shared Wireless ISPs
typically use TDM techniques to share customers, and these radio systems
are terrible for JITTER, which kills VoIP, and incidentally, RemoteRig.
(Jitter being the difference in ping time over time. )  RemoteRig will
tolerate a TON of latency, but not a lot of jitter.  (These systems can
produce anything from 10-1000 mS of jitter, all the way to packet loss).
DSL systems are usually very good.  Fiber/cable are usually awesome.

if you get the three-tiered tone, it simply means it cannot connect to the
far party -- exactly like the "Service Not Available" tone you get from the
phone company.   This can be that the other end is not turned on, you have
the wrong DNS/IP, port forwarding is incorrect, or, you are not matching
the values specified in the station-end RRC.

If you get connected but the K3/0 is stuck in TERM, you have an RS-232
control problem (lots of guys have trouble with this).  Especially with a
K2s, when you are in either USB or RS-232 mode.

Also -- when you get connected and are adjusting menus, always remember you
are controlling the REMOTE K3, not local.  So don't change RS-232 by
accident!

If you are doing CW and using a logging program, like N1MM+, I recommend
using the mini USB cable for CW and Rig Control.  It is flawless.
At the remote end, RRC's Logical COM1 (Actual port in brackets) is your Rig
Control, and COMextra (Actual port in brackets) is your Winkey control.
(There are some settings to change in your remote RRC if you want this to
work... I can pass them along.)

For SSB, make sure you have the Station's  MIC selection set to RPNL (Rear
panel).

Not RRC or Elecraft related, but I highly recommend getting one or more Web
Power Switches (http://www.digital-loggers.com/lpc.html)
These ~$130 devices will save your butt!   They can remotely control up to
10 devices ... and, more importantly, can automatically reboot the DSL
Modem or router if you get a power glitch and they hang.  Worth their
weight in gold.

Glad to help with any questions.

73, Gerry W1VE
Trustee, VY1AAA Yukon CanAm Contest Club &
Remote Contest Team

Gerry Hull, W1VE   | Hancock, NH USA | +1-603-499-7373
AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM
<http://www.yccc.org> <http://www.yccc.org/>
<http://www.facebook.com/gerryhull>
<https://plus.google.com/+GerryHull/posts>     <http://www.twitter.com/w1ve>

On Sat, Oct 29, 2016 at 5:44 PM, Jim Cary <jimlcary at gmail.com> wrote:

> John/Barry
>
> Thanks for the quick responses.   I’ll be setting up the other side
> tomorrow.  I think when I had them working at home I had both units
> connected before I fired up the mini, so I didn’t have the problem.
>
> 73,
>
> Jim
>
>
> > On Oct 29, 2016, at 5:39 PM, John <john at eeek.org.uk> wrote:
> >
> > Jim,
> >
> > This is actually quite a simple one, luckily!
> >
> > I'm assuming when you say RRC you mean the MicroHAM RemoteRig Control
> system - I've helped set these up and test them for a couple of years now,
> so assuming I've got that bit right...
> >
> > It simply means that it's unable to talk to the other end (ie the kit
> you haven't connected at the far end).
> >
> > The MicroHAM RRC systems use SIP over UDP on three different ports - one
> for voice data, one for CAT data, and one for control signals between the
> remote head and the unit body. If it's a SIP connection error you're
> seeing, it's because the two ends of the RRC system can't see each other
> (which, as you say, is the correct case because you haven't hooked up the
> remote unit yet).
> >
> > If I'm barking up the wrong tree, please correct me.
> >
> > 73, and a firm left handshake,
> > John (XLX)
> >
> > -----Original Message-----
> > From: Elecraft [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of
> Jim Cary
> > Sent: 29 October 2016 22:27
> > To: elecraft at mailman.qth.net
> > Subject: [Elecraft] K3 Mini Error question
> >
> > I just packed up both my control and remote systems and moved them down
> to my ZF QTH, where they will be permanent.
> >
> > I have the K3 mini hooked up to the control RRC unit, but haven’t hooked
> up the remote unit yet/
> >
> > When I powered up the mini, and turned the volume control I got a three
> tone warning signal.  The light over the aux/mic cable is flashing yellow,
> which according to the Remote Rig manual means the SIP connection has
> failed…. but it isn’t clear what that means or what to do about it.  I’ve
> checked and doubled checked all the connections and they look good.
> >
> > Does anyone not in the CQ contest (!!!) have an idea?
> >
> > Jim
> > W2SM
> > ZF2LC
> >
> >
> > ______________________________________________________________
> > Elecraft mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/elecraft
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:Elecraft at mailman.qth.net
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to john at eeek.org.uk
> >
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to gerry at w1ve.com
>