#Use fldigi for general logging download

If you change the contents of cty.dat while fldigi is running you should force fldigi to reload the data from the file. You have the option of changing that file location by either entering the new folder pathname in the edit control, or by using the 'Browse' or 'Default' button. The default location for this file is in the fldigi default files folder. This file is maintained by, and can be downloaded from the following web site: Otherwise the azimuth/distance is computed from the data in the cty.dat file. If the station was previously worked the operator's name and azimuth/distance will be computed from the logbook gridsquare entry (Loc). The data is derived by parsing the callsign and referral to both the logbook and the 'cty.dat' file. The popup will look like one of the following: If you check the 'callsign tooltips in received text' then the Rx text area will popup an information box whenever the mouse is held over a callsign for more than 2 seconds. You can elect to have the RST in/out preset to 599 after you clear the QSO entry fields. That will open a pop-up menu with selections to transfer the data into a number of different log fields. You may also right click on a word (or a phrase that has been highlighted by dragging the cursor over the text). Clicking on the 599 NJ and Bozo would treat each as a separate word. The station being worked might send this as 599-NJ-Bozo. The exchange might be RST, STATE and NAME. This is a useful tool for extracting contest exchange data. You can add word delimiter characters in the designated text box. Each data item is considered to be a single word normally delimited by the space, tab or end-of-line character. The call will be overwritten, but the other log fields need to be blank for the data transfer to be accomplished. The word pointed to by the cursor is parsed to determine it's intended field use call, RSQ, operator name, and QTH. You can also elect to use a single left click method if you prefer. The default is to use a Shift-Left-Click paradigm. You enter your default Transmit Power which is used for the logbook record.įldigi has various ways to transfer data in the Rx panel to the qso logging fields. You can force the callsign field to be upper case independent of capture or keyboard entry.

#Use fldigi for general logging download

Auto-fill Country and Azimuth uses the data found in the file 'cty.dat' that you should download and place in the fldigi default folder. You can also elect to whether to clear all of the qso fields when the log is saved or to leave them intact. You can request to be prompted whenever there is an unsaved entry in the qso log area.

It would have been a lot easier if fldigi's docs had had the protocol specification but the provided server and client are written in tcl/Tk so it was not that hard to figure out what was going on.Fldigi has a built in logbook. Took me a dozen live contacts to get it working right - but once I had it running, it worked perfectly. After each command I checked for the proper return value from fdserver. I then sent commands to fdserver to LOGON my call on the proper band, DUPCHECK the other call, then ADD the other call with class and section, before LOGOFF to reset the connection. Each line that came in on the UDP socket was parsed for stuff like callsigns, the band, the exchange (class and section). Can't post it here, but all I did was open up a UDP socket on a local port (to which I had already pointed wsjtx's secondary UDP output) and a TCP socket on a local port (the fdserver process). The script I ended up using was pretty straightforward.