Date   

Re: MaxSTM3.6 motors not moving

Howard Dutton
 

On Thu, May 19, 2022 at 11:45 AM, glyderman wrote:
I have not populated ST4, RJ3,  RJ4, and J2 positions on the board as I will not be using them yet and the parts are very difficult to get at the moment. I can't see that this would affect anything but perhaps I am wrong.
None of this matters.


Re: MaxSTM3.6 motors not moving

Howard Dutton
 

On Thu, May 19, 2022 at 11:45 AM, glyderman wrote:
I have soldered in the pull down resistors, R19 and R20, that would be used on pin for DCO/CLK on TMC5160 drivers. I did this as I may use these drivers later.
Was this correct or should I have left them out with these TMC2130 drivers?
Only needed for some TMC5160 drivers; present or not doesn't matter for TMC2130 drivers in all cases I know of.

As mentioned before, I used in C1, C2, C3 100uF 100v not 100uF 50v. All other components are as recommende
Using a higher voltage rated cap makes no difference.


Re: MaxSTM3.6 motors not moving

glyderman
 

Hi Howard,
The board is MaxSTM3.62

The motors used are bipolar Nemo17 with planetary gearbox, Gear ratio 50.89. Model number 17HS19-1684S-PG51. These work with previous MKS-Gen L V1 controller I have been using along with software v3.16. All wiring to the  motors is correct.

I am using the latest onstep software 4.24q firmware configuration 3. I also am using the default config.h suggested for the blackpill with just the mount type changed to ALTAZM. Every thing else I  left as default in order to test the motors.

Wifi and SWS connect with no problems.

The motors only buzz with no movement and if I press the alignment east west or north south arrows on the android app the motors sometimes give a 0.2 second noise as if they are going to move. This happens maybe 1 press of an arrow out of 5 times. Other times nothing happens, the motors just continue buzzing. They do not get hot nor do the heatsinks on the drivers.

I have checked continuity between the drivers and the screw down connectors and also to the motors in case of a dry joint.There is no problem there.

The drivers are both Bigtree TMC2130 v3.

I have not populated ST4, RJ3,  RJ4, and J2 positions on the board as I will not be using them yet and the parts are very difficult to get at the moment. I can't see that this would affect anything but perhaps I am wrong.

Various error messages show on the status page of the SWS.They seem to change after every other refresh of the page.
I have attached photos of my setup and also screen grabs of the error messages. Some refer to 'short gnd AB'or 'short Gnd B'.
Sometimes the staus even says 'OK' on both axis until next page refresh.

I have read about sometimes a pin on the other suggested driver needs to be cut but Icould see nothing on the wiki that said that these drivers needed modifiying.

I have soldered in the pull down resistors, R19 and R20, that would be used on pin for DCO/CLK on TMC5160 drivers. I did this as I may use these drivers later.
Was this correct or should I have left them out with these TMC2130 drivers?
As mentioned before, I used in C1, C2, C3 100uF 100v not 100uF 50v. All other components are as recommended.


Re: FYSETC E4

Drew 🔭📷🚴‍♂️
 

That worked! Now onto the real world testing. Grinding noises, screeches, blown fuses and smoke, oh my!


Re: FYSETC E4

Drew 🔭📷🚴‍♂️
 

On Thu, May 19, 2022 at 02:02 PM, Howard Dutton wrote:
ESP32 software serial library
Thank you. I am trying to use this one: https://github.com/plerup/espsoftwareserial.


Re: FYSETC E4

Howard Dutton
 

I tested with 6.15.2 but there are already updates...

https://www.arduino.cc/reference/en/libraries/espsoftwareserial/


Re: FYSETC E4

Howard Dutton
 

You have to have the ESP32 software serial library installed.  Its trying to use the built-in one.


Re: FYSETC E4

Drew 🔭📷🚴‍♂️
 
Edited

I am getting this compilation error with the MaxESP3 and TMC2209U.

d:\Arduino\libraries\SoftwareSerial\SoftwareSerial.cpp:41:10: fatal error: avr/interrupt.h: No such file or directory
 #include <avr/interrupt.h>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
exit status 1
Error compiling for board Node32s.

I am using your SoftwareSerial library.

isn't this Teensy stuff?


Re: FYSETC E4

Howard Dutton
 

On Thu, May 19, 2022 at 10:41 AM, Michael Ring wrote:
Will did deeper in enabling debug messages and will come back to you.
I don't see that I changed anything that matters during this.

Also, debug mode can cause OnStepX instabilities (too much time spent outputting debug messages) especially when the baud rate is low and on ESP32's.
TMC2209 debug mode can interfere with the transmitted data too (breaking the timing.)  Depends on the mode.


Re: opinion on rebuild mini pcb 2 #mini

alex.military95@...
 

Grazie per la risposta. il mio problema è avere una tavola il più compatta possibile eliminerò la tensione 4.1 e metterò la 4.0 ok questo mi permette di ridurre ulteriormente lo spazio. per quanto riguarda i condensatori ho in mente di ordinare la scheda premontata direttamente dal produttore in questo modo per non rifare ci sono problemi di cortocircuito. L'altro problema non ho capito cosa intendi dato che uso google translate e non capisco quale sia il problema. il fatto è che ho bisogno di un pcb molto piccolo per il mio mini mount che ho progettato. poi non so se è possibile ordinare la bord già premontata da loro con il disegno originale.


Re: FYSETC E4

Michael Ring
 

Something is very odd at the moment, with the latest git build I have quite some instabilities like Nina not connecting to the Ascom Driver and instead of a constant rotation in RA when I turn on tracking I get two small moves and then nothing.

Will did deeper in enabling debug messages and will come back to you.

Michael

Am 19.05.22 um 18:14 schrieb Howard Dutton:

For the driver testing I have debug code in the TMC2209 driver I find useful, you enable it from OnStepX TmcDrivers.h:

// -----------------------------------------------------------------------------------
// axis step/dir TMC SPI motor driver
#pragma once

#include <Arduino.h>
#include "../../../../Common.h"

#if defined(TMC_UART_DRIVER_PRESENT) || defined(TMC_SPI_DRIVER_PRESENT)

#ifdef TMC_UART_DRIVER_PRESENT
  #ifndef SERIAL_TMC_INVERT
    #define SERIAL_TMC_INVERT OFF
  #endif
  #if SERIAL_TMC == SoftSerial
    #define TMC2209_SOFTWARE_SERIAL
    #include <SoftwareSerial.h>
  #endif
  #define TMC2209_DEBUG false
  #include <TMC2209.h> // https://github.com/hjd1964/TMC2209
#endif

#ifdef TMC_SPI_DRIVER_PRESENT
  #include "../../../softSpi/SoftSpi.h"
#endif


Re: Having challenges with the browser interface, need help!.

Peter Boreland
 

On Thu, May 19, 2022 at 10:00 AM, Chad Gray wrote:
I mean there is a version of SWS that the buttons should not act that way.  Long press on a button should not turn into select text. 
toggle quoted messageShow quoted text
Chad. Where do I get this version? Do you have a copy you could email me?

Peter


Re: Having challenges with the browser interface, need help!.

Peter Boreland
 

For example:

Clock button that works:
"<button name='qb' class='bb' value='st' onpointerdown='SetDateTime();' title='" L_HINT_CLOCK "' type='submit'>" CLOCK_CH "</button>"

Park and unpark buttons that are disabled
"<button id='unpark' class='bb' onpointerdown=\"g('pu')\" title='" L_HINT_UNPARK "' type='button' disabled>P" ARROW_UR "</button>"
"<button id='park' class='bb' onpointerdown=\"g('pk')\" title='" L_HINT_PARK "' type='button' disabled>" ARROW_DR "P</button>";

Peter


Re: Having challenges with the browser interface, need help!.

Peter Boreland
 

Well looking at the control HTML code  it would seem that all the buttons are disabled except for the clock. ??


Re: Having challenges with the browser interface, need help!.

Chad Gray
 

I mean there is a version of SWS that the buttons should not act that way.  Long press on a button should not turn into select text. 


On Thu, May 19, 2022 at 12:45 PM Peter Boreland via groups.io <pcboreland=yahoo.com@groups.io> wrote:
Chad,

I think this must be the case. Do I have to edit the ccs code out? Why was it added?

Peter


Re: Having challenges with the browser interface, need help!.

Peter Boreland
 

Chad,

I think this must be the case. Do I have to edit the ccs code out? Why was it added?

Peter


Re: FYSETC E4

Howard Dutton
 

For the driver testing I have debug code in the TMC2209 driver I find useful, you enable it from OnStepX TmcDrivers.h:

// -----------------------------------------------------------------------------------
// axis step/dir TMC SPI motor driver
#pragma once

#include <Arduino.h>
#include "../../../../Common.h"

#if defined(TMC_UART_DRIVER_PRESENT) || defined(TMC_SPI_DRIVER_PRESENT)

#ifdef TMC_UART_DRIVER_PRESENT
  #ifndef SERIAL_TMC_INVERT
    #define SERIAL_TMC_INVERT OFF
  #endif
  #if SERIAL_TMC == SoftSerial
    #define TMC2209_SOFTWARE_SERIAL
    #include <SoftwareSerial.h>
  #endif
  #define TMC2209_DEBUG false
  #include <TMC2209.h> // https://github.com/hjd1964/TMC2209
#endif

#ifdef TMC_SPI_DRIVER_PRESENT
  #include "../../../softSpi/SoftSpi.h"
#endif


Re: FYSETC E4

Howard Dutton
 

On Thu, May 19, 2022 at 08:58 AM, Chris Whitener wrote:
O I have one of these boards.  What do I need to start testing?  Howard knows I love to test.
I'd say hang on for a bit until Michael gets the drivers figured out.  Almost there.


Re: FYSETC E4

Howard Dutton
 

I fixed that overloading issue with the TMC2209 library.


Re: FYSETC E4

Chris Whitener
 

O I have one of these boards.  What do I need to start testing?  Howard knows I love to test.

4141 - 4160 of 47837