I figured it out. It's crashing the head on the X-axis due to the probe point for the leadscrew being slightly off. I just need to adjust that.

@wilriker Would help if we knew exactly what was going on.

Also, if all is he looking to do is change power at the heater block he can change the PWM duty cycle and get the same results. If he's looking to increase power draw on a FET or something then he would need some power resistors.

@mrehorstdmd @zapta @mendenmh @mwolter @arhi I just replaced the Igus bushings with the LM16UU I ordered. No more issues. Now I have no idea what to do with all these Igus bushings I have.

@DIY-O-Sphere Okay, this is what ended up working.

; Heaters
; Bed
M308 S0 P"e6temp" Y"thermistor" T100000 R4700 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H7 C"!exp.heater7" T0                           ; create bed heater output on exp.heater7 and map it to sensor 0
M307 H7 A223.1 C298.7 D1.2 V22.8 B0            ; Disable bang-bang mode for the bed heater and set PWM limit
M140 H7
M143 H7 S80                                   ; set temperature limit for heater 0 to 80C

The naming conventions for pins and thermistor inputs, as well as having the number offset for them seems like an oversight.

@tekkydave Yep, mine is fake as shit. Looks like I need to get some better ones.

Yeah, definitely my Z-axis. I ran some prints and changed my pause and resume to not lift Z and the indentation is gone. Looks like I need to get some pillow block bearings for the leadscrews and new couplers.

Yeah, definitely my Z-axis. I ran some prints and changed my pause and resume to not lift Z and the indentation is gone. Looks like I need to get some pillow block bearings for the leadscrews and new couplers.

@o_lampe It's a corexy. There are 4 Z motors. I need to get the spider couplers instead of the spring couplers.

@engikeneer Doubtful. 16mm rods on the y axis and 12mm rods on the x axis and it's really rigid, besides the fact that I just use the load/unload macro, so I don't really push on anything. I'm running a test print right now. My z couplers are kind of fucked up, so I'm guessing that's the issue.

@phaedrux No idea. I think it's mechanical. I'll look into my couplers and lead screws. I have no idea what happened to the one where it worked correctly. I'll change my pause and resume g-codes so it doesn't change Z height and we'll see what happens.

@o_lampe It's a hemera. There should be plenty of print moves to "build up" chamber pressure before it moves onto the next layer. It would also show issues with retractions as well, which it does not, and it is even on all of the parts. I think it might be an issue with my Z axis not moving back into place correctly.

@phaedrux It is most definitely primed. I have 9 of these parts I print simultaneously and it happens on every single one exactly the same.

@dc42 I extrude anywhere from 55-110mm of filament before the 10mm to purge and prime the nozzle, so yes, there is a ton of filament that comes out of the nozzle.

@phaedrux Notice the angled transition from white to red

Same one with green to white.

It should look like this where the layer is solid and you can't really see the transition.

This happened on multiple of them. I'm thinking it might be my Z axis.

Hi all,

I'm getting into multi color printing. Right now I have is set up in prusaslicer so there is a M600 on my color change. The print head parks, I run an unload macro, then I swap the filament, run a load macro, then resume the print.

I'm having issues with what appears to be under extrusion after the filament change. There is an indentation on the color change layer. It is not a layer shift, and it happens for the whole layer, independent of model size.

This is my pause.g :

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Nov 16 2018 19:13:04 GMT-0500 (Eastern Standard Time)
M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y300 F6000 ; go to X=0 Y=300

This is my unload macro:

T0		;Select tool
G1 E-5 F500	;Retract 5mm filament at low speed 
G1 E-60 F3000	;Retract 60mm filament at high speed
M84 E0 		;turn extruder motor off to let user unload if filament locked - 

This is my load macro:

T0		; Select tool
G1 E55 F200	; extrude 55mm at low speed
M84 E0	        ; turn extruder motor off so the user can feed by hand - change for another tool

and this is my resume.g:

; resume.g
; called before a print from SD card is resumed
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Nov 16 2018 19:13:04 GMT-0500 (Eastern Standard Time)
M83                  ; relative extruder moves
G1 E10 F2000         ; extrude 10mm of filament
G1 R1 X0 Y0 Z5 F6000 ; go to 5mm above position of the last print move
G1 R1 X0 Y0          ; go back to the last print move

This is the gcode from a file that has a layer change in it:

G1 X136.521 Y141.794 E43.84769
G1 X136.949 Y141.853 F12000.000
;LAYER_CHANGE
;Z:14
;HEIGHT:0.2
G1 Z14.000 F12000.000
;COLOR_CHANGE,T0
M600
G1 E42.44769 F2400.000
G92 E0
G1 Z14.200 F12000.000
G1 X216.752 Y221.763
G1 Z14.000
G1 E1.40000 F2400.000
;TYPE:Perimeter
G1 F3600.000
G1 X217.521 Y221.020 E1.44871
G1 X218.325 Y220.315 E1.49745

I believe that there is an issue somewhere that comes from my load or unload macro and the gcode that the slicer inserts. Can anybody point me in the right direction?

Thank you

@Phaedrux I had 2 cat5 cables that were wired for the toolhead. The stepper motor as well as wires for other items (fans, limit switches, z-probe, filament sensor) were in the cat cable. The IR z-probe was in the same bundle as the stepper motor, and they went through the same quick disconnect automotive connector. I think I was getting interference on the IR sensor, because I could see it jump around when the printer was homing. It wouldn't trigger the IR sensor, but it would jump between random values from 0-467 (sometimes it would throw 150, 200, or 350. This is not how the IR sensor works so I had to be getting interference) The IR sensor plugs into the duet right next to the paneldue header. I'm not sure where the traces are, but they may be running near the paneldue traces. This is probably where the interference was coming from for the paneldue. I can test it some more by extending the cable for the paneldue to see if I still get interference with a longer cable, but I think that's what my issue was. Now the stepper motor wires are twisted in pair with the coils on the motor.

@Phaedrux Well I've done a few prints now and it seems to be much better. I think the wiring I had for the toolhead was causing some issues, and the braiding probably helped as well.