Using with Indi

[Jon Garrod]

Hi All

Build is complete and works perfectly. I have connected it up to Ekos using Indi. I have selected the Mooonlite focuser. Under Ekos the Moonlite only has 2 Steping options, full and half. Will Ekos override the controller setting as I am using 1/4 step?

Cheers

Rishi

[Jon Garrod]

Just checked it out using the Windows test program and the Indi Moonlight driver does set the step mode. I hope I can modify the Moonligh Indi driver to add 1/4 stepping mode.

[brownrb]

Hi
If you are only ever using 1/4 then I would recommend setting this in the firmware and then prevent any vcall to setting the step mode. That way it will not be over-written

You should only ever set the step mode once - during setup - you would have calculated what the should be as part of the focuser basics - firs tpart of the manual in determining your focuser setup

I have never had any occassion to change my step mode once initialised.

Regards
Robert

[Jon Garrod]

Hi Rob

Do you mean make a change in the the large switch statement to disable?
case: 18003 and case 18515 seems to be the commands that will typically be send to a Moonlight focusser. If I simply replace these with a break statement will that stop the Indi driver setting it?

Is Case: 21311 just used by the Windows test program? If so I assume I can leave that one active which would be my preference.

I do have one other option. I am currently using a Nema17 PG5 but I also have a PG15. I could run the 15 at Full step although it does not have such an accurate gearbox as the PG5.
Are there any advantages to running at Full step (except being able to switch off coil power when idle).

Cheers

Rishi

[brownrb]

Hi Jon

// set the microstepping mode for DRV8825
void setstepmode( byte stepmode)
{
// quarter step
digitalWrite(DRV8825M0, 0);
digitalWrite(DRV8825M1, 1);
digitalWrite(DRV8825M2, 0);
}

Full-step has more torque and alsomore accurate positioning,

[Jon Garrod]

Thanks. decided to hook up the PG14 instead. Now running on Full Step with the option of going half step if I want more resolution. Works great. I do get an error message when running from Ekos.
2019-03-03T20:56:24: [INFO] Focuser reached requested position.
2019-03-03T20:56:24: [ERROR] Unknown error: isMoving value (1#)
2019-03-03T20:56:24: [INFO] Focuser is moving to position 1000

It doesn't seem to effect the functioning. Any idea what is expected?

[brownrb]

It might be caused by recent 175 changes as this has not been reported before
I would try changing this
case 18759 : // :GI# motor is moving - 1 if moving, 0 otherwise
replystr = String(isMoving) + "#";
sendresponsestr(replystr);
break;

 to
     case 18759 : // :GI# motor is moving - 1 if moving, 0 otherwise
 if( isMoving == 0 )
     replystr = "00#";
     else replystr = "01#";
  sendresponsestr(replystr);
  break;

  then reprogramming and run the tests again to see the reported ERROR occurs

  Regards
  Robert

[Jon Garrod]

Hi Rob

Thanks, that did it. No error messages anymore. As far as I can make out it works perfectly in Ekos. Now I need clear skies to try it out in anger. Thank for all your help.

Cheers

Rishi

[brownrb]

Thanks for the feedback Rishi, much appreciated