Fast Log Entry (FLE) - Step-by-Step - Version 2.11

Contents

Sample log files

Four different sample log files can be loaded by clicking on one of the Load sample log menu items under the Help Menu.

FLE Sample log files

The examples below are taken from the DXpedition sample log.

Header Section

Beginning with FLE 2.7 your Station Call Sign and - optionally - the Operator, your own WWFF and SOTA references are now stored in each log as header lines with the following keywords (all keywords are not case-sensitive):

1 mycall wb9zzz
2 operator
3 qslmsg Please QSL via bureau
4 mywwff KFF-0156
5 mysota W7A/AP-001
6 nickname Home QTH

The mycall keyword is your Station Call Sign and it is mandatory. This is the logging station's call sign (the call sign used over the air). Saving ADIF files without your own call is prevented. There is only one unique station call sign per log. If you use another call on the air, use a new log.

Your call sign is shown in the lower status bar:

FLE status bar

The call sign of the Operator can optionally be added to the ADIF file, it is not mandatory. Use the operator keyword and add the call sign of the operator. It can be different from the Station Call Sign but it may not be the name of the operator! The operator keyword can be repeated further down the log with other operator call signs if you had more than one and if they changed.

The optional qslmsg keyword is used to add the same QSL Message Text to each QSO in the ADIF file. This can be useful e.g. for eQSL.cc. It is not mandatory but valid for the entire log once entered here. QSL Messages can alternatively be entered in single QSO lines and are embedded in square brackets []. See the Optional information paragraph. They overwrite this qslmsg header text.

The mywwff keyword is used to register your own WWFF reference number in WWFF Logging. See also chapter WWFF logging. The syntax is: AAFF-CCCC: AA = national prefix, CCCC = 4-digit numeric code (e.g. ONFF-0001).

The mysota keyword is used to register your own SOTA reference number in SOTA Logging. The syntax is: AA/NN-CCC: Association/Name-3-digit numeric Code (e.g. G/CE-001). Your own SOTA reference number is mandatory for SOTA Logging.

The nickname keyword can be used for eQSL ADIF uploads. See chapter Uploading logs to eQSL.cc.

If you use the same call on the air but from different WWFF or SOTA references, use a new log.

The required header lines are inserted either automatically or by Insert Menu > Insert Log Header or by using the keyboard shortcut Alt+C.

Entering QSOs

Now start your log with the date of the first QSO using the Keyword DATE. DATE is not case-sensitive, all keywords are not case-sensitive.

1 date 2016-10-30

The Date Format is year-month-day (yyyy-mm-dd) and there are no other date formats. As long as the date is not completely entered or not valid the date entry is higlighted with a yellow background color.

1 date 2016-1
2 date 2016-13-05

Year, month and day may be typed abbreviated and you may use any separators other than dash.

1 date 16/2/1

Hint: The current date can be inserted at the cursor position using the function key F1.

Now enter Band and Mode of your first QSO. It can be any band according to the ADIF specifications (160m, 80m, 40m...) and any mode (for example CW, SSB, RTTY). Find the list of valid bands and valid modes at the bottom of this page.

1 date 2016-10-30 80m cw

Date, band and mode can be entered in a single line or in separate lines.

1 date 2016-10-30
2 80m cw

Now enter your QSOs each in a new line with Time (in UTC!) and Call Sign (in this sequence).

1 date 2016-10-30
2 80m cw
3 2335 ra3ax

Hint: The current UTC time can be inserted at the cursor position using the function key F2.

Everything can be entered in one line as well but each new QSO must be entered in a new line.

1 date 2016-10-30
2 80m cw 2335 ra3ax

Next QSO is with DJ2MX at the same minute (2335). The minute hasn't changed from the previous QSO. So all you need to do is to enter the call sign.

1 date 2016-10-30
2 80m cw 2335 ra3ax
3 dj2mx

Next QSO is at 2340. You enter only the changed part of the time compared to the previous QSOs.

1 date 2016-10-30
2 80m cw 2335 ra3ax
3 dj2mx
4 40 dk4rm

Next QSO is at 2342. The changed part of the time is minute 2. You have given OH7RM 449 and received 559 from him. Entry of sent and received reports is only needed if they differ from standard reports 59/599.

1 date 2016-10-30
2 80m cw 2335 ra3ax
3 dj2mx
4 40 dk4rm
5 2 oh7ms 449 559

In fact, only the first relevant numbers of the report need to be entered, e.g. 44 is 449 and 5 will be translated into 559.

5 2 oh7ms 44 5

If you have received 559 but sent standard report 599, both sent and received reports need to entered (in this order).

5 2 oh7ms 9 5

Again, all information for one QSO must be entered in one line. Each new QSO must be a entered in a new line. A valid QSO line contains at least a call sign.

1 date 2016-10-30 80m cw 2335 ra3ax
2 dj2mx
3 40 dk4rm
4 2 oh7ms 449 559
5  
6 50 ku1t 15m jt65 -17 -12

Empty lines are ignored, you can enter as many as you want.

Note: Standard reports are automatically added if missing with:

Reports other than standard reports or for modes not listed above should be entered in the QSO line.

Hint: Use the function key F5 to update the Log Grid from time to time to view all QSOs.

Off-Line and Real-Time Logging

FLE is by default an off-line QSO editor but FLE can also be used as a simple and effective real-time logger. Click on Real-Time Mode in the Logging menu:

FLE Realtime Mode

Logging type and logging mode are shown in the lower status bar:

FLE status bar

Enter at least a valid call sign and hit the ENTER key.

9 yo3jw

The current UTC time will automatically be added in front of the QSO line.

9 1454 yo3jw

Hint: The current UTC time can alternatively be inserted by using function key F2.

Typing or logging errors

Typing or logging errors are indicated with yellow background color, in particular date, time and call sign errors. February doesn't have 30 days, 1860 is not a valid time and call signs may e.g. not contain a question mark. Date, time and call sign errors are shown in red in the Log Grid Panel and you cannot save the ADIF file unless you have fixed all errors.

FLE logging errors

Optional information

FLE can also export QSO Comments and Grid Locators and QSL Messages for a single QSO. QSO comments must be embedded in brackets <>, grid locators must have a preceeding hash # and QSL Messages must be embedded in square brackets [].

9 51 dl5mo < strong signal > #JO50 [QSL message]

QSL Messages can alternatively be set for the entire log using the optional qslmsg keyword in the Header Section. The optional header QSL Message Text is added to each QSO in the ADIF file. It is then valid for the entire log once entered there. QSL Messages entered in single QSO lines overwrite the QSL Message of the header. An empty message [] generates no QSL Message in the ADIF file.

Remarks can be embedded in curly braces {}. Remarks are not exported in ADIF.

1 { Sample FLE DXpedition log }

Remarks can also be set in lines marked with a hash # at the first position:

311 # next day
312 day +

Changing date, band and mode

If your log continues on the next day, you can use the DAY Keyword and the + sign (plus).

13 day +

If your log continues two (or more) days later, use two (or more) + signs. Based on the last date 2016-10-30 the day ++ command will set the date to 2016-11-01.

13 day ++

Change of date, day, band and mode can be entered either before or in a new QSO line in any order.

13 day ++ 40m ssb

or

13 ssb 40m day ++

or

13 day ++
14 40m
15 ssb

Interpolating log times

If you had a high QSO number in a Contest or on a DXpedition, interpolation of times is useful. Be sure to check Interpolate Log Times in the Logging Menu. This option is only available in the Off-line Logging Mode.

Enter a start time and the next time every 20 minutes or so. FLE will interpolate the missing non-entered times based on the first and the last entered time.

20 0014 g3fpq
21      ra6au
22      oh2pj
23      oh3es
24      sm5wp
25      f5lge
26      sp8brq
27   38 ua3tcj

Contest Logging

Contests require the entry of serial numbers and/or consecutive serial numbers. Check Contest Logging in the Logging Menu.

FLE Contest logging

Sent exchanges must have a preceeding , (comma) and received exchanges a preceeding . (dot).

18 1856 ku1t ,337 .781

Standard reports other than 59/599 do not need to be entered. If they differ from 59/599 enter them in the full or the abbreviated format.

18 1856 ku1t 579 ,337 589 .781
18 1856 ku1t 7 ,337 8 .781

If consecutive serial numbers are to be sent, check Consecutive Serial Numbers in the Logging Menu. No more need to enter your own serial number; just enter the received serial number.

18 1856 ku1t .781

WWFF Logging

WWFF Logging

WWFF Logo  

The WWFF Logging option is an extension to FLE to support the World Wide Flora and Fauna in Amateur Radio Program. Please visit external link www.wwff.co.

To submit your log to WWFF some extra ADIF fields are required, see external link wwff.winqsl.com/logsearch/logsearch-faqs-log-format/. In addition to CALL, QSO_DATE, TIME_ON, BAND, MODE your own and/or your hunter's WWFF reference number are supported by FLE in the WWFF Logging mode.

Your own activator's WWFF reference can be entered in the Header Section using the keyword mywwff.

The reference numbering is XFF-YYYY or XXFF-YYYY (X or XX depending on the national prefix, YYYY four numbers 0001-9999). The ADIF field is MY_SIG_INFO and is valid for the entire log. If you enter an own WWFF reference MY_SIG is set to “WWFF”.

If your QSO partner/hunter has a WWFF reference enter it by using the keyword wwff:

1 date 2016-04-10 40m ssb 2335 m0yza wwff gff-0002

The wwff keyword is not required but the reference is always validated.

1 date 2016-04-10 40m ssb 2335 m0yza gff-0002
2 37 on4vt onff-3 { not valid, must be 4 numbers}

The ADIF field SIG_INFO is used for this reference and SIG is set to “WWFF”.

You should also enter your Station Call Sign (mycall) and Operator Call Sign (operator) as shown in the Header Section.

SOTA Logging

SOTA Logging

WWFF Logo  

The SOTA Logging option is an extension to FLE to support the Summits on the Air Program. Please visit external link www.sota.org.uk. SOTA logs are exported in the CSV file format as describe here: external link www.sotadata.org.uk/ActivatorCSVInfo.htm. You will find an extra File menu entry and a button "Export SOTA CSV File" with SOTA Logging.

Your own activator's Summit reference must be entered in the Header Section using the keyword mysota. You must also enter your Station Call Sign (mycall) as shown in the Header Section.

If your QSO partner/hunter has a SOTA reference enter it by using the keyword SOTA :

1 1716 dl/on6zq/p sota dl/al-093

The sota keyword is not required but the reference is always validated.

1 1716 dl/on6zq/p dl/al-093
2 28 on4vt/p on/on-3 { not valid, must be 3 numbers}

The syntax is: AA/NN-CCC: Association/Name-3-digit numeric Code (e.g. G/CE-001). The list of associations, regions and codes can be found here: external link www.sota.org.uk/Associations.

WWFF and SOTA Logging can be used simultaneously by checking the WWFF + SOTA Logging option. Both WWFF ADIF files and SOTA CSV files can be generated then.

Exporting QSOs in ADIF

Click on the Update Log Grid button or hit function key F5 to fill the log data grid with the QSO records. Click on the Save ADIF File button or use the shortcut key Ctrl-I to export the QSO data into an ADIF file (the log data grid is automatically updated when saving the ADIF file). The ADIF file can be imported into your logging software or uploaded to LoTW or eQSL.cc.

It is mandatory to enter your Station Call Sign in the Header Section before saving ADIF.

Uploading logs to LoTW

Please consider using LoTW, the ARRL Logbook of The World.

FLE has an integrated ADIF log upload to LoTW using TQSL. Prerequisites are that you are a registered LoTW user, you have TQSL 2 and your LoTW certificate(s) installed and you have set one or more station locations. Once the ADIF log is saved on disk, the Upload ADIF to LoTW menu item and button are enabled. The LoTW ADIF Upload dialog pops up and your log call sign is preset. If you have more than one station location be sure to select the right one before hitting the Upload button.

LoTW Uplooad

TQSL is launched in the background. The TQSL messages are captured and displayed in the dialog. Please check the reasons if an upload has not been successful.

Uploading logs to eQSL.cc

FLE has also an integrated ADIF log upload to eQSL.cc. Prerequisites are that you have a valid eQSL.cc account with an eQSL user and password. Once the ADIF log is saved on disk, the Upload ADIF to eQSL.cc menu item and button are enabled. The eQSL.cc ADIF Upload dialog pops up and your log call sign is preset as eQSL User as well as the eQSL account password and an optional QTH Nickname. The password can be saved and preset again for the next eQSL uploads if you check Save Password.

FLE eQSL upload

Please note that the eQSL User ID can be different from the call sign of your portable activity and your log. If you have different WWFF or SOTA portable activities and want to upload your logs to eQSL, you should register new attached accounts in eQSL.cc using different unique QTH Nicknams for these activities. The QTH Nickname can be entered in the Header Section of each log using the keyord nickname. Example:

1 nickname Home QTH

The ADIF file is then exported with the ADIF field APP_EQSL_QTH_NICKNAME.

A wrong QTH Nickname is reported as error by the eQSL ADIF web interface and the log rejected:

FLE eQSL Upload wrong QTH nickname

Exporting Cabrillo

FLE can export in the Cabrillo Format. See the Cabrillo page for more hints.

Saving the log file

The log text file can be saved (Ctrl-S) and opened again at any time. Next time you start FLE the last log file is opened and loaded automatically. Set the Auto Save Log option in the Options menu to let your modified log file automatically be saved once every two minutes.

Editor Options

FLE uses context-sensitive highlighting. All QSO data elements can be distinguished by different colors or styles as set in the Editor Options under the Options Menu. You can also set the font and font size of the QSO editor.

FLE Editor Options

More hints

Use the F4 function key to hide or unhide the QSO log grid panel or use the View menu:

FLE Compact

Keyboard shortcuts

Shortcut Function   Shortcut Function
Ctrl+A Select all text   F1 Insert current date at cursor position
Ctrl+B Choose a band to insert   F2 Insert current UTC time at cursor position
Ctrl+C Copy text   F3 Find next
Ctrl+D Insert the date picker combo date at the cursor position   Shift+F3 Find previous
Ctrl+F Find text   F4 Hide or unhide log grid panel
Ctrl+H Replace text   F5 Update log grid
Ctrl+I Save the ADIF file      
Ctrl+M Choose a mode to insert   Alt+C Insert header lines
Ctrl+O Open a log file   Alt+E Editor Options
Ctrl+N New log file   Alt+X Exit
Ctrl+S Save the log file      
Ctrl+V Paste text      
Ctrl+X Cut text      
Ctrl+Y Redo text changes      
Ctrl+Z Undo text changes      
Ctrl++ Insert the next day at the cursor position      
Ctrl+Home Jump to first line      
Ctrl+End Jump to last line      

Keywords

All keywords are not case-sensitive.

Keyword Description
mycall The mycall keyword is your station call sign and it is mandatory. This is the logging station's call sign (the call sign used over the air). Saving ADIF files without your own call is prevented.
operator The call sign of the operator can optionally be added to the ADIF file, it is not mandatory. Use the operator keyword and add the call sign of the operator. It can be different from the station call sign but it may not be the name of the operator! The operator keyword can be repeated further down the log with other operator call signs if they change.
qslmsg QSL Messages valid for the entire log can be entered in the header section of the log. It is not mandatory.
mywwff The mywwff keyword is used to register your own WWFF reference number in WWFF Logging. See also chapter WWFF logging. The syntax is: AAFF-CCCC: AA = national prefix, CCCC = 4-digit numeric code (e.g. ONFF-0001).
mysota The mysota keyword is used to register your own SOTA reference number in SOTA Logging. The syntax is: AA/NN-CCC: Association/Name-3-digit numeric Code (e.g. G/CE-001). Your own SOTA reference number is mandatory for SOTA Logging.
nickname The nickname keyword can be used for eQSL ADIF uploads. See chapter Uploading logs to eQSL.cc.
date The date format is year-month-day (YYYY-MM-DD), e.g. 2016-12-31. Year, month and day may be abbreviated and you may use separators other than dash.

Valid Bands

2190m 630m 560m 160m 80m 60m 40m 30m 20m 17m
15m 12m 10m 6m 4m 2m 1.25m 70cm 33cm 23cm
13cm 9cm 6cm 3cm 1.25cm 6mm 4mm 2.5mm 2mm 1mm

Valid Modes

CW SSB AM FM RTTY PSK JT65 JT9 FT8
ARDOP ATV C4FM CHIP CLO CONTESTI DIGITALVOICE DOMINO DSTAR
FAX FSK441 HELL ISCAT JT4 JT6M JT44 MFSK MSK144
MT63 OLIVIA OPERA PAC PAX PKT PSK2K Q15 QRA64
ROS RTTYM SSTV T10 THOR THRB TOR V4 VOI
WINMOR WSPR

The valid bands and modes are synchronized with the ADIF specifications at adif.org.uk and FLE is compliant with the ADIF standards 3.0.6. A distinction is drawn between modes and submodes in ADIF. Please note that FLE only supports modes but no submodes. An example is PSK and it's many submodes like PSK31, PSK63, PSK125, QPSK31, QPSK63, QPSK125, SIM31 and others. PSK31 for example has to be entered as PSK. JT65A has to be entered as JT65 and so on.