Hi again, Dave,
I can now clarify a little. If I run ASCOM Diagnostics and treat the AAF2 driver as a 32 bit driver, the diagnostic reports that all is well, pulling in data from the Nano. But back in the real world, I can see no way of telling Windows to accept the driver, and it is rejected with a long ASCOM error message about 32 bit drivers.
From the ASCOM site comes this little gem:
"Running on a 64-bit Windows operating system does not mean all applications and ASCOM drivers are 64-bit. Virtually all astronomy applications run under the 32-bit subsystem, and use 32-bit drivers. They are unaware that they are running on a 64-bit system. This is a technical miracle from Microsoft.........Thus, if your driver is 32-bit, that will probably be sufficient for now and into the near future."
Apparently we are now beyond the near future, and it seems that my problem won't be resolved without a 64 bit driver, and I wouldn't know where to start!
I can't even say when the change occurred, so as to track the Win10 update that screwed it. My main thrust for the past few months has been adapting my scope and imaging gear to be entirely wireless. I can now sit in what I pathetically call my "Astroshack" (far end of the extension alongside the downstairs loo) in the warm, and control every aspect of my scope and camera using a laptop and an iPad. Well, every aspect except the focuser. Not a cable in sight.
My aim is to let people see what imaging is like at star parties, along with basic processing. I want to encourage more of our members to try by showing them how easy it is. The AAF2 focuser was a perfect part of this, especialy since we have some members who dabble in electronics.
I'll have to cross my fingers that a keen programmer-type chips in and offers to write a 64 bit driver - I don't think there's any way round it.
Ah, well...
Thanks anyway for a great project,
Pete