I have a problem that seems to be intermittent. I'm using a Easydriver with a Nano. Motor is a NEMA17pg27. I've been using this setup for over a year and on occasion I'm seeing the following.
I will be using the scope and finish the night with say a 2453 focus position. On another evening when I set up I notice the focus postion says 5000.
I know based on the position markings that nothing has moved. Again, this is intermittent as most of the time everything works correctly.
Where should I start looking.
Thanks
Gordon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you on occassion run the Windows app and on other times the ASCOMdriver? Or is it just one of them.
A logfile can help.
Generally speaking there are only three ways this can happen,
First
Windows app-should not be possible
ASCOM app-On settings form, under focuser settings, Update on connect is checked [this will show up in a tracelog file]
Second
Windows app-Menu option Extra Settings-Write focuserdefault settings which writes 5000/10000 [this will show up in a logfile]
Third
On startup, the controller cannot read a valid eeprom setting so writes a default setting of 5000/10000 [no way to capture this at present]
Before powering down, I would recommend that you wait 1m from closing the application referencing the focuser to powering down the focuser, giving sufficient time to write focuser settings.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do use both the Windows app and the ASCOM app however I'm pretty careful to shut one down before opening the other. My settings should be okay but I will check them.
Powering down could be the issue. I typically run everything remote and power is the last thing to happen. However I will do some double checking on everything you mentioned.
Gordon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Gordon
I have found that sometimes (not often) after updating the ASCOM driver or Windows App some of the settings get stuffed (because I did not use Save/Restore settings before updating) and thus a default to 5000/10000 occurs. I dont recall any other time though
Regards
Robert
Turn logging on. You can delete logs when things are ok, but a log file may help. How intermittent is it?
Last edit: brownrb 2019-01-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
I have a problem that seems to be intermittent. I'm using a Easydriver with a Nano. Motor is a NEMA17pg27. I've been using this setup for over a year and on occasion I'm seeing the following.
I will be using the scope and finish the night with say a 2453 focus position. On another evening when I set up I notice the focus postion says 5000.
I know based on the position markings that nothing has moved. Again, this is intermittent as most of the time everything works correctly.
Where should I start looking.
Thanks
Gordon
Do you on occassion run the Windows app and on other times the ASCOMdriver? Or is it just one of them.
A logfile can help.
Generally speaking there are only three ways this can happen,
First
Windows app-should not be possible
ASCOM app-On settings form, under focuser settings, Update on connect is checked [this will show up in a tracelog file]
Second
Windows app-Menu option Extra Settings-Write focuserdefault settings which writes 5000/10000 [this will show up in a logfile]
Third
On startup, the controller cannot read a valid eeprom setting so writes a default setting of 5000/10000 [no way to capture this at present]
Before powering down, I would recommend that you wait 1m from closing the application referencing the focuser to powering down the focuser, giving sufficient time to write focuser settings.
Regards
Robert
Thanks Robert!
I do use both the Windows app and the ASCOM app however I'm pretty careful to shut one down before opening the other. My settings should be okay but I will check them.
Powering down could be the issue. I typically run everything remote and power is the last thing to happen. However I will do some double checking on everything you mentioned.
Gordon
Hi Gordon
I have found that sometimes (not often) after updating the ASCOM driver or Windows App some of the settings get stuffed (because I did not use Save/Restore settings before updating) and thus a default to 5000/10000 occurs. I dont recall any other time though
Regards
Robert
Turn logging on. You can delete logs when things are ok, but a log file may help. How intermittent is it?
Last edit: brownrb 2019-01-10