I'm not the author of CCDciel but can run and modify the code in the compiler. The error is a OleException, divide by 0. See image. Any idea how to fix this and what change in the Ascom inteface could have caused this?
CCDciel ole exception.png
I'm not the author of CCDciel but can run and modify the code in the compiler. The error is a OleException, divide by 0. See image. Any idea how to fix this and what change in the Ascom inteface could have caused this?
CCDciel ole exception.png
Selecting the driver in the setup works without a problem for all drivers. The error occurs in the code on the moment AscomDriver. Connected Property is set true.
Tried driver 1.03.7. Similar behavior. If you first select camera SETUP to display the ZWO menu then the camera connects without problems. However if you CONNECT directly without using SETUP the exception error occurs. So calling the SETUP seems to set something in the driver which allows connecting.
I tried several thing like using ansistrings rather then unicodestrings for the driver name but nothing fixes the problem. The CCDciel software does nothing special. Create a CreateOleObject and set AscomDriver.Connected property as true.
C-language based programs connect without problems. I have tried ASCOM versions 6.2 and 6.3.
Han
yang wrote:You should configure the setup at first
Yes of course it is required to configure setup. This has been done.
The problem is that next time, the connection fails with division by zero. This can only be prevented by briefly selecting setup. The CCCciel program has no problem with other ASCOM drivers and has no problem with the 1.02.25 driver. Something in the ASCOM interface of the 1.03.x drivers makes it incompatible with CCDciel or better the COM unit of FPC compiler.
I hoped the programmer of the 1.0.3.x driver could give hint what has changed in the driver and if there is a way to solve this compatibility problem.
Han
Okay let me try again:
0) Install ZWO ascom driver 1.03.7
1) Install and run CCDciel imaging program.
2) Setup as camera ASI1600MM, run setup and set the camera parameters as required.
3) Connect all. (The camera will connect without problems, camera indication will turn green)
4) Stop the CCDciel program.
5) Restart the CCDciel program, connect all => This will result exception error divide by zero. The camera indication will not turn in green.
The problem in step 5) will not occur with ascom driver 1.02.25.
Can you reproduce this problem?
Regards, Han
Thank you very much!
It is a bug that we didn't test.
Please try this driver:
Thanks
chad
You have found quick a solution. Thank you!
The only thing Im' still hoping for is a solution for the older ASI1600 camera's to control the
"rolling shutter mode and the global shutter mode switch over."
The make my flats, I connect the camera with a USB2.0 extension rather then USB3.0 and expose at 4.99 seconds. See
http://zwoug.org/viewtopic.php?f=29&t=7267
I switch to force usb2.0 mode ?
Best regard, Han
Look at the response to that question.
If you really want to solve that problem, Please contact our customer services after 1600MM/MC-Pro come out.
Thanks
chad