Error message with ASCOM driver IPX800

[Fred M]

• This issue is reproducible
• This issue happened with version 3.0 or 3.1beta but not older versions (i.e. 2.3.1.9001)
• Prerequisites: install this ascom driver : https://www.elendil.software/fr/logiciels/ipx800-switch.html for switch device

Description

When I try to configure my switch IPX800 I get an error message (see attchment)

Steps to Reproduce

• Select “Equipment” menu
• Select “Switch” submenu
• Choose “IPX800 switch” device
• Clic on setting button

Expected behaviour

The setting view of the IPX800 device appears

Actual behaviour

A popup error appears (see attachment)

[Stefan B]

Hi,

please run your driver against the ASCOM conformance checker and post the result. Then we can verify if the driver is conforming to the specs or if there is something to be fixed there. The new ASCOM client library that NINA >v3 is using is more strict.
You can find the tool here: https://github.com/ASCOMInitiative/ConformU/releases/tag/v2.1.0%2B23787

[Fred M]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Fred M]

Hi Stefan,

Thanks for your reply.

Please find in attachment le log about the IPX800 with the ASCOM conformance checker

Best Regards

‌

[Stefan B]

Ok thank you. Looks like it runs fine. Unfortunately I’m not sure why it is not able to connect via N.I.N.A. to your driver, as this is an internal error inside the ascom framework.

[Fred M]

OK, you think you can’t do anything on your side, right ?

[Stefan B]

Can you share one of the nina logs where this error happens, just in case there is more info available?

[Fred M]

OK no problem:

System.TypeLoadException: Creating an instance of the COM component with CLSID {A1A13862-AA94-48B9-BF6F-447F1C2AFD8D} from the IClassFactory failed due to the following error: 80131522 Could not find or load a type. (0x80131522).
at System.RuntimeTypeHandle.AllocateComObject(Void* pClassFactory)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
at ASCOM.Com.DriverAccess.DynamicAccess..ctor(String ProgID)
at ASCOM.Com.DriverAccess.ASCOMDevice..ctor(String progid)
at ASCOM.Com.DriverAccess.Switch..ctor(String ProgID)
at NINA.Equipment.Equipment.MySwitch.Ascom.AscomSwitchHub.GetInstance() in C:\Projects\nina\NINA.Equipment\Equipment\MySwitch\Ascom\AscomSwitchHub.cs:line 81
at NINA.Equipment.Equipment.AscomDevice`1.SetupDialog() in C:\Projects\nina\NINA.Equipment\Equipment\AscomDevice.cs:line 259

‌

[Stefan B]

Can you attach the complete log please?

[Fred M]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Stefan B]

Ok thank you. yea nothing really to fix on NINA side there. it seems like the ascom driver is missing a library it depends on.

[Fred M]

May be I need to see with the driver IPX800 developer ?

For now I keep the NINA version 2.3.1.

Unfortunatly I used the Hocusfocus plugin but it doesn’t exist on this version. Too bad !

Anyhow, thanks for your help

[Stefan B]

Yea it could be some dependency that is inside the Global Assembly Cache - but this construct is no longer available in the new .net versions going forward.

[Fred M]

OK thanks

Have a good night !

[Fred M]

Just for information the driver creator propose on his website a little sowtware “switch” to use the Ascom driver and it works properly

https://www.elendil.software/en/softwares/switch.html

Probably he will tell me it’s not an issue on his side !

[Fred M]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Stefan B]

It could be a clash of dependencies. looking at that ascom driver there are quite a few assemblies that it pulls in that nina is also using, which could result in a conflict. Hard to tell from the stack trace though, as these issues are difficult to analyse.

[Stefan B]

What you can do to work around the issue is using the optec ascom server. It basically wraps a driver and isolates it.
You can install it from here: https://optecinc.com/downloads/legacy/optecascomserver/
Then you head to its setup options in nina by selecting “Optec ASCOM Server”, hitting the gears icon and select your switch driver there and connect.

[Fred M]

OK I just install optec ascom server and now I’m able to open the IPX800 properties without issue

I can’t try to connect the IPX800 because actualy I’m on holliday but it seems an interesting solution !

I test in one week

Many thanks !

[Stefan B]

Great. Please keep me updated if it works with the actual device. I will also add this tip to a troubleshooting page of our documentation.

[Fred M]

  <div class="preview-container wiki-content"><!-- loaded via ajax --></div>
  <div class="mask"></div>
</div>

</div> </form>

[Fred M]

OK I will let you know

Bye

[Stefan B]

Marking as resolved via using the Optec Hub. Please reopen in case this doesn't work still.

[Stefan B]

I have also added steps to the manual for this case
https://nighttime-imaging.eu/docs/master/site/troubleshooting/ascom_connection_issues/