×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

indi_getprop mount busy or not

  • Posts: 314
  • Thank you received: 34
Hi
Inspired by EQASCOM's Polaris Alignment Tool I currently write my own one (c++ qt very-noob beginner project...) that talks to an indiserver.
At step 2 I want the mount to go to the home position and unpark.


My current code simply sends the two commands for park and unpark.

void AlignmentDialog::slewHome()	// Park to Home and unpark
{
	QString program = "/usr/bin/indi_setprop";
	QStringList arguments;
	arguments << "-h" << ui->lineEdit->text() << "EQMod Mount.TELESCOPE_PARK.PARK=On";
	QProcess *myProcess = new QProcess(this);
	myProcess->start(program, arguments);
	myProcess->waitForFinished();
	arguments.clear();
	arguments << "-h" << ui->lineEdit->text() << "EQMod Mount.TELESCOPE_PARK.UNPARK=On";
	myProcess->start(program, arguments);
	myProcess->waitForFinished();
}

The problem with that is the mount tries to park and moves very short and then stops. I guess I have to add some check
for the mount being busy while moving to the park position and then issue the unpark command.
Does someone know which value from indi_getprop I can use for that?
The ones I found seem a bit strange to me because there are some busy even when the mount is not moving:
indi_getprop -h rp | grep STATUS
EQMod Mount.RASTATUS.RAInitialized=Ok
EQMod Mount.RASTATUS.RARunning=Busy
EQMod Mount.RASTATUS.RAGoto=Busy
EQMod Mount.RASTATUS.RAForward=Ok
EQMod Mount.RASTATUS.RAHighspeed=Busy
EQMod Mount.DESTATUS.DEInitialized=Ok
EQMod Mount.DESTATUS.DERunning=Busy
EQMod Mount.DESTATUS.DEGoto=Busy
EQMod Mount.DESTATUS.DEForward=Ok
EQMod Mount.DESTATUS.DEHighspeed=Busy
--= human, without Windows™ =--
pls excuse my bad english! :)
7 years 10 months ago #8858

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 34
It seems "Busy" means "Idle".
I will try to use EQMod Mount.DESTATUS.DEGoto / EQMod Mount.RASTATUS.RAGoto
--= human, without Windows™ =--
pls excuse my bad english! :)
Last edit: 7 years 10 months ago by pauledd.
7 years 10 months ago #8859

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 95

Replied by Oleg on topic indi_getprop mount busy or not

How can I try it?
You can try my open project Astronomy Linux
7 years 10 months ago #8860

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 34
you can get it here but it does not work as expected yet and the align routine is not added yet and its written to talk to "EQMod Mount" only. Use it at your own risk :pinch:
github.com/pauledd/polarisAlignmentTool
--= human, without Windows™ =--
pls excuse my bad english! :)
7 years 10 months ago #8861

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 95

Replied by Oleg on topic indi_getprop mount busy or not

I have the SW NEQ6 Pro SynScan and EQmod cable.
You can try my open project Astronomy Linux
7 years 10 months ago #8862

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 34
Please dont try it yet :whistle:
You could start indiserver with your mount and use "indi_getprop" to test if it communicates correctly and test some of the properties with "indi_setprop". My program does the same, in theory
--= human, without Windows™ =--
pls excuse my bad english! :)
7 years 10 months ago #8863

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 95

Replied by Oleg on topic indi_getprop mount busy or not

Ok.
You can try my open project Astronomy Linux
7 years 10 months ago #8864

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 95

Replied by Oleg on topic indi_getprop mount busy or not

It needs the images directory with *.png files
step1.png
step3.png
step4.png
step5.png
step6.png
You can try my open project Astronomy Linux
7 years 10 months ago #8878

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 34
should work now.

By the way and regarding the topic, I removed the function to park and unpark with one button. Instead I made separate buttons for that. Until I will try to find a way to check if the mount is busy or idle later one has to check visually if the park process has finished and because you already have to be next the mount to look through the polar scope.
--= human, without Windows™ =--
pls excuse my bad english! :)
7 years 10 months ago #8880

Please Log in or Create an account to join the conversation.

I wouldn't be using indi_getprop, but I can see how it can be easier than writing the program as an INDI client. What's the use case for this? On field setup for visual north hemisphere polar alignment? This assumes there is no hand set?
7 years 10 months ago #8886

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 34
If you have clear view to south you dont need this. Yes, its (in my case just north) pure visual alignment using polaris.
EQASCOM implemented this tool long ago eq-mod.sourceforge.net/docs/PolarScopeAlignment.pdf
I really need this because my telescope location only allows polaris alignment, I have no view to south.
I got quite good alignment results with this method.
--= human, without Windows™ =--
pls excuse my bad english! :)
7 years 10 months ago #8887

Please Log in or Create an account to join the conversation.

Ok quick read on that it seems it is useful for slewing the RA so you can quickly adjust Alt/Az knobs to center Polaris in the polar scope. Otherwise, you'd have to guesstimate the relative orientation of Polaris and then move the RA axis manually in order to center it, but it might be off. With this procedure, the RA drive rotates precisely.

But it seems your program is doing a simpler approach?
Last edit: 7 years 10 months ago by Jasem Mutlaq.
7 years 10 months ago #8888

Please Log in or Create an account to join the conversation.

Time to create page: 0.320 seconds