petequin

This is all very well, but will someone please tell my wife why a 3D printer is a good idea and where I can stick it so it won't be seen as clutter. Hmm. Could have phrased that better. Sigh... Pete

Ah, it's the way of the world. 3D printers? Cool! Sadly, my lovely wife has made it plain that a 3D printer would be a gadget too far. Sigh... However, redtail's mention of a POTH hub got me excited (yes, that's all it takes these days). I ran to my astro laptop and tried it and it ran the AAF2 with no problem. The secret to my wireless system is a Pipo 8.9" Win10 wedge tablet - tons of connectivity and a 1900x1200 touch screen. I'm currently using it with BackyardEOS, but I see no reason why POTH won't go alongside it and run the focuser. I'll try it out this weekend (it's the Society meeting tonight, one of my, er, less favourite speakers - can't win 'em all), and if it's fine, it'll be live! Wheeeeeeeee! My thanks to you and everybody for help and comments - I should have called by sooner! Pete

Oh, forgot - I wondered if there might be a useful hint on this page - http://tigra-astronomy.com/blog/the-well-travelled-photon/understanding-ascom-driver-registration Pete

Dave, I just want to reassure you that I am just an amateur bumbling around in an amateur way. I do appear on local radio and TV and other places to talk about astronomy, but in my position as the Deputy Chairman of the Bristol Astronomical Society. Sadly, I don't get even a penny for it, but it is nice when someone comes up and tells me that they heard me the other day, etc. The Society is a registered charity (you can look us up) and our stated mission is to inform and educate about astronomy both by regular meetings and by outreach. We meet over forty times a year, and run twenty or so star parties a year. My worry is that our average membership is aging, and we are not good at encouraging younger people to join. My personal feeling is that in the age of the computer, the mobile phone, Skype and Facetime, would-be astronomers need to see that they don't need to freeze their n**s off to see anything. At a star party, I let people look through an eyepiece first then see how much more exciting it can be to do even simple imaging, and that it can be done very cheaply with modern tech. (I push Celestron Sky Portal as a sky atlas because it's free, and can aslo be used for control of C's wifi scopes. One radio presenter downloaded it while the next track was playing then couldn't stop waving it around and looking at it for the rest of the programme!) I think astronomy should be fun, and I do get a lot of pleasure out of projects like this (mounting the focuser on different scopes is an interesting challenge - I've gone for articulating the motor with spring tensioning for a consistent drive). Curse evil Microsoft for messing with it! And that a curse from a very old Yorkshireman, so they'd better listen! Sorry, I'll stop ranting... Pete

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

Thanks, Dave. And eek! I don't think I've had a machine running XP since sometime last century. Trouble is, I also use the Astroshack (!!!) machine for processing and most apps won't work right under anything without a 10 at the end of it. I am doomed. I did try the ASCOM Profile explorer and diagnostic before I posted here, and when it came to look at the focuser it reported that it was trying to run a 32 bit driver on a 64 bit system - contact the manufacturer. That really helped. Trying to run the AAF2 program in XP compatibility mode didn't help either. Thanks, too, Rich. No, I can't pinpoint when it happened. I let updates install automatically (lazy, I know). Also my scope is a nice and stable platform. I usually run it with a modded Canon 650d and a flip mirror. Once focused, I lock the mirror (two mirror locks on the EdgeHD!), and it hold focus really well from day to day. Also lazy, but when you look at it and it looks pin sharp, you don't want to screw with it. A concern, though, is that if I found the potentially problematic update and removed it, what might then go wrong? It feels like it's actually something really trivial that's getting in the way - trivial, but not obvious. The fact that you can push 'Blink' onto the Nano means that it's probably not the Arduino programmer. But both Win10 and the ASCOM platform have been updated quite a bit since this came out, and a change in either could be the cause. I'm a bit surprised that this hasn't happened before to someone. Am I the only one running an up-to-date system to drive it? Does this mean that Microsoft have singled me out for pain? (Highly likely - I'm writing this on a Macbook - they can't see me, heh, heh.) Still hoping for a miracle... Pete

Ah, should have mentioned that. The AAF2 utility crashes out with a long and obscure error message, lots of mentions of ASCOM problems and more. This really was an overnight development. All worked fine for ages, then suddenly it didn't. It does feel like some update screwed it, but I don't know what. As I implied, I'm sure this isn't a hardware problem. But Win10 and ASCOM have updated quite a bit since I built them, and it does seem that the problem lies somewhere in that great morass of code. I do think you created a very cool and remarkably straightforward project there and I've shown it off to many friends (I'm the Deputy Chair of the Bristol Astronomical Society - translates as gopher/class clown). I really hope you can work some magic! Again! Pete

I haven't contributed to this discussion before - I've simply built four of these wonderful focusers and enjoyed using them enormously. Until now. Now, none of them work. Mostly. Oddly, occasionally, driven by BackyardEOS, the one on my Celestron 1100EdgeHD works for about 30 seconds, then bombs and is no longer recognised by the software, even though Win10 recognises the port. If I run an ASCOM diagnostic, it says that I'm trying to run a 32 bit driver on a 64 bit system, but I'm not convinced that's the answer. I should add that I have the same problem with all three Win10 computers I use for astro imaging. Has anyone else experienced this, or is it just me? I did connect one focuser up and run the programmer loaded with 'Blink' just to see if it worked. It did, blinking away just fine, so it's not simply the combination of Win10 and Arduino Nano. The obvious conclusion is that some recent update to Win10 clashes with the Focuser code, but I would have though that there'd be a raft of panic posts by now. Any help would greeted by ecstatic sighs of relief! Pete