@fcwilt Swapped that all to mesh.g and called G29 instead. Redid, MBLA, Z Trigger height, and ran a 100 point to start. Definitely yield improved results and is functioning correctly. Just some fine-tuning and I think I will eventually implement something like a 400-point height map once more things on the machine are finalized. Thanks for the help as always! Your explanations are always a nice balance of basic enough to fully understand but not patronizingly so

@Mr-Yod @jumpedwithbothfeet

Originally I tried the actual outX pins on OUT4-6 to no avail so I tried the tach pins, but I'll switch back. The jumper for the OUT4-6 is on the 12V connection.

Just tried powering the relay board with an external 5V and used the out pins (instead of tach) and still didn't have any luck. Seems like it's a board issue then, I'll have to find a new one or use the remaining IO pins I was hoping to save.

Thanks for the help, hope everyone has had an enjoyable holiday.

Over Extrusion ended up being the problem on this one. After dropping the DWC EM control down to 75% yielded proper layer width, height, and adhesion. A few questions on what to do with this information.

Does anything from the DWC extrusion factor control actually stick or is just for watching live and then going into my configuration file and adjusting?

Is there a flow test or calibration I could run to double-check/calibrate this properly? I thought my E-step calibration would mostly account for this error but that doesn't seem to be true.

@jrcl said in Servo Configuration Check:

@fcwilt I don't unfortunately. I'm no electrical engineer, but could I use some sort of amplification module on the signal? Not sure if PWM signals work like that/or can be amplified like that.

Managed to find the control signal specs. What are the PWM signals on the Duex able to supply?

@phaedrux Awesome! This is the type of stuff I was looking for, much appreciated.

@phaedrux The M997 S1 command fixed it for me. Amazing! Okay back to your walkthrough

@the-chairman I'm not an expert but this would be used if you used the VIN terminals on the board to power your bed, which you would know. Seeing as you're using a 120V bed with an SSR you probably aren't using those.

Just an aside. Got in my MG995S servo and swapped it out and was rewarded with immediate success. Still interested in hearing your findings on the higher torque servo signal @fcwilt

@o_lampe Thanks for the insight! Just some additional clarification

So other than the logic being wrong, I need to either jumper 5V to the fan ports and use those instead, or add in a level shifter board so I can drop the 12/24V heater signal down?

However, using the M42 command to set the pins to HIGH and LOW is the correct way to do it. I just need to make sure the logic is proper.

@phaedrux You guys are awesome! I have 3.3 and updated paneldue firmware on the machine successfully now. Thank you!

@infiniteloop @droftarts It was the fan miniblade fuse! Should've checked this sooner but haven't blown many fuses yet, lesson learned. I had even swapped my Duet 2 wifi with another at a point so I thought no way both have a blown fuse....sure enough they both did. I think it was long before I was setting up this machine as the electromagnet has less than 1A draw on 12V, but I'll be double checking

Trying to use the fan ports on a Duet 2 wifi to control a 12V electromagnet. I have the fan jumper on the VIN selection and the board is powered at 12V. However, my always-on fans (just as a check) never turn on and I can't turn on the fan0 with M42 either. I checked both sets of pins with a multimeter and didn't get much of a reading, but unsure if you can given the PWM signal (though I thought I had before). M98 on my config yields no issues either. Any help is appreciated

; General preferences
G90                                     ; send absolute coordinates...
M83                                    	; ...but relative extruder moves
M550 P"FSR Test Bench"                  ; 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 S1				; physical drive 0 goes reverse
M569 P1 S0				; physical drive 1 goes forward
M584 X0:1                          	; set drive mapping

M350 X16 I1                     	; configure microstepping with interpolation
M92 X80.0           		; set steps per mm
M906 X1000 I30                 ; set motor currents (mA) and motor idle factor in per cent
M84 S30                         	; set idle timeout

; Axis Limits
M208 X0 S1                        	; set axis minima
M208 X267 S0                      	; set axis maxima

; EndStop
M574 X1 S3 							; X endstop on low end with sensorless homing
M915 X R0 F0

;Relays
M950 F0 C"fan0" Q500					;tray electromagnets
M106 P0 S1 H-1

@droftarts this was what I needed! I had been using the table above that, that says PCB Pinout, but I'm now realizing it's for the BL Touch's pins not the boards. Thanks!

@mikeabuilder it did live in a cable chain for a while but since troubleshooting and the rewire its been removed and still seems to have the issue

@Phaedrux yes the self test upon startup is working fine, which is the first time I've seen that working but holding a triggered state in DWC. It is wired like so to my MB6HC:

By servo commands do you mean just sending M42 or M280 commands to try and get it to go manually? If so I haven't tried those yet and will give that a go next

@zBeeble Unfortunately I tried a full rewire and different set of pins before posting this

My BL Touch deploys correctly upon turning on my machine but doesn't respond to M401 or M402. The Z-Probe signal in my DWC seems to always show it as triggered so when I try to test dynamically it ofc triggers immediately. I seem to have it wired correctly so I believe something in my config.g is wrong. Just looking for a second set of eyes to see if anything sticks out in my config.g or where else to look. Thanks in advance!

; Enable network
G4 S5														;wait for board to start
if {network.interfaces[0].type = "ethernet"}
    M552 P192.168.1.14 S1
else
    M552 S1
 
;General Prefrences
G90                             							;send absolute coordinates...
M83                             							;...but relative extruder moves
M586 P0 S1 										; enable HTTP
M586 P1 S0 										; disable FTP
M586 P2 S1 										; enable Telnet
M586 C"*"
M550 P"RL1 V3"                  							;set printer name
M669 K1											;switch to CoreXY mode

; Drives
M569 P0.0 S1												;X motor runs 
M569 P0.1 S0												;Y motor runs 
M569 P0.2 S1												;Z1 motor runs 
M569 P0.4 S1												;Z2 motor runs
M569 P0.5 S1												;Z3 motor runs
M569 P50.0 S0												;E moves
M569 P0.3 S0												;U motor runs
M569 P50.1 S1												;V motor runs (front clamp driver)
M569 P50.2 S1												;W motor runs (back clamp driver)

M207 S1.5 F7200 Z0.2										;set retract length
M584 X0.0 Y0.1 Z0.2:0.4:0.5 E50.0 U0.3 V50.1 W50.2     		;Set drive mapping

M350 X16 Y16 Z16 E16 U16 V16 W16 I1           				;configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E685.37234 U100 V80 W80        	;set steps per mm
M566 X900.00 Y900.00 Z60.00 E300 U900.00 V900 W900   		;set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E7200 U17000.0 V6000 W6000 	;set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E3000 U500.0 V500 W500  		;set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1200 U3800 V800 W800 I30        		;set motor currents (mA) and motor idle factor in per cent												
M84 S30                         							;Set idle timeout

; Axis Limits
M208 X0 Y0 Z-1 U0 V0 W0 S1                    										;set axis minima
M208 X100 Y100 Z38.45 U330 V55 W55 S0              								;set axis maxima

; Endstops
M574 X1 S1 P"0.io8.in" 										;configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
M574 Y2 S1 P"0.io7.in" 										;configure switch-type (e.g. microswitch) endstop for high end on Y via pin io1.in
M574 Z2 S1 P"0.io2.in+0.io1.in+0.io5.in"					;configure switch-type (e.g. microswitch) endstop for high end on Z
M574 U2 S1 P"0.io6.in"										;configure switch-type (e.g. microwswitch) endstop for high end on U
M574 V1 S1 P"50.io6.in"										;configure switch-type end stop for low end on V
M574 W1 S1 P"50.io5.in"										;configure switch-type end stop for low end on W

; Z-Probe
M950 S0 C"0.io4.out"              						; create servo pin 0 for BLTouch (use IO_4/5/7 for 6HC)
M558 P9 C"0.io4.in" F100 H5 R0.2 T6000 A5 B1			; set Z probe type to bltouch and the dive height + speeds
G31 P25 X-19.14 Y0 Z4.242            					; set Z probe trigger value, offset and trigger height
M557 X0:80 Y12:100 P3        							; define mesh grid

;Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950         	; configure sensor 0 as thermistor on pin temp0
M950 H0 C"0.out0" T0                                   	; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.075 K0.161:0.000 D3.07 E1.35 S1.00 B0
M140 H0                                               	; map heated bed to heater 0

M308 S1 P"50.temp_0" Y"thermistor" 							; configure sensor 1 as thermistor on pin temp1
M950 H1 C"50.out0" T1                                  	; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R4.585 K0.421:0.683 D3.75 E1.35 S1.00 B0 V24.2	 	; 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"0.out7" Q500 								; create fan 0 on toolboard out1 and set its frequency
M106 P0 S0 H-1 T50       									; set fan 0 value. Thermostatic control is turned on
M950 F1 C"0.out8" Q500 								; create fan 1 on toolboard out2 and set its frequency
M106 P1 S0 H-1    										; set fan 1 value. Thermostatic control is turned off

;Tool Definitions
M563 P0 D0 H1 F0										; tool 0 uses extruder drive 0 and heater 1. Fan 0 and Fan 1 are mapped to 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

;Misc
M950 P3 C"0.out2" Q500								; allocate port 3 to out2 on MB6HC for Inlet valve
M42 P3 S0  											; set to off
M950 P4 C"50.out2" Q500								; allocate port 4 to out2 on Mini5 for IPV Direction
M42 P4 S0  											; set to off
M950 P5 C"50.out1" Q500								; allocate port 5 to out1 on Mini5 for Chamber Valve
M42 P5 S0  											; set to off
M950 P6 C"0.out3" Q500								; allocate port 6 to out3 on MB6HC for Release Valve
M42 P6 S0  											; set to off

; Epilogue
M556 S100 X0 Y0 Z0                                 		; Put your axis compensation here
M912 P0 S0                                        		; Put your CPU temperature sensor correction here
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
T0

@dc42 appreciate the clarification. I assume polling is the only way with ethernet boards then?

@oliof I had never heard of this but just did some reading. How cool! Thanks for your quick response

I read a few posts from 2017 and 2018 talking push notifications and webhooks. However, it seems like RepRap Notify was the most cohesive project to tackle that problem and is no longer maintained with newer versions of Reprap. I'm wondering if any other developments have been made on this topic? Is polling rr_model the best way to get notifications when jobs are complete or other events happen?