AZ-GTi Mount does not slew when plate solving

[admin]

Thanks for taking the time to do that - the more messages they get, the more likely it is to get fixed

cheers,

Robin

[Antonio]

New Skywatcher app... maybe... I can't try it this night but..

https://inter-static.skywatcher.com/dow ... ws_244.zip

[Antonio]

Now aviable 2.4.5. From original site:

"## 2023-09-02 v2.4.5
Changes compared to v2.3.9
• Serial: will try to upgrade to 921600. If failed will try 115200
• User object: fix not able to add while disconnected
• Re-enabled PAE, where were disabled from 2.3.4 to 2.3.9
• Replaced "Align with Sync" page with "Sync samples" page.
• Multi-star alignment, where performing any of the following adds a sync sample:
• Using one of the alignment methods from the Alignment page
• Centering on a celestial object at the prompt after any catalog object GOTO
• Receiving a `SyncTo` command from ASCOM with a plate-solving software"

[luca857]

Thanks. Using this version (2.4.5) of the SynScan app the Sync feature seems to be working!

[procyon12]

Hi,

After installing the latest versions (synscanpro_windows_245, synscan_app_ascom_driver_140 - to be safe I set the ascom driver readout time from the default 800 ms to 1500 ms) under W10-64, ascom hub, indoor testing worked with AZ-GTi (latest firmware) and a 10" Flextube Skywatcher dobson. Also a 3h test with the Flextube under the sky worked (unfortunately, it was not SC , but a DVTI+CAM-430, which has its own control programme - but I got a positive 0.6 sec occultation of a 8 km asteroid ...).

Christian

[StarGazerUk]

Hi,

After installing the latest versions (synscanpro_windows_245, synscan_app_ascom_driver_140 - to be safe I set the ascom driver readout time from the default 800 ms to 1500 ms) under W10-64, ascom hub, indoor testing worked with AZ-GTi (latest firmware) and a 10" Flextube Skywatcher dobson. Also a 3h test with the Flextube under the sky worked (unfortunately, it was not SC , but a DVTI+CAM-430, which has its own control programme - but I got a positive 0.6 sec occultation of a 8 km asteroid ...).

Christian

Hi Christian,
I am trying to connect my mount via wifi to sharpcap via synscan app. I too have installed synscan pro 2.4.5 (windows 10 laptop) and synscan app ascom driver 1.4.0 but I cannot get the ascom to connect to synscan. Please can you tell me what settings you use in the ascom telescope chooser properties. I have the IP set to 127.0.0.1 but the remote port I can't seem to find any mention of by anyone else, I have tried 11881, 11882 and 10001, none work.

Thanks

[luca857]

Hi StarGazerUk,

let me chime in here. The setup that works for me (sort of, see below) is to select the SynScan App Driver in ASCOM and using port 11881 in properties. See screenshots below. Of course, I didn’t touch the default settings in the SynScan App where, if I’m not mistaken, you could also specify different ports. For me this configuration works with SynScan App 2.3.3 and ASCOM driver 1.4.0.

Unfortunately, the very same configuration does not work (for me) using the latest SynScan app (2.4.5), which is also the one that fixed the “slew after solve” functionality. You can try to do the following to see whether we’re having the same issue: After you’ve configured everything as described above, in the ASCOM hub select “View Activity Log” from the Tools menu, then select “Telescope” among devices (top row) as well as “Other activity” (bottom row). Keep the log window open and try to connect (SynScan App must be running of course). I get a “Telescope Connection Error” and the log shows a very low level kind of error (System.InvalidCastException).

I’m not sure whether this error is due to a messy configuration of my laptop (I’ve upgraded/reinstalled many things…), or if it’s been introduced in the recently updated SynScan App and/or SynScan ASCOM driver. When I reported success in using “slew after solve” functionality (few posts above) I was using an older version of the ASCOM diver (1.3.9), but I haven’t managed to downgrade to it.

Regards,
Luca

[StarGazerUk]

Hi Luca,

Thankyou for the info. I have installed an older version of the synscan app version 1.19.20 which was provided further up this topic and it is working perfectly. I haven't tried plate solving with this setup yet though so I can't comment on the slew after solve function.

Thanks
Phil

[admin]

Hi,

if you have the full text of the 'InvalidCastException' error somewhere then please do share it - it might just point in the direction of what is going wrong and if anything can be done to fix it.

cheers,

Robin

[luca857]

Hi Robin,

below is the full log showing the error I get when I try to connect the ASCOM hub to the Synscan App 2.4.5 using the SkyWatcher ASCOM driver 1.4.0. My impression is that the problem is either within the SynScan app or the ASCOM driver. For sure it's unrelated to SharpCap (which isn't even running when I try this connection), nonetheless I would be interested to know whether this error can be reproduced by others or if I'm the only one affected.

Thanks.

Luca

Code: Select all

15:28:56.863: Telescope - Others:       Get Connected flag - False
15:28:56.879: Telescope - Others:       Set Connected flag -> True (connected)
15:29:00.062: Telescope - Others:       Connection took 0 milliseconds.
15:29:00.062: Telescope - Others:       Get Connected flag - True
15:29:01.229: Telescope - Others:       Attempting to initialize telescope operation caught an unhandled exception. Details follow:
15:29:01.246: Telescope - Others:       System.InvalidCastException: At least one element in the source array could not be cast down to the destination array type.
   at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
   at System.Collections.ArrayList.ToArray(Type type)
   at ASCOM.DeviceHub.TelescopeParameters..ctor(TelescopeManager mgr) in C:\ASCOM Build\Export\Drivers and Simulators\ASCOM Device Hub\DeviceHub\Business Object Classes\Telescope Classes\TelescopeParameters.cs:line 37
   at ASCOM.DeviceHub.TelescopeManager.ReadInitialTelescopeDataTask() in C:\ASCOM Build\Export\Drivers and Simulators\ASCOM Device Hub\DeviceHub\DeviceManagers\TelescopeManager.cs:line 992
   at ASCOM.DeviceHub.TelescopeManager.<Connect>b__234_0() in C:\ASCOM Build\Export\Drivers and Simulators\ASCOM Device Hub\DeviceHub\DeviceManagers\TelescopeManager.cs:line 220
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
15:29:01.246: Telescope - Others:       Set Connected flag -> False (disconnected)
15:29:01.762: Telescope - Others:       Disconnection took 0 milliseconds.
15:29:01.829: Telescope - Others:       Get Connected flag - 
15:29:01.829: Telescope - Others:       Get Connected flag -