E 3d BIGBOX Duel head
-
@phaedrux Yes and you are correct the past owner did a fine job of jamming filament into the extruder without the fan on so when it did melt, it melted all the way up onto the extruder (where air fins are). once i removed the extruder and hit it with a hand held propane torch it became unclogged. put it back to together and new it extrudes.
ok the next things to be done are leveling the bed and calibrating the head with the bed and then our first print.
any ideas on these?
-
Some calibration steps here: https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40
-
@phaedrux thanks for the form but i am still having issues even with the form. i have leveled the bed so the most i am out between all four corners is 0.53 mm. I think this is good.
i have ran the bed level program and it takes 110 points for a mesh map? well it completed and stated i needed to make the Z=0 datum? So my Z probe or Z sensor needs to be calibrated to 0, is this a focal point of the sensor?
by the way how would i go about loading a drawing to print in this software?
do i need to send the stl file into a slicer and if so which one? i have leachee and chuto box -
The probe would need to be calibrated, yes. That means determining the distance between the nozzle tip and the bed when the probe is triggered. Here's how: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
For the mesh, it can use as many points you want up to 441. See more on mesh compensation here: https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation
The Z=0 datum is the point where the nozzle is actually touching the bed. Having the correct probe offset calibrated is the first step, the second step is using the probe to home z and determine where that Z0 is. Then when you create the mesh, it will be relative to that 0 point. So your homeall.g (G28) needs to use the probe to home the Z axis (using G30). Post your homeall.g file if you're unsure.
For a slicer I would suggest setting up Prusa Slicer. https://www.prusa3d.com/prusaslicer/
-
@phaedrux
ok on this probe calibration for Z. in the paper work under calibrate the Z probe trigger heightsteps 5 thru 7 go well but two issues i am having.
-
the Z probe value is not reporting any where i can see. i give the command and the console shows the command is good but i do not get any value to read.
-
once the Z probe triggers the bed backs off some.
-
-
Are you looking in the full console tab?
What commands are you sending specifically? -
@phaedrux
Are you looking in the full console tab? Well i click on it and it comes up and the code is shown to be good but not data. there is a value under the z probe between 0-1000.What commands are you sending specifically? the ones the instructions show.
Cancel any currently active mesh compensation with M561
Use the X and Y jog buttons to position the nozzle over the centre of the bed
Jog the nozzle down until it is just touching the bed or just gripping a sheet of paper. If the firmware doesn't let you jog it down far enough, send M564 S0 to disable axis limits.
Once you have the nozzle touching the bed, send command G92 Z0 to tell the firmware that the head is at Z=0
Jog the head up by 5 to 10mm
Send command G30 S-1. The nozzle will descend or the bed rise until the probe triggers and the Z height at which the probe stopped will be reported. If you are using a nozzle-contact Z probe, the trigger height will be slightly negative. For any other type of Z probe where the probe triggers before the nozzle contacts the bed, it will be positive.it is at this point i do not have a value on the z probe to enter
-
@testpro said in E 3d BIGBOX Duel head:
Send command G30 S-1. The nozzle will descend or the bed rise until the probe triggers and the Z height at which the probe stopped will be reported.
If you're in the gcode console tab the results should be reported there. Can you take a screenshot and show what you have there?
It would say something like "probe stopped at 1.567mm"
-
@phaedrux
ok went back redone it again today and i am now getting a value. i think i was leaving our the "-" the last command.ok so it is now calibrated and the offset for X & Y is now set as well.
so what would be next so i can get a test print off and running.
-
Well if you have the G31 offsets entered in config.g now you should be able to homeall reliably.
Now you can try doing a mesh compensation run to see what the bed looks like. https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation
Or calibrate the extruder, etc. https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40
If that's all done, then set up your slicer and try a simple test print.
-
@phaedrux
and the saga continues.i believe we have a good Z datum now.
the mesh comp program does not work to well because when i run it it states it can not reach half or most of the points for some reason.
so i have moved the x axis to the right with the +100 mm move button on console and the x ends up around 140 on the marked bed after hitting that button 3 times so no moving in mm or something ?
i also have the axis set for x=290 Y= 190 Z=290 but nothing goes that far in reality in the printer so i think it is reading in steps and not mm if that is possible or it is half stepping?
also think the printer thinks the homing puts the extruder in the middle of the bed instead of most front left corner which is what it does.
files you will ask for:
; Configuration file for Duet WiFi (firmware version 3); executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"big Print 1" ; set printer name ;M669 K1 ; select CoreXY mode ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E320.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 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 X290 Y190 Z190 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z2 S2 ; configure Z-probe endstop for high end on Z ; Z-Probe ;M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds M558 P5 C"e0stop" H5 F120 T3000 ; Z probe connected to E0 endstop input ;M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X90 Y150 Z1.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R160 S240 ; set initial tool 0 active and temp 240C and standby temperature to 160C ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 18:51:26 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-235 Y-215 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-235 ; home X axis
G1 H1 Y-215 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-215 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X10 Y10 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@testpro said in E 3d BIGBOX Duel head:
because when i run it it states it can not reach half or most of the points for some reason.
Well the probe has an offset from the nozzle, so it can't physically reach all the places that the nozzle can. If your mesh grid defined in M557 includes points that it can't physically reach with the probe then you'll get that warning. So you can update the M557 grid range to take the probe offset into account, or ignore the warning.
-
@testpro said in E 3d BIGBOX Duel head:
so i have moved the x axis to the right with the +100 mm move button on console and the x ends up around 140 on the marked bed after hitting that button 3 times so no moving in mm or something ?
I'm not exactly sure what you mean by this. Can you use a ruler to measure the actual distance moved when you command 100mm? the steps per mm may be incorrect.
@testpro said in E 3d BIGBOX Duel head:
i also have the axis set for x=290 Y= 190 Z=290 but nothing goes that far in reality in the printer
The best thing to do is to measure the actual reachable range once you have confirmed that the steps per mm are correct and that 10mm commanded equals 10mm of actual movement.
Send M564 H0 S0 to allow all movement without restraint, then carefully move the nozzle to the front left corner of the bed and send G92 X0 Y0. Now jog the X and Y axis until you reach the other end of travel. The resulting X and Y positions will be your M208 maxima values. If the endstops require the nozzle to move off the bed slightly to trigger, then you can use a negative number for the M208 minima. That will keep 0,0 on the print bed.
-
@phaedrux
ok we finally have a print (Mr. Fuzzy). So there is some more fixing to be done but at least after 6 years sitting in my boss office broke it finally prints.i am going to need to clean up this print some so i can print the bottom piece i need for the duel head set up. right now the right head is working and left has melted out because i did not have the fan on.
the bed seems to raised in the middle for some reason so must figure this out as well.
At this point we can continue here or i can start new thread on print quality after looking over the history of questions first or other threads. also about the bed level thing as well.
what do you think? and any suggestions on the print quality or bed?
thank you for all your help with this project without this forum and your advice i would still be at it.
so thank you. -
Same recommendation as before:
Now you can try doing a mesh compensation run to see what the bed looks like. https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation
Or calibrate the extruder, etc. https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40
This thread is a bit long at this point. If after going through those you have more specific questions, probably best to start a new thread. It'll get more eyes on it as well. Try to include as much fresh info as possible off the hop just to get everyone up to speed with what you have going.
-
@phaedrux
ok here we go again. i can't seem to get a good bed compensation grid down. i am usingM557 x05:250 y05:200 s40 which gives me 35 points and then use G29 S0 and all it gives me is four points and tells me the z axis cannot reach the other points? kinda lost here.
-
@phaedrux i do have height map file but no mesh file?
RepRapFirmware height map file v2 generated at 2021-06-28 11:26, min error -0.544, max error 0.151, mean -0.065, deviation 0.281
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
5.00,250.00,5.00,200.00,-1.00,40.00,40.00,7,5
0, 0, 0, 0, 0, 0, 0
0, 0, 0, 0, 0, 0, 0
0, 0, 0, 0, 0, 0, 0
0, 0, 0, 0, 0, 0, 0
0, 0, 0, 0.114, -0.544, 0.151, 0.018 -
@phaedrux would this have anything to do with my Z stepper motors being wired backwards on the duet board ?
-
How do you mean wired backwards?
If you're getting a lot of skipped points you'll have to adjust your grid range to take into account the Z probe XY offset. Due to that offset there will be parts of the bed that the nozzle can reach but the probe cannot.
35 points isn't a lot of detail. It can be very informative to do a high detail probing so that you can see what the topology of the bed actually looks like. You can use up to 441 points.
Instead of using M557 S40 which defines the spacing of 40mm, you can use P# which lets you define the number of points to use and it works out the spacing for you.
-
@phaedrux
ok went back over everything and got the bed compensation to work and i now have 99 points for bed leveling. so not bad i think.now onto calibration the extruder with the test files.
