Hi Folks,
Playing with PstRotatorAz for a remote connection. I have it working from two Windows PCs. to two Windows PCs. That part is easy. I wanted to see if I could get it to work with CQRLog to a Windows PC. I have messed with the al of the addresses, but no success. Can it be done, has anyone here done it?
Also, is there a to have some of the setting set? I know one of the is auto/manual. I see there is a way to set limits. Have not figured that out yet either.
Any extra help would be awesome!
WC2L
Hi!
At least Hamlib 4.7 rotctld lists model #3 as "YO3DMU PSTRotator". That means Cqrlog supports it if Hamlib used supports it.
If you can find it from Cqrlog's rot model selector then your Hamlib rotctld should support it.
"Host" is localhost, "Port" is 4533, "Run rotctld when program starts" is checked. That starts the rotctld at Cqrlog PC side.
Then rotctld needs to connect your remote PST.
In rotctld man page it is not clearly stated, but I would try same "Device" setting as TCP connected rigs. I.E put your remote PST IP address to "Device" column.
I would also try to put the port number with it although it is not clear stated in rotctld man pages.
I.E XXX.XXX.XXX.XXX:4001 where XXX is the Ip address of remote PST.
It might be that that the ":4001" suffix is not needed and rotctld uses always port 4001 as default. But that you can find by testing with plain IP address and then IP address with Port separated with ":"
PST manual says you need two PSTs one for remote and and one for local. I believe Hamlib rotctld with rot model #3 can replace the local PST
I can not test that, but I would start testing from this point if I had a PST to test with.
Then the limits.
Consult Cqrlog and rigctld manuals for that.
You have to fill the "Extra command line arguments" to have something like:
--set-conf=min_az=10,max_az=355
with numbers replaced by your rotor limits.
That would be a good starting point. AI is a good tool for finding information, but unfortunately it might totally mislead you as well.
--
Saku
OH1KH
Sorry for the very slow reply. I had major surgery after I sent the message. I have not had time till tonight. I have not been successful via the CQRLog GUI. I thought I could make it work or communicate via CLI.
PSTRotator is running on 172.25.35.40
I did see a reference to this: The Default Protocol is intended primarily for the communication between Hamlib library functions and rotctld (“NET rotctl”, available using rotator model ‘2’).
I will keep poking around. Thought this would be easier ;-)
Will WC2L
Hi Will!
If you have tried this:
Have you noticed to start the TCP server at PST computer side?
Have you opened Windows firewall to pass communication from Debian pc 172.25.35.40 to WIndows pc port 4001 ?
Both must be set to get TCP communication work.
In case PST's TCP remote supports Hamlib commands directly you can try:
Also in this case you have to ensure that PST's TCP server is started using port 4001
and that Windows firewall enables TCP communication from Debian pc 172.25.35.40 to WIndows pc port 4001
After you get connected and rotator moves it is time to try the "Extra command line arguments" to limit rotator turning.
I just do not believe it is necessary if the limits have been set at Windows PST. Then it should not let remote connection
to drive over limits.
--
Saku
OH1KH
No joy or happiness in those examples.
I will have to get the correct command line to see if that works. At this point not sure what is going on.
Will WC2L
I did a little testing. Not sure if the rotctl is what is actually listening, Here are the commands tried
rotctl -m 2 -r 172.25.35.40 -t 4001
No replies, blinking cursor. p does not work
rotctl -m 3 -r 172.25.35.40 -t 4001 -v
Opened rot model 3, 'PstRotator'
Rotator command: p
rotctl_parse: input_line: p
Azimuth: 0.00
Elevation: 0.00
Rotator command:
Please suggest better things to try.
Will WC2L
I was told that you need to run PstRotator.exe not PstRotatorAz.exe. AZ does not have Hamlib support.
I have installed PstRotator.exe. This has not helped with the problem. I did it with both of your suggestions.
Any other suggestions?
Hi Will!
Unfortunately there are no Windozes in house so I can not test any setup variations.
Pst does not run under Wine/Linux.
But if there is YO3DMU Pst rotator support in rotctld rotator list it must work with some kind of setup.
Keeping that in mind I created a emulation setup and found out that Hamlib rotctld supports PST UDP-interface:
At left I have started rotctld from console. Then I have connectted to rotctld with Telnet connection (localhost:4533)
At right I have UDP server program that emulates PST UDP interface using port 12000.
When AZ and EL are given from telnet with "PAZ EL" command same appears to rightmost UDPserver using PST XML format.
So my next suggestion is:
Using that setting I can see in mu UDP server emulator that Cqrlog is polling it and if I define AZ to go it sends it to UDP:
So:
Check that the UDP interface is enabled and uses port 12000 at PST side.
Then try Cqrlog rotctl settings above picture.
Replace address 127.0.0.1:12000 in my test config with your Windows IP address 172.25.35.40:12000
Check that WIndows firewall will allow UDP datagrams from the Cqrlog-Pc's Ip address.
Please tell did you get any success !
--
Saku
OH1KH
No reason to apologize for NO Windows. I still have to support others under Windows. I'm slowly moving more and more to Linux.
enabling UDP and setting the rotor control does display the beam heading.
There is no directional stuff happening. Moving right or left does nothing.
There is no way to manually set the beam heading.
I can telnet to port 4533, If I send P: 45, 0
The rotor will move to 45. So that works.
I'm guessing some stuff is missing. Not sure what or ??
Is there more we need to add to the extra command set??
I know we also need to address the 180 to 180 turning.