| |
YT7MPB > BPQ 31.10.23 15:31l 128 Lines 3703 Bytes #108 (0) @ WW
BID : 4868_YT7MPB
Read: GUEST
Subj: Re: FT-847 radio control issue
Path: IW8PGT<IZ3LSV<I0OJJ<LU1DBQ<LU6DJ<LU9DCE<GB7YEW<VE3CGR<N3HYM<YT7MPB
Sent: 231031/1328Z 4868@YT7MPB.#NSD.SRB.EU LinBPQ6.0.24
Hi all who use FT-847,
In order to solve the CAT issue, I have been testing LinBPQ version
6.0.24.17 (October 2023). The first impressions are positive: After
starting LinBPQ the "CAT" icon appears on the radio's display, and
stays there permanently. Furthermore, scanning the two frequencies
returned back, as well as forwarding on preselected frequencies.
Will continue tests in days to come ...
On Sat, 21 Oct 23 15:11:45 Z
YT7MPB wrote:
> Hi all,
>
> I noticed that after using LinBPQ, Yaesu FT-847 is *not* anymore set
> as the radio intended to be used for TRX radio control in the SCS
> Dragon's DR-7400 internal setup. For example (by using minicom
> terminal):
>
> cmd: trx
> >>> Transceiver Control Menu active - Type Help for
> >>> information
>
> trx: ty
> Current transceiver settings:
> -----------------------------
> Type: YAESU
> Baudrate: 9600 BD
> VFO: A
> Interface: V24/RS-232
>
> trx: yt
> *** Yaesu TRX type: 0
> trx:
>
> As seen above, the TRX type had value '0' which was not proper for
> FT-847. In other words, looks as if a wrong Yaesu radio was set. So I
> made an experiment:
>
> - At first, I double checked if FT-847 was properly configured in the
> PTC's internal setup (by using minicom terminal):
>
> trx: h yt
> YType:
> defines Yaesu transceiver sub-type.
> 0= FT-890, 1= FT-990/1000, 2= FT-1000 MP, 3= FT-100, 4=
> FT-920, 5= FT-847, 6= FT-817/FT-857/FT-897, 7 = FT-950, 8 = FT-2000, 9
> = FT-9000, 10 = VX-1700, 11 =
> FT-991(A).
> trx: yt 5
> *** Yaesu TRX type: 5
> trx: yt
> *** Yaesu TRX type: 5
> trx: sap
> *** PARAMETERS SAVED
> trx:
>
>
> - Then I exited the terminal, and also checked if FT-847 was
> configured in bpq.cfg file:
>
> RADIO 1
> PTCPORT 9600 YAESU FT847
> 6,14.1023,USB,P0
> 4,14.1089,USB
> ****
>
> Seems that all was there. I started LinBPQ, but radio control still
> did not scan the two frequencies, neither had I seen 'CAT' icon in the
> radio's display.
>
> - Third, then I tried to execute the sample fwd script, for a station
> where the script started with this:
>
> ATTACH 2
> #RADIO 14.09640 USB
> \TRX F 14098.00
>
> (Please note that RADIO command was disabled, but \TRX F <frq> was
> enabled instead.)
>
> The 'CAT' icon appeared on the 847's display, following by scanning
> the two frequencies set within the bpq.cfg file. After a while and
> according to the forwarding schedule, some outgoing forwarding
> sessions were initiated. (Those having proper RADIO command within
> the script.) So far - so good.
>
> - Then I exited LinBPQ and reopened the terminal:
>
> cmd: trx
> >>> Transceiver Control Menu active - Type Help for
> >>> information
>
> trx: ty
> Current transceiver settings:
> -----------------------------
> Type: ICOM
> Baudrate: 1200 BD
> Address: 4 (dec), 04 (hex)
>
> trx: yt
> *** Yaesu TRX type: 0
> trx:
>
>
> It seems that LinBPQ somehow left the PTC Dragon modem 'thinking' that
> I was using an Icom radio and not Yaesu.
>
> - Ok, I decided not to fix that error this time, but instead to exit
> the terminal, and start LinBPQ again:
>
> LinBPQ started scanning the two 'parking' frequencies immediately, as
> well as to initiate forwarding sessions. It worked well but remained
> so strange to me. Any idea why LinBPQ saw an Icom radio instead of
> Yaesu?
>
--
73 de Misko YT7MPB@YU7BPQ.#NSD.SRB.EU
Read previous mail | Read next mail
| |
