That's awesome NMAC, thanks for that.
I did some rs232 port sniffing and compared the values between using V4Control and ASCOM with the ASCOM LittleFoot Driver and I think I may have found an (hopefully the) issue.
As part of the ASCOM connection test, it passes a request to the mount for a few things, which are: #0:VX#, #:GR# and #:GD#. The mount replies to all of the requests, but it sends an extra character with the #:GD# which I believe kills the ability for ACSOM and EQMOD to correctly connect to the mount.
When the mount receives #:GD# it returns - "+00ß00".
It's very strange that the "ß" is in there, but V4Control still works fine with that, but ASCOM doesn't like it.
The Latitude and Longitude ASCOM shows after the connection (in Device Connection Tested) is 1612345:00:00.000 4898765:00:00.000, with the first numbers in each being clearly wrong.
When trying to connect in the LittleFootClassic Setup it errors saying 1612345 is out of range.

I am using MCU Firmware 4.17D and I did reflash my MCU Firmware to 4.10D, but is still had the same issue.

My next thought is to try and get the MCU firmware and modify it to remove the "ß", or try and get the ASCOM LittleFoot driver source code and modify it to correctly read values with "ß" in it.

Do you know if there is a later version firmware that 4.17D? I did see messages from Rajiva (from many years ago) talking of a version 6 Firmware, but can't find anything close and it seems there are no longer any traces of Rajiva on the Internet (maybe he was NEO )?

Any thoughts on the "ß" in the value returned by the mount?

Read More...