Building a DIY public domain low cost stepper motor analyzer
-
Implemented the first analysis screen, still crude but shouldn't be difficult to clean. It shows the histogram of the stepper speed. vertical axis is speed from 100 steps/sec (bottom) to 2000 steps/sec (top). The length of the bars is the relative time the stepper was at that speed.
This is the result of stepper A of a CoreXY printer while printing Calicat. The movements are relatively and the insufficient time to accelerate result in low overall speed:
This video shows it updated in real time while using PanelDue to move a few times 10mm (slow) and then a few times 100mm (fast):
https://www.dropbox.com/s/mw2pdjfm5h5n9b8/stepper_speed_histogram.MP4?dl=0
The blue button resets the histogram data when you want to start from scratch.
I believe that the Duet boards have sufficient information to provide such histograms. This could be another useful differentiator.
Next I will try to implement a similar histogram that show the peak current in each speed. I believe that this will be able to diagnose the problem I had with a high inductance extruder stepper as the bars will be significantly shorter for the higher speeds.
BTW, the microcontroller in the video is Teensy 4.0, a 600Mhz M7 beast that leaves a lot of room for future expansion, both in memory and computation.
-
Interesting.
I am still battling on with 12V on my current 'in progress' machine. I noticed similar issues with the commonly touted 3600 instant speed and 3600 max speed. I could hear it on my machine. Things got very rattly on retracts and things sounded so much better (clean tones) after I dropped the instant speed to 1100 and the speed to 2100.
If you paired up what you are building with something like the test on this you tube video you could have a very powerful tool.
https://www.youtube.com/watch?v=GVs2d-TOims
In a crude manned you could train a USB camera at the scales display and capture X number of frames around the point where the requested speed no longer matches the actual.
If you are looking at the current or voltage plots I would imagine it wouldn't be a huge stretch to investigate if the electrical characteristics of the motor indicate when the motor is about to stall. That said the effect of the current choppers may make things too muddied to see.
In relation to the retracts there could be an argument for two speeds on the retract. Unloading the filament could be really quick as the torque requirements are just about over coming the rotor and gear inertia (which in itself may indicate mass dampers would help avoid resonances) and then the true retract where you are looking to pull the filament back up away from the nozzle during which you have to overcome the viscosity of the material, but not pull a vacuum in the hotend which would encourage out gassing of the polymer.
-
@DocTrucker said in Building a DIY public domain low cost stepper motor analyzer:
I noticed similar issues with the commonly touted 3600 instant speed and 3600 max speed. I could hear it on my machine. Things got very rattly on retracts and things sounded so much better (clean tones) after I dropped the instant speed to 1100 and the speed to 2100.
This is how the coils current look in a too-fast scenario
There is not enough time for the current to build up in the coils, the sine wave forms are distorted, the peek current are lower, and the torque level is ver low if at all. Currently the analyzer detects it by noticing invalid stepper phase errors and count them as bad steps. The current histogram by step speed will allow to diagnose it better and predict the max useful stepper speed. At lease I hope so
-
Just measured the extruder stepper (~26 full steps per mm) stepper speed histogram when printing Calicat with pressure advance of 1.0.
Majority of the time the speed is in the 100-200 full steps per sec range, with very short time going up to ~1800 full steps per sec (during retraction).
This suggests to me that the retraction speed has little affect on the overall print time.
-
Thank you for this thread! It really shows how a simple tool used with intelligence gives a lot of insight.
-
The firmware of the stepper analyzer proof of concept is done and the prototype has four functioning screens (see below) which demonstrate the viability of the hardware design. Next I will work on a PCB layout.
Screen1: general information in text form (current in coils A.B, total steps, phase errors, etc)
Screen2: histogram of time spent in each speed range (botton = slow, top = fast).
Screen3: histogram of coil current vs stepper speed. Will indicate issues such insufficient power voltage or too high inductance, which cause lower currents in high speeds.
Screen4: general signal waveforms of coils A (green) and B (red).
-
Slowly slowly progressing with the stepper analyzer project. The PCB design is completed and I ordered it from a PCB house. Should arrive in a week or two. Snapshots of the schema and PCB are included below. The schema is straight forward, two current sensor, a Teensy 4.0 MCU module, small display, two buttons for user interaction and 4 dip switch for configuration (e.g. to reverse the step count direction). The dotted region includes optional stuff for firmware developers.
PCB Layout
Schema
stepper_analyzer.pdf -
Nice work. I need to read through this in detail, forgive me if the following is already answered.
Does the detail of the plots change under acceleration vs deceleration? Any indication that lag or advance of the rotor may be delectable? I'm not talking about hundredths of a degree resolution, just and indication of where the rotor is relative to target on dynamic moves?
-
@zapta this is a great project! thanks for documenting it as you go through. Worth a submission to hackaday once complete I think!
-
Awesome project! Thanks for sharing!
-
This is neat. One time I thought of building a step motor dynamometer to compare motors by looking at their torque curves. I wish I followed through. Maybe that can be another module for this device?
-
This could be a good project for a electronic magazine (I mean as an article in the magazine with explanation): a useful topic for many users, nice images and a PCB project. Something like Elektor in germany.
-
@DocTrucker said in Building a DIY public domain low cost stepper motor analyzer:
Does the detail of the plots change under acceleration vs deceleration? Any indication that lag or advance of the rotor may be delectable?
Good question. I don't know. I clearly observed that the current does not reach full amplitude when the speed was too fast that voltage and stepper combination but I don't know if the current signals are sufficient to detect missing steps.
-
@T3P3Tony said in Building a DIY public domain low cost stepper motor analyzer:
@zapta this is a great project! thanks for documenting it as you go through. Worth a submission to hackaday once complete I think!
Hi Tony, yes I plan to do that, to get more awareness. My goal is to provide a baseline hardware and firmware such that more knowledgable and creative people can use to provide useful tools for the community.
-
After procrastinating on this project for some time I realized that having to implement the UI with a low level screen API was distracting so I decided to switch to a smart touch display (Nextion 4.5") and things started to move fast. Here are a few pictures with the current state. Next I plan to redesign the PCB for the new LCD and clean up the UI.
The old PCB with connected to the new display:
The home screen with summary data:
The setup screen. It allows to set the zero current and to reverse the steps direction.
The distance graph. Graphs moves up/down in real time with the steps counter:
Histogram of time by speed. I am thinking adding a similar screen with histogram of distance by speed.
Histogram of peak current vs speed. In this example, a 12V 1.2A stepper, the max current starts to drop at ~7000 steps per sec.
A tachometer that shows speed in real time.
A capture of the current signals in the two stepper coils. This one is at high speed with only 12V supply which resulted in poor current pattern, close to the speed limit of the system. (ideally the two signals should look like sine/cosine).
-
@zapta your project is very interesting. Can you tell me please whether you were able to analyse currents with microstepping and to which detail?
Thank you for pointing me to the ACS70331. I have a couple of ACS712, but they are much too slow.
I would like to analyze the correlation between step commands to the TMC, the created currents from TCM to stepper and the resulting movement of the stepper.
-
Hi @JoergS5, think it shouldn't be too difficult to decode x16 microsteping. When going through a full step, the current in the two coils behave like the graph below. X16 can be achieved by breaking the cycle to x4, x2 and x2:
x4 - detection of a quadrant (90deg) is already already done and needed to determine the direction.
X2 - each quadrant can be divided int two (45deg each) by comparing the absolute value of the two channels.
X2 - each sub quadrant can be divided by 2 using the ratio of the high coil current to the low coil current.
I think this is straight forward and doable, given the two currents, and can also be come manually using the two current readings.
BTW, I send the new PCB layout to manufacturing. Should arrive in a few weeks. It's a small 40x50mm board.
All the source files are on github and should work though I plan to do some cleanup.
https://github.com/zapta/misc/tree/master/stepper_analyzer
Schema is in the link below. As you can see there is no much there:
https://github.com/zapta/misc/blob/master/stepper_analyzer/kicad/main/stepper_analyzer.pdf -
@zapta Thanks for your information and the source location. Lucky me I bought a Nextion 3.5 last year, because I liked the idea that the display offers GUI logic, so I can start with your source.
It will take some time until I can start with the project, but I can keep you informed what I develop. -
@zapta said in Building a DIY public domain low cost stepper motor analyzer:
All the source files are on github and should work though I plan to do some cleanup.
I don't see how to download all of the files related to this project.
Does each file have to be downloaded separately?
Frederick
-
@fcwilt easy way is to clone or download the whole https://github.com/zapta/misc repository.
Alternatively you can turn to google to try and download just a sub directory from github