Bl-Touch self extended
-
post your M122 of both the duet and the toolchanger when that happens
-
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S8-6JTDG-3SJ6P-KB0UG Used output buffers: 1 of 40 (10 max) === RTOS === Static ram: 154604 Dynamic ram: 163292 of which 136 recycled Exception stack ram used: 224 Never used ram: 74960 Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,204) MAIN(running,4944) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:50:37 ago, cause: software Last software reset at 2020-12-20 06:24, reason: User, spinning module LinuxInterface, available RAM 75036 bytes (slot 2) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 28.9, current 29.5, max 29.8 Supply voltage: min 24.7, current 24.7, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0 Driver 0: standstill, reads 24546, writes 21 timeouts 0, SG min/max 0/0 Driver 1: standstill, reads 24546, writes 21 timeouts 0, SG min/max 0/0 Driver 2: standstill, reads 24547, writes 21 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 24547, writes 21 timeouts 0, SG min/max 0/0 Driver 4: standstill, reads 24547, writes 21 timeouts 0, SG min/max 0/0 Driver 5: standstill, reads 24548, writes 21 timeouts 0, SG min/max 0/0 Date/time: 2020-12-20 07:15:34 Slowest loop: 3.99ms; fastest: 0.14ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 2 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "M122" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon* is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 0.88ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 12121, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 16ms ago RX/TX seq numbers: 31465/31467 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 32.00 -
are you using usb to connect to your duet?
see https://duet3d.dozuki.com/Wiki/USB_ground_loops -
Only raspberry with spi. I doun't use Usb
-
This is my wiring
-
normally when someone post the diagnostics without newlines, its because it was not copied from the web console and they used usb.
-
I have copy with my smartphone.
But I think now my bl-touch is damaged. I have make a g32 and the bed drive in the nozzel. Bl-touch was red but nothing stop
-
check the extension wire, that is know to make bad contact and cause issues.
-
Have make new connections last week bevor i have it install in the HevORT
-
Found the bug. It was due to the contact resistance at the on-board connection. I thank you for the help and patience
-
ok now i'm confused. Since I no longer trusted the old Bl-touch, I installed a new one. It's the same problem that it just goes in and out without me triggering it. The connection on the board is new. That happens when you print or afterwards. If I had the printer off, that didn't happen for days.
-
The Bl-Touch doesn't seem to be the problem, nor does the wiring. If the pin is inside or outside, DCW says "not stopped" When I have the BL-Touch off, the board tells me "at min stop" I measure 4-10mV at pin outside with pin inside 3.3V on the white cable to ground
-
Please post your full config.g and homeall.g as well as the results of M98 P"config.g"
-
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Aug 26 2020 16:14:58 GMT+0200 (Mitteleuropäische Sommerzeit) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet3" ; set printer name M912 P0 S-5 ; sstzt CPU Temp korrektur M669 K1 ;switch to core X/Y mode ; Drives M569 P0.0 S0 V30 D3 ; X physical drive 0.0 goes forwards M569 P0.1 S0 V30 D3 ; Y physical drive 0.1 goes forwards M569 P0.2 S1 V30 D3 ; Z1 physical drive 0.2 goes forwards M569 P0.3 S1 V30 D3 ; Z2 physical drive 0.3 goes forwards M569 P0.4 S1 V30 D3 ; Z3 physical drive 0.4 goes forwards M569 P0.5 S0 V30 D3 ; E physical drive 0.5 goes backwards M584 X0.0 Y0.1 Z0.2:0.3:0.4 E0.5 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z800.00 E419.00 ; set steps per mm M566 X1000.00 Y1000.00 Z300.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z600.00 E3000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z200.00 E450.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z900 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S120 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X300 Y300 Z295 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io2.in" ; configure active-high endstop for low end on X via pin io2.in M574 Y1 S1 P"io1.in" ; configure active-high endstop for low end on Y via pin io1.in M574 Z1 S2 ; Z-Probe M950 S0 C"io7.out" ; create servo pin 0 for BLTouch M558 P9 C"^io7.in" H5 F400 T5000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X38.884 Y-6.578 Z2.21 ; set Z probe trigger value, offset and trigger height M557 X40:260 Y40:260 S40 ; define mesh grid M671 X-33.985:142.224:318.433 Y-16.206:312.004:-16.206 S50 ;Z lift Point Position ; Heaters M308 S0 A"Bett" P"temp0" Y"thermistor" T100000 B4100 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 A176.1 C1192.2 D31.2 S1.0 V24.3 B0 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; qmap heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 A"Hotend" P"temp1" Y"thermistor" T100000 B4395 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S0.80 ; disable bang-bang mode for heater and set PWM limit M308 S2 A"Elektro" P"temp3" Y"thermistor" T100000 B4100 ; configure sensor 1 as thermistor on pin temp1 M141 H2 M308 S3 Y"drivers" A"Stepper" ; configure sensor 3 as temperature warning and overheat flags on the TMC2660 on Duet M308 S4 Y"mcu-temp" A"MCU" ; configure sensor 4 as thermistor on pin e1temp ; Fans M950 F1 C"out7" Q500 ; create fan 1 on pin out7 and set its frequency M106 P1 C"Hotend" S1 H1 T50 ; set fan 1 name and value. Thermostatic control is turned on M950 F0 C"out4" Q1000 ; create fan 0 on pin out4 and set its frequency M106 P0 C"Bauteil1" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off M950 F2 C"out9" Q500 ; create Light on pin out9 and set its frequency M106 P2 C"Licht" S0 H-1 M950 F3 C"out8" Q500 ; create fan 3 on pin out8 and set its frequency M106 P3 H3:4 T33 ; set fan 3 value ; Tools M563 P0 S"Hotend" 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 M564 S1 H0 T0 ; Miscellaneous ;M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory M911 S21 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss; homeall file for use with dc42 Duet firmware on CoreXY printers ; This file assumes the endstop switches are at the low end of each axis. ; Reverse the X and Y movement for high-end switches. ; Adjust the bed upper and lower limits in config.g (M208 commands) to get the correct homing positions T0 G91 ; relative mode G1 Z5 F400 G1 H1 X-240 Y-240 F6000 ; course home X or Y G1 H1 X-240 ; course home X G1 H1 Y-240 ; course home Y G1 X4 Y4 F6000 ; move away from the endstops G1 H1 X-10 ; fine home X G1 H1 Y-10 ; fine home Y G90 ; back to absolute mode ; The following code assumes you are using a Z probe to do Z homing. ; Adjust the XY coordinates in the following to place the Z probe over a suitable spot, ; preferably near the centre of the bed if your Z probe supports that G1 X112 Y156.8 F6000 G30 ; This file leaves the head at the zprobe trigger height so that you can slip a piece of paper under it and then do G0 Z0 to check the height. ; If you prefer to send the printer to X0Y0Z0, un-comment the following lines ;G1 X0 Y0 F6000 ;G1 Z5 F400M98 P"config.g" Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 201C Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 201C -
@Phaedrux ok I hope that help.
When I measure from ground to white I have 3.3V when retracted, <20mV when extended. DWC always says "not stopped"
If I measure 5V pin to ground I have 4.94V. -
Startcode
T0 G32 ; True Bed Leveling und Meshbedleveling G29 S1 P"heightmap.csv" ; Load Mesh G1 X5 Y5 Z15 F6000 ; Move the platform down 15mm ;M117 Prime the extruder G92 E0 ; reset extruder G1 E3 F200 ; Extrude 3mm ;M117 Purge Extruder G92 E0 ; reset extruder G1 Z1 F1000 ; move z up to prevent scratching of surface G1 X10 Y10 Z0.3 F5000 ; move to start-line position G1 X10 Y200 E15 F1500 ; draw 1st line G1 X10.8 Y200 F5000 ; move to side a little G1 X11.6 Y2 E30 F1500 ; draw 2nd line G1 Z17 F3000 ; Move Bed 17mm down G1 E15 F300 ; Extrude 15mm G92 E0 ; reset extruder G4 S5 ; Wait 5 secondEndcode
M104 S0 M140 S0 M107 G92 E1 G1 E-1 F300 ;Retract the filament G1 X5 Y300 Z290 F6000 -
@Heartleander81 I was just reading the BLT documentation the other day and it mentioned it being susceptible to noise from the hotbend heater wires (guessing 12/24v pwm stepping on the BLT 3.3/5v signal) Wondering if this is your issue...
Of course I can't find it now to link...
-
@BDubs That would be an explanation. Was the fault on the board or was it from the cables? is the best way to shield the Bl-Touch?
-
@Heartleander81 said in Bl-Touch self extended:
@BDubs That would be an explanation. Was the fault on the board or was it from the cables? is the best way to shield the Bl-Touch?
Still can't find it...arrg...
They mentioned turning off the nozzle heater (to effectively kill the PWM signal) when probing to prevent it from being susceptible to noise.
In terms of shielding, I'd try using shielded cable and be sure to properly connect the ground/drain to your chassis in such a way as to avoid a ground loop.
-
M558 B1 will turn off the heaters during the probing move.
https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M558_Set_Z_probe_type
@Heartleander81 said in Bl-Touch self extended:
DWC always says "not stopped"
Where are you seeing not stopped?
How are you testing the BLTouch?If you send M401 and M402 does the pin deploy and retract?
If you send G30 does the pin deploy and start to move the z axis?
Does triggering the pin by hand stop movement?
