Hi Robert, I congratulate for the excellent and complex work to be done I need you kindly clarify some points during the first configuration of my focuser just realized in full version with encoder and DRV8825 driver in connection with a VIXEN VISAC 200mm f9. The stepper motor used by me already because of my possession is a SANYO DENKI 103-546-5342 used in 1/16 step mode decision taken after developing my calculations for the step size (35mm extraction / revolution full 360 ° of 2300 steps = 0.0152173 ...) and the CFZ (9 * 9 * 2.2 = 178.2). Having calculated the limit to 69mm with just under two complete revolutions of the pulley and 4550 steps, on myfocuserPRO I decided to set the limit at 4000 steps, the value I will now also enter for the ascom driver setup for use with FocusMax but it is not accepted because it defaults to 5000, also having a 15:22 microns measure to pass, when I enter this value either myfocuserPRO is in the window of ascom settings I get an error message for value outside. How can I remedy this? Thank you in advance and waiting to greet your own friendly and decisive response on the matter. Biagio Speranza
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have sent you some details. This might help in resolving the issues. I am not sure about 15:22 do you mean 15.22? We cannot use : as a separator - it would not be recognized. At moment there is a range check boundary of step size - between 0.001 microns to 50 microns.
I am assuming 15:22 means 15.22 microns?
Cheers
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert, I apologize for the misspelling. yes, I was talking to 15:22 microns by step. As I wrote to you, it is the result of my calculations: 35mm extraction / revolution full 360 ° of 2300 steps = 0.0152173 ... then round at 15.22 right?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Biagio
So if you enter 15.22 as the stepsize value on the extra settings form then click close the form.
Next click on the extra settings again to reopen the form - you will see the value is remembered.
To send this to controller., set the value to 15.22, then on the same form click Enable in controiller so it is green, then click update on connect so its green then click close, after that connect to controller
Thanks Robert but after entering in extra setting the 15:22 value at the end does not accept it, and when I open it I find the value added is 500. I attach the following screens. thank you for your patience.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What is your windows locale setting? Is it US-English or something else?
In Win10 this is bottom of taskbar. Also can access via Windows Key and Space.
If you set it to US English what happens?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Robert, just tried it but nothing to do. only if I enter the value without the second decimal (ie 15.2 instead of 15.22) The field accepts it as a whole, I think, as the new opening keeps me 152. I do not think is fine as 152 microns are thus not 15.22!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Biagio
I can confirm that Windows App v2.3.5.0 I can enter 15.22 in as step size and it stays there - remembered. If this is not happening on your system, I suggest use control panel to remove windows application, reboot, then install latest windows app v2.3.5.0 and try again.
Cheers
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Roberto ok, thank you for your immeasurable patience and through several attempts on my system looks like the 2.3.4.8 version is the one that manages to turn better. I take this opportunity just to bring one last question: taking a look at the pdf that speaks of options for configurations of EasyDriver board I noticed that in the full scheme of EasyDriver MS1 pin is connected to the pin D7 arduino while the photograph of that EasyDriver describes the connections to arduino pins are instructed to connect the MS1 pin to pin D5 arduino. Why this difference? just because the picture of EasyDriver belongs to the old version, not the 203? the right pin to be connected is the D7 or the D5? thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Biagio
You probably need to adjust the motor speed parameters - see PDF page 33 wirh section starting 8: CHECK THE SPEED SETTINGS
In v2350 these were altered. So need to be set for value that is best for your controller
Yes D7 is correct - I probably did not remove the older NON hw203 which from memory used D5 - thanks I will look at changing it.
Glad to hear you have success.
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thanks again Robert then wanting to create the version that makes use of the rotary encoder EasyDriver and what pattern should I follow? one related to both the drv8825 and EasyDriver or turnover relating solely EasyDriver? in which directory should I see?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You really dont need Rotary Encoder unless for manual operation, no point with computer control as no we have a jogging control in the software. There is a software lag issue with the rotary encoder. IT works but if you try to turn the encoder too quickly the hardware cannot keep up with the pulses coming up and so it might keep stepping after you stop turning the encoder. It can take a little time to get the hang of it.
Cheers
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks again Robert then as a developer I you realize you recommend to the version using the buttons in place of the encoder as regards the manual controls as it turns out to be more powerful reactive, right?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As long as the RE is not turned at crazy speeds then its fine. Its only when the knob is turned too fast that the Software/Hardware cannot keep up and the issues arise. Over time one gets a feel for what is too fast... I am just trying to show the limitation and not raise expectation to a level where one expects too much. It does woek, and very reliabiliy, at lower knob turn speed. I think its better at manual focusing than the buttons.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert, I congratulate for the excellent and complex work to be done I need you kindly clarify some points during the first configuration of my focuser just realized in full version with encoder and DRV8825 driver in connection with a VIXEN VISAC 200mm f9. The stepper motor used by me already because of my possession is a SANYO DENKI 103-546-5342 used in 1/16 step mode decision taken after developing my calculations for the step size (35mm extraction / revolution full 360 ° of 2300 steps = 0.0152173 ...) and the CFZ (9 * 9 * 2.2 = 178.2). Having calculated the limit to 69mm with just under two complete revolutions of the pulley and 4550 steps, on myfocuserPRO I decided to set the limit at 4000 steps, the value I will now also enter for the ascom driver setup for use with FocusMax but it is not accepted because it defaults to 5000, also having a 15:22 microns measure to pass, when I enter this value either myfocuserPRO is in the window of ascom settings I get an error message for value outside. How can I remedy this? Thank you in advance and waiting to greet your own friendly and decisive response on the matter. Biagio Speranza
I attach also photos of my configuration.
I have sent you some details. This might help in resolving the issues. I am not sure about 15:22 do you mean 15.22? We cannot use : as a separator - it would not be recognized. At moment there is a range check boundary of step size - between 0.001 microns to 50 microns.
I am assuming 15:22 means 15.22 microns?
Cheers
Robert
Hello Robert, I apologize for the misspelling. yes, I was talking to 15:22 microns by step. As I wrote to you, it is the result of my calculations: 35mm extraction / revolution full 360 ° of 2300 steps = 0.0152173 ... then round at 15.22 right?
YES 15.22 microns
I apologize for the question to neophyte just joined, but where I go to find the details that you say you sending me? :)) Thanks again, Biagio
You need to login to Sourceforge - it was a private message
Hi Biagio
So if you enter 15.22 as the stepsize value on the extra settings form then click close the form.
Next click on the extra settings again to reopen the form - you will see the value is remembered.
To send this to controller., set the value to 15.22, then on the same form click Enable in controiller so it is green, then click update on connect so its green then click close, after that connect to controller
Thanks Robert but after entering in extra setting the 15:22 value at the end does not accept it, and when I open it I find the value added is 500. I attach the following screens. thank you for your patience.
hmmm
What is your windows locale setting? Is it US-English or something else?
In Win10 this is bottom of taskbar. Also can access via Windows Key and Space.
If you set it to US English what happens?
Thanks Robert, just tried it but nothing to do. only if I enter the value without the second decimal (ie 15.2 instead of 15.22) The field accepts it as a whole, I think, as the new opening keeps me 152. I do not think is fine as 152 microns are thus not 15.22!
my windows local setting is italian
Hi Biagio
I can confirm that Windows App v2.3.5.0 I can enter 15.22 in as step size and it stays there - remembered. If this is not happening on your system, I suggest use control panel to remove windows application, reboot, then install latest windows app v2.3.5.0 and try again.
Cheers
Robert
Roberto ok, thank you for your immeasurable patience and through several attempts on my system looks like the 2.3.4.8 version is the one that manages to turn better. I take this opportunity just to bring one last question: taking a look at the pdf that speaks of options for configurations of EasyDriver board I noticed that in the full scheme of EasyDriver MS1 pin is connected to the pin D7 arduino while the photograph of that EasyDriver describes the connections to arduino pins are instructed to connect the MS1 pin to pin D5 arduino. Why this difference? just because the picture of EasyDriver belongs to the old version, not the 203? the right pin to be connected is the D7 or the D5? thank you.
Hi Biagio
You probably need to adjust the motor speed parameters - see PDF page 33 wirh section starting 8: CHECK THE SPEED SETTINGS
In v2350 these were altered. So need to be set for value that is best for your controller
Yes D7 is correct - I probably did not remove the older NON hw203 which from memory used D5 - thanks I will look at changing it.
Glad to hear you have success.
Robert
Ok I think pdf is now updated
It is the Rotary Encoder version that uses D5 and not D7
Last edit: brownrb 2016-11-11
thanks again Robert then wanting to create the version that makes use of the rotary encoder EasyDriver and what pattern should I follow? one related to both the drv8825 and EasyDriver or turnover relating solely EasyDriver? in which directory should I see?
If you want to build the rotary encoder version I suggest
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/DRIVER%20BOARDS/BOARD%20DRV8825%20EASYDRIVER%20Rotary%20Encoder/
and PDF
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/DRIVER%20BOARDS/BOARD%20OPTION%20DRV8825-EASYDRIVER%20ROTARY%20ENCODER.pdf/download
and firmware
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/CODE%20ARDUINO/DRV8825_F_RE/
You can use either DRV8825 or EasyDriver.
You really dont need Rotary Encoder unless for manual operation, no point with computer control as no we have a jogging control in the software. There is a software lag issue with the rotary encoder. IT works but if you try to turn the encoder too quickly the hardware cannot keep up with the pulses coming up and so it might keep stepping after you stop turning the encoder. It can take a little time to get the hang of it.
Cheers
Robert
Thanks again Robert then as a developer I you realize you recommend to the version using the buttons in place of the encoder as regards the manual controls as it turns out to be more powerful reactive, right?
As long as the RE is not turned at crazy speeds then its fine. Its only when the knob is turned too fast that the Software/Hardware cannot keep up and the issues arise. Over time one gets a feel for what is too fast... I am just trying to show the limitation and not raise expectation to a level where one expects too much. It does woek, and very reliabiliy, at lower knob turn speed. I think its better at manual focusing than the buttons.