FSR + DuetWifi

[Char'les Grey]

Already I swapped out the rambo for the duetwifi, and the HE280. Did my first test temp and it held... right out of the box... I've been struggling MONTHS to get a stable HE temp from the 280 and RAMBO... anyways. The issue I'm having is that the JOHNSL FSR's aren't communicating to the Duet? Well they are and aren't, when I do a G32 it won't crash the board anymore, but very softly taps it and goes on, when it probes I get the error "Error: Z probe was not triggered during probing move" every time it probes. Here's my Config.g

Code: Select all

; Configuration file for SeeMeCNC Rostock MAX V3

; Communication and general
M111 S0                             	; Debug off
M550 PSeeMeCNCRostockMAXV3		; Machine name and Netbios name (can be anything you like)
M551 Preprap                        	; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits

;*** Wifi Networking
M552 S1					; Enable WiFi

M555 P2                           	; Set output to look like Marlin
M575 P1 B57600 S1			; Comms parameters for PanelDue

G21                                 	; Work in millimeters
G90                                	; Send absolute coordinates...
M83                                 	; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S1				; Drive 0 goes forwards
M569 P1 S1				; Drive 1 goes forwards
M569 P2 S1				; Drive 2 goes forwards
M569 P3 S0				; Drive 3 goes forwards
M569 P4 S0				; Drive 4 goes forwards
M574 X2 Y2 Z2 S1			; set endstop configuration (all endstops at high end, active high)
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
M665 R144.158 L291.06 B130 H360 X0 Y0 Z0		; set delta radius, diagonal rod length, printable radius and homed height H415
M666 X0 Y0 Z0				; put your endstop adjustments here, or let auto calibration find them
M350 X16 Y16 E16 I1    			; Set 16x microstepping with interpolation
M92 X80 Y80 Z80				; Set axis steps/mm
M906 X1000 Y1000 Z1000 E800 I60		; Set motor currents (mA) and increase idle current to 60%
M201 X1000 Y1000 Z1000 E1000		; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600		; Maximum speeds (mm/min)
M566 X1200 Y1200 Z1200 E1200		; Maximum instant speed changes mm/minute

; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0	; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B4725 R4700 H30 L0 C7.06e-8	; Put your own H and/or L values here to set the first nozzle thermistor ADC correction, B was 3974, added c7.06e-8
;M305 P2 T100000 B3974 R4700 H30 L0	; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M570 S180				; Hot end may be a little slow to heat up so allow it 180 seconds

; Fans
M106 P1 H-1 				; disable thermostatic mode for fan 1

; Tool definitions
M563 P0 D0 H1                       	; Define tool 0
G10 P0 S0 R0                        	; Set tool 0 operating and standby temperatures
;*** If you have a single-nozzle build, comment the next 2 lines
;M563 P1 D1 H2                      	; Define tool 1
;G10 P1 S0 R0                       	; Set tool 1 operating and standby temperatures
M92 E92.4:92.4                       	; Set extruder steps per mm

; Z probe and compensation definition
M558 P4 X0 Y0 Z0 H26 F2400 I1 T1000	; Was H5 added I1 F1200 T2400

; grid compensation
M557 R110 S15

G31 X0 Y0 Z0 P18			; Set the zprobe offset and threshold (determine your printer's Z offset value). For a delta, use zero X and Y offset. added P500 changed to P20 Z-.05

;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0                   	; Axis compensation here

T0						; select first hot end

Thoughts on where I went awry?

[dc42]

Does the JohnSL board produce an active low output (I1 in your M558 command)? I thought it was active high.

Here's how to test the Z probe. Set the nozzle well above the bed and send G30. It should start a probing move towards the bed. Tap the bed sharply to trigger the FSRs and the head should stop moving. If it doesn't, kill the power before the nozzle reaches the bed. If it does stop, re-home before you do anything else because the Z=0 position will be incorrect.

[Char'les Grey]

Does the JohnSL board produce an active low output (I1 in your M558 command)? I thought it was active high.

Here's how to test the Z probe. Set the nozzle well above the bed and send G30. It should start a probing move towards the bed. Tap the bed sharply to trigger the FSRs and the head should stop moving. If it doesn't, kill the power before the nozzle reaches the bed. If it does stop, re-home before you do anything else because the Z=0 position will be incorrect.

So I switched I1 to I0, and the "Z-probe" went to 1000 in the web interface. Switched it back and it was at 0. I tested G30, and it didn't stop on it's way down once I tapped the bed.

[dc42]

Check the connections between the JohnSL board and the E0 endstop input on the Duet. If you have connected it to the ZProbe connector instead, use P5 instead of P4 in your M558 command.

Does the JohnSL board have an led to indicate when it triggers?

[Char'les Grey]

Okay, I'll switch it to p5. The board does indicate when I put force on it.

[Char'les Grey]

Switched to P5, ran G30, again, it didn't crash the bed but came with the error "G30 S-1
Error: Z probe was not triggered during probing move" which leads me to think that for some reason a Z probe is expected vs. the E0 switch? Just my thoughts, I don't know how far off I am.

[dc42]

I suspect you have a bad crimp connection in the output wire from the JohnSL board to the Duet, or you have connected the output wire to the wrong pin on the Duet Z probe connector.

[Char'les Grey]

I gave the connectors a gentle tug to make sure they're snug and secure. I've checked the wiring to make sure that it's correct. Is the E0 end stop wiring the same in the duet .85 vs the duet wifi?

[Char'les Grey]

I'm at a loss... anyone have a wiring/pictures of the john fsr and duet wifi boards?

[Char'les Grey]

alright, after a couple scoops of ice cream, I figured it out, it was the wiring that was off at the duet. Although I followed the directions and pictures in the write ups and walk through... Now the issue I'm having is that the extruder motor is going much faster than it should while printing (as fast as the loading/unloading command)... I'm sure it's a setting's issue somewhere, I measured the filament with the 100mm test, and I'm getting 99.5 Avg.

The following is what I'm using (same as above)

Code: Select all

M92 E92.4:92.4  

[Xenocrates]

That is usually a symptom of bad G-code. Check your slicer settings. Change your M92 statement out for M92 E92.8 and see if that helps your accuracy of extrusion as well. Best of luck with things.

[dc42]

Yes, that's normally caused by slicing with absolute extruder coordinates but not having M82 in the start gcode. Preferably, slice using relative extruder coordinates instead and use M83 in your start gcode. Cura doesn't yet support relative extruder coordinates, so if you are using Cura you need to put M82 in your start gcode.

[Char'les Grey]

I'm using KISSlicer and these are under the Prefix tab

Code: Select all

G28
M190
M104 S<TEMP>
M190 S<BEDTEMP>
M109 S<TEMP>

so it should look like:

Code: Select all

G28
G82
M190
M104 S<TEMP>
M190 S<BEDTEMP>
M109 S<TEMP>

?

[IMBoring25]

I've never used KISSlicer, but you have to change it to actually use the coordinates you want to use. It will output completely different extrusion commands all the way through the G-code as a result of the mode you select. Putting the command in the start G-code just makes sure the machine will interpret the sliced data correctly.

It's M82 (absolute) or M83 (relative). Gs and Ms are not interchangeable. G82 is not defined. http://reprap.org/wiki/G-code

[Xenocrates]

As a nitpick, G82 is defined, but not implemented in 3d printer controllers (It's a drilling cycle or counterboring cycle, intended for subtractive CNC tools). I would be not entirely surprised if eventually G82 and similar subtractive specialized gcodes made their way into the RepRap code list, considering that project like Smoothieware and Duet do support mills as well (Smoothie encourages the use of the board for mills and laser cutters, while the Duet has a mode for controlling a Roland Mill, and could run a bunch of stuff like the X-carve or Shapeko pretty trivially at this point).

Now, pedantry aside, in KISSlicer, to change the extrusion mode to relative, go to printer, Firmware, Firmware type, 5D - Relative E. The speed tab should also be checked to ensure it's going the right speed for what you want.

[Char'les Grey]

Okay, good news. I did my first test cube with the upgrades. Only thing I need to do is adjust the print head so it's not pressed up against the glass on the first couple layers.