Page 1 of 1

Fldigi - RUMLogNG AppleScript modification

Posted: Sun 11. Oct 2015, 16:25
by K3DCW
For anyone who operates with Fldigi, you likely know there's an AppleScript that allows for logging from Fldigi direct to RUMlogNG. Instructions are available in the RUMlogNG online (http://dl2rum.de/RUMlogNG/docs/en/pages/FAQ.html) with further help at NF4L's site (http://nf4l.com/ngconfig/).

One thing not covered in this initial script is setting the power level in RUMlog. Working with Tom, he helped me identify a couple ways to do this.

The first and easiest (if you always use the same power level) is to simply place a value in the script in the "tell application "RUMlogNG" section. Simply add the following line:

set power to "100"

You can set the power to whatever your normal power level is. You can also use text, such as "high power", "mid power", "QRP", etc.


However, sometimes you'll need to adjust power levels on the fly depending upon the mode/station being worked/propagation conditions; oftentimes with different power levels between different QSOs. There is a way to set and save this value using AppleScript as well.

You'll need to add the follow text in the AppleScript BEFORE the "tell application "RUMlogNG"" section:

display dialog "Enter power level" default answer ""
set opPower to text returned of result

Then, in the "tell application "RUMlogNG"" section, you'll need to enter the following text:

set power to opPower

This will cause a dialog to pop up with each QSO you save, asking you for the current power. You can type anything; "100", "500", "5", "QRPP", "Low-Power" etc and that variable value will be saved in the RUMlogNG database as your power level.


I hope this is of use to someone.

73 de Dave

Re: Fldigi - RUMLogNG AppleScript modification

Posted: Sat 24. Dec 2016, 12:50
by EA3HOE
I think there is a need for a GOOD explanation on how to set up integration between RUMlogNG and Fldigi. I, at least, are still having trouble setting this up.

I have CAT working in RUMlogNG and RUMlogNG is supposed to send its info to Fldigi. But what do i set up in Fldigi to make it receive this info?
In RUMlogNG i have set Fldigi to be at 127.0.0.1:7373, but where do i set this in Fldigi?

XML-RPC, for me the most obvious one, doesn't work.
When i set it in flrig and press Reconnect, fldigi crashes.
RigCAT and HAMlib all use the physical interface, so that's a no-go as well.
Hardware PTT and GPIO are out of scope here.

So if anyone has this working i would really like to see some screenshots how fldigi and RUMlogNG are configured.

Do i sound frustrated? Maybe that's because i am.....

Ton EA3HOE.

Re: Fldigi - RUMLogNG AppleScript modification

Posted: Sat 24. Dec 2016, 13:08
by DL2RUM
Fldigi uses the port 7362 for xml-rpc!
Activate xml-rpc under the XML-RPC tab in the RIG configuration section.
Do not configure RigCAT, HAMlib, flrig or anything else in Fldigi.

There are to many options and different settings available. You should post your settings to find out more failures.

Re: Fldigi - RUMLogNG AppleScript modification

Posted: Sat 24. Dec 2016, 15:43
by EA3HOE
DL2RUM wrote:Fldigi uses the port 7362 for xml-rpc!
That was it!!

Thanks,

Ton.

Re: Fldigi - RUMLogNG AppleScript modification

Posted: Fri 9. Jul 2021, 13:35
by Carl
After participating in the DL-DX RTTY contest, I discovered that the old Applescript for transferring QSO info from FLDIGI to RUMlogNG didn't fill in fields in the contest log. However, with a little sleuthing in RUMlogNGs field names, I discovered that I could set most of those fields in the exchange by adding the following commands to the script.
	
        set c_callsign to qsoCallsign
	set c_frequency to qsoFrequency
	set c_rstRX to qsoRcvdRST

Unfortunately, I couldn't find any field name that allows setting the serial number in the contest log; perhaps Tom can add a definition for c_serialNumber in a future version.

For anyone not familiar with the script, I've attached the full script that I'm using for reference.

Enjoy,
Carl
WG1V

----
On a Mac (which I assume you have since this is an Applescript), this FldigiToRumlogNG.applescript goes in the folder ~/fldigi/scripts. You then bind the script to one of your FLDIGI buttons to log the QSO over to RUMlogNG.
set qsoCallsign to system attribute "FLDIGI_LOG_CALL"
set qsoFrequency to system attribute "FLDIGI_LOG_FREQUENCY"
set fldigiModemName to system attribute "FLDIGI_MODEM"
set qsoSentRST to system attribute "FLDIGI_LOG_RST_OUT"
set qsoRcvdRST to system attribute "FLDIGI_LOG_RST_IN"
set opName to system attribute "FLDIGI_LOG_NAME"
set opQth to system attribute "FLDIGI_LOG_QTH"
set opLocator to system attribute "FLDIGI_LOG_LOCATOR"
set qsoNote to system attribute "FLDIGI_LOG_NOTES"

tell application "RUMlogNG"
	clearFields
	if fldigiModemName = "BPSK31" then
		set mode to "PSK31"
	else if fldigiModemName = "BPSK63" then
		set mode to "PSK63"
	else if fldigiModemName = "BPSK63" then
		set mode to "PSK63"
	else if fldigiModemName = "BPSK125" then
		set mode to "PSK125"
	else if fldigiModemName = "BPSK500" then
		set mode to "PSK500"
	else if fldigiModemName = "BPSK1000" then
		set mode to "PSK1000"
	else
		set mode to fldigiModemName
	end if
	set callsign to qsoCallsign
	set c_callsign to qsoCallsign
	set frequency to qsoFrequency
	set c_frequency to qsoFrequency
	set rstTX to qsoSentRST
	set rstRX to qsoRcvdRST
	set c_rstRX to qsoRcvdRST
	set nick to opName
	set qth to opQth
	set locator to opLocator
	set note to qsoNote
	logQSO
end tell