Date   

Re: OnStep + ESP32 (WemosD2R32) + Motor Shield V3 + Wii Nunchuk

Ken Hunter
 

Howard... HELP !

I have run into a problem, not quite as bad as releasing all the smoke but...

Here's part of my Pin map for the Wemos D1 R32 and CNCV3

// -------------------------------------------------------------------------------------------------
// Pin map for CNC Shield Version 3 (with WeMos D1 R32)
// Modified 2021-1-18: 12:00 by Ken Hunter
// As built... 
 
#if defined(ESP32)
 
// Serial ports
#define SERIAL_C_RX          32     // Wemos D1 Mini Wifi TX
#define SERIAL_C_TX          33     // Wemos D1 Mini Wifi RX
 
#define SERIAL_B_RX          13     // GT-U7 GPS module TX
#define SERIAL_B_TX            5     // GT-U7 GPS module RX
 
// Multi-purpose pins 
#define Aux2                 18     // RST pin on side of case
#define Aux3                 21     // I2C SDA to BME280 THB sensor
#define Aux4                 22     // I2C SCL to BME280 THB sensor
#define Aux7                 39     // GT-U7 GPS module PPS
#define Aux8                 23     // PWM Signal to (Ground LED) Mosfet driver
 
 
// Misc. pins
#define AddonResetPin      Aux2     // ESP8266 RST switch on side of case
#define ReticlePin               Aux8     // Drain
#define TonePin                        2     // For a piezo buzzer
 
// The PPS pin is a 3.3V logic input, OnStep measures time between rising edges and adjusts the internal sidereal clock frequency
#define PpsPin                    Aux7     // PPS time source, GPS for example
 
#define LimitPin                   Aux7     // The limit switch sense is a logic level input normally pull high (2k resistor,) shorted to ground it stops gotos/tracking
 
// Axis1 RA/Azm step/dir driver
#define Axis1_EN             12     // Enable [must be low at boot 12]
#define Axis1_M0             32     // Microstep Mode 0 or SPI MOSI
#define Axis1_M1             33     // Microstep Mode 1 or SPI SCK
#define Axis1_M2             15     // Microstep Mode 2 or SPI CS
#define Axis1_M3         Aux2     // SPI MISO/Fault
#define Axis1_STEP         26     // Step
#define Axis1_DIR            16     // Dir
#define Axis1_DECAY    Axis1_M2     // Decay mode
#define Axis1_HOME             Aux3     // Sense home position
 
// Axis2 Dec/Alt step/dir driver
#define Axis2_EN         SHARED     // Enable pin control shared with Axis1
#define Axis2_M0             32     // Microstep Mode 0 or SPI MOSI
#define Axis2_M1             33     // Microstep Mode 1 or SPI SCK
#define Axis2_M2              0     // Microstep Mode 2 or SPI CS
#define Axis2_M3           Aux2     // SPI MISO/Fault
#define Axis2_STEP           25     // Step
#define Axis2_DIR              27     // Dir
#define Axis2_DECAY    Axis2_M2     // Decay mode
#define Axis2_HOME         Aux4     // Sense home position
 
// For rotator stepper driver
#define Axis3_EN         SHARED     // Enable pin control shared with Axis1
#define Axis3_STEP                19     // Step
#define Axis3_DIR                   14     // Dir
 
// For focuser1 stepper driver
#define Axis4_EN         SHARED     // Enable pin control shared with Axis1
#define Axis4_STEP           17     // Step
#define Axis4_DIR              14     // Dir

As you may recall I requested an additional Serial port which you kindly set up for GPIO 32 & 33
and I have that in my config.h file... The problem is, I am having a conflict with the #define
for those 32 & 33 pins (M0 and M1). I have tried commenting out the axis 1 & 2 lines but
that just results in many errors for the missing lines in the validate.h process...

Having the conflict on GPIO 32 which is tied to the TX pin of the Mini causes the Mini to lock 
up. removing that connection allows the Wifi to kinda work but not as we would desire.

There also looks like a possible similar problem with Aux 2 and Aux 7  but I haven't
gotten that far yet...

How can I ignore the #define for those pins without getting 5 pages of errors?
I have been reading and banging my head on the floor for over 24 hours on this one
and I'm stumped.

Ken


 


Re: BigTreeTech S109 Drivers

GuitsBoy
 

That sounded like a good suggestion.  I bench tested the s109 drivers with a 19v laptop power supply, but they were still jittery and uneven in their tracking, no matter how I fine tuned the Vref pot.  I don't know if I just got a bad batch, but these drivers just don't seem to work very well.  I even threw in some cheap a4988 drivers just to test, and while they were noisy, they were dead even and consistent. 

Anyway, I'm giving up on these s109s and sticking with the lv8729s for now.

Thanks.


And what voltage are you running? 
In my first onstep built was missing steps at 12v, but then at 19v its working great. 


 


Re: STM32 - DS18B20 connection

 

Thanks Howard, meanwhile I have tested the hardware and it worked perfect. I had some trouble with a three channel PWM module which I used to have more options to tune the power for the different heater.

For the tube and the OAG area I use a foil heater from here (http://vi.raptor.ebaydesc.com/ws/eBayISAPI.dll?ViewItemDescV4&item=274440565377&category=84185&pm=1&ds=0&t=1609409192000&ver=0).

For the secondary heater I used a  simple 1,2m constantan wire (10 Ohm/m).

It is really nice how you programmed the DS2413 also the Intervalometer feature.

For those who would like to know how I connected my hardware I attached a circuit with the figures of resistors and transistors. Might be that there is a better way to do it but this circuit I have tested.

Also thanks to Dave and Khalid.


All the Best

Joe     Karlsruhe
Here its cloudy and foggy all the days, sadly.



Below are my settings in the config file. The DS addresses you have to change in your setting.

#########################################

...
...
#define FEATURE1_NAME          "DH-OAG" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE1_PURPOSE              DEW_HEATER //    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE1_TEMP                 0x28862F56B5013C50 //    OFF, DS1820, n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE1_PIN                  0x3A291A4600000097 //    OFF, AUX, DS2413, 0x3A2E574600000017 n. Where n is ds2413 s/n (gpio0) or n=0 to 255 (pin#.)      Adjust
#define FEATURE1_DEFAULT_VALUE ON
// #define FEATURE1_ACTIVE_STATE LOW // Not possible for DS2413
#define FEATURE2_NAME          "DH-OTG" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE2_PURPOSE              DEW_HEATER //    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE2_TEMP                 0x28B6CD56B5013CE4 //    OFF, DS1820, n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE2_PIN                  CHAIN //    OFF, AUX, CHAIN (ds2413 gpio1,) n. Where n=0 to 255 (pin#.)                   Adjust
#define FEATURE2_DEFAULT_VALUE ON
// #define FEATURE2_ACTIVE_STATE LOW  // Not possible for DS2413

#define FEATURE3_NAME          "TEMP-FOC" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE3_PURPOSE              OFF //    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE3_TEMP                 0x28706556B5013CC4 //    OFF, DS1820, 0x28862F56B5013C50 n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE3_PIN                  OFF //    OFF, AUX, DS2413, n. Where n is ds2413 s/n (gpio0) or n=0 to 255 (pin#.)      Adjust
#define FEATURE4_NAME          "TEMP-OAG" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE4_PURPOSE              OFF//    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE4_TEMP                 OFF //    OFF, DS1820, 0x28B6CD56B5013CE4 n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE4_PIN                  OFF //    OFF, AUX, CHAIN (ds2413 gpio1,) n. Where n=0 to 255 (pin#.)                   Adjust

#define FEATURE5_NAME          "INTERV" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE5_PURPOSE              INTERVALOMETER //    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE5_TEMP                 OFF //    OFF, DS1820, n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE5_PIN                  0x3A841946000000CF //    OFF, AUX, DS2413, n. Where n is ds2413 s/n (gpio0) or n=0 to 255 (pin#.)      Adjust
#define FEATURE6_NAME          "DH-SEC" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE6_PURPOSE              DEW_HEATER //    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE6_TEMP                 0x280CED56B5013CD4 //    OFF, DS1820, n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE6_PIN                  CHAIN //    OFF, AUX, CHAIN (ds2413 gpio1,) n. Where n=0 to 255 (pin#.)                   Adjust

#define FEATURE7_NAME          "FEATURE7" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE7_PURPOSE              OFF //    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE7_TEMP                 OFF //    OFF, DS1820, n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE7_PIN                  OFF //    OFF, AUX, DS2413, n. Where n is ds2413 s/n (gpio0) or n=0 to 255 (pin#.)      Adjust
#define FEATURE8_NAME          "FEATURE8" // "FE..", Name of feature being controlled.                                        Adjust
#define FEATURE8_PURPOSE              OFF //    OFF, SWITCH, ANALOG, DEW_HEATER, INTERVALOMETER.                              Adjust
#define FEATURE8_TEMP                 OFF //    OFF, DS1820, n. Where n is the ds18b20 s/n for DEW_HEATER temperature.        Adjust
#define FEATURE8_PIN                  OFF //    OFF, AUX, CHAIN (ds2413 gpio1,) n. Where n=0 to 255 (pin#.)                   Adjust
...
...


#########################################


Re: S6 heater control

Serge CLAUS
 

I only have 3 cables:

One for AD + limits + house + PEC.

It is a 12 conductor cable. (En, Step, Dir, 18V, GND, 5V, PEC, Home, Limits)

I am using two Bigtreetech 42B motors (closed loop). USB cable for cameras and filter wheel

One for DEC + Heaters + focuser + park, limits, intervalometer, 12V camera and reticle

It is a 24 conductor cable.

I have a small box attached to a DEC bracket with multiple sockets for focuser, heaters...

Le 16/01/2021 à 22:28, Khalid Baheyeldin a écrit :
On Sat, Jan 16, 2021 at 04:14 PM, Jay Murphy wrote:
I don't trust myself to remember to keep the sliders below 50% 
You don't have to.
There are options you can add to make this totally automated.
The BME280 sensor measures ambient temperature and humidity.
OnStep calculates the dew point.
And a thermometer measures the temperature of the heating
element as a feedback.
OnStep then keeps the heating element above the dew point.

Works well, and tested by a few people, Dave included.

But, for me it involves more components and more cables, which
I am averse to ...


Re: S6 heater control

Serge CLAUS
 

For my heaters, i use the fan pins (12V)
The hot bed output has separated input voltage. You can use this output with 12V. I use this output for my 12V camera.
Le 16/01/2021 à 03:22, Jay Murphy a écrit :

So it looks like the heater control is working on the S6, but how is the voltage controlled? I want to power the board with 24V but does that mean my heaters will get 24V as well? 


Re: OnStep + ESP32 (WemosD2R32) + Motor Shield V3 + Wii Nunchuk

Khalid Baheyeldin
 

On Sun, Jan 17, 2021 at 02:20 AM, Kedar wrote:
it would seem that ESP32 with a processor clock of 240MHz should be able to do fastest step rate at ~200 KHz. But the performance differences page mentions ESP32 to be capable of only 67 KHz.
Good question.

But that is how things are, based on actual testing of how fast each microcontroller can actually pulse the motors.
Counterintuitive, but that is how reality is different than theory.


Re: How to... Additional serial port for GPS .

Khalid Baheyeldin
 

On Sat, Jan 16, 2021 at 10:18 PM, Ken Hunter wrote:
 
// This configuration was automatically generated using the Online Configuration Generator
// Authored by: Khalid Baheyeldin
// Slewing Speed: 134.33 degrees/second (estimated)
// Generated on: 2021-01-09 16:48
I can't directly comment on the CnCV3 board, because I don't have one.

But the 134 deg/sec is TOTALLY INSANE ...

You must have input one or more wrong values to end up with that.

Tell us what you used as input (GR1, GR2, Motor Steps, Microsteps, ...etc)


Problem with SHC

Prasad
 

I have two SHC units, both running ESP32, and kits were from my good friend George Cushing.  

Today I uploaded SHC firmware using the latest "Master" version into one of my ESP32 based SHC. I connected it to my MiniPCB2 controller that runs OnStep v3.16. After the initial wait, I got "Connection Warning" followed by "Coordinates Observed Place..." on the display. 

I disconnected the SHC and kept it aside. I then took out my other (second) SHC that has its firmware v3.16 and connected this SHC to my MiniPCB2. This SHC started up correctly without the error. I got to see the RA and DEC coordinates as it always does. 

My problem seems to be only with one SHC that has its firmware taken from the latest "Master". 

Any tips on what could be going wrong? 

Prasad
Eastern PA, near Philly


Re: DEC Axis Homing problem....

Martin Bonfiore
 

The pullups are discrete resistors located immediately adjacent to the output pins of the opto-interrupter (2.4Kohms...reasonably stiff).  I guess it is possible that the one could say they are "floating" relative to very fast transients that appear further down the cable that would see the wire inductance.  Note however, that the problems for me were when the opto-interrupter output NPN transistor was fully turned on (I measured the resulting output LOW as just a handful of millivolts...pretty much what a saturated transistor would read Collector to Emitter).  :The drive impedance of the signal line in that case would be dominated by the output impedance of  the saturated output transistor. 

As recall, the output of these optos are rated at being able to sink 50 ma and maintain a nominally LOW level.  My guess is inductively rather than capacitively coupled noise inducing voltage spikes in the sensor signal line forming in essence a loop with the turned on transistor at one end and the PA13 input at the other end.  The R/C filter at the STM32 end attenuates the voltage spikes...or at least that is the theory.


Re: Connection issues with iOS but not with Android

Dave Schwartz
 

I don't think the use of Gotomote can be recommended anymore.

Howard wrote and maintains the Android app but it is not open source and he has no intention of porting it to iOS.

So a bit over 2 years ago, member Satnam Singh, took a stab at creating a similar app for iOS and Gotomote was born. However, it appears to have been abandoned... the last update was over 2 years ago (Jan 7, 2019) and Satnam does not seem to be active on the group anymore either (last post Jan 26, 2019).

On 2021-01-17 12:42 p.m., Jesco Topp wrote:

Update for the record and others who might encounter this: After some more trial and error it turns out that Gotomote was the culprit that caused OnStep 3.16 to crash.

What works fine is to use the web portal at 192.168.0.1 to set location, date/time and then initiate the alignment. Afterwards SkySafari works for completing alignment. The controller does not crash anymore and I can use SkySafari for all GoTos.

So all is well. :)


Re: Connection issues with iOS but not with Android

Jay Murphy
 

Interesting. I think there was a bug with certain external programs trying to set the date and time. Was that the issue with gotomote?


Re: DEC Axis Homing problem....

Mike Ahner
 

Hi Martin, I wonder if it's picking up noise or just needs a Pullup resistor at the STM32 module? It seems your pullups are at the opto-isolators and depending on where they're located, the line might still be floating. That could explain why Curly has the same issue. Did you measure the voltage at the four pin header on the STM32 or at the opto-isolators? The internal STM32 pullups may not be strong enough in this case.

Either way, good work finding a solution.


Re: Connection issues with iOS but not with Android

Jesco Topp
 

 

Update for the record and others who might encounter this: After some more trial and error it turns out that Gotomote was the culprit that caused OnStep 3.16 to crash.

 

What works fine is to use the web portal at 192.168.0.1 to set location, date/time and then initiate the alignment. Afterwards SkySafari works for completing alignment. The controller does not crash anymore and I can use SkySafari for all GoTos.

 

So all is well. :)


Re: DEC Axis Homing problem....

Martin Bonfiore
 

My intuition was incorrect...it definitely looks like a noise pickup issue in my setup.  I reverted from 5.1o (which works with my setup) back to 4.22h which exhibits the failure to home on the DEC axis. 

I then added an R/C filter immediately adjacent to where the DEC home signal enters the STM32 (at the four pin header...PA13)...so 1K resistor in series; 0.47 uf cap between the PA13 pin and the ground pin on the four pin header.  The homing now works properly on 4.22h. 

Howard's SW addition of the debounce filter appears to have addressed the root cause (noise) in my setup. 

What remains interesting and possibly a coincidence is why Curly's system shows a very similar behavior?? 

I am also curious where the noise is getting coupled into my setup.  My current guess is that even though the Home signals travel on their own cable there is a small but possibly significant area where the signal cable passes near the wiring to the RA stepper motor (an artifact of how I mounted the cable connectors in my setup).  

Thanks again to Howard.


Re: Flashing S6 #fysetc

masterploxis@...
 

Hi Dave,

thanks for the fast response.

The serial monitor indeed gives me the response : On-Step#
So the firmware was flashed successfully and the board is working with the onstep firmware.

Now i can go futher with my project.

Thanks again
Andy


Re: Flashing S6 #fysetc

Dave Schwartz
 

Perfect.

As to testing whether OnStep is running, read the last section of the 'Uploading the Firmware' chapter of the Wiki https://groups.io/g/onstep/wiki/Getting%2C-Configuring-and-Uploading-Firmware

On 2021-01-17 10:56 a.m., masterploxis@web.de wrote:
Hello,

i did everything what was described in the manual for flashing the FYSETC S6 (V2) board.
I have received the following status:

Arduino: 1.8.13 (Windows 10), Board: "3D printer boards, FYSETC_S6, STM32CubeProgrammer (DFU), Enabled (generic 'Serial'), CDC (generic 'Serial' supersede U(S)ART), Low/Full Speed, Fastest (-O3), Newlib Nano + Float Printf/Scanf"
Der Sketch verwendet 179856 Bytes (39%) des Programmspeicherplatzes. Das Maximum sind 458752 Bytes.
Globale Variablen verwenden 14016 Bytes (10%) des dynamischen Speichers, 117056 Bytes für lokale Variablen verbleiben. Das Maximum sind 131072 Bytes.
-------------------------------------------------------------------
                       STM32CubeProgrammer v2.5.0
-------------------------------------------------------------------
USB speed   : Full Speed (12MBit/s)
Manuf. ID   : STMicroelectronics
Product ID  : STM32  BOOTLOADER
SN          : STM32FxSTM32
FW version  : 0x011a
Device ID   : 0x0421
Device name : STM32F446xx
Flash size  : 512 KBytes (default)
Device type : MCU
Device CPU  : Cortex-M4

Memory Programming ...
Opening and parsing file: OnStep.ino.bin
  File          : OnStep.ino.bin
  Size          : 180352 Bytes
  Address       : 0x08010000
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [4 5]
erasing sector 0004 @: 0x08010000 done
erasing sector 0005 @: 0x08020000 done
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:07.226
RUNNING Program ...
  Address:      : 0x8000000
Start operation achieved successfully

I assume the flash was sucessfull. How to open the onstep program and check if it works ?

Sorry - i give myself a big facepalm.. But i don't know how to open the interface to the card and the screen as seen in the previous post from Ken.

Thanks
Andy


Re: Flashing S6 #fysetc

Dave Schwartz
 

With the Arduino IDE, when you open the OnStep.ino file it will automatically load all the other files from that directory in separate tabs and when you click the 'Upload' arrow it will automagically pull in everything needed to complete the compilation and upload it as a single executable.

On 2021-01-17 10:24 a.m., masterploxis@web.de wrote:
Hello,

how exactly is the flashing done ?

- what files re needed to be loaded in Ardunio IDE ?

I have managed everything else (STM32, CubeProgrammer, DFU Mode)
Only the process of flashing and wha files need to be flashed is currently my biggest question..

And sorry for double incase my previous post will show up someday..

Andy


Re: Flashing S6 #fysetc

masterploxis@...
 

Hello,

i did everything what was described in the manual for flashing the FYSETC S6 (V2) board.
I have received the following status:

Arduino: 1.8.13 (Windows 10), Board: "3D printer boards, FYSETC_S6, STM32CubeProgrammer (DFU), Enabled (generic 'Serial'), CDC (generic 'Serial' supersede U(S)ART), Low/Full Speed, Fastest (-O3), Newlib Nano + Float Printf/Scanf"
Der Sketch verwendet 179856 Bytes (39%) des Programmspeicherplatzes. Das Maximum sind 458752 Bytes.
Globale Variablen verwenden 14016 Bytes (10%) des dynamischen Speichers, 117056 Bytes für lokale Variablen verbleiben. Das Maximum sind 131072 Bytes.
 
      -------------------------------------------------------------------
                       STM32CubeProgrammer v2.5.0                  
      -------------------------------------------------------------------
USB speed   : Full Speed (12MBit/s)
Manuf. ID   : STMicroelectronics
Product ID  : STM32  BOOTLOADER
SN          : STM32FxSTM32
FW version  : 0x011a
Device ID   : 0x0421
Device name : STM32F446xx
Flash size  : 512 KBytes (default)
Device type : MCU
Device CPU  : Cortex-M4

Memory Programming ...
 
Opening and parsing file: OnStep.ino.bin
  File          : OnStep.ino.bin
  Size          : 180352 Bytes
  Address       : 0x08010000 
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [4 5]
erasing sector 0004 @: 0x08010000 done
erasing sector 0005 @: 0x08020000 done
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:07.226
RUNNING Program ... 
  Address:      : 0x8000000
Start operation achieved successfully

I assume the flash was sucessfull. How to open the onstep program and check if it works ?

Sorry - i give myself a big facepalm.. But i don't know how to open the interface to the card and the screen as seen in the previous post from Ken.

Thanks
Andy
 
 
 


Re: BigTreeTech S109 Drivers

GuitsBoy
 

I believe I found my mechanical issue with the mount.  The motors weren't stalling as I suspected.  The pulley was actually slipping on the worm shaft.  To the eye, everything looked as if it was working correctly.  And the mount seemed to slew to targets just fine.  But at certain times, the mount just wouldn't track, and I would get shot after shot of star trails.  Now I realize it was at these times that the pulley was slipping on the shaft, and the mount was stalled.  A bonehead / facepalm oversight.

Still, I took the opportunity to completely disassemble the mount.  The mount consists of 8 standard tapered axle wheel bearings that were heavily coated in thick, dirty, old grease.   I cleaned and stripped them all down with solvent, the gave the open bearings a quick shot of silicone to offer some protection from rust. I lightly applied superlube to the bearings and races, which has given me good results on other mounts, even in the cold.   The mount spins freely and easily, and the worms are nice and tight.  It should be much easier to get good balance with the mount loosened up, and I'm sure the LV8729s at 1.0 amp should be more than enough now.

Tomorrow night might offer good enough conditions to test the mount, but probably not clear enough for any imaging. 

Thanks to everyone for your help and suggestions,
-Tony


On 1/15/2021 12:36 PM, Khalid Baheyeldin wrote:
On Fri, Jan 15, 2021 at 12:30 PM, GuitsBoy wrote:
I think I'm going to just write these off.  If I still want to up the amperage, Ill have to go with the TMC5160s. 
Those are really great, but kind of expensive, and you need to figure out if your board supports SPI drivers as is.

But then again, will it really buy me much compared to the LV8729s at 1.3 or even cranked to 1.5 amp? 
1.5A is the maximum on the LV8729, and you should be running any electronic component at its maximum.
Stay 20% below the maximum, and you will be fine.

I always wonder why people go for 1.7A or 2A motors, when there is a 0.9A 400 step motor that works very
well (at least with EQ5 sized mount).

Yeah, you need to rule out any mechanical issues, regardless.
If you are suspecting the lubricant, try out the type that is used for snowmobiles, since it does not stiffen
up in below freezing temperatures.


Re: BigTreeTech S109 Drivers

GuitsBoy
 

Yes, but the geartrain has largely been removed, and replaced with a 1:2.25 belt drive before the 1:180 worm.  But you're right, the mount came stock with woefully inadequate motors, which required Meade overvolting the mount to 18v just to get adequate performance.  However, they did work.  Theres no reason any nema17 size motor shouldn't be strong enough, IMO.


On 1/16/2021 2:24 PM, George Cushing wrote:
The LXD650 used LX200 drives. These had small Mabuchi rear view mirror DC motors. They had a 53.334:1 motor to worm ratio and 9600:1 final ratio (180 tooth worm wheel). Thus even if the motor only provided a few ounce-inches of torque at the motor shaft it got fairly large after the gear train. 

1 - 20 of 29343