Well Mike & all.. I finally solved the mystery! I had followed the rabbit down the hold for too long, so I decided to do a full review of all my Marlin settings I had eliminated V-Grove issues and such, nothing was wrong there. Then I stumbled upon #define RESTORE_LEVELING_AFTER_G28 and presto! like magic the results were perfectly repeatable. I figure that G28 was homing just fine, butby Trackerman - Mechanics
sorry folks, I'll get there eventually ! Link should be good now.by Trackerman - Firmware - Marlin
Hopefully this link to YouTube will work.by Trackerman - Firmware - Marlin
Thanks, I will try to load the image to youtube for sharing. I'm using a Creality stock board on Ender 5by Trackerman - Firmware - Marlin
Have you guys noticed a behavior in Marlin where G29 randomly drops the Bltouch probe just after taking a measurement? I have recorded it here... I don't think it's a BLtouch issue, it looks more like a false deploy command is sent to the probe then retracted. I have also observed this on G28 command. Thanks Rayby Trackerman - Firmware - Marlin
Excellent stuff Mike, I was worried that my post was not understandable! I will indeed try your suggestions, and yes it could be the things you suggested. Thanks for the advice, I particularly like the idea about test points on one axis to check for a wheel signature! Come to think about it I recall the wheels had a divot or dent in them from sitting on the shelf for too long when I received thby Trackerman - Mechanics
Folks, I was testing my BLtouch repeatability and discovered something interesting. I think my results show z height changes due to the V-grove wheels being not perfectly circular. For example, if I repeatedly probe a single point on the bed, I can measure very low standard deviation, in the region of 0.005 to 00001 But if I perform several G29 commands (grid leveling), then the calculated stdby Trackerman - Mechanics
Thanks, I'll try that.by Trackerman - Firmware - Marlin
Enabled 4 corner leveling in configuration.hby Trackerman - Firmware - Marlin
No no no, let me explain. The pin27 board cuts the buzzer out of circuit. It's the firmware which still produces the tones signal. I tried this with an un modified board. The buzzer makes beep sounds with the line enabled and disabled... The define_speaker function seems to have lost its control over the normal tones produced, like store eprom which emits a long beep etc.by Trackerman - Firmware - Marlin
Has anyone else noticed that commenting out # Define speaker does not disable the buzzer? I found this on an Ender 5 with stock board. Present in both Marlin 1.1.9 and Bugfix 1.1.x This issue played havoc with my BLtouch on pin 27 until I scoped it and saw the buzzer was still sending beeps on pin 27. Now I'm looking for a better way to disable buzzer on pin 27.... any ideas? Thanks Rayby Trackerman - Firmware - Marlin