|
YT7MPB > BPQ 30.06.23 17:40l 58 Lines 1783 Bytes #999 (0) @ WW
BID : 2750_YT7MPB
Read: DJ6UX GUEST
Subj: ALE features in LinBPQ?
Path: DB0FHN<DB0FFL<OE5XBL<DB0RBS<DB0ERF<DK0WUE<PE1RRR<GB7YEW<N5MDT<N3HYM<
YT7MPB
Sent: 230630/1535Z 2750@YT7MPB.#NSD.SRB.EU LinBPQ6.0.23
I tested QtTermTCP in LinBPQ for ALE (Automatic Link Establishment)
commands, after upgrading Dragon DR-7400 to the ALE firmware. It seems
that QtTermTCP accepts most ALE commands pretty well (of course
provided you have ALE firmware installed in SCS Dragons):
Connected to TelnetServer
att 2
LPTP:YU7BPQ} Ok
#ale scan 1
SCS} OK
#ale soundnow
SCS} OK
#ale mode 1
SCS} OK
#trx ty y 4800 a ttl
SCS} OK
#trx yt 6
SCS} OK
#ale scan 1
SCS} OK
#ale mode 0
SCS} OK
#ale mode 1
SCS} OK
#ale sound 5
SCS} OK
#ale soundnow
SCS} OK
#ale sound 5
SCS} OK
Disconnected
I noticed that QtTermTCP tends to disconnect the user from the console
after a while of inactivity in an ALE session started at the terminal,
say after 10 mins or so since the last command was entered. In the
example above, I entered the last command: #ale sound 5 (that was
supposed to transmit ALE sounding every 5 minutes). However, after some
10 minutes or like I got disconnected. It would not be a big deal, but
whenever that disconnection happens LinBPQ tends to add into scanning
the frequencies which were previously solely set for the BBS purpose
(and hence non-related to the ALE controller within the SCS firmware).
For example, ALE system is supposed to scan only the frequencies
explicitly set for ALE, but not to scan frequencies 'outside' the ALE
configuration. (Particularly not to transmit ALE 'sounding' on non-ALE
frequencies.)
So it makes me wonder if a new ALE 'module' can be considered to be
added as a new part of LinBPQ in the future. I ask that because I found
only LinBPQ (up to now) as a software that runs neatly in Linux and
supports most of ALE commands. (I found some Windows-related ALE
software behaving badly when run under Wine in Linux.)
--
73 de Misko YT7MPB@YU7BPQ.#NSD.SRB.EU
Read previous mail | Read next mail
| |