Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

BYE won't connect to Ioptron cem25ec


bradsheard@comcast.net

Question

  • Answers 20
  • Created
  • Last Reply

20 answers to this question

Recommended Posts

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!

Link to comment
Share on other sites

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...

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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!

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use