On 05/03/2015 10:28, [email protected] wrote:
Hi Stewart,
what's the reason behind? If you want to make sure the remote K3 does
not stay in TX state when you loose the connection it depends on your
solution. If you're using the Remoterig boxes they take care of it
automatically. As soon as the connection between both controllers
fails the remote RRC shuts down the remote K3 completely.
Thanks Olli
I plan to go the teamviewer/skype/HRD route - a little voice but mainly
data (PSK and WSPR). The remote h/w is too much to carry on a plane or
into the office etc. I just want a use stuff I already carry such as my
macbook.
Concerning TX-INH: Yes, you can do it that way. This is what I use in
my K3 sequencer, too. Detect PTT from KEY-OUT as the trigger. Keep
TX-INH pin high or low (depending on menu setting) to avoid any RF
until you release it. The K3 will be in transmit mode but not emit any
power when TX-INH locked.
OK that sounds good, but if it is already transmitting will TX-INH
override any other TX commands (such as an active TX; command)
and unconditionally take it back to RX?
BTW I am surprised that there is not an addon that provides ToT and also
command system on, two feature that are standard in all of the otherwise
rather less capable transceivers.
73 Stewart/G3YSX
73, Olli - DH8BQA
http://www.dh8bqa.de
> Stewart Bryant <[email protected]> hat am 5. März 2015 um 11:10
geschrieben:
>
>
> Does the TX-INH state over-ride all other TX commands?
>
> I am trying to find a very simple way of preventing the
> K3 from transmitting for more than (say) 10 mins when
> used remotely.
>
> I can tell if it has gone into transmit by looking at the
> KEY-OUT. What I need is a way of unconditionally
> killing any transmit, and I am hoping the setting
> TX-INH will do that.
>
> Since I use cat TX control, I imagine the only
> alternative is to become a man in the middle
> of the CAT interface, relaying the RS232 bytes
> back and fourth and interjecting an RX command
> if I detect the timeout state. This fails my
> criteria that failsafes must be so simple
> they are obviously bug free.
>
> 73
>
> Stewart
>
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[email protected]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
