WriteLog
[Top] [All Lists]

Re: [WriteLog] Now REMOTE CW/RTTY

To: "'Robert'" <woodr90@gmail.com>
Subject: Re: [WriteLog] Now REMOTE CW/RTTY
From: "Tom Georgens" <tomgeorgens15@gmail.com>
Date: Fri, 26 Jun 2020 14:10:03 -0700
List-post: <mailto:writelog@contesting.com>
Hi Robert

With a remote, it is important to be able to power off the radio (and anything 
else).  You don't want to get stuck in some situation where the radio is stuck 
key down, rotor stuck with brake retracted, etc.  and you are 1000 miles away.  
There are some simple WEMO solutions and more complicated web power switches.  

I asked about the K3 power control since it needs external hardware to power 
on/off cleanly.   One simple, but not recommended, approach is to just ground 
the power on pin in the ACC connector.  The will turn on the K3 when power is 
on, but will not turn off with the serial power command.  It will go into an 
odd state.  You have to take down the 12V for it to work.  If you just crash 
the 12V to turn it off, any changed settings are not saved.  As I said, it will 
work, and I have done it, but it is not clean and may have other issues.  

The N6TV boxes solve the problem cleanly, reliably and do not require any 
soldering, but cost money

Robert, I am curious why you did not use the momentary pulse on the ACC power 
pin to turn it on.  Then you can use the serial port power command mapped to a 
keystroke to turn the radio off.  This would avoid soldering to the internal 
PCB.   This is what I do.  I pulse DTR to drive an NPN transistor to pull down 
the power on pin on ACC to turn on the radio.

Good luck with your testing..

Tom







-----Original Message-----
From: Robert <woodr90@gmail.com> 
Sent: Friday, June 26, 2020 1:41 PM
To: 'Tom Georgens' <tomgeorgens15@gmail.com>
Cc: 'Gordon LaPoint' <gordon.lapoint@gmail.com>; 'Writelog Forum' 
<writelog@contesting.com>
Subject: RE: Now REMOTE CW/RTTY


this email covers the Remote K3 ON/OFF control My first thought was leave the 
rig on when departing remote site but power failures do occur and K3 will be 
dark when power restores.

Breadboard type wiring/tests good and no smoke got out This method is not 
approved or commented on by Elecraft, any reproduction  at your own risk.... 
etc. etc.
Ideas always welcome 

K3
The K3 uses a momentary switch on front panel to turn rig on/off.
The schematic shows the POWER button has 12VDC one side of switch and the other 
side to control circuit which when 12vdc is supplied & removed by pushing POWER 
button, whatever state the radio is in, will change to other state.

The back side of the PC board on K3 front panel has two feed throughs to on/off 
switch.
the furthest away from side is the one of interest (the closest feedthrough has 
the 12vdc - which is available elsewhere) Installed an insulated stranded #20 
to POWER button - cut away few strands and soldered the #20 to connection of 
interest of the on/off switch.  I will call this the control wire for this 
discussion.
Brought control wire out through back of rig (reference port opening for now)

put power cables on K3
attach volt meter to control wire and to K3 ground.
TEST:   push on button on front of K3, 13VDC appears on control wire.
release power button, voltage drops to zero.  same when turning K3 off.
Confirms method being used in K3.

I have W3YY FSK/CW interface which contains three optical isolated switches - 
the CW one is unused (as I key CW another method) I'm using the YY device as 
it's already connected to desktop and has solid state switch ready to go.  
Certainly other switches or relay contacts should work too.
The important item is there is a spare "switch" and it's wired to DTR on com 
port into desktop Took 12vdc to one side of the switch output, and connected 
the control wire from K3 to the other side of output of YY interface device.
observing correct polarity

Plug power cable into back of K3,
Open WSJT program to test toggle DTR(your method may vary) change the PTT to 
DTR and push test PTT (after confirming rig communications) release TEST PTT
K3 under test powers up... YEAH!
click TEST PTT again - release, rig powers off   YEAH!!
repeat several times - no smoke, works.

don't hold TEST PTT long when powering up, that might be sign to K3 to enter 
some special mode or failure mode (I'm not privy to such info)

so the breadboarded concept works, after FD will work on cleaning up. 
some forward thinking: bring new control wire out on same connection that is on 
ACC port for powering ON (remove existing POWER ON, then replace with new 
control wire) Or Install new connector at reference port 
idea is find clean way to bring Control wire outside K3   
Find program/method to fire DTR on com port that is available at control site 
(can be done remote) 

IF one is using FIDI USB to RS232, set "Disable Modem Ctrl At Startup" 

On wiring the front K3 PC board.
Need to be proficient on soldering  & use small pencil type heater with small 
diameter solder Even then, it's like three hands needed...

POST FD, will see about schematic and post on web page.

73 W5AJ
Robert
Midland, Texas

-----Original Message-----
From: Tom Georgens [mailto:tomgeorgens15@gmail.com]
Sent: Thursday, June 25, 2020 4:47 PM
To: Robert <woodr90@gmail.com>
Cc: Gordon LaPoint <gordon.lapoint@gmail.com>; Writelog Forum 
<writelog@contesting.com>
Subject: Re: Now REMOTE CW/RTTY

Hi Robert

Glad you are making progress

I have two radios and my audio source is essentially a Y of what the operator 
would hear on site after the audio switching.  It will do either radio in both 
ears and split based on the automation.  Since I am using headphone audio I 
have to adjust the af gain when I connect.  If you are sending headphone audio, 
it is good to leave the radios AF gain at a nominal setting when you are gone.

RIT can easily be done with keyboard shortcuts.  Make command macros for rit up 
and rit down and map them to shortcuts.  I think rit clear is in the default 
set up.  I use the same keyboard shortcuts For RIT even when I am not doing 
remote.  Eliminates moving you hands from the keyboard

Not a RTTY person so will leave that to experts

I use TeamViewer to startup the remote side.  It works fine.  They can get 
aggressive about commercial use, but the product works.  I have used anydesk as 
well.  Not quite as polished as TeamViewer but has done everything I need.  I 
recommend having two remote management tools installed.  The recent windows 
upgrade broke TeamViewer and the station is 4000 miles away and inaccessible.

All of my station gear is controllable by computer and the software is all 
remote able.   Once the remote side is running, I don’t need TeamViewer 
anymore.  Eliminates problems like timeouts.

The phone hotspot is how I tested as well.  

Two things.  You need a way to get the IP address of your home network.  You 
can TeamViewer in and look at your router. If your router supports a ddns 
service, like no-iP, then it will create a url and automatically keep the 
dynamic ip updated.  Barbados has a carrier grade NAT (not a real IP address) 
which made life difficult.  I can explain if necessary.  In the US, it is less 
likely.

Also, what is you plan to turn on the radio remotely?

GL Tom W2SC 8P5A

Sent from my iPhone

> On Jun 25, 2020, at 1:32 PM, Robert <woodr90@gmail.com> wrote:
> 
> 
> spent few hours working remote setup on laptop that will travel.  this 
> session, all behind same router.
> rig com port linked fine.   Audio would link but never heard anything.
> Finally switched rig to AM on 10Mhz then 5Mhz WWV, still nothing.
> (you know, wasn't just no RTTY but no CW either late last night)
> 
> my settings on audio were too low at rig site.  K3 - turned up the 
> line out
> (15) and then could hear audio fine at control site.
> zing  - I'd be interested what K3 line out values others are using 
> when doing remote.
> sample rates all set same between sites
> 
> today's study:   
> CW   Can RIT be implemented or is RC1101 required?  
> 
> RTTY - (It is what it is):
>  can't get to MTTY to allow AFC
> and once AFC is on, then set to off to do S&P, need to insure Mark set 
> at
> 2125
> Seems Option is set AFC on or off before leaving the remote (Rig) Site...
> AFC off is good for S&P, AFC on good for CQ CQ As noted before, can't 
> see the waterfall or RTTY tuning indicators at control site (No rig 
> site).
> 
> TEAM MEETING - is this good method to run/operate remote (has Rig) 
> computer can see screen and operate mouse as if at the Home site?
> Other worthy options?
> IF I want FT8 remote, remote control of Rig PC seems in order.
> 
> 
> Going to test the router today by setting Cell Phone to Hot Spot, 
> connect laptop to Hot Spot and come in that method to insure can get 
> through router fine (opening up 3 port #s)
> 
> 73 W5AJ
> 
> Robert
> Midland, Texas
> 
> -----Original Message-----
> From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of 
> Tom Georgens
> Sent: Tuesday, December 31, 2019 8:56 AM
> To: 'Gordon LaPoint' <gordon.lapoint@gmail.com>; 'Writelog Forum'
> <writelog@contesting.com>
> Subject: Re: [WriteLog] Is Digirite remotable?
> 
> Digirite is not remoteable in its current form.
> 
> I have not tried either of these, but they might work.  
> 
> 1. Use a remote control program like Teamviewer and just run  Writelog 
> and Digirite on the computer connected to the radios.
> 
> or
> 
> 2. Use a second computer on the control end.  The first computer runs 
> WL control site as you do now.  The second computer Runs WL in regular 
> mode and digirite, and is networked to the first computer to keep the logs in 
> synch.
> The second computer looks like a head set to the first computer and 
> connected to the headphone and mic jacks.  The first computer can 
> still control the remote radio.  You many need to enter the 
> frequencies on the second computers manually.  (Writelog has some kind of 
> frequency synch
> utility, but I don know if it is generally available.)   I always meant to
> try this but never got around to it.  The latency may be a problem or 
> there may be some flaw in my thinking.  I do know that networking the 
> two versions of Writelog at the control end does work.
> 
> GL Tom W2SC 8P5A
> 
> 
> 
> -----Original Message-----
> From: WriteLog <writelog-bounces@contesting.com> On Behalf Of Gordon 
> LaPoint
> Sent: Tuesday, December 31, 2019 12:48 AM
> To: Writelog Forum <writelog@contesting.com>
> Subject: [WriteLog] Is Digirite remotable?
> 
> Can Digirite be remoted like RTTY?  I have the remote setup working 
> for RTTY for the upcoming ARRL RTTY RU, but don't see how to remote the 
> Digirite.
> 
> Thanks,
> 
> Gordon - N1MGO
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
> 


_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/
<Prev in Thread] Current Thread [Next in Thread>