For immediate release.
- new arduino code versions for all driver boards (F=support LCD/push buttons/temp probe)
(M=minimal, NO lcd or push button or temperature probe support)
- windows app - supports all builds
- ASCOM driver - a single driver supports all builds
- windows ascom tester - windows app for testing ASCOM focuser drivers
- new PDF's - for easydriver, drv885 and myFocuser (recommended you download this!)
Old versions deleted as no longer supported.
EEPROM in controller now used to remember focuser position.
Email me with any issues,
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are going to use the L298N driver, download all the changed files that got uploaded today. I have finished testing this and made a number of changes, new Arduino code also for the L298N.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Uploaded today a minor revision of all Arduino .ino code.
There is no point updating the EEPROM immediately after a move. Consider if one was auto-focusing using FocusMax, that would result in a huge number of writes. So I took another approach. Only write the focuser position to EEPROM if there was a recent move, and no further move after 30s had elapsed. After all, that would best indicate if focus had been achieved (one would not move the focuser if it was in focus?)
However, to cover all bases (lets say a user updates the focuser position value using a SET command, or MaxSteps using a SET command) in which these values might change without a focuser move being initiated, I made a small change to all .ino versions.
// Modified driver code to write values to EEPROM on SP and SM commands
// At present code only updates 30s after a move. Using the Set() commands for
// position and maxStep does not initiate a move so these would not be saved
// unless there was a move() command that followed before shutdown/power-off
// Doubtful whether user would ever actually alter these parameters like this
// scenario describes, however included just in case
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Breaking News:
I have decided to implement a DC relative motor focuser controller, essentially an Arduino Nano equivalent of the RigelSys Focus Controller, which will obviously fit in with the existing application and ASCOM driver. Circuit has been designed and code written. At the moment bread-boarded, code written, will design layout soon. I can test this with my existing Rigelsys DC motors, essentially the controller will be a hand held device with two push buttons for In/Out as well as two pots for controlling pulse length (time motor is on) and delay between motor pulses (speed). Obviously LEDS for the direction and buzzer.
It can run off 3xAA batteries or 5V USB - using the USB obviously allows you to operate the focuser remotely using the existing myFocuser App or ASCOM driver.
I have started this because I actually sold most of my RigelSys gear now that myFocuser is operational, I still have a dc motor on my solar telescope but now no focuser controller - hence I think that's a good reason to start another project!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have uploaded pdf of the Canon EOS lens driven by myFocuser DRV8825 controller and NEMA17 belt drive. Works very well. I used APT as the software to connect and control the Canon EOS500D, using Liveview mode, connected to focuser using ASCOM driver and was able to jog the focuser position In and Out using the controls in APT, and just watch the liveview screen on the laptop till the focus looked best. Awesome!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
myFocuserWin_1402.zip
This is the Windows application for controlling the focuser directly.
// 23122014 v140
// Increased size of Temperature text box slightly
// Code change so that stepmode is remembered between sessions
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tonight I had a very good test of the L293D focuser with a NEMAPG5 stepper on the Orion ED80T-CF. Perfect. Flawless. Not a single issue. In comparison - a professional stepper motor version, very expensive piece of gear, the supplied software kept disconnecting, the usb controller would intermittently fail to respond etc. And that's usual, night after night and each new release of that software just seems to make things worse. I have never had one night where I didnt have issues with that "professional" version. Their own software kept disconnecting. Out of frustration I tried myFocuserAscomApp and was able to complete the nights session with the professional stepper and not one disconnect. So myFocuser worth about $40 completely ran rings around the $400USD professional version. So that professional version is coming off now and I will replace it with a myFocuser DRV8825 and a NemaPG27 stepper.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have made a minor change to the Windows App (now version 1.4.1) and the DRV8825 code (now version 128), which better supports now 1/4 and 1/8 stepping. I added a sortof double step setting under settings on the menu that doubles the step size - ie the -500 button changes to -1000 which is real handy when micro-stepping. I might also add a speed option (low/high) to the settings menu, which will require an arduino code change later on.
In normal operation once you have the focuser setup for your system, you should not be changing the stepmode during operation. Doing so can invalidate your 0 and maxsteps setting and potentially give rise to limited focuser travel length or focuser damage if you keep switching the stepmodes and moving the focuser.
In other words, experiment, but be careful. Once you have decided on whats best for your setup, then set the 0 and maxsteps settings and leave the stepmode set to whatever value you decided on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Recent updates over the last few days to support speed settings and allowing setting double step mode (eg, instead of -100 steps it becomes -200 steps). Changes made to windows application, ascom driver, ascom client application and all arduino code versions.
Recommend you uninstall the existing versions first before installing the newer releases.
The 1/4 and 1/8 stepping on the DRV8825 has been much improved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have uploaded a new pdf document file v127. This has information related to where you might want to run two myFocuser controllers on the same computer. ASCOM drivers are not re-entrant thus do not support running the same instance of the driver twice. The document explains what is required for you to run two drivers. What this means is that to run two focusers, you need two separate ASCOM drivers. The first is already posted here. I have finished the development of a second ASCOM focuser in case two controllers might be used - please email me for the second ASCOM driver if you wish to test it.
Cheers
Robert
Last edit: brownrb 2015-01-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many thanks to Pierre from France for pointing out an error in the PCB layout for the full version of the DRV8825 support board and the full version layout for the ULN2003. One of the 1.2k resistors was wired to VIN instead of 5V. I have uploaded the corrected layouts today.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
25-Jan-2015
New arduino file for L293D_F Shield - have changed temperature precision to 12bit.
New Windows Focuser App, v1412, added refresh comport button, handy when you start the application but forgot to connect the focuser, now you just connect the focuser then click "refresh"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
11 Feb 2015
Have updated ALL pdf documents
Have uploaded new schematic for ALL versions - very minor fix to a text label which was shown incorrectly, no circuit changes
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Congratulations jimmie1234 on your successful build and thanks for the feedback. I hope you find this as useful as I have. If you have the chance I would like to see a picture and perhaps post it in here of your setup. It would be nice to have a photo album here of all the successful builds so others can look at the work that others have achieved.
Best regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have added a folder called '3D Printing Brackets' which I designed a few months ago,
This folder contains designs for two brackets, the U bracket I use on the ED80 and the L bracket for the Stellarvue (or ED80) or U2 type crayford focusers (Skywatcher, Orion etc).
They should be printed with PLA. They are strong enough to hold the focus motor and should fit most refractors.
You can print them using a RepRap 3D printer. The bracket measurements are in mm are were designed as solid objects in SketchUp Make 2015.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
24 Feb 2015
I have uploaded changed today for all schematics and veroboard layouts. I have removed the 10A10 diode and replaced it with a MC78Txx voltage regulator, to ensure that excess voltage is not sent to VIN of the NANO controller or the various subdriver boards (such as L298N, EasyDriver, ULN2003 and DRV8825). The ULN2003 uses an LM7809 whilst the EasyDriver, L298N and DRV8825 boards use an LM7812. This means the external battery power in all cases is 12V (or a car battery at 13.6V).
In some Nano variations, they appear to suffer damage if VIN rises above 12V - even though the specs indicate they should handle up to 20V.
Last edit: brownrb 2015-02-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
25 Feb 2015
I am not happy with the use of the VR's. I am going to explore an alternative. In the meantime, I will revert back to previous versions of the schematics and layouts.
The issue is around an external supply being too high a voltage supplying VIN on the Nano and thus damaging the Nano. A Zener diode can achieve this also. For now, I would recommend ensuring the external DC input is not connected to VIN. If your focuser is already working then you probably dont have an issue. Of the four I have built so far, 3 are fine, the 4th (a nano from a different supply) fried immediately upon external 12V connection (though it was working fine at 9V).
Apologies for the rapid reversal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
26 Feb 2015
All versions: New Schematic, New layout, New Arduino code
Changes: Power ON/OFF switch, Reset circuitry for Moonlite compatibility, Zener protection for VIN when using 12V external power with Nano.
NEW SOFTWARE
ALL: Arduino Code versions
Windows Application
ASCOM Driver
ASCOM Second Driver
Changes: Support for MaxSteps up to 64000, when using PG27 with half steps (I found I needed a MaxStep of 34747 to support the entire focuser range, so its been upped to 64000 - make sure you set MaxSteps correctly else you can damage your focuser). Windows and ASCOM drivers will now report larger values.
SOME CHANGES TO THE FOLDERS AND NAMES
OLD FILES REMOVED AS NO LONGER SUPPORTED
IF YOU ARE IN THE PROCESS OF BUILDING A CONTROLLER NOW JUST CONTINUE WITH THE OLD SCHEMATIC AND LAYOUT (but advice is to include the Zener protection for VIN if using DRV8825/Easydriver/L298N driver boards). ALL NEW CODE WORKS WITH PREVIOUS HARDWARE.
MAKE SURE YOU DOWNLOAD AND READ THE LATEST PDF FOUND IN THE DOCUMENTATION FOLDER (myFocuser_133.pdf).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
26 Feb 2015 CAUTION NEEDED - REALLY IMPORTANT
Make sure you record the values for focuser position and maxsteps BEFORE you update the Arduino Code to the latest firmware. You will need to reset these values using the Windows Application once you restart the controller as they will be no longer valid after the update.
(They have been changed from a 32 bit value to a 64 bit value to allow higher values for MaxSteps when using a PG27 and microstepping).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
28 Feb 2015
In case one was wondering why I did not add the VIN Zener protection to the ULN2003 versions, this is due to the board using a 9V external battery. It is not recommended to run the ULN2003 boards at 12V.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For immediate release.
- new arduino code versions for all driver boards (F=support LCD/push buttons/temp probe)
(M=minimal, NO lcd or push button or temperature probe support)
- windows app - supports all builds
- ASCOM driver - a single driver supports all builds
- windows ascom tester - windows app for testing ASCOM focuser drivers
- new PDF's - for easydriver, drv885 and myFocuser (recommended you download this!)
Old versions deleted as no longer supported.
EEPROM in controller now used to remember focuser position.
Email me with any issues,
Cheers
Highly recommend you uninstall existing drivers or apps before installing new drivers or apps
Finished building and final testing of DRV8825 controller today. Posted final build images for DRV885.
If you are going to use the L298N driver, download all the changed files that got uploaded today. I have finished testing this and made a number of changes, new Arduino code also for the L298N.
Uploaded today a minor revision of all Arduino .ino code.
There is no point updating the EEPROM immediately after a move. Consider if one was auto-focusing using FocusMax, that would result in a huge number of writes. So I took another approach. Only write the focuser position to EEPROM if there was a recent move, and no further move after 30s had elapsed. After all, that would best indicate if focus had been achieved (one would not move the focuser if it was in focus?)
However, to cover all bases (lets say a user updates the focuser position value using a SET command, or MaxSteps using a SET command) in which these values might change without a focuser move being initiated, I made a small change to all .ino versions.
// Modified driver code to write values to EEPROM on SP and SM commands
// At present code only updates 30s after a move. Using the Set() commands for
// position and maxStep does not initiate a move so these would not be saved
// unless there was a move() command that followed before shutdown/power-off
// Doubtful whether user would ever actually alter these parameters like this
// scenario describes, however included just in case
Breaking News:
I have decided to implement a DC relative motor focuser controller, essentially an Arduino Nano equivalent of the RigelSys Focus Controller, which will obviously fit in with the existing application and ASCOM driver. Circuit has been designed and code written. At the moment bread-boarded, code written, will design layout soon. I can test this with my existing Rigelsys DC motors, essentially the controller will be a hand held device with two push buttons for In/Out as well as two pots for controlling pulse length (time motor is on) and delay between motor pulses (speed). Obviously LEDS for the direction and buzzer.
It can run off 3xAA batteries or 5V USB - using the USB obviously allows you to operate the focuser remotely using the existing myFocuser App or ASCOM driver.
I have started this because I actually sold most of my RigelSys gear now that myFocuser is operational, I still have a dc motor on my solar telescope but now no focuser controller - hence I think that's a good reason to start another project!
Have uploaded pdf of the Canon EOS lens driven by myFocuser DRV8825 controller and NEMA17 belt drive. Works very well. I used APT as the software to connect and control the Canon EOS500D, using Liveview mode, connected to focuser using ASCOM driver and was able to jog the focuser position In and Out using the controls in APT, and just watch the liveview screen on the laptop till the focus looked best. Awesome!
myFocuserWin_1402.zip
This is the Windows application for controlling the focuser directly.
// 23122014 v140
// Increased size of Temperature text box slightly
// Code change so that stepmode is remembered between sessions
Tonight I had a very good test of the L293D focuser with a NEMAPG5 stepper on the Orion ED80T-CF. Perfect. Flawless. Not a single issue. In comparison - a professional stepper motor version, very expensive piece of gear, the supplied software kept disconnecting, the usb controller would intermittently fail to respond etc. And that's usual, night after night and each new release of that software just seems to make things worse. I have never had one night where I didnt have issues with that "professional" version. Their own software kept disconnecting. Out of frustration I tried myFocuserAscomApp and was able to complete the nights session with the professional stepper and not one disconnect. So myFocuser worth about $40 completely ran rings around the $400USD professional version. So that professional version is coming off now and I will replace it with a myFocuser DRV8825 and a NemaPG27 stepper.
I have made a minor change to the Windows App (now version 1.4.1) and the DRV8825 code (now version 128), which better supports now 1/4 and 1/8 stepping. I added a sortof double step setting under settings on the menu that doubles the step size - ie the -500 button changes to -1000 which is real handy when micro-stepping. I might also add a speed option (low/high) to the settings menu, which will require an arduino code change later on.
In normal operation once you have the focuser setup for your system, you should not be changing the stepmode during operation. Doing so can invalidate your 0 and maxsteps setting and potentially give rise to limited focuser travel length or focuser damage if you keep switching the stepmodes and moving the focuser.
In other words, experiment, but be careful. Once you have decided on whats best for your setup, then set the 0 and maxsteps settings and leave the stepmode set to whatever value you decided on.
Recent updates over the last few days to support speed settings and allowing setting double step mode (eg, instead of -100 steps it becomes -200 steps). Changes made to windows application, ascom driver, ascom client application and all arduino code versions.
Recommend you uninstall the existing versions first before installing the newer releases.
The 1/4 and 1/8 stepping on the DRV8825 has been much improved.
myDCFocuser has gone into beta release. This works with DC motors.
ASCOM driver v134 update - has speed settings AND a drop down combobox for selecting the com port (overcomes errors in user entry).
Previous versions MUST be uninstalled first via Control Panel as there has been a change in the user config file for the driver.
Any feedback appreciated.
Regards Robert
I have uploaded a new pdf document file v127. This has information related to where you might want to run two myFocuser controllers on the same computer. ASCOM drivers are not re-entrant thus do not support running the same instance of the driver twice. The document explains what is required for you to run two drivers. What this means is that to run two focusers, you need two separate ASCOM drivers. The first is already posted here. I have finished the development of a second ASCOM focuser in case two controllers might be used - please email me for the second ASCOM driver if you wish to test it.
Cheers
Robert
Last edit: brownrb 2015-01-09
Many thanks to Pierre from France for pointing out an error in the PCB layout for the full version of the DRV8825 support board and the full version layout for the ULN2003. One of the 1.2k resistors was wired to VIN instead of 5V. I have uploaded the corrected layouts today.
25-Jan-2015
New arduino file for L293D_F Shield - have changed temperature precision to 12bit.
New Windows Focuser App, v1412, added refresh comport button, handy when you start the application but forgot to connect the focuser, now you just connect the focuser then click "refresh"
08Feb2015
Updates to all Arduino code versions posted today
11 Feb 2015
Have updated ALL pdf documents
Have uploaded new schematic for ALL versions - very minor fix to a text label which was shown incorrectly, no circuit changes
Congratulations jimmie1234 on your successful build and thanks for the feedback. I hope you find this as useful as I have. If you have the chance I would like to see a picture and perhaps post it in here of your setup. It would be nice to have a photo album here of all the successful builds so others can look at the work that others have achieved.
Best regards
Robert
I have added a folder called '3D Printing Brackets' which I designed a few months ago,
This folder contains designs for two brackets, the U bracket I use on the ED80 and the L bracket for the Stellarvue (or ED80) or U2 type crayford focusers (Skywatcher, Orion etc).
They should be printed with PLA. They are strong enough to hold the focus motor and should fit most refractors.
You can print them using a RepRap 3D printer. The bracket measurements are in mm are were designed as solid objects in SketchUp Make 2015.
24 Feb 2015
I have uploaded changed today for all schematics and veroboard layouts. I have removed the 10A10 diode and replaced it with a MC78Txx voltage regulator, to ensure that excess voltage is not sent to VIN of the NANO controller or the various subdriver boards (such as L298N, EasyDriver, ULN2003 and DRV8825). The ULN2003 uses an LM7809 whilst the EasyDriver, L298N and DRV8825 boards use an LM7812. This means the external battery power in all cases is 12V (or a car battery at 13.6V).
In some Nano variations, they appear to suffer damage if VIN rises above 12V - even though the specs indicate they should handle up to 20V.
Last edit: brownrb 2015-02-23
25 Feb 2015
I am not happy with the use of the VR's. I am going to explore an alternative. In the meantime, I will revert back to previous versions of the schematics and layouts.
The issue is around an external supply being too high a voltage supplying VIN on the Nano and thus damaging the Nano. A Zener diode can achieve this also. For now, I would recommend ensuring the external DC input is not connected to VIN. If your focuser is already working then you probably dont have an issue. Of the four I have built so far, 3 are fine, the 4th (a nano from a different supply) fried immediately upon external 12V connection (though it was working fine at 9V).
Apologies for the rapid reversal
26 Feb 2015
All versions: New Schematic, New layout, New Arduino code
Changes: Power ON/OFF switch, Reset circuitry for Moonlite compatibility, Zener protection for VIN when using 12V external power with Nano.
NEW SOFTWARE
ALL: Arduino Code versions
Windows Application
ASCOM Driver
ASCOM Second Driver
Changes: Support for MaxSteps up to 64000, when using PG27 with half steps (I found I needed a MaxStep of 34747 to support the entire focuser range, so its been upped to 64000 - make sure you set MaxSteps correctly else you can damage your focuser). Windows and ASCOM drivers will now report larger values.
SOME CHANGES TO THE FOLDERS AND NAMES
OLD FILES REMOVED AS NO LONGER SUPPORTED
IF YOU ARE IN THE PROCESS OF BUILDING A CONTROLLER NOW JUST CONTINUE WITH THE OLD SCHEMATIC AND LAYOUT (but advice is to include the Zener protection for VIN if using DRV8825/Easydriver/L298N driver boards). ALL NEW CODE WORKS WITH PREVIOUS HARDWARE.
MAKE SURE YOU DOWNLOAD AND READ THE LATEST PDF FOUND IN THE DOCUMENTATION FOLDER (myFocuser_133.pdf).
26 Feb 2015 CAUTION NEEDED - REALLY IMPORTANT
Make sure you record the values for focuser position and maxsteps BEFORE you update the Arduino Code to the latest firmware. You will need to reset these values using the Windows Application once you restart the controller as they will be no longer valid after the update.
(They have been changed from a 32 bit value to a 64 bit value to allow higher values for MaxSteps when using a PG27 and microstepping).
28 Feb 2015
In case one was wondering why I did not add the VIN Zener protection to the ULN2003 versions, this is due to the board using a 9V external battery. It is not recommended to run the ULN2003 boards at 12V.