Fldigixml archive 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 You could also try something like VARA Chat, or VarAC.XmlRpc remote connection to fldigi is an alternative way to transfer qso data to cqrlog. I'd suggest working with a known reachable station on voice, then switching to VARA, so you know it's not some other issue. I always use 10, and some stations reply on try 9 regularly) and getting zero response, it would probably be really helpful if you could attempt a direct VARA connection to another station, without Winlink in the mix, to see if that works properly. If you're just sending out the 10 requests (or whatever you have it set to.
Understanding the issue might help with the resolution. That was with the FT-857, and I can't recall now what setting made it work.
Fldigixml archive windows#
My Windows audio Speaker/Line are both set to 0.0dB (full to the right) for Winlink.Where is your Drive Level set in VARA Settings>SoundCard? Should probably be default -5dB.This is an area worth experimenting with: Windows audio wasn't talked about enough in the doc. Set your RF POWER where you want, check your PO meter.
Make sure your antenna is tuned and your SWR is low.(re the previous line: not everyone does it this way though, I know some that use AMP1 and AGC=ON, RF Gain knob at 100%.).I have my ATT=OFF, IPO=IPO, AGC=OFF, I use my RF gain knob to keep the "Audio Input" needle in VARA in the green.Some things the document doesn't mention: I don't think these difference are causing your issue, digital modes do have some flexibility. Also, I reduce my bandwidth to 2400Hz to fit closer to the red lines in 2300, but that's habit more than anything else and just adds work. Mine differ in that I have AMC set to 50, and RPORT GAIN set to 10. That said, the doc does cover most settings. What it misses is the "PRESET" button (firmware dependent I think), which works quite well for FT8/JS8Call, and for VARA as well. I'm not an expert by any stretch, but I've got it working fine on the FTdx10. For what it's worth, I use Winlink daily (usually just once a day, sometimes more) with stations all over the country, on 80m, 40m, and 20m depending on the time of day.
0 kommentar(er)
