4 replies to this topic

[genericnj]

I've had so many issues getting the gti to work for me that I just miss the simplicity of the 2i...

 

So... when i power on the mount in the home position and not touch the clutches after that, if i use the synscan app, it can slew to locations roughly. This is after doing multi star alignment etc.

 

Now, if i try to slew via CCDCiel it just goes all wrong places and i see the RA and Dec location reported by the indi driver is way off... I tried to plate solve and sync mount but all plate solves via ASTAP integration are failing - it seems that ASTAP wants a rough RA and Dec entered and the one being sent by CCDCiel is just way off. I tried to also manually use the indi driver control panel 'sync' tab to manually 'set' the coordinates, but it doesnt seem to change trhem since the same location keeps reflecting on the RA and Dec.

 

What am I doing wrong? how do i get this mount to know right location it is pointing to ? And why on earth does the mount keep two locations, one in the synscan app and one in the indi driver... so confusing...

[bmcclana]

I don’t know the INDI part… is it a mount controller talking directly to the motor controllers, or is it talking to the Synacan app?

If it is talking to the app, I don’t think I can help.

But if both it is talking to the motor controller AND the synacan app are talking to the motor controller, (one via serial and one via WIFI) that is the problem. You can only have 1 brain/model in control. If you try to use 2 they will disagree and cause this issues.

I.e I can have the Synscan app control the mount, but then if I try to control with a different controller like eqmod or green swamp server, the same thing happens.

But I can have multiple other software all talk to the synscan app via ASCOM and it is the only thing with a model and in control of all movement and sync’s. Every other piece of software just reads data or sends commands to this one central brain.

[bmcclana]

As a more fundamental answer, the mount isn’t keeping ANY locations…. That information is in the control software.

So the Synscan app has its own model that converts the motor positions to coordinates and the INDI driver has its own model that converts the motor positions to coordinates and the two don’t share information.

The mount only keeps track of the motor positions. You have to choose only one piece of software to be in charge and maintain the model.

[genericnj]

So when i connect to the mount via the synscan app and goto anywhere, it correctly goes to those locations. The pointing to location is correct in the app. But if I disconnect the app and try to connect via indi drivers using any software such as planetarium software or ccdciel, which i use for imaging, the indi driver reports back a completely different location from the mount. And if i go to any location it is completely off. The indi driver has a sync option to manually override the location the telescope is pointiung to, but when I attempt that it does not actually change the location, the mount retains the location it thought it is pointing at no matter what.

 

Software also has this capability, where you can goto then sync, meaning it goes to location, then plate solves and then syncs the actual location back to the mount driver, however the plate solve requires a 'rough idea' of where it is pointing to and because the mount has completely different coordinates in the driver, it fails the platesolve completely.

[bmcclana]

you shouldnt start from the app and switch to the driver.  that is confusing the whole situation.

 

 

when you goto in the app and then disconnect and connect the INDI driver, the location isnt transferred.  i know the sync function sometimes has limits on how far away from the current location it is allowed to be, or if it is outside slew limits, or if it results in an unsolveable model,  it can refuse them. 

 

if you wan tot use INDI, you should power on in home position, connect with INDI and run that way.  switching between control software is a recipe for this problem. 

 

same if you try to switch between the hand controller and a the app...its like trying to have two different brains control the same body without being able to talk with each other.