Using 127.0.0.1 and tried default port and also 55555 on FLRIG and FLDIGI. FLDIGI works fine with audio but no connection to FLRIG server (frequency or PTT). But having troubles with the DDElibrary as its no longer being supported and trying to figure out some issues isn’t panning out well. FLRIG OK but not communicating with FLDIGI. Use the Drop-Down menu below to select your radio type.
Youtube fldigi windows 10#
This is a quick howto on installing FLDigi FLMsg and FLWrap on your windows 10 PC. The box is very compact at 80x40x20mm making it ideal to hide away behind the PC or transceiver using no desk space. Installing FLDigi and supporting software on your Windows 10 PC. The cables from the interface box to the transceiver is 0.6m. I have started re-writting the gateway in vb.net as windows 10 on my computer will no longer let me use the dll file that communicates with Fldigi. Cable length is 1.5m from the USB port on your PC to the interface box. Hopefully someday I can re-write things so it uses TCP messages but its not yet.
SO there could be a little delay depending on when the timer went off and when the gateway detects Fldigi has sent the TX’ing signal. the timer for keeping track of the tx/rx setting is set to 400ms there are 5 timers in all. But the gateway uses timers to keep tabs on changes made in Fldigi. I’m not sure what is causing the trasmit delay. SO there is a delay set to see if the frequency is the same as commander or if it didn’t come from commander is the frequency still being updated in Fldigi.
Because of the techniqe used in Fldigi I have no way of knowing if Fldigi changed frequency because A you actually changed the frequency or B you changed the frequency via commander. There is a delay built in when changing the radio in Fldigi.
0 kommentar(er)
