Auto Bed Leveling Map on Tronxy X5SA
-
Hi, i'm new to Duet 2 wifi, i have completed all the wiring, checked all the motors.
The printer homes correctly but when it comes to the Auto bed compensation the height map shows the following..
Here is my config file..
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Tue Jan 08 2019 05:35:50 GMT+0000 (GMT); General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder movesM667 S1 ; Select CoreXY mode
; Network
M550 P"Tronxy X5SA" ; Set machine name
M551 P"Stealth6178: ; Set password
M552 S1 ; Enable network
M587 S"Duet2" P"Duet2wifi" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S1 ; Enable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E436.54 ; Set steps per mm
M566 X600.00 Y600.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z180.00 E1500.00 ; Set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z250.00 E10000.00 ; Set accelerations (mm/s^2)
M906 X950.00 Y950.00 Z950.00 E950.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X330 Y330 Z400 S0 ; Set axis maxima; Endstops
M574 X1 Y1 S0 ; Set active low and disabled endstops; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M558 P5 I1 H5 F120 T6000 ; Set Z probe type to modulated and the dive height + speeds
G31 P500 X-30 Y0 Z0.56 ; Set Z probe trigger value, offset and trigger height
M557 X10:285 Y25:320 S40 ; Define mesh grid; Heaters
M307 H0 B0 S1.00 ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M591 D0 P1 C3 S1 ; Filament Senor
; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss; Custom settings are not configured
I hope someone can help.. i' sure its just something simple i'm missing...
-
It looks to me that the X5SA has dual Z motors. My guess is that either they are badly out of sync, or only one of them is moving during bed probing.
What is the specification of the Z motors? The Duet WiFi has the two Z motor outputs connected in series; but some recent printers deliberately use low-current Z motors because many other controllers connect them in parallel.
-
Hi, yes it does have 2, and connected to z1 and z2 but they are moving in sync with my eye and with a spirit level on the bed.
they are 1.8 step
-
The bed may be level according to your spirit level; but is the X gantry parallel with it?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@pr0xyfl00d3r As a tip, there is a nice assistant for manual leveling that you can use to get it at least somewhat right for a start:
https://duet3d.dozuki.com/Wiki/Using_the_manual_bed_levelling_assistant -
@dc42 i have now checked the x axes and this also level to the bed in multiple places around the bed
-
I'm using the stock NPN sensor that comes with the Tronxy X5SA
I have connected this to the Z Probe IN for Signal and + and - to an Always on Fan with 12v turned on,
Stepper Motors
Step Angle:1.8degI have just done another Auto Bed Comp and this what i got.
-
It's totally possible that the bed is actually that warped. The color map exaggerates the differences to make them easy to see, but the actual deviations aren't that extreme. -1.5 to +0.4mm wouldn't surprise me for a Tronxy bed.
What happens if you print a test file like this? Does the bed compensation work to keep the first layer in contact?
-
The bed is not warped works perfect with factory board setup, i am running the file you posted and video what is does, when i tried a file earlier it rams in the heatbed
-
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
M558
Can you try adding
A10 R0.5 S0.003 B0to your M558 command?This will set it to try up to 10 probes until it gets 2 consecutive readings within 0.003, and it will wait 0.5 seconds between probe travels to let the machine settle, and will disable any heaters during the probe move to eliminate any electrical interference.
-
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
M558
Can you try adding
A10 R0.5 S0.003 B0to your M558 command?This will set it to try up to 10 probes until it gets 2 consecutive readings within 0.003, and it will wait 0.5 seconds between probe travels to let the machine settle, and will disable any heaters during the probe move to eliminate any electrical interference.
I will after this file is finished..
in my simplify3d setting for the starting script i had the following
G28 ; home all axes
G29 ; auto bed level
G1 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E10 F600 ; prime nozzlewhich i changed to
G28 ; home all axes
G29 ; auto bed level
G28 ; home all axes
G1 Z0.56 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E10 F600 ; prime nozzlenow it did not hit the bed and does go through the print, the 0.56 i got from following https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
But can i simplify it or need much of it?
-
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
A10 R0.5 S0.003 B0
just to check add this to the end of the code i already have ?
-
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
It's totally possible that the bed is actually that warped. The color map exaggerates the differences to make them easy to see, but the actual deviations aren't that extreme. -1.5 to +0.4mm wouldn't surprise me for a Tronxy bed.
What happens if you print a test file like this? Does the bed compensation work to keep the first layer in contact?
This is from the print
-
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
A10 R0.5 S0.003 B0
just to check add this to the end of the code i already have ?
Yup, add it to what you have already in your M558. Did it change the resulting heightmap at all?
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
the 0.56 i got from following https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
That would be used in the G31 command to tell the printer how far the nozzle is from the bed when the probe triggers, but isn't useful elsewhere. You can prime the nozzle at whatever height you like. I use 0.3, but as long as it's doing what you want for the prime it can be whatever height you want. The slicer will move to the correct first layer height afterwards. Though it should be noted that having a Z move like that to prime the nozzle can confuse the DWC and result in the first layer height and layer counter to behave oddly. It may be better to move that nozzle prime into it's own macro that lives in the sys folder on the Duet. Then you can use M98 0:/sys/NozzlePrime.g to call it in your slicer start code.
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
This is from the print
That doesn't look too bad... Can you try again, this time with no brim, single perimeter, and a single layer of 0.2? That should make it easier to see.
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
But can i simplify it or need much of it?
Once you have the heightmap sorted out you may be able to get away with just doing a single detailed G29 once in a while and then loading the saved heightmap before the print rather than doing a less detailed but faster G29 before every print. It will depend on how well your bed maintains it's geometry/leveling.
-
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
A10 R0.5 S0.003 B0
just to check add this to the end of the code i already have ?
Yup, add it to what you have already in your M558. Did it change the resulting heightmap at all?
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
the 0.56 i got from following https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
That would be used in the G31 command to tell the printer how far the nozzle is from the bed when the probe triggers, but isn't useful elsewhere. You can prime the nozzle at whatever height you like. I use 0.3, but as long as it's doing what you want for the prime it can be whatever height you want. The slicer will move to the correct first layer height afterwards. Though it should be noted that having a Z move like that to prime the nozzle can confuse the DWC and result in the first layer height and layer counter to behave oddly. It may be better to move that nozzle prime into it's own macro that lives in the sys folder on the Duet. Then you can use M98 0:/sys/NozzlePrime.g to call it in your slicer start code.
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
This is from the print
That doesn't look too bad... Can you try again, this time with no brim, single perimeter, and a single layer of 0.2? That should make it easier to see.
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
But can i simplify it or need much of it?
Once you have the heightmap sorted out you may be able to get away with just doing a single detailed G29 once in a while and then loading the saved heightmap before the print rather than doing a less detailed but faster G29 before every print. It will depend on how well your bed maintains it's geometry/leveling.
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
A10 R0.5 S0.003 B0
just to check add this to the end of the code i already have ?
Yup, add it to what you have already in your M558. Did it change the resulting heightmap at all?
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
the 0.56 i got from following https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
That would be used in the G31 command to tell the printer how far the nozzle is from the bed when the probe triggers, but isn't useful elsewhere. You can prime the nozzle at whatever height you like. I use 0.3, but as long as it's doing what you want for the prime it can be whatever height you want. The slicer will move to the correct first layer height afterwards. Though it should be noted that having a Z move like that to prime the nozzle can confuse the DWC and result in the first layer height and layer counter to behave oddly. It may be better to move that nozzle prime into it's own macro that lives in the sys folder on the Duet. Then you can use M98 0:/sys/NozzlePrime.g to call it in your slicer start code.
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
This is from the print
That doesn't look too bad... Can you try again, this time with no brim, single perimeter, and a single layer of 0.2? That should make it easier to see.
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
But can i simplify it or need much of it?
Once you have the heightmap sorted out you may be able to get away with just doing a single detailed G29 once in a while and then loading the saved heightmap before the print rather than doing a less detailed but faster G29 before every print. It will depend on how well your bed maintains it's geometry/leveling.
Ok retrying the file...
-
What can i do to stop the Heatbed and hotend warming up before the bed leveling in the start script?
i keep getting Error: Z probe readings not consistent
-
i have added Z Baby Stepping
Current Offset: 0.2 mm and seems to be ok, i think i can see a slight bubble to the sheet on the bed -
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
What can i do to stop the Heatbed and hotend warming up before the bed leveling in the start script?
i keep getting Error: Z probe readings not consistent
The slicer will add temp commands automatically if you don't add your own, so you could add some after the homing commands if you want.
The probe readings not consistent error is because we've set the tolerance quite low with M558 S0.003 You can increase that value to make it less sensitive I think the default is 0.005.
-
@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
What can i do to stop the Heatbed and hotend warming up before the bed leveling in the start script?
i keep getting Error: Z probe readings not consistent
The slicer will add temp commands automatically if you don't add your own, so you could add some after the homing commands if you want.
The probe readings not consistent error is because we've set the tolerance quite low with M558 S0.003 You can increase that value to make it less sensitive I think the default is 0.005.
Ok, will have to look into added some code maybe, thank you for your help with this is very appreciated.
-
@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:
i have added Z Baby Stepping
Current Offset: 0.2 mm and seems to be ok, i think i can see a slight bubble to the sheet on the bedIf you find a consistent amount of baby stepping that you need you can add it to the G31 Z value to make it permanent.
Has the height map image improved at all? Is the first layer going down better?
