StarChaser 4

Great, thanks Colin
The DLVersion script only runs if you include the path to it, even if you are in the root where the file is located.
So I got:
Maxim DL 64bit 7.1.4.0
32bit dlapi: 3.0.0.0
32bit DLAPIWrapper: 2.8.0.0
32bit ASCOM Camera: 6.4.24.0
32bit ASCOM Guider: 6.4.24.0
32bit ASCOM FW: 6.4.23.0
64bit dlapi 4.0.2.0

thats it

 

Ok....ran the uninstaller...interesting how it would not remove the dlapi.dll because it was read only. I located the file and it was dated at some point in 2024. I removed the read attribute and all was well.
Went through the install order, reran the version ps1 file and now my installation matches your description. For a completely clean uninstall, I would suggest you develop the utility that clears out any registry entries too.

Everything connected ok in Maxim but the same error occurred in PHD2...clicking on the 'config' icon does nothing and if I press connect, PHD throws an error 'Could not create ASCOM camera object' Its almost as if the only thing PHD2 can 'see' is the 64bit driver....and that's what happened previously, so I had to install a 32bi driver, but that is installed now so that is odd.

Also, before I fixed up all of the right drivers, my earlier tests showed a dramatic reduction in the number random star jumps, but they are still there...about 1 or 2 every 60 seconds......and of course, the camera records that. See the attached pic, you can see the star tails.

Martin

 

I did rerun the DLversion script and the results are exactly as you described in the above post.

 

no change in PHD2 behaviour. I tried reinstalling the 32bit driver, but still it throws the same error “Could not create ASCOM camera object” I will look for the log.

 

Colin, both logs attached. In the PHD log it says something about CLSID.

 

Well, a new PC gets installed tomorrow, so I will see how it behaves then.
Meanwhile, as far as I can see there are 2 issues that remain a problem.
Calibration - being able to calibrate the mount and AO at the bin mode you intend to use them at.
guide star jumping around - while vastly reduced it would seem, it is still there and when it occurs images are unusableas the stars either have long trails or the image is populated with double stars.

 

These are completely random jumps, not induced by aggressive AO guiding.

 

Colin....brand new PC installed and this includes a fresh installation of all the DL programs in the order specified.

In PHD2 I can now click on the configuration button for the SC4 (DL Imaging (ASCOM) and it brings up the dialogue and I can now see the camera. However, when I click on ok, it throws 'Unhandled exception has occurred......The given key was not present in the dictionary."

Random star jumps continue.

 

Doug,

It is not my intention to hijack this post, but the AOX twitch phenomena has been reported in several posts over the past few months. My own is here: https://forum.diffractionlimited.com/posts/61148/ which describes experiments that largely eliminate possible mechanical explanations, although never entirely.
With regards to AOX settings, the file below is a video of AOX tracking with Aggressiveness and Max Move set to 1. There is no discernible difference in the twitch w/r/t other more aggressive settings.

https://1drv.ms/v/c/fad37fcb1da1ebec/ERZRLoTbigVLuvC9oDRyfaQBWnzvtt4z9Rge8Uygt078VA?e=bIu1V0

 

Thank you for hijacking, seriously!!! I am grateful you did because this problem has existed from the beginning and I bet you are not using the same hardware as I am in terms of the mount etc. So DL still need to fix this along with the calibration problem.

Alas, your link does not open, so perhaps you could repost that somehow as I would love to see it.

 

Drat. Here's another try at the file link: https://1drv.ms/v/c/fad37fcb1da1ebec/ERZRLoTbigVLuvC9oDRyfaQBWnzvtt4z9Rge8Uygt078VA?e=r0yaHl

 

Thanks for reposting. Got it now and that is exactly what I see....what mount and other hardware? I am L600 mount, Moravian C3-61000, FW, SC4, AOX. Camera directly connected to an Intel 13th Gen i9 PC with 64GB RAM and mount is also directly connected via USB.