No Connection to Rigel NFocus

[astroguy8730]

 I am newb with BYN.  I have ES127ED scope on iOptron iEQ45 mount and Rigel Systems NFocus USB focuser. I use BYN trial version to test with Nikon D5300. I see already there is topic on iOptron that cannot connect until new version. I also get alarm bell and message that there is no connect to NFocus but I know ASCOM driver installed and working separately. Is this normal to have no focusing?   

[astroguy8730]

The problem solve by uninstall and reinstall focus driver from disk. Maybe driver conflict with other USB serial device? Now focus work. Still no move of iOptron mount but that is coming soon?

[astroman133]

If other ASCOM focuser client applications are able to connect to your focuser then BYN will connect.

 

What do you mean by "working separately"? Often device manufacturers provide a program that will communicate with the device using the native protocol. They do not use, or rely on, ASCOM. So if the native app works it means that the device is functional and that the cable is working. The first thing that I would check are parameter settings in the ASCOM driver setup dialog.

[astroguy8730]

Native application and other photo applications connect no trouble. I am able use auto-focus other not-Nikon CMOS camera and also move focus manual with MaxImDL 5.07. No connection with same ASCOM driver in BYN...just alarm bell and error message.  

[astroman133]

This may require a look at the BYN log files.

[astroguy8730]

OK. Here is last showing the error.

logfile-20170325-14h26m33s668-2428-2017-03-25.txt

[admin]

This is the error in your log file.

 

2017-03-25 14:26:49,580 [Main] ERROR - Input string was not in a correct format.

2017-03-25 14:26:49,580 [Main] ERROR -    at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

   at System.Int16.Parse(String s, NumberStyles style, NumberFormatInfo info)

   at System.String.System.IConvertible.ToInt16(IFormatProvider provider)

   at System.Convert.ToInt16(Object value)

   at ASCOM.DriverAccess.AscomDriver.get_InterfaceVersion() in c:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 274

   at ASCOM.DriverAccess.AscomDriver..ctor(String deviceProgId) in c:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 51

   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)

2017-03-25 14:26:49,580 [Main] ERROR - Input string was not in a correct format.

2017-03-25 14:26:49,580 [Main] ERROR -    at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

   at System.Int16.Parse(String s, NumberStyles style, NumberFormatInfo info)

   at System.String.System.IConvertible.ToInt16(IFormatProvider provider)

   at System.Convert.ToInt16(Object value)

   at ASCOM.DriverAccess.AscomDriver.get_InterfaceVersion() in c:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 274

   at ASCOM.DriverAccess.AscomDriver..ctor(String deviceProgId) in c:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 51

   at BinaryRivers.ASCOM.Platform60.FocuserASCOM.Connect(String drivername)

2017-03-25 14:26:49,596 [Main] INFO  - ASCOM Focuser disconnected (or unable to connect).

 

 

What is the name of the focuser (from the ASCOM chooser dialog) you are trying to connect?

[astroman133]

By chance are you using a comma as the decimal separator?

[astroguy8730]

I only connect same as Maxim DL. I choose "GCUSB_nSTEP.Focuser". That is driver that connect all other program.  

[admin]

2017-03-25 14:26:49,580 [Main] ERROR - Input string was not in a correct format.

2017-03-25 14:26:49,580 [Main] ERROR -    at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

   at System.Int16.Parse(String s, NumberStyles style, NumberFormatInfo info)

   at System.String.System.IConvertible.ToInt16(IFormatProvider provider)

   at System.Convert.ToInt16(Object value)

   at ASCOM.DriverAccess.AscomDriver.get_InterfaceVersion() in c:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 274

 

 

This is where ASCOM throws the error, in getting the InterfaceVersion at line 274 in AscomDriver.cs.  This is an ASCOM issue.  What I don't understand is why other program using the same ASCOM driver do connect.  I'm stumped.  From a pure code perspective this is an ASCOM bug, but since other programs are working it appears to be a BYE bug... but I can't figure out why yet

 

Regards,

[astroguy8730]

I like BYN interface that place all camera and telescope and focus on same screen. Very nice thinking, but with now no connect to my mount or focuser is not so useful  . I hope it solved. . 

[astroman133]

There is something strange going on with your focuser driver. I cannot see how you can communicate with the focuser from other ASCOM apps. The exception is happening when BYN constructs the focuser object and the exception is thrown by the ASCOM driver base class, AscomDriver when it gets the Interface version from the derived driver class.

 

If you are not a programmer, then my analysis will likely leave you scratching your head, but it will mean something to Guylain.

 

The fact that nobody else has reported problems connecting to their focuser means that the code in BYN is sound and that there is some ASCOM-related issue with your focuser driver. I would suggest contacting Rigel Systems for help.

[astroman133]

Good news, glad that you are working!

[admin]

YEAH!