LRotor, a program for turning a rotor, gets heading information from RUMLogNG and classic RUMLog, using an Applescript application.
V2.0 of LRotor is now scriptable, it no longer uses GUI scripting. This should result in smoother, more reliable operation, with no configuration issues for users.
Thanks to Tom for making the logs scriptable, and for his assistance with scripting for LRotor.
More information and download at: http://nf4l.com/rotor/
73, Mike NF4L
Rotor control update
Rotor control update
73, Mike NF4L
Re: Rotor control update
Hi Mike,
Would be nice integrate the rotator control in to Rumlogng ....I mean do settings on Rumlogng and do not run as a separate app
But anyway thank you Mike for the great job!
Would be nice integrate the rotator control in to Rumlogng ....I mean do settings on Rumlogng and do not run as a separate app
But anyway thank you Mike for the great job!
Re: Rotor control update
Will RLog work with a DCU-2?
Marv wa2bfw
Marv wa2bfw
Re: Rotor control update
For those who want to roll their own Rotator control this is what I do...
To get the current station, I have modified and made much smaller the RumLonNG2LRotor to 2 lines of AppleScript.
If you want to get this from a bash prompt then the general way is like this
You can then call as pass the heading as a parameter to whatever control program you want.
If (like me) you have your own Rotor Control program (in Python) - then this needs to work from Python.... So the code to get the heading is like this.
I hope that helps if anyone is trying to do this for themselves.
73s de Tim, A45WG
To get the current station, I have modified and made much smaller the RumLonNG2LRotor to 2 lines of AppleScript.
If you want to get this from a bash prompt then the general way is like this
Code: Select all
#!/bin/bash
heading=$(/usr/bin/osascript << EOT
tell application "RUMlogNG"
return headingToCountry
end
EOT)
if [ $? -eq 0 ]
then
echo "Heading is $heading"
else
echo "No sure About the heading"
fi
If (like me) you have your own Rotor Control program (in Python) - then this needs to work from Python.... So the code to get the heading is like this.
Code: Select all
#!/usr/bin/python3
import subprocess
script = '''tell application "RUMlogNG"
return headingToCountry
end tell
'''
proc = subprocess.Popen(['osascript', '-'],
stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
stdout_output = proc.communicate(script.encode('utf-8'))[0]
heading=int(stdout_output)
print(str.format('Heading is {} Object Type is {}',heading,type(proc)))
73s de Tim, A45WG
Re: Rotor control update
Hi guys,
I was looking to ask Mike NF4L a request on his LROTOR scripts he made.... but when searching in QRZ.com for his name.... It is indicated "Silent Key SK"!!
I am really sad to find this bad news today...... He done an excellent job to support rotor control with RUMlogNG.
What will be next now ??? I was looking a way to ask to add the support for the Green Heron RT-21 rotor controller.... Actually, it is working if I select "DCU-1" protocol. But I unfortunately I cannot see the actual rotor heading in the application window. But I can drive the rotor with the script, but without the actual direction displayed in the application window.
Any idea how I can resolve this??
73
Jeff | VA2SS
I was looking to ask Mike NF4L a request on his LROTOR scripts he made.... but when searching in QRZ.com for his name.... It is indicated "Silent Key SK"!!
I am really sad to find this bad news today...... He done an excellent job to support rotor control with RUMlogNG.
What will be next now ??? I was looking a way to ask to add the support for the Green Heron RT-21 rotor controller.... Actually, it is working if I select "DCU-1" protocol. But I unfortunately I cannot see the actual rotor heading in the application window. But I can drive the rotor with the script, but without the actual direction displayed in the application window.
Any idea how I can resolve this??
73
Jeff | VA2SS
NF4L wrote:LRotor, a program for turning a rotor, gets heading information from RUMLogNG and classic RUMLog, using an Applescript application. V2.0 of LRotor is now scriptable, it no longer uses GUI scripting. This should result in smoother, more reliable operation, with no configuration issues for users. Thanks to Tom for making the logs scriptable, and for his assistance with scripting for LRotor.
More information and download at: http://nf4l.com/rotor/
73, Mike NF4L
Re: Rotor control update
also would so nice completely integrate in to Rumlogng.... full package
-
- Posts: 7
- Joined: Wed 7. Jan 2009, 14:12
Re: Rotor control update
No reply from NF4L, email is bounced...
I was about to ask for more info on using a HyGain DCU-3x with RumLogNG :
My HamIV gave up after 36 years of good service and a new one is thus needed.
If I cannot obtain info very soon (winter is coming...) it wil be a HamIV with manual control...
No problem with that, but it was a good occasion to improve the station hi.
tnx for any news out of the group.
73 de Louis ON5EN
I was about to ask for more info on using a HyGain DCU-3x with RumLogNG :
My HamIV gave up after 36 years of good service and a new one is thus needed.
If I cannot obtain info very soon (winter is coming...) it wil be a HamIV with manual control...
No problem with that, but it was a good occasion to improve the station hi.
tnx for any news out of the group.
73 de Louis ON5EN