Logbook Server
The logbook server maintains a large set
of QSO
logbook fields that will probably be sufficient for casual operating,
contesting and some certificate logging. All of the fields that
are captured in the logbook are maintained in an ADIF database that can
be read by any logbook program that can read the ADIF text
format. The server can open any logbook adif file, including
those created by fldigi. You should NOT open an adif logbook file
by more than one program at a time. The database uses "flat
files" and simultaneous use by more than a single program may corrupt
the file.
The complete set of logbook fields are:
* - these fields are sent to fllog by the client program, which may be fldigi
The data in the fllog logbook can be exported to external text files; ADIF, text, and CSV (comma separated value). The ADIF can be read by any ADIF compatible logbook program. The text output is suitable for use in a wordprocessor and for printing. The CSV can be read into many spreadsheet programs such as Excel, Open Office or Gnumeric.
The complete set of logbook fields are:
| ADIF FIELD | USE | ADIF FIELD | USE | ||
| BAND | QSO band (computed from frequency) | STATE | * | contacted stations state | |
| CALL | * | contacted stations call sign | QSLRDATE | QSL received date | |
| COMMENT | * | comment field for QSO | QSLSDATE | QSL sent date | |
| COUNTRY | * | contacted stations DXCC entity name | STX | * | QSO transmitted serial number |
| FREQ | * | QSO frequency in MHz | SRX | * | QSO received serial number |
| GRIDSQUARE | * | contacted stations Maidenhead Grid Square (Loc) | TIME_OFF | * | end time of QSO in HHMM format |
| MODE | QSO mode | TIME_ON | * | start time of QSO in HHMM format | |
| NAME | * | contacted operators name | TX_PWR | * | power transmitted by this station |
| QSO_DATE | * | QSO data at start of contact | IOTA | Islands On The Air | |
| RST_RCVD | * | received signal report | VE_PROV | * | 2 letter abbreviation for Canadian Province |
| RST_SENT | * | sent signal report | XCHG1 | * | received contest exchange |
| QTH | * | contacted stations city | MYXCHG | sent contest exchange | |
| CNTY | county | ||||
| DXCC | contacted stations DXCC country code | ITUZ | ITU zone | ||
| IOTA | Islands-On-The-Air designator | CQZ | CQ zone | ||
* - these fields are sent to fllog by the client program, which may be fldigi
The data in the fllog logbook can be exported to external text files; ADIF, text, and CSV (comma separated value). The ADIF can be read by any ADIF compatible logbook program. The text output is suitable for use in a wordprocessor and for printing. The CSV can be read into many spreadsheet programs such as Excel, Open Office or Gnumeric.
Fllog will respond to a both duplicate and last contact queries from the client program
If you have previously worked a station the logbook will be searched for the most recent qso and fill the Name, Qth and other fields from the logbook. This data is then passed back to the client program.
You open the logbook by selecting from the View menu; View/Logbook. The logbook title bar will show you which logbook you currently have open. fldigi can maintain an unlimited (except for disk space) number of logbooks.
The full pathname of the open log file will appear in the File: control. The file name will be on the title bar.
If you have previously worked a station the logbook will be searched for the most recent qso and fill the Name, Qth and other fields from the logbook. This data is then passed back to the client program.
You open the logbook by selecting from the View menu; View/Logbook. The logbook title bar will show you which logbook you currently have open. fldigi can maintain an unlimited (except for disk space) number of logbooks.
The full pathname of the open log file will appear in the File: control. The file name will be on the title bar.
You can resize the dialog to suit
your screen size and operating needs. Fldigi will remember the
placement and size for subsequent use.
You can create new entries, update existing entries, and delete entries using this dialog. You can also search for an entry by callsign. The browser can be sorted by Date, Callsign, Frequency or Mode. The sort can be forward or backward with the most recent being the default selected entry after each sort. You execute the sort by clicking on the column button at the top of the column to be sorted. Each click causes the sort to reverse. I like to view my log with the most recent at the top. You might want to view it with the most recent on the bottom.
There are no frills such as keeping track of DXCC worked, fancy printouts etc. Fldigi's logbook is primarily a capture function. You can export your data for use with an external database or for uploading to LOTW or eQSL. Data from those sources can also be used for importing into the logbook.
Exporting logbook data: Log Exports.
Cabrillo reporting: Contest Reports.
You can create new entries, update existing entries, and delete entries using this dialog. You can also search for an entry by callsign. The browser can be sorted by Date, Callsign, Frequency or Mode. The sort can be forward or backward with the most recent being the default selected entry after each sort. You execute the sort by clicking on the column button at the top of the column to be sorted. Each click causes the sort to reverse. I like to view my log with the most recent at the top. You might want to view it with the most recent on the bottom.
There are no frills such as keeping track of DXCC worked, fancy printouts etc. Fldigi's logbook is primarily a capture function. You can export your data for use with an external database or for uploading to LOTW or eQSL. Data from those sources can also be used for importing into the logbook.
Exporting logbook data: Log Exports.
Cabrillo reporting: Contest Reports.