Barry,
The RemoteRig system generates its own CW using an internal protocol,
which solves latency issues. You use your key at the control end and the
radio side RRC generates a clean CW without hiccups. It has error
control and is (I believe) very robust. I know of someone doing 40 wpm
full BK with no problem, but your mileage will vary, depending upon the
internet connection.
As for the internet connection; there is a lot of discussion on the
RemoteRig forum at their web site www.remoterig.com, so you can search
there. In general, here are some tips:
The sum of bandwidth required:
- COM0 serial port bps
- COM1 and/or COM2 bps if used (i.e. for CAT or rotor control)
- which CODEC you are using, refer to appendix A in the Manual or
http://www.remoterig.com/wp/?page_id=388
I use CODEC 0 for almost all of my stations, which has proven to be
more than adequate for SSB and CW.
- If you are running single or dual-channel audio (this doubles the
codec rate requirement)
- There is some overhead in the 20-50 bps range
Remember also that this is doubled, up and down! Most DSL lines are
asynchronous and have a lot less bandwidth going up than down, but the
internet provider usually only advertises the down speed. You need
therefore to take into account that the bandwidth used by RemoteRig is
the same in both directions.
Take into account the serial ports sent over the RRC, including CAT. It
is not always necessary to run them at 38,400 bps! I recommend setting
the K3 to 9600 bps to reduce your bandwidth that way.
I also need to point out that I believe that the latency is far more
important than the bandwidth, especially once you are over about 250k
bps. Often 3G lines have severe latency problems making them unusable,
and satellite is not advisable at all.
Feel free to contact me directly if you have any further questions.
73,
Mitch DJ0QN
Mitch Wolfson
DJØQN / K7DX
Neubiberger Str. 21, 85640 Putzbrunn
Skype: mitchwo - Home:+49 89 32152700 - Mobile:+49 172 8374436
Echolink: 3001 - IRLP: 5378
On 14.07.2014 03:36, Barry wrote:
A while back we tried Remoterig with a Kenwood radio and the CW generated was
poor on the other end. This was presumably from dropped packets and or
latency issues (Comcast on one end and a terrestrial microwave connection on
the other end). Some dits/dahs were lost and others were prolonged, due to
the lost stop signal. My understanding of the remoterig protocol for CW is
it's not very robust, with no error correction or ACKing.
We got around the CW problem by using a VNC and the CW is generated at the
host end within the VNC window, using N1MM, directly keying the radio.
If we were to use a K3 and K3/remote for the radio, would there be potential
radio control issues due to the flaky internet connection, or is there
redundancy and/or error correction built into the Elecraft remote protocol?
Barry W2UP
--
View this message in context:
http://elecraft.365791.n2.nabble.com/How-reliable-an-internet-connection-is-needed-for-A-K3-remote-to-work-well-tp7591154.html
Sent from the Elecraft mailing list archive at Nabble.com.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@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 dj...@arrl.net
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@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 arch...@mail-archive.com
