Plate solve error with new driver Ioptron CEM120

[admin]

Hi,

I wonder if it might be that SharpCap is using ASCOM 6.5 when I create the software and somehow ASCOM 6.6 is slightly incompatible? I am going to try updating to see if that helps.

This is definitely a weird one!

cheers,

Robin

[Astrogarage]

Hello Robin,

it would be great, if you fix this bug.
Its also happening with the new CEM70 drivers.
If you will need some further informations on the bug, then don´t hesitate to ask for log files.

Greetings
Peter

[admin]

Hi Peter,

please try tomorrow's update when it comes out - I have updated SharpCap to take account of ASCOM Platform 6.6, which might just help.

Otherwise I might be needing to test with an iOptron mount - does the new 'problem' version work with all of their mounts?

cheers,

Robin

[Astrogarage]

Hi Robin,

as mentioned before, i think its the new update from May.
___
Releasenotes
2022-05-10
8.00

Major update!

New features:
Added support for HEM27, HEM27-EC and SkyHunter.
Added 2 decimal digits for coordinates. (Future firmware updates are required)
Added support for ASCOM platform 6.6.

Improvements:
Rebuilt communication between iOptron Commander and ASCOM driver from scratch.
______

I have a new astro-PC now, so I wanted to use the newest versions. I think on old Notebook with 7.0, everything would still work.
Tomorrow it should be clear an I will try the new SharpCap version and report my results.
Thank you for your quick response.

Greetings
Peter

[Menno555]

.... - does the new 'problem' version work with all of their mounts?

cheers,

Robin

Hi Robin.

No. It looks like the problem version is Commander 8 and that is for CEM120, CEM70, CEM40, CEM26, GEM45, GEM28, HEM27 and SkyHunter.
Other mounts like my CEM25EC use Commander 5.9.0.2 and that is working like usual.

[admin]

Let's hope the ASCOM update helps then, all of those look expensive!!

cheers,

Robin

[Astrogarage]

Hi Robin,
just came back from observatory.
The update did not fix the problems.
In the Telescopsection, I am still getting coordinates like 2147483648:-2 in every line. Some with +, +-, -- sign.

If you need further information, just ask.

Greetings
Peter

[Menno555]

Hi Robin

I don't know if you have already received a SharpCap log file from one of the users who are having trouble with the latest Ioptron driver with Commander 8.0 software?
Just in case, here is my log file for comparison. I have the Ioptron CEM25EC with it's latest drivers and Commander 5.90 and with that, everything is working fine. It too has the 2 decimals added but that is causing no problems.
Hope it helps a bit.

Menno

Log_2022-07-08T01_03_18-10056.zip

(31.61 KiB) Downloaded 32 times

[admin]

Hi folks,

thanks for the reports on testing this. Shame the ASCOM update did not help

Please could someone with the problem try the following

1) Make sure they have the very latest ASCOM platform (6.6sp1 I think) installed - please update if you are out of date and test again
2) Set up SharpCap to talk to the mount via the ASCOM Device hub - that is select 'Device Hub Telescope' in SharpCap, then press 'Properties' and choose the iOptron drive inside the device hub. Test to see if that configuration works.
3) If there are still issues in device hub mode, please turn on 'Driver Trace Enabled' in the ASCOM Device Hub Setup, then test again - this should create an ASCOM log file which records all the communication from the ASCOM side, which will be an interesting contrast to the log showing the data as seen from the SharpCap side. The ASCOM log file will end up in a logs folder inside an 'ASCOM' folder inside your 'Documents' folder.

cheers,

Robin

[Astrogarage]

Hi Robin,

thank you for your tips.
When doing everything with ASCOM Hub, as you described, its working again.
The position coordinates of the telescope are looking fine in SC.

I think its a nice quick solution.
Thank you for your help

Greetings
Peter