grblHAL
Spindle Stops after using Speed Ovveride command
I just found out that the Spindle Stops in the middle of the gcode cycle after I use speed override commands.
Tested it with the following control software:
- Focus (https://www.sourcerabbit.com/Shop/pr-i-91-t-focus-cnc-control-software.htm)
- Universal GCode Sender (https://winder.github.io/ugs_website/)
Works ok for me with ioSender and a STM32F756 board. Which board map are you using and is laser mode enabled?
I am using an ESP32-DevKitC-32D with the SourceRabbit 4-Axis CNC motherboard.
SourceRabbit 4-Axis CNC motherboard works totally fine with the Grbl_ESP32. I changed to GrblHAL in order to check the backlash compensation.
It seems the pin assignments for the spindle is wrong, this is the official mapping (?) vs the grblHAL mapping. Can you try with fixing the grblHAL map? However, I have no good explanation for why feedrate overrides should affect the spindle output - and I am not able to do any ESP32 debugging before I am back home at the end of January.
Hello, happy new year !
Indeed, the pins are wrong. The correct pins can be found here https://github.com/SourceRabbit/GRBL_ESP32/blob/main/Grbl_Esp32/src/Machines/sourcerabbit_Quantum.h I used the correct pins for my tests.
Correction: The speed (RPM) override stops the spindle and NOT the feedrate overrides
I earlier managed to implement the backlash compensation to our Grbl _ESP32 fork (https://github.com/SourceRabbit/GRBL_ESP32) so I really do not need to use GrblHAL at the moment.
In case you can take a look at the bug I will be happy to test it.
Parece que as atribuições de pinos para o fuso estão erradas, este é o mapeamento oficial (?) versus o mapeamento grblHAL . Você pode tentar consertar o mapa grblHAL? No entanto, não tenho uma boa explicação de por que as substituições da taxa de avanço devem afetar a saída do fuso - e não posso fazer nenhuma depuração do ESP32 antes de voltar para casa no final de janeiro.
Hello, I'm using GRBLHAL with ioSender and it's been great, I recommend it to anyone who needs great performance.
Case I need help with the map of pins I'm available to adjust you.
I am not able to replicate this with a upcoming release, tested with ioSender, UGS and the SourceRabbit map on a bare dev board. Do you remember if it was the spindle enable or PWM signal (or both) that went away? Was Laser mode enabled?