Fldigi 4.1.20 Download !EXCLUSIVE!
Trina Human
I have the same experience with Linux Kali and Ubuntu 19. After removing all additional fonts fldigi works in proper way. I am sure that fldigi is in conflict with some fonts but I need fonts for qsl design (inkscape) and qsl printing (glabesls).
Parameter "Drop after SyncErr >" automates remote mode closing when fldigi is closed. But as it may affect also (in slow PCs) fldigi started by cqrlog it can be changed. 0 disables, 1-20 means timer rounds until drop. When closing happens it leaves text "Socket error, check fldigi!" to NewQSO field "Comment QSO".
In all cases fldigi must be started from command line with parameter: fldigi --xmlrpc-server-port 7362When closing fldgi properly and answering YES to save setup changes the next start should open xmlrpc server without parameters from usual icon.
You can set preferences so that cqrlog will start fldigi and/or wsjt-x programs for you when you enter remote mode. This is very handy, but doing that has also one risk.
When fldigi or wsjt-x has been started as a child process of cqrlog they will die at the moment cqrlog crashes for some reason.
If you start them manually as processes of their own and then activate remote mode from cqrlog they keep on running if cqrlogdies. You can finish your ongoing qso, start cqrlog again, set remote mode on and then log the qso in normal manner.
BPQ uses the KISS interface in FLDIGI. This has to be enabled using the Configure/IO Menu
"Dual Port" must be checked. Normally "Enable CSMA" and "Enable Busy Channel" should be unchecked. as BPQ handles Buay detect. If you want to run FLDIGI and BPQ on different machines, specify the IP address of the BPQ machine instead of 127.0.0.1 BPQ Configuration.The driver is defined to BPQ32 with DRIVER=FLDIGI. A typical configuration is:PORT ID=FLDigi DRIVER=fldigi PACLEN=64 CONFIG ADDR 127.0.0.1 7342 TIMEOUT=10 RETRIES=5 DEFAULTMODEM BPSK250/1500 UPDATEMAPENDPORT Use the ADDR command to define the IP address and Port of FLDIGI, and an optional PATH to FLDIGI.exe. If PATH is omitted, bpq32 won't start FLDIGI, and you will have to run FLDIGI before starting bpq32.
For example
ADDR 127.0.0.1 7342 PATH C:\FLDIGI\FLDIGI.exe
Note that two ports are used, one for eac direction of traffic. Data a sent to FLDIGI addressed to the specified port, and reponses are expected on the next higher port (7343 with the abouve example)
Other possible configuraton parameters are:
TIMEOUT
Sets the acknowledge timeout. Default is 5 seconds.
RETRIES
Sets the retry count. Default is 6
WINDOW
Sets the Window Size (similar to MAXFRAME in ax.25). Default is 16
DEFAULTMODEM
Sets the Modem and Centre Frequency to return to after each connection. Specify as Name/Freq.
UPDATEMAP
The modem logs connects to the Nodemap if you have specified a LOCATOR in your BPQ32.cfg. If you specify UPDATEMAP, stations heard will also be sent to the map.
The protocol operates a sliding window, with selective repeats of missed frames, so normally sending fairly large numbersof small frames in a burst is most efficient. The default PACLEN and WINDOW of 64 and 16 are ok for reasonably fast modes, but could result in very long trasmissions with slower modems. Having a very short PACLEN will increase the protocol overhead, and having too short a burst length will slow the overall transmission down due to the extra link turnrounds and ACK delays.Operation.To make an outgoing call, first use the ATTACH command to allocate the FLDIGI port. You can then use the following commands:
MODEM ModemName - Selectes the specified modem - eg MODEM BPSK250
FREQ n - Sets the centre frequesncy - eg FREQ 1500
SQUELCH ON - Enables Squelch
SQUELCH OFF - Disable Squelch
SQUELCH n - Set Squelch Level (n = 0 - 100)
MODE RAW - Sets interface to RAW mode, normally used to connect to FLARQ
MODE KISS - Sets interface to KISS mode, nurmally used between two BPQ stations. This is the default
C CALLSIGN - Initiates an ARQ connection to CALLSIGN
For axample, a Connect Script for BBS forwardinging in BPSK250 mode could be:ATTACH 2MODEM BPSK250C BBSCALL.Exchanging Mail with FLARQ.You can send plain text messages composed using the FLARG "Compose" menu to a BPQ BBS. As FLARQ doesn't have an interacive mode you can't request messages using the normal BBS commands, but if you send a file called "BBSPOLL.txt" to the BBS it will beinterpreted as a reverse forward request. The file can be empty.
You can also forward from BPQ Mail to FLARQ. The Connect Script must select RAW Mode and tell the BBS is is connecting to FLARQ. EGatt 10mode rawflarqc g8bpq
After playing with WSJT-X on QO-100 it was about time to experiment with some of the ancient modes on SAT. With Abdel, M0NPT operating C5C I did some QSOs in RTTY and PSK31. But obviously it was a pain to setup the IC-9700 to work with fldigi. Hamlib does not cope with the SAT mode of the TRX. Thats why I am using the rig with two VFOs. But in fldigi it would use the sound input from the TX VFO for decoding rather than the Sub-VFO for RX.
I copied them to the Scripts folder under the .fldigi folder, made them executable from the Terminal (chmod +x mldx5*.scpt), and set up the appropriate macro command:
/usr/bin/osascript $HOME/.fldigi/scripts/mldx5Key.scpt &
/usr/bin/osascript $HOME/.fldigi/scripts/mldx5Unkey.scpt &
... for each of two buttons, labeled PTT ON and PTT OFF.
As there is no way to use the EXEC command somehow inline I built a "dirty workaround". This AppleScript just runs the whole time fldigi is opened in the background and detects fldigi's RX/TX status through the XMLRPC interface. According to this status it sends the RX/TX commands to MacLoggerDX.
df19127ead