#FLDIGI HELP PC#

0 disables, 1-20 means timer rounds until drop. But as it may affect also (in slow PCs) fldigi started by cqrlog it can be changed. Parameter 'Drop after SyncErr >' automates remote mode closing when fldigi is closed.

#FLDIGI HELP PC#

If you use fldigi on other PC remember to open firewall at fldigi-PC side for TCP traffic to port 7362 from your local network. There is no IP address validation, so you have to type correctly formatted If you have fldigi running on other PC put here the IP address of fldigi-PC. Port number should be ok, but IP address may change depending your needs.Īddress is normally 127.0.0.1 (localhost) if you run fldigi on same PC than cqrlog. Selection to use XmlRpC.With selection you can choose “the old way” for fldigi remote, or the XmlRpc way. Port and Address for fldigi network connection and In cqrlog’s preferences/fldigi/wsjt interface there are some new settings.

WiFi, wired, or even internet(when you should use openVPN to make secured tunnel between sites) Settings You get qrz/HamQth data immediately after adding call to fldigi’s call field You see qso before/dxcc statistics from cqrlog before firing TX the first time You can run fldigi on other computer than cqrlog if they have common network. You get qso saved to cqrlog and fldigi entry is cleared, but not saved. Press “Save this qso” on cqrlog XmlRpc form. Press “save qso” on cqrlog’s NewQSO form and press save on fldigi. This leads to situation where fldigi logging can not be used to act like indicator to cqrlog to save qso and saving must be done by operator on cqrlogs side. Because of this cqrlog can not know if “save to log” button is pressed at fldigi because it tells it’s information only With XmlRpc cqrlog acts as client what is opposite way compared to wsjt-x remote where cqrlog acts like XmlRpc remote connection to fldigi is an alternative way to transfer qso data to cqrlog.

Fldigi help