Topics created by flobler

@flobler OK, I figured it out already 😄

This was a stupid typo that I then carried from bed-temperature.g to hotend-temperature.g via copy paste. I tried all these files with PLA previously which worked fine. This time I had PETG loaded but unfortunately looked for PTEG in the object model and not PETG.

Therefore the loaded filament and my bed-temperature.g and hotend-temperature.g system files did not match and therefore not use PETG temperatures before trying to start the print.

Sorry for the noise 😉

This fixed my issue, thank you for your help @Stephen6309!

@dc42 my bad, as you can see above I failed to remove the G1 H1 X5 F1200

I re-tested without and this works now. Thank you very much!

@mfs12 it needs updating on the docs site too
Screenshot_20220321-090429.png

I can't see anything in the gcode that would indicate a problem.

All I notice is that you use Z hop. Is there perhaps some backlash or inaccuracy in your Z movement? Have you tried without Z hop?

The other thing is that it's simply a matter of flow rate being a bit off? It looks good for the first layer, but maybe only because it's actually too close? And then the next layer is actually under extruded?

You could also try a different slicer, just to remove that as a variable. It's not a bad idea to have two setup anyway.

@owend Thank you very much!

@pakue thank you! I have seen that but I'd like to know for sure instead of working/planning based of an assumption 🙂

Great, thanks everyone for the help! Looking forward to the fix!

@flobler thanks for confirming this. I'm sorry it took a while to resolve.

@flobler said in PID Tuning macro - not waiting for procedure to finish:

M106 P0 S0.3 ; set part cooling fan to 30% M303 H1 S245 ; perform tuning routine at 245C

YOu are tuning the fan on manually. To let the firmware control the fan and take that into account you. need to leave the fan off and use M303 T0 S245 instead. That tunes the heater as part of the tool it's associated with. T0.

It may have to be done in separate zip files. One for configs, one for firmware, and one for macros, uploaded to their respective places.

@mfs12 it looks like upgrading everything to 3.4.0 fixed this for me and all messages are now displayed as they should 🙂 thank you very much for your help along the way!!!

@phaedrux Thanks!

Gcode: low_cube_80_0.2mm_PET_MK3_41m.gcode

Probe: SuperPinda

Extruder is calibrated, yes.

I am using mesh bed compensation.

bed.g

; bed.g ; called to perform automatic bed compensation via G32 ; G28 ; home all M400; ; wait for current moves to finish M558 A3 ; set times to probe to 3 G30 P0 X24 Y104 Z-9999 ; probe near left leadscrew, front of Y axis G30 P1 X228 Y104 Z-99999 S2 ; probe near right leadscrew, back of Y axis and calibrate 2 motors M400 ; wait for current moves to finish ; G91 ; relative positioning G1 Z5 ; raise nozzle 5mm M400 ; wait for current moves to finish ; G90 ; absolute positining G28 ; home all G29 ; mesh bed leveling G1 X0 Y-3 Z0.4 F3000 ; bring nozzle into prime line position M558 A1 ; reset times to probe to 1 ;

macros called in homeall.g

; homing_modifications.g ; tune motor drivers, set motor current and V parameter for homing moves ; apply modifications M569 P0.1 V10 ; reduce V to ensure stealthChop is enabled for X M569 P0.2 V10 ; reduce V to ensure stealthChop is enabled for Y M913 X70 Y70 ; drop motor current to 50% G4 P100 ; wait 100ms ; tune drivers G91 ; relative positioning G1 H2 X0.2 Y0.2 F3000 ; power up motors to ensure they are not stalled G4 P100 ; wait 100ms M400 ; wait for current moves to finish ; homing_modifications_reset.g ; reset all homing modifications applied in homing_modifications.g ; M913 X100 Y100 ; return current to 100% for X and Y M569 P0.1 V2000 ; restore default V for X M569 P0.2 V2000 ; restore default V for Y G90 ; absolute positioning

I think I have potentially fixed it. I added the ";E" comment in Prusaslicer to the end gcode:

G4 P200 ; wait M104 S0 ; turn off temperature M140 S0 ; turn off heatbed M107 ; turn off fan {if layer_z < max_print_height}G1 Z{z_offset+min(layer_z+30, max_print_height)}{endif} ; E Move print head up G1 X0 Y200 F3000 ; home X axis M84 ; disable motors

Now the print also shows the right size in DWC + whatever value is used for Z-hop. Example:

Z-hop = 0.4mm object height = 10mm height displayed in DWC = 10.4mm

It also seems to print the second layer fine now. Initially when I added the ";E" comment, it caused the first layer to be squished way too much (it was dialed in nicely before applying the comment). So I think something was off with the first layer before I added the comment which caused me to compensate with baby stepping and then carried into the second layer.

I will do a few more tests now.

@flobler said in Using WiFi and Ethernet networking setting in universal config.g:

So if I have M552 S1 in the network settings, it should not matter if I use a WiFi or Ethernet board?

That should work for any Duet board and DHCP.

For anyone reading this later, this is a working macro to calibrate the Z trigger height for the Pinda/Superpinda: z_offset_calibration.txt

EDIT: one might want to heat the bed to the bed temperature that will be used for printing to get an accurate result throughout the procedure. In my case with the MK3 bed and a temperature of 85C for printing PETG the value was about 0.15mm off compared to running the macro with a cold bed.

yes the initial diagram was incorrect.

I am very thankful I found this thread because I was having the very same issue and, after some experimenting with your scripts it works better for me too now.

However, I do have a question: why there is no M915 command on these routines? I assume if ignored it assumes a certain value lie S3??

I mean, I tried with and without M915 and it works, so... I am confused, somehow

the einsy has a seperate line on the board for the heated bed.
the duet does not. if your heatbed does not exceed the rated current for the duet that one connection from the psu is fine (using wires with sufficient diameter)
if it is more than the duet can handle use an external mosfet and connect the second line to that.

Would you mind posting your motor settings once you are done? I'm still having trouble with configuring SpreadCycle on the Prusa MK2.