3.2 Servo making a grinding noise on reboot/M999
-
@Phaedrux said in Servo making a grinding noise on reboot/M999:
Do you have any servo movement commands in there as well?
Yes you do.
@Reefwarrior said in Servo making a grinding noise on reboot/M999:
M402
M401
M402Maybe try adding a few G4 pause commands in between those deploy and retract commands.
-
@Phaedrux Sorry I was too hasty in my reply.
Even without the M402/401 commands, it does the same. It's asif there is a PWM spike to the servo just prior to the 'reset' command actually being initiated by the firmware. -
What I also did notice is that all my fans goes on / off for a fraction of a second when sending the M999 command....
-
@Phaedrux said in Servo making a grinding noise on reboot/M999:
What firmware version and what Duet board?
Also, is this an actual BLTouch?
Does it do this on a normal power cycle, or only when doing a M999?
-
@Phaedrux No it's not a BL touch. It's basically a servo that moves my optical sensor's probe into position/out of position, to commence a probe for the Z axis.
It happens only during M999 or when it is rebooted (or emergency stop) from the webgui (eg. after editing the config.g file)
Switching the machine off/on with the physical switch does not give this problem.
Also:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2 (2021-01-05)
Duet WiFi Server Version: 1.25 -
And did this behaviour only start after updating to 3.2?
-
As far as I can recall, yes. Printer has been out of action for quite some time doing upgrades on the Z-axis - so I did go and flash the newest firmware before commencing the configuration of it - though before I worked on the printer, I did not have this issue... Think it was firmware 3.0 or something. Not too sure.
Just downgraded to 3.1.1; and still the same....
-
Would you be able to test the behaviour in 3.1.1?
It should be pretty easy to switch between versions by uploading the respective release zip files to the system tab in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/Duet2and3Firmware-3.2.zip
-
nevermind, looks like you beat me to it.
-
@Phaedrux haha nothing more than luck on my side
But yes, still the same is being observed.... Even if I go and issue M280 P0 S180 before the M999; it still does the same.... -
Thanks. Will add this to the list to investigate.
-
@Phaedrux Thank you
-
Would you be able to make a short video showing what it's doing?
-
sure. Where must I upload it?
-
Also a bit off topic, but with 3.2 the end-stop status on the 'Machine-Specific' tab is also missing....
-
Also found something else now. If I don't send any commands to the servo, and then issue M999; then there is no grinding or any activity. But as soon as I have issued a command to the servo; and then reboot, then this phenomenon occurs....
-
@Reefwarrior said in Servo making a grinding noise on reboot/M999:
Where must I upload it?
you can upload a small mp4 here to the forum or use dropbox or the like.
@Reefwarrior said in Servo making a grinding noise on reboot/M999:
end-stop status on the 'Machine-Specific' tab is also missing....
yes. hoping that will make a come back soon.
@Reefwarrior said in Servo making a grinding noise on reboot/M999:
If I don't send any commands to the servo, and then issue M999; then there is no grinding or any activity. But as soon as I have issued a command to the servo; and then reboot, then this phenomenon occurs
And that is true regardless of whether you have the M401/M402 commands present?
-
@Phaedrux Yes, Issued M280 instead of M401/2 and it does the same. So seems it is not linked to the M280/401/402 code; but perhaps something in the M999 code? Like basically sending a PWM pulse to the servo upon 'flushing' the memory before reboot or something.
-
@Phaedrux Attached the clip. Hope it is of some help - I have taken the 'arm' off the turning mechanism on the servo so it doesn't damage the gears inside...VID_20210114_193516 (1).mp4
-
Just to be super clear, you have no M401/M402/M280 commands at all in config.g, right?
