Posts made by TimV 0

@Phaedrux
Sorry for the delay. It turns out that I made some slicer changes to try to center the print on the bed, and then homed the printer, and wire tied the extruder tube...

The point is that I "fixed" multiple things at the same time, and my X limit switch became loose and that caused a huge set of issues until I figured out that it was not actually working / connected.

This is an ender 5 pro that I converted to the Duet 2 Wifi board. I kept the ender5 limit switches but replaced the wiring with generic 3 pin wires to the board. I am having problems keeping the wires connected at the end stops. I applied heat shrink tubing at the limit switch end, so they now all look perfect but seem to vibrate loose.

Would you be willing to offer an opinion on a more reliable end stop setup that I could connect directly to the duet 2 endstop to stop having endstop switch connection issues?

@Phaedrux
I am very happy with the print quality that I am getting. I'm trying to deal with a couple of small things that remain.

It happens from time to time between prints that I will get a message that I do not have an extruder selected or online or whatever. I can click on the tool and it will resolve. I would appreciate knowing how to make sure that it is always on when I either turn on the printer or send a job.

It would also be nice if it would automatically heat the nozzle to the temperature that I want up front. I suspect that I am missing a key line somewhere. Should I put it in config.g, or in the start code from the slicer?

Along the same lines, when the print finishes, I would like to shut off both the nozzle heater and the bed heater.

@TimV-0
All my plug ins say they are 3.4.4

@Phaedrux
Thanks for the file. I can't be certain for all of the files, but the .zip file is the one that I have loaded.

The heightmap tab was a big orange icon that said stop in the plugins. All the other plugins said start. Is this backwards or was it the only plug in running and I just shut it off? I clicked it again and it still shows the big green icon that says start?

I have lost the heightmap icon on the main DWC which is what I clicked to see it in the first place. Not there any more.

I'll just pretend I know what I am doing for now as I don't really want to restart the print

The screens don\t seem to display what I would expect...

@TimV-0 Hi: I sent out the G29 last night to generate a heightmap.
It sampled lots of spots on the bed and I got no feedback.

I tried printing today and I have a small forest of PLA that I wasn't expecting.

I clicked on the heightmap and it is empty. I'm sure the bed is not perfectly flat.

Is there somewhere I should have saved it when it finished? I think I sent an M500 because I thought I should.

@Phaedrux
Always good solid advice. Most of my issues with why I wrote in for help are related to no knowing which problem was creating which challenge.

@Phaedrux Thanks for all of your help and for sticking with me.

I will do the auto bed levelling next. I did look at the height map that I had and it looks terrible. I am currently printing a case for the duet 2 board to make it a little safer and hopefully protect the actual wiring. I know I should have done the auto bed levelling first. |I had some quality issues and some print lifting. I should have really cleaned the print surface first. Just because it's brand new doesn't mean it is ready to go. I will also need to go over the extruder setup as I can see from the print that it is no set properly.

I did add a dual gear extruder, but I am thinking that maybe I should stack it on the carriage and get rid of the long bowden tube. Any thoughts or cautions I should know about?

@TimV-0 Sorry, it is not perfect. I think I need to run the autobed levelling to set up the heightmap properly. I just hope it doesn't undo what I have done

@Phaedrux
Once more for good luck.
From the Test and Calibrate Document
HomeX Ok
HomeY Ok
HomeZ Ok After G30 is run, bed raises until bltouch triggers. Bed stops raising at 2.73mm from nozzle

Calibrate the Z probe trigger height
Issue M561 - done
Center nozzle at center of bed - done
Z is still reporting height = 2.73mm
Raise the bed to remove the 2.73mm
Bed not trapping paper
Issue M564 S0
Nozzle contacts paper at -0.4mm
Nozzle stops paper at -0.45mm
Issue G92 S0 - Confirm bed height indicates 0.00
Lowered Bed by 5mm
Measured distance to confirm 5mm
G30 S-1 stopped at 2.73
G31 P500 X-45 Y0 Z2.73 set in config.g
edited G31 in config.g.bak

Reset the duet 2 board.

Position indicator says Z 0.00

That is not true. after the board reset, the nozzle is 10mm above the bed

HomeX -- ok
HomeY -- ok
HomeZ -- ok

Tool position reports Z at 2.73mm

I don't want to do anything else on my own until I understand for sure what is happening.
Is this not the result of what I set in the G31 command in config.g?

Ok, I am really confused now. I started a print job and it is printing perfectly. I have a good, even first layer.

@Phaedrux
config.g

homeall.g

bed.g

cube.gcode

@TimV-0
I’m still fighting with this. I figured out that my bed kept climbing because the bltouch was off the left side of the plate

I have gone through the document several times and I end up in the same place.

I have brought up the bed and levelled it with a piece of paper until it is consistently perfect. I set the z height to zero, drop the bed by 10mm, issue the g s-1 command and I end up with 2.5mm. I’ve put that in my config.g file, and when I start a print, the filament is falling in thin air to the bed.

I’ve tried to adjust z by microstepping, but since the print has started, I can’t adjust z through DWC, since it needs to be homed again.

@TimV-0 Sorry, I bet you wish I would read the whole document before applying one sentence and reporting back. I'll try

@TimV-0 Finished the last paragraph in the document and the probe is triggering reliably. Tool position is consistent at 2.875

@TimV-0 When I fixed the last problem with the double S1's I didn't realize that the probe was trying to trigger while off the bed on the minimum side. I adjusted the x position to 35 and now the probe is triggering properly.

It triggers repeatably at 2.5 mm on the probe and then lowers to exactly 7.5 according to the tool position display.

Perhaps I should try a test print?

@Phaedrux Thanks - will do. There are too many documents on this subject imho

@TimV-0 Reset the 2nd S1 to S0
Z does not stop when the BL Touch touches the bed. It keeps going.

@Phaedrux

G28 ;Home

G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up
G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position
G1 X10.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line
G1 X10.4 Y200.0 Z0.28 F5000.0 ;Move to side a little
G1 X10.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up

Thanks for spotting the S1

Hi: I have been trying for a week now, and clearly do not understand Gcode well enough or the concept clearly enough to set the bed height for my duet2 wifi to correctly print.

I believe I have read everything in the documentation, but my bed ends up far too low on z to print.

X,Y,Z all home successfully.
My BL Touch is triggering properly and everything looks fine while it is starting.

When the printer starts printing, the bed is nowhere near the correct level to print. I looks to be 25-35 mm too far from the nozzle.

This is the bed file content
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.14 on Sat Nov 12 2022 13:27:36 GMT-0500 (Eastern Standard Time)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation

This is the config file
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.14 on Sat Nov 12 2022 13:27:36 GMT-0500 (Eastern Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender 5 Pro" ; set printer name

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes forwards
M569 P2 S0 ; 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 E420.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 X220 Y220 Z300 S1 ; set axis maxima

; Endstops
M574 X2 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.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 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
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

This is homeall
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.14 on Sat Nov 12 2022 13:27:37 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X225 Y225 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-5 Y-5 F6000 ; go back a few mm
G1 H1 X225 Y225 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X15 Y15 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

This is homez
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.14 on Sat Nov 12 2022 13:27:37 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lower Z relative to current position
G90 ; absolute positioning
G1 X15 Y15 F6000 ; go to first probe point
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z-5 F100 ; lift Z relative to current position
G90 ; absolute positioning

I would appreciate input on which file(s) need to be reviewed and which documentation is the best source to correct what I have missed. I will find the error if I can get some ideal of which file it is in.

Thanks

@Phaedrux
Wow, you always have the best questions

I can shine a light on the display and see absolutely nothing. I really think it is smoked (although none leaked out and there are no signs of burning).

Pressing on the screen did not produce any response either in audio or visual.

The truth is I don't really need the screen to print or do anything else now that DWC is working.

I've got the endstops working and the motions going in the right directions.

I have a BLTouch that I would like to put on it, but in reading ahead on the install, I'm not sure I am that brave.

@Phaedrux connected fine with Brossa to the paneldue. It wrote 668 pages and said it was successful.
I have replaced the 4 pin cable between the boards and actually connected it to the panel due port this time, and it is still dark. I'll try later tonight when I have a better chance if seeing if the backlight is trying