Date   

Re: Simple smart hand controller

Jerry
 

The value of the pull ups is not critical. 2.2k is lower than I would use personally, i usually use 4.7k. But anything in that range will be fine. 

-Jerry

On Apr 8, 2020, at 9:57 PM, Matthias <post@...> wrote:

Hello, Dave,
That's exactly what I thought. The system of pull-ups is clear and now also the twisting or non-twisting concept. Thank you very much for your patience and detailed answer. I will let you know if it works. Matthias


Re: Simple smart hand controller

Matthias
 

Hello, Dave,
That's exactly what I thought. The system of pull-ups is clear and now also the twisting or non-twisting concept. Thank you very much for your patience and detailed answer. I will let you know if it works. Matthias


Re: Track speed is very hy #define

Jorge Oliveira
 
Edited

Olá amigo, qual tipo de onstep está usando? 
Eu estou usando um kit vendido aqui mesmo , e uso dois Nema 17, está tudo perfeito.
Jorge 

Hello friend, what type of onstep are you using?
I'm using a kit sold right here, and I use two Nema 17's, everything is perfect.
Em qua, 8 de abr de 2020 20:29, Khalid Baheyeldin <kbahey@...> escreveu:

Looks like you are making the travel mount that Roman Hujer designed.

Is that correct?

 

 


Re: My OnStep conntroller on base Mega2560

hmsampaio@...
 

Hi, how you does to work your small travel 3d mount with steps motor planetary ruduction 100:1, unhappy my mount doesn't work in track speed, is very fast, I try all ways. Please help me 
Thanks 


Re: Track speed is very hy #define

Khalid Baheyeldin
 

Looks like you are making the travel mount that Roman Hujer designed.

Is that correct?


Re: Steppers and EQM-35

Khalid Baheyeldin
 

On Wed, Apr 8, 2020 at 06:54 PM, Kane Mcvicar wrote:
So I want to modify a eqm-35 non goto to be a goto mount using onstep,
The question I have is which type of drive would be most suitable, more for astro photography than high slew rates, the RA is 180 tooth and the Dec is 65 tooth.
I'm thinking a precision planetary drive on nema17 200 step motor with a ratio of 1:40 for the DEC, and a planetary with a ratio of 1:20 for the RA, both coupled to the moint with a 1:1 drive belt to reduce harmonics. Would these ratios be suitable? Or should I lower or increase them? 
This is a good strategy that is not in wide use yet.
The motors you quoted should do a decent job with very good resolution, using 1/16 microsteps.
And with that, you should be able to get 2.5 to 3 degree/second, so not slow at all (but not super fast either).

My concern would be the RPM of the motors. If you use 10:1 for RA, and 30:1 for DEC, the RPM is lower.
In that case 1/32 microsteps will be better.

The geared motors allow using the 1:1 pulley which need less space, and have less chance of obstruction.

Most imagers prefer not to have any backlash, and therefore opt for 400 steps motors and a 3:1 pulley reduction.
That leaves out only the backlash in the motor and in the worm/wheel.

But even with some backlash, things do work out. OnStep can compensate for backlash, and Ph2 too.
So worth exploring this approach.

The other option would be a 400 step motor with no gearbox and directly couple it with a suitable drive belt and ratio? Although I wouldn't get the high ratios as I would with the planetary gearboxes.
See above. That is what most OnStep users do.

In that case, RA should work with 3:1 with good resolution.
However, DEC would be a challenge since you need 6:1 for a decent resolution.
Finding a pulley that is 6:1 will be a problem.

In the Wiki Showcase page, check the EQ3 and CG-4 mounts, some have a 65:1 worm wheel on DEC.


Steppers and EQM-35

Kane Mcvicar
 

Hi all
So I want to modify a eqm-35 non goto to be a goto mount using onstep,
The question I have is which type of drive would be most suitable, more for astro photography than high slew rates, the RA is 180 tooth and the Dec is 65 tooth.
I'm thinking a precision planetary drive on nema17 200 step motor with a ratio of 1:40 for the DEC, and a planetary with a ratio of 1:20 for the RA, both coupled to the moint with a 1:1 drive belt to reduce harmonics. Would these ratios be suitable? Or should I lower or increase them? 

The other option would be a 400 step motor with no gearbox and directly couple it with a suitable drive belt and ratio? Although I wouldn't get the high ratios as I would with the planetary gearboxes. 

As I said I'm not too worried about the slew speed as long as its still moves to a target within under a minute. 

Thanks 
Kane 


Re: Track speed is very hy #define

Howard Dutton
 

Custom hardware?  How are drivers mode control pins wired in?


Re: Simple smart hand controller

Dave Schwartz
 

Yes, your example where you have the N from the momentary switch (pushbutton) connected to the N input pin on the ESP32S and also to N on the resistor network is correct. I won't explain the function of the pull-up resistors - you can look it up it you need to know more. The 7-resistor network is for the pushbuttons, the 4-resistor network is for the auxiliary RJ12 (guider pass-through) jack performing the same function as those resistors in the controller. If you're not going to need the pass-through function you can leave off the 4-resistor network and RJ2.

Typically we don't draw all the lines between the points in a multiply-connected circuit on the schematic because it gets very messy very quickly. Its a convention that every point identified by the same-labelled pentagon shape is somehow connected in the same 'net' by the traces of the PCB. It tends to leave a bunch of seemingly-disconnected parts but makes sense once you understand the convention.

On 2020-04-08 4:04 p.m., matzgp@... wrote:
Hello, Dave and thanks for the quick answer!
I understood about the resistors, but is my exemplary wiring (N) correct?
One more question, sorry, which socket (RJ12) is for the ST4 connector on the onstep... I think RJ1.
I think this wiring from Khalid works without the 5-way switch and yes a 1.3" is much better.
Happy Easter, despite covid...
Matthias


Re: Track speed is very hy #define

hmsampaio@...
 

i´m using arduino mega 2560 classic


Re: Track speed is very hy #define

hmsampaio@...
 

Oi, obrigado por responder. Minha montagem é um projeto sobre uma montagem 3d de viagem pequena e pequena, com dois motores de passo com redução de planetário 100/1, mas quando eu finalizo tudo, a velocidade da pista é muito alta.
esta a minha maneira de mudar no arduino IDE

// AXIS1 RA / AZM
// consulte https://onstep.groups.io/g/main/wiki/6-Configuration#AXIS1
#define AXIS1_STEPS_PER_DEGREE 1777.77778 // 12800, n. Número de etapas por grau: <-Req'd
                                          // n = (stepper_steps * micro_steps * overall_gear_reduction) /360.0
#define AXIS1_STEPS_PER_WORMROT 64000 // 12800, n. Número de etapas por rotação do worm (somente modo PEC Eq :) <-Req'd
                                          // n = (AXIS1_STEPS_PER_DEGREE * 360) / conversion_final_stage
 
#define AXIS1_DRIVER_MODEL DRV8825 // OFF, (Veja acima.) Modelo de driver de passo. <-Often
#define AXIS1_DRIVER_MICROSTEPS 32 // DESLIGADO, n. Modo Microstep ao rastrear. <-Often
#define AXIS1_DRIVER_MICROSTEPS_GOTO 16 // OFF, n. Modo Microstep usado durante gotos. Opção
#define AXIS1_DRIVER_IHOLD OFF // OFF, n, (mA.) Corrente durante a parada. OFF usa a opção IRUN / 2.0
#define AXIS1_DRIVER_IRUN OFF // OFF, n, (mA.) Corrente durante o rastreamento, apropriada para stepper / driver / etc. Opção
#define AXIS1_DRIVER_IGOTO OFF // OFF, n, (mA.) Corrente durante as rotações. OFF usa o mesmo que IRUN. Opção
#define AXIS1_DRIVER_REVERSE OFF // OFF, ON Inverte a direção do movimento ou inverte a fiação para corrigir. <-Often
#define AXIS1_DRIVER_STATUS OFF // OFF, TMC_SPI, HIGH ou LOW. Pesquisa para informações de status do driver / detecção de falhas. Opção
 
#define AXIS1_LIMIT_UNDER_POLE 180 // 180, n. Onde n = 150..180 (graus). Ângulo máximo da hora do HA + ou - para os modos Eq. Infreq
#define AXIS1_LIMIT_MAXAZM 360 // 360, n. Onde n = 180..360 (graus.) Azimute máximo + ou - somente para o modo AltAzm. Infreq
 
// AXIS2 DEZ / ALT
// consulte https://onstep.groups.io/g/main/wiki/6-Configuration#AXIS2
#define AXIS2_STEPS_PER_DEGREE 1760.88889 // 12800, n. Número de etapas por grau: <-Req'd
                                          // n = (stepper_steps * micro_steps * overall_gear_reduction) /360.0
 
#define AXIS2_DRIVER_MODEL DRV8825 // OFF, (Veja acima.) Modelo de driver de passo. <-Often
#define AXIS2_DRIVER_MICROSTEPS 32 // DESLIGADO, n. Modo Microstep ao rastrear. <-Often
#define AXIS2_DRIVER_MICROSTEPS_GOTO 16 // OFF, n. Modo Microstep usado durante gotos. Opção
#define AXIS2_DRIVER_IHOLD OFF // OFF, n, (mA.) Corrente durante a parada. OFF usa a opção IRUN / 2.0
#define AXIS2_DRIVER_IRUN OFF // OFF, n, (mA.) Corrente durante o rastreamento, apropriada para stepper / driver / etc. Opção
#define AXIS2_DRIVER_IGOTO OFF // OFF, n, (mA.) Corrente durante as rotações. OFF usa o mesmo que IRUN. Opção
#define AXIS2_DRIVER_POWER_DOWN OFF // OFF, ON Desliga 10s após o movimento parar ou 10min após o último guia <= 1x. Opção
#define AXIS2_DRIVER_REVERSE OFF // OFF, ON Inverte a direção do movimento ou inverte a fiação para corrigir. <-Often
#define AXIS2_DRIVER_STATUS OFF // OFF, TMC_SPI, HIGH ou LOW. Pesquisa para informações de status do driver / detecção de falhas. Opção
#define AXIS2_TANGENT_ARM OFF // OFF, ON + faixa de limite abaixo. Definir cntr com [Redefinir página inicial] Voltar cntr com / [Localizar página inicial] Infreq


Re: Track speed is very hy #define

hmsampaio@...
 

Hi, thanks to respond. My mount is a project about thingverse, small travel 3d mount, it have two step motors whith planetarium reduction 100/1, but when i finist all, the track speed is very high.
this my way to change in arduino IDE

// AXIS1 RA/AZM
// see https://onstep.groups.io/g/main/wiki/6-Configuration#AXIS1
#define AXIS1_STEPS_PER_DEGREE    1777.77778 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0
#define AXIS1_STEPS_PER_WORMROT     64000 //  12800, n. Number of steps per worm rotation (PEC Eq mode only:)                <-Req'd
                                          //         n = (AXIS1_STEPS_PER_DEGREE*360)/reduction_final_stage
 
#define AXIS1_DRIVER_MODEL            DRV8825 //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS1_DRIVER_MICROSTEPS       32 //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS1_DRIVER_MICROSTEPS_GOTO  16 //    OFF, n. Microstep mode used during gotos.                                     Option
#define AXIS1_DRIVER_IHOLD            OFF //    OFF, n, (mA.) Current during standstill. OFF uses IRUN/2.0                    Option
#define AXIS1_DRIVER_IRUN             OFF //    OFF, n, (mA.) Current during tracking, appropriate for stepper/driver/etc.    Option
#define AXIS1_DRIVER_IGOTO            OFF //    OFF, n, (mA.) Current during slews. OFF uses same as IRUN.                    Option
#define AXIS1_DRIVER_REVERSE          OFF //    OFF, ON Reverses movement direction, or reverse wiring instead to correct.   <-Often
#define AXIS1_DRIVER_STATUS           OFF //    OFF, TMC_SPI, HIGH, or LOW.  Polling for driver status info/fault detection.  Option
 
#define AXIS1_LIMIT_UNDER_POLE        180 //    180, n. Where n=150..180 (degrees.) Max HA hour angle + or - for Eq modes.    Infreq
#define AXIS1_LIMIT_MAXAZM            360 //    360, n. Where n=180..360 (degrees.) Max Azimuth + or - for AltAzm mode only.  Infreq
 
// AXIS2 DEC/ALT
// see https://onstep.groups.io/g/main/wiki/6-Configuration#AXIS2
#define AXIS2_STEPS_PER_DEGREE    1760.88889 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0
 
#define AXIS2_DRIVER_MODEL            DRV8825 //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS2_DRIVER_MICROSTEPS       32 //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS2_DRIVER_MICROSTEPS_GOTO  16 //    OFF, n. Microstep mode used during gotos.                                     Option
#define AXIS2_DRIVER_IHOLD            OFF //    OFF, n, (mA.) Current during standstill. OFF uses IRUN/2.0                    Option
#define AXIS2_DRIVER_IRUN             OFF //    OFF, n, (mA.) Current during tracking, appropriate for stepper/driver/etc.    Option
#define AXIS2_DRIVER_IGOTO            OFF //    OFF, n, (mA.) Current during slews. OFF uses same as IRUN.                    Option
#define AXIS2_DRIVER_POWER_DOWN       OFF //    OFF, ON Powers off 10sec after movement stops or 10min after last<=1x guide.  Option
#define AXIS2_DRIVER_REVERSE          OFF //    OFF, ON Reverses movement direction, or reverse wiring instead to correct.   <-Often
#define AXIS2_DRIVER_STATUS           OFF //    OFF, TMC_SPI, HIGH, or LOW.  Polling for driver status info/fault detection.  Option
#define AXIS2_TANGENT_ARM             OFF //    OFF, ON +limit range below. Set cntr w/[Reset Home] Return cntr w/[Find Home] Infreq


Re: Simple smart hand controller

Matthias
 

Hello, Dave and thanks for the quick answer!
I understood about the resistors, but is my exemplary wiring (N) correct?
One more question, sorry, which socket (RJ12) is for the ST4 connector on the onstep... I think RJ1.
I think this wiring from Khalid works without the 5-way switch and yes a 1.3" is much better.
Happy Easter, despite covid...
Matthias


Re: DEC after flip

Howard Dutton
 

"Strange" pointing problems can be caused by not configuring OnStep's site (Latitude, Longitude, UTC Offset) and Time correctly.

If those are correct and the motion still isn't right OnStep's Config.h file has settings to reverse each axes direction of motion....

To determine if each axis is moving in the proper direction I use a planetarium program and "zoom in" on the NCP area then do short gotos left-right of the pole (at an hour angle of +6 or -6) and watch to be sure the mount mimics those motions to verify Declination is correct.  Once that is done and working I do a goto further away from the pole and up into the visible sky toward the Zenith a bit.  If the 'scope starts to point up, RA is correct.  If it points down, RA is reversed.

Sometimes folks misconfigure the steps per degree values in Config.h and that leads to bad pointing also so if all else fails double check those figures also.


Re: Simple smart hand controller

Dave Schwartz
 

The resistor networks are 2.2K (2K would also work). You can use discrete resistors by tying one end of each to the common pin (pin 1... the square pad) and then then other ends into the individual round pad. The idea is that the resistance is 2.2K between the square pad and each round pad.

The other issue is that the ESP32S SHC PCB on EasyEDA is designed for a 5-way pushbutton in the center ... not something everyone is likely to have lying around.

Your schematic shows a .98" display but the 1.3" is much more legible for very little extra cost. Some people are starting to use the 2.4" display but I don't think there's a compelling case for it because its much more expensive but doesn't provide much more in terms of legibility (and the resolution is no better so it's not like you can cram more info on it).


On April 8, 2020 2:38:39 PM EDT, Khalid Baheyeldin <kbahey@...> wrote:
I don't know if 4.7K are enough or not. Dave Schwartz will answer this.
 
But a resistor array can be made from discrete resistors.
For example:

https://learn.pimoroni.com/tutorial/hacks/inline-resistor-network
 
For the SHC, you need a display too, and buttons.
All the parts are on the BOM of the EasyEDA project.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: Simple smart hand controller

Matthias
 

... like that way?


Re: Simple smart hand controller

Khalid Baheyeldin
 

I don't know if 4.7K are enough or not. Dave Schwartz will answer this.
 
But a resistor array can be made from discrete resistors.
For example:

https://learn.pimoroni.com/tutorial/hacks/inline-resistor-network
 
For the SHC, you need a display too, and buttons.
All the parts are on the BOM of the EasyEDA project.


Re: Simple smart hand controller

Matthias
 

Hello Khalid, thank you for pointing that out. Honestly, I'm not familiar with this kind of schematic. Unfortunately I only have normal 4.7K resistors. How do I have to connect them instead of the resistor networks...
Best regards Matthias


DEC after flip

Christian Schulbert <chris.schulbert@...>
 

Hi,
I am writing for a friend, who has a Saturn mount and a Teensy 3.2 but can't write english very well. After a meridian flip the scope is pointing to the ground, seems like the DEC is inversed. Any help would be appreciated, on where to setup the system in oder to fix this problem.
Clear skies!
Chris


Re: Simple smart hand controller

Khalid Baheyeldin
 

On Wed, Apr 8, 2020 at 12:38 PM, <matzgp@...> wrote:
Hello, Howard, or whom it may concern...
now that the latest version is working i want to build the (simple) smart hand controller. Can I build and operate the Simple smart hand controller (with the ESP_wroom_32s) with the current onstep master (version 3.2) I think the schematic was originally for the teenAstro project. Or is there a better current schematic ?
Best regards Matthias and stay healthy!
There is already an ESP Smart Hand Controller that uses the ESP32 microcontroller.

Schematic and PCB are here

https://easyeda.com/dschwartz/onstep-shc