2 Attachment(s)
FocusMax.focuser is not registered
Hello,
After a PC crash last night I got a problem to restart FocusMax which is crashing all the time when the focuser is connected. Focuser is fine I can connect (from properties in FM calling the driver) and move it (a special TCF-S device mounted on the secondary mirror). I think the PC crashed while doing an Autofocus.
I rebooted the PC hoping this will clean the issue but I still have the same issue, one file seems corruped or the registry.
I have reinstalled the (very old) version of FM as it was loading without the proper setup (empty) it but did not help. We are running on that telescope a very old version of ACP (6.1 !) on windows XP ! but all is working perfectly since many many years now. Not a single bug since a very long time.. so long I do'nt remember even how to fix such a problem.
Should I reinstall the driver ?
Here attached the error and log from FM that points to a file FocusMax.focuser that I found in the ASCOM directory.
Attachment 12206
Attachment 12205
Any idea how to fix that ?
Thank you
Emmanuel
FocusMax.focuser is not registered
Emmanuel — I am getting to the edge of my knowledge. The FocusMax log screenshot shows the Optec focuser is connected so that is apparently OK. I also notice that it says PinPoint is not found. I also see an extremely old ASCOM Platform 5. I don’t see the Imaging SW selected to MaxIm so it looks as though FocusMax’s settings have been lost. This is getting complicated, involving extremely old software, and not ACP.
Do you perhaps have a disk-image backup with which you can go back to the state of the system before? Did you install Windows XP newly from a CD? Note that Microsoft has not supported XP for years, and probably cannot provide you with system updates to bring you to the level you had before your disk crashed.
I am sorry to say that I cannot help you much more with FocusMax 3. It too is very old and to be honest I was never very familiar with its details (like under what conditions it would generate that error). The author Steve Brady is not supporting it either.
Please consider building a new system with Windows 10 Pro, etc. If your Linux-speaking friends are telling you Windows is awful, then I really can’t help. It’s not awful but what can I say with the errors that MS made in September? It appears OK now, and has been fine for many many years before that.