-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Erratic step output lathe mode #87
Comments
Fixed I2S stepping issues, added dir > step delay with 4 microseconds minimum delay. Ref. issue #87.
The main issue was that the I2S task had too low priority causing the signals to go crazy. Hopefully fixed now.
Since accessing the FPU in an interrupt context crashes the MCU and the current implementation uses it like that I am not to keen to add it myself. Fixed point math is a possible solution - perhaps someone will add it? |
I'll test i2s correction tonight or tomorrow, i'll tell you if it's ok Thanks |
Everything is ok, tested on the lathe with backlash compensation. Thanks |
Here is two methods to use float in interrupt, use double then fpu is not used, or start the fpu manually. https://esp32.com/viewtopic.php?t=1292 I hope this help |
Hello,
I have flashed a brand new tinybee with the firmware build on the webbuilder, config in lathe mode, no option, no wifi, nothing.
Just two motors, Z and X, no limits.
Reset params before tests
I have already the step by mm, because the lathe run already on grbl uno.
When I move, from 0.01 to 1mm, the number of step send to tje driver is more than ten times that should be!! And more, it's not regular, sometimes its 10, sometimes 5, and sometimes no step send!
I think a problem from the i2S, but what..... ?
Spindle sync will be really a must on this board!
Thanks terj for your work
The text was updated successfully, but these errors were encountered: