On 06/17/2011 01:41 PM, w1hkj wrote:
http://www.w1hkj.com/alpha/fldigi/
http://www.w1hkj.com/alpha/fllog/
fllog reads/writes standard fldigi logbook adif files. It also acts as a server
to multiple clients. These clients may be multiple running copies of fldigi on
the same or multiple machines on the network.
If fllog-0.9.905 and fldigi-3.22.0AB are executing on the same machine then no
special parameters are needed for the client (fldigi) to communicate with the
server (fllog).
If fldigi and fllog are on different machines you will need to know the socket
address of the server machine. The socket address and port are set at the client
end using command line parameters to fldigi. This is similar to the command line
parameters for arq and/or xmlrpc servers.
--xmllog-server-address HOSTNAME
Set the XMLLOG server address
The default is: 127.0.0.1
--xmllog-server-port PORT
Set the XMLLOG server port
The default is: 8421
Do not change the xmllog-server-port in this alpha version. It is fixed in fllog
to the 8421 address.
The fllog server must be running for fldigi to make the connection. I recommend
the following test sequence.
Start flllog and immediately close the program. That will create an fllog files
folder and an empty database.
On Linux / OS X: ~/.fllog/ ~/.fllog/fllog.prefs ~/.fllog/logbook.adif
~/.fllog/status_log.txt
On XP: C:\Documents and Settings\<username>\fllog.files with the same three
files
On Vista: C:\Users\<username>\fllog.files with the same three files
Copy your current logbook file to this folder and name it logbook.adif. (.adi on
Windows)
Restart fllog ... you should now be able to browse your logbook etc.
Start fldigi-3.22.0AB and select the remote logbook:
Access to the internal fldigi logbook is not available when using the server
logbook.
If the logbook server was successfully connected then the "Connect to server"
menu item remains checked. Remember that the server must be running and
accessible either via localhost or over the LAN.
If you want fldigi to always start with access to the logbook server simply save
the configuration "Config / Save config".
Fldigi will default to the internal logbook if at any time the connection to the
server is terminated or not available at start.
OK, all up and running? Try entering a known logbook entry CALL into fldigi's
QSO entry panel. The call data should populate in fldigi. At the same time fllog
browser should point to the found CALL and the data entry controls in fllog will
be populated with the record data.
I'm hoping a few of you might be able to use this during the forthcoming Field
Day.
73, Dave, W1HKJ
Built from source Ubuntu 10.04.
Works like a charm. Sorry no way to test across the LAN.
Ed W3NR
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
