Date   

Re: ESP32 wireless SHC (wSHC)

Dave Schwartz
 

I initially built a wSHC using only a pair of AAA rechargeable Ni-MH batteries, boosted to 5V with a DC-DC converter. This gave an 'acceptable-to-me' battery life over 5 hours and a full night if you kept a spare set handy. I used this configuration because it was what would fit within the case when retrofitting one of my existing SHCs with both RJ-45 sockets.

Based on a suggestion by member Sergei, I have put together a new wSHC with no RJ-45 sockets where I can embed a 4xAAA battery holder (actually 2 2xAAA holders glued together) flush with the back of the case and am now doing battery life testing on it. Sergei indicated that he gets, if I recall correctly, 14 hours out of his. Again, there is no increase in the size of the unit.

This will work with any type of AAA battery because both electronic modules (the ESP32 and the display) run on 3.3V internally and have regulators on-board that will handle the 6+V of alkaline batteries yet still not drop out until the Ni-MH battteries are deeply discharged. The button pullup resistors are also fed from the ESP32's 3.3V output so there is no issue with 5 (or 6) volt tolerance on the button input pins.

On 2021-12-17 11:04 a.m., kevin_kevin_kevin via groups.io wrote:
If they have USB connectors for charging and powering a device to "charge" it  they should have an internal circuit that sorts it all out. i have used a number of them as a convenient way of powering some of my Arduino projects. As mentioned in the Wiki and i thought i would also mention in case you hadn't noticed that bit, that i have had issues with a few of them when powering something that doesn't take a lot of current. THe early ones with a power on/off switch were OK but some of the new "smart" ones without a switch do an auto power off so that they don't flatten their battery when your "phone" is charged.
i don't know what current an ESP SHC takes but if you find it doesn't work from a "charger pack" but does from a USB mains adapter that may be an issue.


Re: confusion over settings for stepper motors

Khalid Baheyeldin
 

I don't know how you reached the steps per degree value that you have in Config.h
with the numbers you are quoting (GR1 = 10).

Your spreadsheet should be like this:

31,911.11111    = 200,    16,    10, 359
31,911.11111    = 200,    16,    10, 359

Go to the Online Configuration Generator, and enter those values again,
then edit the file to add the IRUN and IGOTO values, and you should be
good.

Oh, and don't use VQUIET, just QUIET will do.


confusion over settings for stepper motors

Guy Brandenburg
 

We are having some difficulty getting the settings right for our stepper motors. I know this because on my desk, the RA stepper turns about twice as slow as it should (1 rotation every ~24 seconds instead of every 12 seconds that the previous drive made) and because both steppers make horrible screaming noises that rise both in pitch and in volume; the steppers eventually stop moving at all but continue with the noises when we try to slew towards any dummy target.

Here are the data:

We have two MAXesp boards that were kindly put together by George Cushing and Ken Hunter, respectively, and have NEMA23 steppers that have 200 steps per turn. We installed TMC5160 stepper drivers, and used Khaled B's spreadsheet and Ken's advice to try to set the proper parameters in CONFIG.H. 

The RA drive that we are replacing used to turn at 5 RPM when tracking. From the stepper gear to the worm gear is a 10:1 ratio, and the Byers main gear has 359 teeth. I attach what I think are the pertinent parts of our CONFIG file.

#define AXIS1_STEPS_PER_DEGREE    7977.77778  //  12800, n. Number of steps per degree: 2393    
                                              //         n = (stepper_steps * micro_steps * overall_gear_reduction)/359.0
#define AXIS1_STEPS_PER_WORMROT       16000   //      0, n. Number steps per worm rotation (PEC Eq mode only, 0 disables PEC.)   <-Req'd
                                              //         n = (AXIS1_STEPS_PER_DEGREE*360)/reduction_final_stage

#define AXIS1_DRIVER_MODEL  TMC5160_VQUIET    //    OFF, (See above.) Stepper driver model.                                  <-Often
#define AXIS1_DRIVER_MICROSTEPS       8       //    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             800     //    OFF, n, (mA.) Current during tracking, appropriate for stepper/driver/etc.    Option
#define AXIS1_DRIVER_IGOTO            1000    //    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           TMC_SPI //    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.

and

#define AXIS2_STEPS_PER_DEGREE   7977.77778  //  12800, n. Number of steps per degree:                                          <-Req'd
                                             //         n = (stepper_steps * micro_steps * overall_gear_reduction)/360.0

#define AXIS2_DRIVER_MODEL  TMC5160_VQUIET  //    OFF, (See above.) Stepper driver model.                                      <-Often
#define AXIS2_DRIVER_MICROSTEPS       8     //    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             800   //    OFF, n, (mA.) Current during tracking, appropriate for stepper/driver/etc.    Option
#define AXIS2_DRIVER_IGOTO            1000  //    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               -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



Thanks in advance for any advice.



Re: #sws #wemos #BCG Issue: no pairing between WEMOS ESP 32 and BCG #sws #wemos #bcg

adrien.wyns@...
 

Correction:


Re: #sws #wemos #BCG Issue: no pairing between WEMOS ESP 32 and BCG #sws #wemos #bcg

adrien.wyns@...
 

The version of ESP32 board is the V2.0.0. I share the SWS file (compressed rar.)  and also a print screen of the Tool TAB.


Re: #sws #wemos #BCG Issue: no pairing between WEMOS ESP 32 and BCG #sws #wemos #bcg

adrien.wyns@...
 

The WEMOS ESP32 has been flashed and uploaded as described on the ...wiki/26881. It is just not connecting.


Re: ESP32 wireless SHC (wSHC)

kevin
 

If they have USB connectors for charging and powering a device to "charge" it  they should have an internal circuit that sorts it all out. i have used a number of them as a convenient way of powering some of my Arduino projects. As mentioned in the Wiki and i thought i would also mention in case you hadn't noticed that bit, that i have had issues with a few of them when powering something that doesn't take a lot of current. THe early ones with a power on/off switch were OK but some of the new "smart" ones without a switch do an auto power off so that they don't flatten their battery when your "phone" is charged.
i don't know what current an ESP SHC takes but if you find it doesn't work from a "charger pack" but does from a USB mains adapter that may be an issue.


Re: #sws #wemos #BCG Issue: no pairing between WEMOS ESP 32 and BCG #sws #wemos #bcg

Drew 🔭📷🚴‍♂️
 

If it is just not connecting, my first guess is the ESP32 board version you are using in the Arduino IDE. It must be v2.0.0 the latest v2.0.1 has BLE issues and will not connect. Go into the "Board manager" and check the version.


Re: #sws #wemos #BCG Issue: no pairing between WEMOS ESP 32 and BCG #sws #wemos #bcg

Drew 🔭📷🚴‍♂️
 

There are other areas other than the extended.config.h that may be causing your problem.

I need more information on the issue. Is the SWS firmware compiling and uploading to the Wemos ESP32? Is it just not connecting?


Re: ESP32 wireless SHC (wSHC)

Drew 🔭📷🚴‍♂️
 
Edited

On Fri, Dec 17, 2021 at 08:29 AM, Martin Bonfiore wrote:
I take it there is something internal to the battery pack that keeps the output voltage at 5 volts??
Yes, at least mine does. Since they are intended for USB input, that must be the case. I use nothing but the short USB cable provided with the Power pack This also serves as the On/Off switch.


#sws #wemos #BCG Issue: no pairing between WEMOS ESP 32 and BCG #sws #wemos #bcg

adrien.wyns@...
 

Hello,

I have been trying to connect the BLE control and my esp 32 for weeks without success. It seems to me that I did not make an error in the Extended.config.h 
My material is:
  • MINI D1 ESP32 Wemos WIFI + Bluetooth ESP8266 CP2104 Development Board ESP-32S SE
  • ACGAM R1 Bluetooth 4.0 Wireless Gamepad
I can't figure out what I'm doing wrong.
Can you help me find my error?

Kind regards,


Re: ESP32 wireless SHC (wSHC)

kevin
 

A simple "battery pack"  isn't 5 volts it depends on the battery it uses use however there are a number of things called USB "power banks" or "portable chargers " which are basically a 3.6V rechargeable battery in a box with a charger and a 5v generator built into the same box.  you can charge them from a USB port and then plug in a USB device to charge that device.  some however are "clever" if you don't take enough current from them they think the plugged in device is "charged" and then shut down.


Re: ESP32 wireless SHC (wSHC)

Martin Bonfiore
 

Drew,

I am planning on using that idea…using a phone external battery pack.  Question…are you conditioning or regulating the 5 volts from the battery pack before it powers the shc?  I take it there is something internal to the battery pack that keeps the output voltage at 5 volts??   TIA.


Re: Pulley ratio (same ratio with different pulley combinations)

Robert Benward
 

I want to add only one thing:  The smaller pulley/teeth sizes are limited by the shaft size.  You may find a gear set that may have a larger diameter output shaft than the input.  That shaft diameter will limit the minimum number of teeth you can fit around the pulley diameter.  The smallest pulley/teeth I could find for my planetary shaft (8mm) was significantly larger than the pulley/teeth for the 5mm shaft on the stepper.  So dropping a gearbox onto your stepper, may change the pulleys you choose.  I went for 1:1, so I needed a 20T 8mm bore, 6mm wide, and a 20T 6.35mm bore, 10mm wide. The 10mm width was to extend the reach of the shaft.  All part of the design & planning process.

As said before, stick to GT2.  More common, more sizes, and cheaper.


Re: #dob #dob

Robert Benward
 

I question your 3:1 ratio in the final.  What does this look like?  Usually, the AZ bearing is anywhere from 10" to 30" across.  The pinion on the end of the stepper might be 1" across max,   That gives you a 10:1 at minimum.An 18" dob might have a AZ bearing 20" across.  If you are using NEMA23 and a 10:1 planetary, you should have enough torque.  Same calculations apply for the ALT.  How big is your scope?  Need more details.

Bob


Resources Page

Ken Hunter
 

After months of trying to make this harder than it should be, studying HTML,
hundreds of hours overthinking the situation I finally got a good night's sleep
and woke up with the solution I was seeking.

Here's the first Resources card, hopefully many more to soon be submitted.
See the Wiki FAQ for more info and to get started.


Updated Wiki Page: OnStep Resources #wiki-notice

main@onstep.groups.io Notification <noreply@...>
 

The wiki page OnStep Resources has been updated by Ken Hunter <kb7hunter@...>.

Reason: Completing the Launch of the Resources Page.

Compare Revisions


Re: NiNA, Meridian Flip, Coordinate System

Peter Boreland
 

Howard,

You edited this after my comment :) 

Peter


Re: Pulley ratio (same ratio with different pulley combinations)

Khalid Baheyeldin
 

I should have worded my reply differently.

MXL pulleys and belts do work, but all the components have to match.
We had one user who mixed MXL and GT2, and he got trailing stars, until he realized
what the issue was, and changed the pulley.

But GT2 is the most widely used type in OnStep, and it is the most common type
available at reasonable prices, because we capitalize on the economies of scale
that the 3D and CNC communities create. So GT2 ends up being available at
more outlets, and for less prices (in general).


Re: Pulley ratio (same ratio with different pulley combinations)

Peter Boreland
 

On Thu, Dec 16, 2021 at 09:25 AM, Khalid Baheyeldin wrote:

And to stress the point that Drew made:

Only use GT2 pulleys and belts.

They are readily available as they are the standard for the 3D printing community.

I cancelled my order MXL belts and pulleys (or rather they did as could not supply in a timely way, like before I die!). Good catch. Also the lead time from china was better (though not by much!), So sad for a US company. I want to point out that there is a 16 tooth GT2 pulley, so 3:1 is doable using a companion 48 tooth pulley if you plan to do the reverse worm arrangement on the G11. Is this group not the greatest, $70 back in the bank:) Best of all is the bore size can be picked just right.

Peter

Peter

5201 - 5220 of 44715