Logger
The logging functions in Fldigi are
purposely sparse. They are designed to easily and accurately
transfer QSO information from the modem application to a logbook
application of your preference. The only requirement is that the
logbook application be able to receive data from a message queue that is compatible with the specifications for Xlog. The author's application fl_logbook or Xlog can be used for the receiving application.
Data is captured by mouse click, keyboard entry and by program action for the following fields:
Data is captured by mouse click, keyboard entry and by program action for the following fields:
| Field Name | Value |
| program: | fldigi v V.VVVV where V.VVVV is the program version # |
| date: | current system GMT date |
| time: | system GMT time in HHMM format, taken from the QSO time field |
| endtime: | system GMT time in HHMM at the time the QSO "save" button is pressed |
| call: | other stations CALLSIGN, taken from the QSO Call field |
| freq: | operating frequency = Transciever freq +/- audio freq, in
KHz. +/- iaw with sideband in use for hamlib / memmap i/o controls operating frequency = base frequency for Band +/- audio frequency in KHz for non CAT transceivers. |
| tx: | the other stations RSQ, taken from the QSO Rst(s) field |
| rx: | your RSQ, taken from the QSO Rst(r) field |
| name: | the other stations Operator Name, taken from the QSO Name field |
| qth: | the other stations Qth, taken from the QSO Qth field |
| locator: | the other stations grid square locator, taken from the QSO Locator field |
| notes: | free form notes relative to the QSO, taken from the QSO Notes field |
Fldigi can query one of the following databases to find information on a call sign.
To query the selected database enter the callsign and then press the QRZ button. Either the local QRZ cdrom will be queried, or a request will be sent to QRZ or Hamcall via a temporary socket connection. The data for Name, Qth, Loc and the birthdate if available will be filled in for the requested callsign. If the online service reports the location (grid square) of the queried callsign, the azimuth (and reverse) will be computed and displayed in the AZ widget. You must have previously configured your own location's grid square location on the Oper tab.
You specify the type of QRZ query on the QRZ configuration tab:
The query to the QRZ on-line database is made using a socket connection to the subscription service. QRZ will provide a 1 week complimentary subscription simply by registering your callsign and creating a password at www.qrz.com
The query to the Hamcall on-line database is also made using a socket connection to the subscription service.
- QRZ - on line subscription
- QRZ - local cdrom (or cdrom database on HD)
- Hamcall - online subscription
To query the selected database enter the callsign and then press the QRZ button. Either the local QRZ cdrom will be queried, or a request will be sent to QRZ or Hamcall via a temporary socket connection. The data for Name, Qth, Loc and the birthdate if available will be filled in for the requested callsign. If the online service reports the location (grid square) of the queried callsign, the azimuth (and reverse) will be computed and displayed in the AZ widget. You must have previously configured your own location's grid square location on the Oper tab.
You specify the type of QRZ query on the QRZ configuration tab:
The query to the QRZ on-line database is made using a socket connection to the subscription service. QRZ will provide a 1 week complimentary subscription simply by registering your callsign and creating a password at www.qrz.com
The query to the Hamcall on-line database is also made using a socket connection to the subscription service.
If you are using the cdrom for the database the program will look for the data in the following locations:
Pressing the "Save" button causes fldigi to send an IPC message containing all of the qso data to a log program such as fl_logbook or Xlog which are listeners. The IPC message format is compatible with Xlog. The "Save" also causes the QSO log contents to be appended to an ADIF file named fldigi.adif which can be found in the $HOME/.fldigi folder. That file can then be used as in import file for any adif compatible logging program. fl_logbook has that capability.
If you use fl_logbook and forgot to have it open during the capture of several QSOs for which you want to retain the logging data, have no fear. Besides the adif file, you can simply start the fl_logbook application. It will read all pending IPC messages and load the data into the logbook.
~/callbk/
(the CDROM data base was copied to the users Home directory)
/cdrom/callbk/
/mnt/cdrom/callbk/
/mnt/cdrom0/callbk/
/mnt/cdrom1/callbk/
/media/cdrom/callbk/
/media/cdrom0/callbk/
/media/cdrom1/callbk/
/cdrom/callbk/
/mnt/cdrom/callbk/
/mnt/cdrom0/callbk/
/mnt/cdrom1/callbk/
/media/cdrom/callbk/
/media/cdrom0/callbk/
/media/cdrom1/callbk/
Pressing the "Save" button causes fldigi to send an IPC message containing all of the qso data to a log program such as fl_logbook or Xlog which are listeners. The IPC message format is compatible with Xlog. The "Save" also causes the QSO log contents to be appended to an ADIF file named fldigi.adif which can be found in the $HOME/.fldigi folder. That file can then be used as in import file for any adif compatible logging program. fl_logbook has that capability.
If you use fl_logbook and forgot to have it open during the capture of several QSOs for which you want to retain the logging data, have no fear. Besides the adif file, you can simply start the fl_logbook application. It will read all pending IPC messages and load the data into the logbook.