Date   

Re: Motors not reversing with Control in Sky Planetarium

John Petterson
 

Let's identify where the problem is.  Try downloading a different planetarium program and use that instead.  Cartes du Ciel is one option for PC, there are others.

Do the motors run in correct/both directions when you have it slew to a location?  From one of you comments it appears they do not.  I suspect your cables, I had a similar issue but these tests below can help confirm that.

Assuming that you have verified the jumpers on the FYSETC are set correctly (see Kevin's comment):

What is the overall configuration?  Do you have a Wifi or network add on?  Using the Android App or the web interface can be helpful if either are available.

If you set

     #define AXIS1_DRIVER_REVERSE          ON

     #define AXIS2_DRIVER_REVERSE          ON

 

and then reload the software, does the direction change?  If not, then it is probably the cables - hard to point to driver cards if 4 of them are behaving the same.

And remember that movements around the pole can be confusing for a GEM.  See question 2 in the FAQ.

You can also send movement commands directly to the OnStep via the USB using the Arduino serial monitor (I think, someone will correct this if I am remembering incorrectly).  See the command protocol page of the Wiki.

John


Re: Connecting pwr ground to positive

ghpicard
 

The Schottky diodes are there to guarantee a proper power up sequence to the TMC drivers. They can work with VMOT on and no VIO, but not the opposite. With the diodes in place there is at least VIO-0.2V every time there is VIO applied. You can find this in the Wiki page of (at least) the MaxESP3 board.


On Sun, Jan 16, 2022, 12:09 George Cushing <stm32bluepill@...> wrote:
What confuses me are the Schottky diodes that link 3.3V to the higher voltage lines, in the maxstm circuit. 

Think that they are there to protect the TMC drivers from back EMF damage.


Slew problem

wa1vta01452
 

I have posted about this before. The DEC is running much slower than RA in slew mode using my laptop with ascom. I had changed EVERYTHING in the hardware twice now with no success. This morning I set up for bluetooth with the Android app and lo and behold, the DEC slewed just fine this time. I wonder if someone can take a look at my config.h to see where there may be an issue. I left off all below axis 2 since I am not using anything below that. The mount is a G11 and I am set up with TMC2130s with the 4 soldered jumpers.
Thanks,
Tom

// This configuration was automatically generated using the Online Configuration Generator
// Authored by: Khalid Baheyeldin
// Slewing Speed: 2.17 degrees/second (estimated)
// Generated on: 2021-03-04 13:41
// ---------------------------------------------------------------------------------------------------------------------------------
// Configuration for OnStep
 
/*
 *          For more information on setting OnStep up see http://www.stellarjourney.com/index.php?r=site/equipment_onstep 
 *                      and join the OnStep Groups.io at https://groups.io/g/onstep
 * 
 *           *** Read the compiler warnings and errors, they are there to help guard against invalid configurations ***
*/
 
// ---------------------------------------------------------------------------------------------------------------------------------
// ADJUST THE FOLLOWING TO CONFIGURE YOUR CONTROLLER FEATURES ----------------------------------------------------------------------
// <-Req'd = always must set, <-Often = usually must set, Option = optional, Adjust = adjust as req'd, Infreq = infrequently changed
 
// PINMAP ---------------------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#PINMAP
//   *** See the matching Pins.xxx.h file for your setup (found by looking in src/pinmaps/Models.h) with detailed information ***
//   *** to be sure it matches your wiring.            *** USE AT YOUR OWN RISK ***                                           ***
 
//      Parameter Name              Value   Default  Notes                                                                      Hint
#define PINMAP                        CNC3 //    OFF, Choose from: MiniPCB, MiniPCB2, MaxPCB, MaxPCB2, STM32Blue,             <-Req'd
                                          //         Ramps14, MaxESP2, MaxESP3.  Check Constants.h for more info.
 
// SERIAL PORT COMMAND CHANNELS ------------------------------------ see https://onstep.groups.io/g/main/wiki/6-Configuration#SERIAL
#define SERIAL_A_BAUD_DEFAULT        9600 //   9600, n. Where n=9600,19200,57600,115200 (common baud rates.)                  Infreq
#define SERIAL_B_BAUD_DEFAULT        9600 //   9600, n. See (src/HAL/) for your MCU Serial port # etc.                        Option
#define SERIAL_B_ESP_FLASHING         OFF //    OFF, ON Upload ESP8266 WiFi firmware through SERIAL_B with :ESPFLASH# cmd.    Option
#define SERIAL_C_BAUD_DEFAULT         ON //    OFF, n, ON for ESP32 Bluetooth.                                               Option
#define SERIAL_C_BLUETOOTH_NAME  "OnStep" // "On..", Bluetooth device name for ESP32.                                         Option
 
// MOUNT TYPE -------------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#MOUNT_TYPE
#define MOUNT_TYPE                    GEM //    GEM, GEM for German Equatorial, FORK for Equatorial Fork, or ALTAZM          <-Req'd
                                          //         Dobsonian etc. mounts. GEM Eq mounts perform meridian flips.
 
// USER FEEDBACK -------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#USER_FEEDBACK
#define LED_STATUS                     OFF //     ON, Blinks w/sidereal tracking otherwise steady on indicates activity.       Option
#define LED_STATUS2                   OFF //    OFF, ON Blinks 1s interval w/PPS sync, steady for gotos, off if in standby.   Option
#define LED_RETICLE                   OFF //    OFF, n. Where n=0..255 (0..100%) activates feature sets default brightness.   Option
#define BUZZER                        OFF //    OFF, ON, n. Where n=100..6000 (Hz freq.) for piezo speaker. ON for buzzer.    Option
#define BUZZER_STATE_DEFAULT          OFF  //    OFF, ON Start with piezo buzzer/speaker enabled.                              Option
 
// TIME AND LOCATION -------------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#TLS
#define TIME_LOCATION_SOURCE          OFF //    OFF, DS3231 (I2c,) DS3234 (Spi,) TEENSY (T3.2 internal,) or GPS source.       Option
                                          //         Provides Date/Time, and if available, PPS & Lat/Long also.
#define SerialGPS                     Serial3
#define SerialGPSBaud                 9600
 
// SENSORS -------------------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#SENSORS
// * = also supports ON_PULLUP or ON_PULLDOWN to activate MCU internal resistors if present.
#define WEATHER                       OFF //    OFF, BME280 (I2C 0x77,) BME280_0x76, BME280_SPI (see pinmap for CS.)          Option
                                          //         BMP280 (I2C 0x77,) BMP280_0x76, BMP280_SPI (see pinmap for CS.)
                                          //         BME280 or BMP280 for temperature, pressure.  BME280 for humidity also.
                                          
#define TELESCOPE_TEMPERATURE         OFF //    OFF, DS1820, n. Where n is the DS1820 s/n for focuser temperature.            Adjust
 
#define HOME_SENSE                    OFF //    OFF, ON*. Automatically detect and use home switches. For GEM mode only.      Option
#define HOME_SENSE_STATE_AXIS1       HIGH //   HIGH, State when clockwise of home position, as seen from front. Rev. w/LOW.   Adjust
#define HOME_SENSE_STATE_AXIS2       HIGH //   HIGH, State when clockwise of home position, as seen from above. Rev. w/LOW.   Adjust
                                          //         Signal state reverses when travel moves ccw past the home position.
 
#define LIMIT_SENSE                   OFF //    OFF, ON* limit sense switch close to Gnd stops gotos and/or tracking.         Option
#define LIMIT_SENSE_STATE             LOW //    LOW, For NO (normally open) switches, HIGH for NC (normally closed.)          Adjust
 
#define PEC_SENSE                     OFF //    OFF, ON*, n, sense digital OR n=0 to 1023 (0 to 3.3V or 5V) analog threshold. Option
#define PEC_SENSE_STATE              HIGH //   HIGH, Senses the PEC signal rising edge or use LOW for falling edge.           Adjust
                                          //         Ignored in ALTAZM mode.
 
#define PPS_SENSE                     OFF //    OFF, ON* enables PPS (pulse per second,) senses signal rising edge.           Option
                                          //         Better tracking accuracy especially for Mega2560's w/ceramic resonator.
 
// ST4 INTERFACE ------------------------------------------------------ see https://onstep.groups.io/g/main/wiki/6-Configuration#ST4
// *** It is up to you to verify the interface meets the electrical specifications of any connected device, use at your own risk ***
#define ST4_INTERFACE                 OFF //    OFF, ON, ON_PULLUP enables interface. <= 1X guides unless hand control mode.  Option
                                          //         During goto btn press: aborts slew or continue meridian flip pause home
#define ST4_HAND_CONTROL              OFF //    OFF, ON for hand controller special features and SHC support.                 Option
                                          //         Hold [E]+[W] btns >2s: Guide rate   [E]-  [W]+  [N] trk on/off [S] sync
                                          //         Hold [N]+[S] btns >2s: Usr cat item [E]-  [W]+  [N] goto [S] snd on/off
#define ST4_HAND_CONTROL_FOCUSER      OFF //    OFF, ON alternate to above: Focuser move [E]f1 [W]f2 [N]-     [S]+            Option
 
// GUIDING BEHAVIOUR ---------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#GUIDING
#define GUIDE_TIME_LIMIT                0 //      0, No guide time limit. Or n. Where n=1..120 second time limit guard.       Adjust
#define GUIDE_DISABLE_BACKLASH        OFF //    OFF, Disable backlash takeup during guiding at <= 1X                          Option
 
// TRACKING BEHAVIOUR -------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#TRACKING
#define TRACK_AUTOSTART               OFF //    OFF, ON Start with tracking enabled.                                          Option
#define TRACK_REFRACTION_RATE_DEFAULT OFF //    OFF, ON Start w/atmospheric refract. compensation (RA axis/Eq mounts only.)   Option
#define TRACK_BACKLASH_RATE            25 //     25, n. Where n=2..50 (x sidereal rate) during backlash takeup.               Option
                                          //         Too fast motors stall/gears slam or too slow and sluggish in backlash.
 
// SLEWING BEHAVIOUR ---------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#SLEWING
#define SLEW_RATE_BASE_DESIRED        2.0 //    1.0, n. Desired slew rate in deg/sec. Adjustable at run-time from            <-Req'd
                                          //         1/2 to 2x this rate, and as MCU performace considerations require.
#define SLEW_RATE_MEMORY              ON //    OFF, ON Remembers rates set across power cycles.                              Option
#define SLEW_ACCELERATION_DIST        8.0 //    5.0, n, (degrees.) Approx. distance for acceleration (and deceleration.)      Adjust
#define SLEW_RAPID_STOP_DIST          2.5 //    2.0, n, (degrees.) Approx. distance required to stop when a slew              Adjust
                                          //         is aborted or a limit is exceeded.
 
// PIER SIDE BEHAVIOUR -------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#SYNCING
#define MFLIP_SKIP_HOME               OFF //    OFF, ON Goto directly to the destination without visiting home position.      Option
#define MFLIP_PAUSE_HOME_MEMORY       ON //    OFF, ON Remember meridian flip pause at home setting across power cycles.     Option
#define MFLIP_AUTOMATIC_MEMORY        ON //    OFF, ON Remember automatic meridian flip setting across power cycles.         Option
 
#define PIER_SIDE_SYNC_CHANGE_SIDES   ON //    OFF, ON Allows sync to change pier side, for GEM mounts.                      Option
#define PIER_SIDE_PREFERRED_DEFAULT  EAST //   BEST, Stays on current side if possible. EAST or WEST switch if possible.      Option
 
// PARKING BEHAVIOUR ---------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#PARKING
#define STRICT_PARKING                OFF //    OFF, ON Un-parking is only allowed if successfully parked.                    Option
 
// MOTION CONTROL -------------------------------------------------- see https://onstep.groups.io/g/main/wiki/6-Configuration#MOTION
#define STEP_WAVE_FORM             SQUARE // SQUARE, PULSE Step signal wave form faster rates. SQUARE best signal integrity.  Adjust
 
// Stepper driver models (also see ~/OnStep/src/sd_drivers/Models.h for additional infrequently used models and more info.): 
// A4988, DRV8825, LV8729, S109, SSS TMC2209*, TMC2130* **, and TMC5160* ***
// * = add _QUIET (stealthChop tracking) for example "TMC2130_QUIET"
// ** = SSS TMC2130 if you choose to set stepper driver current (in mA) set Vref pot. 2.5V instead of by motor current as usual.
// *** = SSS TMC5160 you must set stepper driver current (in mA) w/ #define AXISn_TMC_IRUN (IHOLD, etc.)
 
// AXIS1 RA/AZM
// see https://onstep.groups.io/g/main/wiki/6-Configuration#AXIS1
#define AXIS1_STEPS_PER_DEGREE    48000.0 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0
#define AXIS1_STEPS_PER_WORMROT     48000 //  12800, n. Number of steps per worm rotation (PEC Eq mode only:)                <-Req'd
                                          //         n = (AXIS1_STEPS_PER_DEGREE*360)/reduction_final_stage
 
// Configured for G11 with 16:60 pulley gearing and 1/32 microstepping
 
#define AXIS1_DRIVER_MODEL            TMC2130  // TMC2130_QUIET //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS1_DRIVER_MICROSTEPS       32 //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS1_DRIVER_MICROSTEPS_GOTO  8 //    OFF, n. Microstep mode used during gotos.                                     Option
#define AXIS1_DRIVER_IHOLD            600 //    OFF, n, (mA.) Current during standstill. OFF uses IRUN/2.0                    Option
#define AXIS1_DRIVER_IRUN             800 //    OFF, n, (mA.) Current during tracking, appropriate for stepper/driver/etc.    Option
#define AXIS1_DRIVER_IGOTO            900 //    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_MIN              -180 //   -180, n. Where n= -90..-270 (degrees.) Minimum "Hour Angle" for Eq modes.      Adjust
                                          //         n. Where n=-180..-360 (degrees.) Minimum Azimuth for AltAzm mode.
#define AXIS1_LIMIT_MAX               180 //    180, n. Where n=  90.. 270 (degrees.) Maximum "Hour Angle" for Eq modes.      Adjust
                                          //         n. Where n= 180.. 360 (degrees.) Maximum Azimuth for AltAzm mode.
 
// AXIS2 DEC/ALT
// see https://onstep.groups.io/g/main/wiki/6-Configuration#AXIS2
#define AXIS2_STEPS_PER_DEGREE    48000.0 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0
 
#define AXIS2_DRIVER_MODEL            TMC2130  //  TMC2130_QUIET //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS2_DRIVER_MICROSTEPS       32 //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS2_DRIVER_MICROSTEPS_GOTO  8 //    OFF, n. Microstep mode used during gotos.                                     Option
#define AXIS2_DRIVER_IHOLD            600 //    OFF, n, (mA.) Current during standstill. OFF uses IRUN/2.0                    Option
#define AXIS2_DRIVER_IRUN             800 //    OFF, n, (mA.) Current during tracking, appropriate for stepper/driver/etc.    Option
#define AXIS2_DRIVER_IGOTO            900 //    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          ON //    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
 
#define AXIS2_LIMIT_MIN               -90 //    -90, n. Where n=-90..0 (degrees.) Minimum allowed declination.                Infreq
#define AXIS2_LIMIT_MAX                90 //     90, n. Where n=0..90 (degrees.) Maximum allowed declination.                 Infreq

 


Re: Wemos D1 R32 - Need info on Arduino IDE Config

Jamie Flinn
 

Hi All...
New boards arrived today and they immediately connect and can upload, so my original was duff! - I have loaded both OnStep X and 4.24 - can connect when the CNC3 borad is not connected - once I connect the board and power it up, Bluetooth device disappears  - I suspect there is a conflict when the CNC3 is attached and powered.... has anyone seen this before?

1) power wemos D1 R32 from 12v power  with no CNC3 attached = stable connection
2) power CNC3 from 12v and shunt power to wemos with CNC3 attached  = bluetooth for a short bit then it goes out

I was able to power and drive motors for a few rotations  but then the BT goes out and so too does the driving of RA (so I know it is more than juts BT going down)  - when this happens my phone can no longer see the BT device

Thoughts?....thank in advance


Re: New User - Encoders

John Petterson
 

Barry,

A little bit of background is probably valuable at this point.  I have not looked at the code that is servicing that interrupt for a while so it is possible this has some wrong information. If my memory is right the current code updates a second location pointer as the mount is moving, not simply counting pulses but rather recalculating the pointing location as pulses come in. This second encoder location pointer is accumulated on the microcontroller that is running the encoders and network and not directly available on the main processor so doing anything with it is a bit more complex than it looks at first glance.

At some interval depending on your settings it will compare that encoder location with the mount's position and update the mount's position with the encoders reported position if the difference is over a specified value.  (It also moves the data in the other direction when you do an alignment action, setting the encoder's reported position to the mount''s position.) I think it does not do that update during moves however (probably because the time required to move the data between processors makes it less accurate during the moves) but only during tracking, and the comparison value used to determine if it should be updated is generally too high to be valuable in correcting tracking. 

So based on that you may rethink your desire to even use the encoders.  I am happy to have them because I have a Losmandy AZ8 and can point the mount manually wherever I want very quickly and it will resume tracking correctly - not easy to do with an alt-az mount without those encoders.  It also has clutches that allow slippage unless you really lock them down so minor slips are correctable during slews (I simply hit the slew button again a second after it stops and the mount corrects to the right target.) 

If you decide to go forward with the encoders, given the discussion above I think I would be more inclined to try to use a divide by 8 or divide by 16 circuit on each of the two sides of the encoders, seed one of them with half of that number at startup to keep them close to evenly spaced, and feed that output back into the existing software rather than redesigning the whole thing to accumulate counters somewhere else and then try to figure out how to update the pointing position.

John


Re: New User - Encoders

smith_barry
 

Hi John, if the microcontroller is doing the quad decode then I agree with what you are seeing.  I am not sure how implementable it is but there are chips that do the quadrature and counting for you and then can download via the I2C bus which might be an alternative.  I have some chips from IC-Haus that allow up to 2048 interpolation of sin/cos encoders but its a good 5 years since I looked at them in respect of communication between the interpolator and microcontroller.  If you cut out the need for quad decode I would think you could just count single pulses on a pin?  OK this would lower the line count by four but you might be able to track a higher overall count rate?
Barry


Re: DIY One Piece Wormblock for Losmandy GM8/G11

smith_barry
 

Hi Bob, I dont really know as it was second hand to me.  I have got the mount out from the store and remeasured.  The original was 8mm thick and my replacement (in clear anodized) is 12mm.  I also made up and fitted an extension block to help the axis hitting the motor.  At the time I did this I had been looking at variations in worm and axis rotation hence the rather neat canon encoder attached to the worm shaft (81,000 ppr) and the Heidenhain ERN180 encoder and IBV interpolation box giving if I recall right around 6 million ppr.  These were all obtained very cheap on ebay.  Unfortunately my plans to use the mount on a pier in my garden have been put on hold due to new light pollution issues where I live.   As you can see the system has dc servos on at the moment, my real interests with OnStep are to use it to finally finish a large harmonic drive mount thats been on the go for the past 20 years and to make a smaller mount I can set up in the field.
Barry

  


Re: ZWO harmonic drive

George Cushing
 

I leaned Vlad's way until I saw how Kevin Ma used such a drive to convert a Meade LX fork. The fork originally was equipped with a tangent arm Dec adjuster. I had been advising folks to avoid these old forks due to the difficulty of retrofitting a worm gear assembly. Kevin's solution made these mounts a viable choice.


Re: Connecting pwr ground to positive

George Cushing
 

What confuses me are the Schottky diodes that link 3.3V to the higher voltage lines, in the maxstm circuit. 

Think that they are there to protect the TMC drivers from back EMF damage.


Re: Connecting pwr ground to positive

George Cushing
 

The op amp is part of what my diagram calls battery charging circuit. It's a LM321 low power single op amp. The TI part is marked A63A and is what my "WeMOS" D1 R32s uses. The M7s are Zener diodes.

Not sure why a charging circuit is provided as the battery shown on the circuit diagram isn't present. The TI datasheet says, "The input common mode range includes ground and therefore the device is able to operate in single supply applications as well as in dual supply applications. It is also capable of comfortably driving large capacitive loads."

So maybe it's helping deal with some of the 3 power levels present on the circuit?



Re: Motors not reversing with Control in Sky Planetarium

kevin
 

Is that photo Gerry's ?, the jumpers are set to SPI mode


Re: Dobson goto with Onstep

Khalid Baheyeldin
 

On Sun, Jan 16, 2022 at 06:15 AM, <lrosellpardo@...> wrote:
I have big backlash in az axis about 30arc/min.

Can i get better results or it's normal acuraccy?
Not sure if your question is about the length the object is in the field
of view, or the backlash.

You can easily tune the backlash using the daylight method described
on this page on the Wiki.


Re: Started new OnStep hardware design

Khalid Baheyeldin
 

On Sun, Jan 16, 2022 at 02:58 AM, John Scherer wrote:
Maybe he just wants to design a small board and share it with the group, for his own reasons.  I for one welcome this and do this often myself (design boards).
There are certainly valid reasons for creating a new board.
For example, to fill a void in the current offerings, correct a shortcoming, or having a smaller footprint, ...etc.
Or just to learn how to do it, and so on ...

What I am puzzled by in this case, is that he thinks the current boards have a restriction (can only use StepStick form factor drivers), and therefore cannot not do what he wants (use external drivers).
And based on those misconceptions, and wants to create a whole new board.

The truth is all boards can use external drivers. It is merely a matter of wiring.

He is also thinking of modifying the code for that, with all the long term maintenance headaches that this entails, while the code already has support for external drivers.

Reinventing the wheel ...


Re: Motors not reversing with Control in Sky Planetarium

Howard Dutton
 

Could check the DIR pins on the drivers to see if they go from 0V to 3.3V as they should when you change directions.  Just be super careful to only touch the yellow pins with the volt meter probe.


Re: Motors not reversing with Control in Sky Planetarium

Howard Dutton
 

On Sun, Jan 16, 2022 at 04:37 AM, Gerry Byrne wrote:
Here are my Axis Stepper Driver Config.h settings. Can they explain the fact that the motors will only turn in one direction?
There are no settings in Config.h that'd cause what you are describing.


Re: Motors not reversing with Control in Sky Planetarium

Howard Dutton
 

On Sun, Jan 16, 2022 at 04:05 AM, Gerry Byrne wrote:
It occurs to me that the following might be factors: I am giving the motors arbitrary instructions without setting Lat and Long or time
Its a good idea to do this.

and paying no heed to parking or unparking from home position.
Parking functionality is separate from home/homing (the default startup position,) generally its best to ignore parking until/unless you need it.

Could this be an issue?
I seriously doubt it.


Re: Motors not reversing with Control in Sky Planetarium

Gerry Byrne
 
Edited

Here are my Axis Stepper Driver Config.h settings. Can they explain the fact that the motors will only turn in one direction?
Gerry


// AXIS1 RA/AZM
// see https://onstep.groups.io/g/main/wiki/6-Configuration#AXIS1
#define AXIS1_STEPS_PER_DEGREE 16955.5555 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0
#define AXIS1_STEPS_PER_WORMROT    160000 //  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         LV8729 //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS1_DRIVER_MICROSTEPS        16 //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS1_DRIVER_MICROSTEPS_GOTO  OFF //    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 16955.5555 //  12800, n. Number of steps per degree:                                          <-Req'd
                                          //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0

#define AXIS2_DRIVER_MODEL         LV8729 //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS2_DRIVER_MICROSTEPS        16 //    OFF, n. Microstep mode when tracking.                                        <-Often
#define AXIS2_DRIVER_MICROSTEPS_GOTO  OFF //    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

#define AXIS2_LIMIT_MIN               -91 //    -91, n. Where n=-91..0 (degrees.) Minimum allowed declination.                Infreq
#define AXIS2_LIMIT_MAX                91 //     91, n. Where n=0..91 (degrees.) Maximum allowed declination.                 Infreq


On 16/01/2022 12:09, Gerry Byrne via groups.io wrote:
Kevin,
As you may see from my latest post I tried some spare LV8729s and it made no difference. But that doesn't rule out the probability I may have got duds!
Gerry



On 16/01/2022 11:04, kevin via groups.io wrote:
I plugged a LV8729  driver in reversed once ( in a different board ) and afterwords when installed correctly it would only work in one direction. New one worked OK.

I don't have one of those boards but presumably you have the FYSETC pinmap loaded, anyone know if there are there any changes between board revisions required?


--
Copernicus


--
Copernicus


Re: Motors not reversing with Control in Sky Planetarium

Gerry Byrne
 

Kevin,
As you may see from my latest post I tried some spare LV8729s and it made no difference. But that doesn't rule out the probability I may have got duds!
Gerry



On 16/01/2022 11:04, kevin via groups.io wrote:
I plugged a LV8729  driver in reversed once ( in a different board ) and afterwords when installed correctly it would only work in one direction. New one worked OK.

I don't have one of those boards but presumably you have the FYSETC pinmap loaded, anyone know if there are there any changes between board revisions required?


--
Copernicus


Re: Motors not reversing with Control in Sky Planetarium

Gerry Byrne
 

1. I swapped the wiring for the two motors but both continued to  drive one direction only, no reversal possible either in slewing mode or using the control in an attempt to "nudge" the motors in a reverse direction. Both motors resolutely continued to turn anticlockwise only.
2. I swapped the LV8729 drivers for two spares but there was no change in behaviour. Both motors continued to only turn clockwise. The replacements spares had not been adjusted yet for VRef but, apart from getting very hot,  they appeared to act normally. I then put the original drivers back on the board.

It occurs to me that the following might be factors: I am giving the motors arbitrary instructions without setting Lat and Long or time and paying no heed to parking or unparking from home position. Could this be an issue?

Ideas?
Gerry







 

On 16/01/2022 09:36, Gerry Byrne via groups.io wrote:
Mike,
That's a very good point. However I'm using a FYSETC S6 V2 which requires very little soldering. At the same time I have been using a temporary bench  testing connection between the driver and the Axis 1 stepper motor. Could this be an issue, I wonder? I shall re-run the test, this time using the wiring harness, and the driver, for the second motor in its place.

Where does the DIR pin occur? Is it on the main processor? or the driver card (LV8729)? Perhaps I have incorrect, or faulty jumpering? I'll check through them one at a time.
Gerry


On 16/01/2022 02:27, Mike Ahner wrote:
On Sat, Jan 15, 2022 at 05:44 PM, Gerry Byrne wrote:
the motor would have to reverse to reach it but in every case the motor turns in the same direction.
Hi Gerry,
I wonder if your DIR pin is toggling properly. It should change from HIGH to LOW or LOW to HIGH with each required direction change. I'm not familiar with FYSETC, but if you had to wire anything, I suggest checking your soldering, wire connections, etc. If you have a bad connection and the DIR pin never toggles, then the stepper driver will not change direction.

-Mike 


--
Copernicus


--
Copernicus


Dobson goto with Onstep

lrosellpardo@...
 

Hello, I've converted my 8" Dob with Onstep. yesterday I did some test, I did 3 star align (not perfect) but I managed to get a star at 150x during 20 min in FoV.

I have big backlash in az axis about 30arc/min.

Can i get better results or it's normal acuraccy?

5401 - 5420 of 46388