I use the latest nightly build. The dome still greyed out the first time I connect everything. But disconnect and reconnect it again individually solves the problem.

Read More...

Okay. So I updated the nightly to latest. And the mount is fixed immediately.
But the dome is still greyed out. I noticed that the dome status is Unknown (though it closed/parked, indi report this correctly before I go nightly). I disconnect the aldiroof driver and connect it again and the dome option is no longer greyed out and the dome status shown as parked closed as it should be.

Read More...

Oh okay. Let me update and try again. Thanks

Read More...

I am using nightly build and the dome/mount option is greyed out in scheduler tab. As a result, the scheduler does not run.
I am using Aldi roof and can control the roof/mount normaly in ekos. Am I doing something wrong?

Read More...

I believe you can set the guiding deviation under a threshold which the sequence starts (i.e: if the guiding RMS above 1 arcsec then the sequence won't start). See it in the capture tab.

Read More...

I ran into the same problem with the latest stable build (3.6.0 Stable) The guide scope appeared as primary scope but it does not suspend phd2 guiding.

Read More...

Hi Christian.
Did you found a solution to this? I ran into exactly the same problem with my qhy174 and qhy294 . The internal guider works for me but it's extremely limited in feature and I prefer phd2.

Read More...

Hello?
No one have the same problem?

Read More...

So I was using the iOptron CEM70 with INDI nightly build and the driver does not seems to report the pointing of the mount correctly when using PHD2 (PHD2 recalibrate everytime the mount slews, does not calculate the RA and DEC rate...)
PHD2 warned that the driver does not report pointing and I tried to add the AUX mount as INDI CEM70 and it still does not work.
Am I doing something wrong or it's a bug? I used a CEM25p and it shows the correct information but not the CEM70.
I connect the mount directly with my computer using the onboard usb port (not going through the hand controller)
Thanks!

Read More...

Okay so after testing the data line with the ascom driver (I copied your example above and paste it into a text file then change the values) it turns out the column is quite resilient to change in number of digits. I can simply add the minus sign to before the temperature without delete any space and the driver still reads the data. 

Read More...

Actually, in the GIT I posted, I think it's in the older Boltwood file format (there are the older V1) and the example you send in the link is the V2 file that haves a few more column, boltwood drivers usually have backward compatible of the V1 file.

Read More...

Hi Gene,
Thank so much for the help. I am not quite sure about how the boltwood file handles minus values. I think I'd try to make a file from your example and feed it into a boltwood file reader and see if it works. Again, thanks!

Read More...