| |
YT7MPB > BPQ 07.06.24 18:30l 66 Lines 2452 Bytes #102 (0) @ WW
BID : 10322_YT7MPB
Read: GUEST
Subj: Re: ARDOP port and CAT issue
Path: IW8PGT<LU4ECL<JE7YGF<JH4XSY<IW0QNL<IZ3LSV<I0OJJ<I0OJJ<N6RME<YT7MPB
Sent: 240607/1701Z 10322@YT7MPB.#NSD.SRB.EU LinBPQ6.0.24
>From yt7mpb%yt7mpb.#nsd.srb.eu@i0ojj.ampr.org Fri Jun 7 19:03:11 2024
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0p.1) with SMTP
id AA17003202 ; Fri, 07 Jun 2024 19:03:11 +0200
Message-Id: <10322_YT7MPB@i0ojj.bbs>
>From: yt7mpb@yt7mpb.#nsd.srb.eu
X-JNOS-User-Port: Telnet (i0ojj @ 44.134.32.240) -> Sending message
On Fri, 07 Jun 24 01:20:00 Z
N9SEO wrote:
>
> Misko,
>
> INTERLOCK and RADIO I believe are the same, So if you remove one it
> should be ok. I believe G8BPQ said that eventually RADIO will replace
> INTERLOCK on the forums sometime ago. But its been a while so you might
> search around. I think it was in a response to one of my posts a few
> years back. RADIO is also replacing "RIGCONTROL" eventually is my
> understanding.
>
> Tho I dont know are you using RIGCONTROL on a port or RADIO entries in
> CFG. I only use RADIO=1 per port and then define a RADIO (cat)
> definition like:
>
> RADIO 1
> FLRIG 192.168.200.113:12345 HAMLIB=4532 PTTMUX COM4
>
>
>
> The standalone ARDOP client, for me I had to enable PTTMUX and set a
> pair of psuedo ttys to get PTT to work. So in the above it'd be
> something like COM4 to BPQ and COM5 to ARDOPC.exe.
>
> Hope that helps clear up.
>
> 73 de N9SEO
> Kayne
>
>
>
Kayne,
Thank you for your response. In my view, INTERLOCK and RADIO are not the same (but I might be wrong with that). I believe that
INTERLOCK prevents two or more ports to transmit at the same time, while RADIO shall configure an appropriate radio to a port (
e.g. for scanning, etc). In any case, I have been using both of them and haven't had any trouble with my 300bd packet and pacto
r ports.
But now with ARDOP port I noticed that as long as those two lines (or a single line) is within the port settings, there is no C
AT in my radio (FT-847).
So in that situation I am only able to initiate an outgoing ARDOP call, but the radio does not stop scanning before the calls,
which means such calls go to two frequencies scanned. Bad of course.
Furthermore, I also noticed that forwarding scripts (I used for 300bd packet) do not execute with ARDOP port. For example, the
radio does not accept RADIO <freq.> line anymore, which means the radio does not qsy to the partner's channel.
In general, I am unsure about proper syntax and a list of commands in ARDOP world, so I would appreciate any pointer to a good
reading about.
--
73 de Misko <YT7MPB@YU7BPQ.#NSD.SRB.EU>
Read previous mail | Read next mail
| |
