Firmware erroneously adds 4.25-4.50mm to Z height
-
I just now noticed the web interface said the "Maximum deviations: -4.265 / -2.827 mm" so I assumed the 4.25 is from the bed height map. I disabled the line "G29 S1 ; Enable" and it now shows the "true" z height value. I will try to get my deviation values lower with some manual leveling to see if it helps that value out... Is that normal or do I have a problem?
-
One thing about Z max homing is that you need to know exactly how far your z max endstop is from the bed surface. As your homing files are now, it will set your height to be whatever the z axis maxima is set to from config.g. In this case 700mm. So I suspect that this isn't accurate.
There are a few ways to address this. Here's how I do it with my Z max optical endstop. I have a macro that allows me to move the nozzle to just touch the nozzle to the bed, sets Z0, and then moves the z axis to my max z height, in my case, 300mm. I then adjust the flag of the endstop until it's just triggered so that I'm confident when the endstop triggers, it's actually 300mm from the bed surface.
-
@absensmentis said in Firmware erroneously adds 4.25-4.50mm to Z height:
or do I have a problem?
Yes, as I said, I think you should update your firmware.
What is your z probe type? Do you only use it for probing?
-
This is the most recent version available so I'm afraid updating again won't do much. I uploaded with SAM-BA and verified the MD5 hash when downloading to be 100% positive that every last bit was correct. I did this because my (real!) duet arrived in an erased state. For now I am using a nozzle mounted microswitch with a Z offset of 7.18mm and the actual Z height is about 718.55 at room temperature. I only use it for probing, I would like if I could use it to calculate Z also but I haven't seen anything about this FW being able to do such a thing. I just put "safe" values in to prevent a nozzle crash because my Z axis is strong enough to absolutely demolish the machine should it fail to stop at an appropriate distance
-
re-uploading the DC42 firmware has not changed anything sadly
-
Just to confirm, firmware version 2.02?
https://github.com/dc42/RepRapFirmware/releases/tag/2.02 -
@absensmentis said in Firmware erroneously adds 4.25-4.50mm to Z height:
I just put "safe" values in to prevent a nozzle crash because my Z axis is strong enough to absolutely demolish the machine should it fail to stop at an appropriate distance
One way to minimize the risk of this is to reduce the motor current to the bare minimum during probe and homing moves and reverting to normal afterwards.
If you're confident that your microswitch accurately sets Z0 you can use it to home Z. Is there a particular reason you need to home to Z max, especially on such a long Z axis.
-
I am rather confused, I downloaded it from that github but my version is 1.21???... I will get the actual latest version uploaded. As for the reduced current during homing, I will have to do that. thanks for the great suggestion.
-
You'll need to update to firmware 2.0 first using the normal method described here: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
https://github.com/dc42/RepRapFirmware/releases/tag/2.0Then you can use the new simplified update method by uploading the entire 2.02a zip file. The Duet will extract the binaries and install what needs updating automatically.'
https://github.com/dc42/RepRapFirmware/releases/download/2.02/Duet2Firmware-2.02a.zipI would recommend taking a look at the release notes between 1.21 and 2.02 as well.
-
No matter what I do it wont change from the following versions.
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 1.21RC1 (2018-01-25)
WiFi Server Version: 1.21
Web Interface Version: 1.21.2-dc42it recognizes the bin files and claims to upload them but it lies. I guess now nuke the board and use SAM-BA again?
-
Now I believe the current 2.02 bin file is incorrect, if I upload it to the board it becomes entirely unresponsive
-
Can you try the full version of 1.21 first?
https://github.com/dc42/RepRapFirmware/releases/tag/1.21Then if that works, 2.0.
Then if that works, 2.02.
Are you using the "Usual procedure" as shown here? https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Usual_procedure
Samba should be the last option if the other fall back procedures don't work.
-
May not be your problem but I had a similar problem when homin it would stop above the bed by about that amount
found out it was my Z probe that if it was moved evey so little would get a bad read and trigger early.
Checking it was tight straight etc. it would home correctly. It drove me crazy as I thought it was something in the config.g
and tried so many things to no avail. -
As you are on 1.21RC1 you may need to follow the procedure for updating from 1.20 to 1.21 or later. See https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Upgrading_a_Duet_2_WiFi_or_Ethernet_to_firmware_1_21_or_later_from_1_20_or_earlier.
