BYE won't connect to Ioptron cem25ec

[bradsheard@comcast.net]

Just upgraded to BYE 3.1.8 to try ASCOM dithering with Ioptron cem25ec, unguided. Laptop connects to mount fine, but BYE says incompatible driver and won't dither. Anyone have any ideas?

Thanks!

[bradsheard@comcast.net]

So I re-installed the ASCOM 6.2 platform, and am no longer getting the incompatible driver message!  It seems to be working on Windows XP now!

Thanks for all your help!

[s3igell]

Are you trying to use the Manual Dither or the "Standard" PHD2 Dither function??

 

Details and Log Files please...

[admin]

What is your dither configuration in the BYE's Settings?

[bradsheard@comcast.net]

Wow, thanks for fast response!

In settings menu, chose ASCOM as provider, aggressiveness as default 2, calm down default 10, every 1 image, rest is greed out

In ASCOM telescope menu, settings panel, selected IOptron telescope.net....this is when it has a pop up that says incompatible driver, then PEReader exception, please check ASCOM application event log for details

Working on getting log file into post....

Thanks!

[bradsheard@comcast.net]

Having trouble uploading log file, too big

[bradsheard@comcast.net]

Here is a truncated section of the log file, the whole thing was too big

logfile-20161112-19h25m28s750-3508-2016-11-12 copy.txt

[s3igell]

In settings menu, chose ASCOM as provider, aggressiveness as default 2, calm down default 10, every 1 image, rest is greed out

This section of your effort is "BYE".  The rest is actually ASCOM Code and Configuration Dialogs...

 

In ASCOM telescope menu, settings panel, selected IOptron telescope.net....this is when it has a pop up that says incompatible driver, then PEReader exception, please check ASCOM application event log for details

These elements are fully the Code and Dialogs generated by ASCOM code - a totally different group of Developers and Supporters than Guylain and BackyardEOS/NIKON.

You will likely need to get the ASCOM Support Group to weigh-in on these issues.  

Else you may want to look to the iOptron Support Group, as they surely have direct experience with Connecting their iOptron Gear to ASCOM Drivers.

 

Here is a truncated section of the log file, the whole thing was too big

You'll likely want to Upload the larger Log file to a Cloud Site such as Dropbox or OneDrive, and then share with Guylain.  But only Guylain can interpret the Details contained within...

[admin]

Sorry, truncated log files are not useful.  I'm missing the whole story and I can not effectively debug.

 

In fact, the truncated log file you posted has no evidence that you ever attempted to connect the telescope in the first place.

 

Are you able to connect the telescope with the iOptron software?

 

Are you able to connect the telescope to another ASCOM compliant software?  Are you using planetarium such as Cart du Ciel?  If yes does it connect to it.

[astroman133]

I believe that the PEReader error is caused by changes that Microsoft made in Windows 10. You should upgrade ASCOM to version 6.2 to fix this error.

[bradsheard@comcast.net]

Thanks folks, appreciate your feedback.

So, I was trying to do this on a laptop running windows xp.

I have been able to connect the laptop to the Ioptron commander using ASCOM on the same computer, and this successfully controls the mount, slews fine etc. I'm pretty sure I am running ASCOM 6.2.

I will do a short run today just trying to connect to the telescope, camera etc and upload that log.

Thanks again for your help!

[bradsheard@comcast.net]

here is a new log just trying to connect the mount and camera, taking a few pictures....

Thanks!

logfile-20161113-11h48m08s906-1344-2016-11-13.txt

[astroman133]

So, is this on the XP system where everything works? or on the Windows 10 system where it is broken?

[bradsheard@comcast.net]

Update, I tried the same thing with a different laptop running windows 10....It connects fine to mount and dithers (although a lot, have to play with settings)

so, it seems to be a problem with windows xp or the drivers I have on that loptop

[astroman133]

Is this BYE 3.1.8 that you are dithering with? There were some fairly recent changes to the dither aggressiveness.

[bradsheard@comcast.net]

yes, 3.1.8

[admin]

Set the aggressiveness to 1.  This is what I use with my mount and this is usually sufficient.

 

If this is still to much and can probably add another parameter to reduce it even more.

 

Regards,

[astroman133]

How big is the change that dithering is making? I believe that conventional wisdom for a camera with a Bayer matrix is to dither enough that hot pixels will not affect the same de-Bayered pixel in successive exposures.

[admin]

I looked at the new log files and this issue is ASCOM it seems.  BYE does not even get a selected telescope from the ASCOM chooser.

 

Is your XP a 32 bits or 64 bits?

 

If it is 64 bits make sure you install the 32 bits ascom drivers for your mount as well because BYE is a 32 bits application is requires the ASCOM 32 bits drivers for your mount even you your XP is 64 bits.

[bradsheard@comcast.net]

OK, I will check that....could be the issue.

Thanks!!

[astroman133]

Whether BYE can access a 64-bit driver depends on whether the driver is in-process (a DLL) or out-of-process (an EXE). If the telescope driver is a DLL then it needs to be compiled and registered for 32-bit operation, even on a 64-bit computer, in order to be compatible with BYE or any 32-bit application. If the driver is built as a Local Server EXE it does not need to be 32-bit in order to be compatible with BYE..

 

If your Telescope driver supports concurrent connections from multiple applications, via a serial port, then it is a Local Server and the bitness of the driver does not matter to BYE.

 

If all this is confusing...blame Microsoft!