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