Posts made by bubblevisor

Is there a live way of showing the end stop status on DWC. I realise there are LEDs on the board but it once installed in a housing at the bottom of your printer they're not much help. I am trying to diagnose a problem whereby the x axis is intermittently not homing. It behaves as is the end stop is already triggered.

@jay_s_uk I've just been trying to update the firmware. But no matter which .zip firmware I upload the installed version remains at 3.4.0beta.

@jay_s_uk Here is the M122. It has done a few successful prints but just now it stopped just before it started laying the first layer:

m122
=== Diagnostics ===
RepRapFirmware for big-dipper version 3.4.0beta5+1 (2021-10-23 18:16:14) running on Duet 3 big-dipper WiFi (standalone mode)
Board ID: RZAN1-D2401-8D3J0-40188-K3T0Z-7YR20
Used output buffers: 3 of 40 (12 max)
=== RTOS ===
Static ram: 102180
Dynamic ram: 101368 of which 0 recycled
Never used RAM 38164, free system stack 198 words
Tasks: NETWORK(ready,15.8%,249) HEAT(notifyWait,0.0%,343) Move(notifyWait,0.0%,338) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.0%,338) TMC(notifyWait,1.2%,114) MAIN(running,82.0%,425) IDLE(ready,0.1%,30) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:14 ago, cause: software
Last software reset at 2023-10-21 16:25, reason: HardFault imprec, Display spinning, available RAM 37884, slot 2
Software reset code 0x406f HFSR 0x40000000 CFSR 0x00000400 ICSR 0x0047d803 BFAR 0xe000ed38 SP 0x20003f18 Task MAIN Freestk 1066 ok
Stack: 00000000 200290a8 00000571 00000570 00000348 00076857 00076872 61030000 00000000 00000000 369dc3a0 3edb75d2 3331bb4c 41880000 3e178897 3e1cd04f be09b238 3e3a3fd4 3e639b49 00000000 00000000 412ccccd 3f800000 00000000 60000010 a5a5a5a5 0000000f
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 0, ADC conversions started 254285, completed 254285, timed out 0, errs 0
Step timer max interval 752
MCU temperature: min 44.6, current 44.8, max 45.4
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: pos 0, standstill, SG min/max 10/10, read errors 0, write errors 1, ifcnt 22, reads 23088, writes 9, timeouts 0, DMA errors 0
Driver 1: pos 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 22, reads 23088, writes 9, timeouts 0, DMA errors 0
Driver 2: pos 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 21, reads 23088, writes 9, timeouts 0, DMA errors 0
Driver 3: pos 0, standstill, SG min/max 14/14, read errors 0, write errors 1, ifcnt 21, reads 23087, writes 9, timeouts 0, DMA errors 0
Driver 4: pos 0, standstill, SG min/max 14/14, read errors 0, write errors 1, ifcnt 22, reads 23088, writes 9, timeouts 0, DMA errors 0
Driver 5: pos 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 20, reads 23088, writes 9, timeouts 0, DMA errors 0
Driver 6: pos 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 23087, writes 9, timeouts 0, DMA errors 0
Date/time: 2023-10-21 16:29:37
Cache data hit count 436204769
Slowest loop: 2.92ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle 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
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
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 2288, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 1272/0/0
Tx timeouts 0,0,1271,0,0,1015 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 15.37ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.25
  WiFi MAC address bc:ff:4dxxxxxxxx
  WiFi Vcc 3.38, reset reason Power up
  WiFi flash size 2097152, free heap 25600
  WiFi IP address 192.168.1.xxx
  WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

My duet 2 mini 5+ controlled printer has recently developed a problem whereby it stops dead randomly. I have yet to catch it when the failure occurs but it appears as though someone just cut the power momentarily. Could it literally be a fault with the power supply? I have attached a shot of the console that may indicate something. Any ideas?

@oliof Is there a thread here somewhere that describes implementing strain gauges?

@oliof Yes, I hear what you are saying with regards merits of semi industrial type machines. Cost is a big factor however. I need maximum user serviceability, ability to print ABS in a 65degree chamber and strong mechanics/motion system for print quality and reliability. Speed is irrelevant.

I was wondering if it would be possible to run consumer machines such bambu Labs P1P or Creality K1 with RRF. I run a small printer farm based on my own custom printers and prefer the total control of RRF. Of course I would expect you will need to replace the board and screen with say duet 3 mini but can reprap be used to control all the hardware including strain gauges etc?

@dc42 Yes that's correct. The PL05 does not work with less than 5v hence using the expansion port. Does it matter where I connect to GND? I was wondering if it made a difference using the GND on the z probe port or the pin2 GND on expansion.
Although it seems to work ok on the 5v so far, I was thinking of taking 24v directly from the power supply as the probe does indicate 6v - 30v. Are there any issues doing this? Which GND should you use in this setup?

@dc42 Hmm. Does that apply if I use the 5v and GND from the expansion but signal goes to z probe in. I have a v1.04 duet 2 wifi.

@dc42 That's very helpful David, thanks. Can you also confirm if all the duet 3 boards also have that protection?

I tend to use the cheap PL08 or PL05 type induction probes. I normally use them with a BAT85 diode on the signal wire however I recently forgot to include this and it still seemed to work ok on my duet 2 wifi board. My question is this: is the diode necessary for the duet boards?

@Phaedrux Do you mean I need to fully define M558 in the bed.g as well as in config.g? such as M558 K0 P5 C"^zprobe.in" H10 F1000 T6000 A20 S0.01

THe other point to make is that the printer IS responding fine to the induction K0 probe just fine, but ignoring K1 tool length in favour of the induction probe during homeZ.

go to z-switch.g

@Phaedrux Well, the problem exists even with the fan off. Plus I have moved the probe into a location that should not receive interference from the fan.

The weird thing is I cannot get the printer to react to the tool length probe anymore. This is despite the fact that the z-stop led responds when I press the micro switch.

config.g homeall.g homez.g bed.g

@dc42 Could my issue be a board fault? The printer now is completely non responsive to the tool length probe micro switch (that also doubles as Z endstop). Instead it now z end stops via the induction probe. All without me touching the config!. Can this be a board/firmware fault??

Btw, the board is a duet 2 wifi.

Here's the homez.g

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Jul 20 2021 13:11:51 GMT+0100 (British Summer Time)
;G91 ; relative positioning
;G1 H2 Z5 F6000 ; lift Z relative to current position
;G90 ; absolute positioning

M98 P"go to z-switch.g"
G30 K1 Z-999 ; home Z by probing the bed via K1
G1 Z5 F2000 ;lift z

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Jul 20 2021 13:11:51 GMT+0100 (British Summer Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Saphire" ; set printer name
M669 K1 ; select CoreXY mode

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 D2 ; physical drive 0 goes forwards
M569 P4 S1 D2 ; physical drive 4 goes forwards
M569 P2 S0 D2 ; physical drive 2 goes forwards
M569 P3 S0 D2 ; physical drive 3 goes forwards
M569 P1 S0 D2
M584 X0 Y4 Z1:2 E3 ; set drive mapping

M350 X128 Y128 Z128 E16 I0 ; configure microstepping without interpolation
M92 X640.00 Y640.00 Z6400.00:6400.00 E669.00 ; set steps per mm
M566 X1000.00 Y1000.00 Z100:100 E520.00 P1 ; set maximum instantaneous speed changes (mm/min)
M203 X20000.00 Y20000.00 Z800.00:800.00 E70000.00 ; set maximum speeds (mm/min)
M201 X20000.00 Y20000.00 Z200.00:200.00 E4000.00 ; set accelerations (mm/s^2)
M906 X1100 Y1100 Z1300 E850 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y299 Z340 S0 ; set axis maxima
;M556 S100 X0 Y0 Z0:0:0 ; set skew x.xxmm on 100mm square x-y obtuse

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin !xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin !ystop
M574 Z0 P"nil" ; No Z endstop

; Z-Probe
M558 K0 P5 C"^zprobe.in" H2 F1000 T6000 A20 S0.01 ; set Z probe type to effector and the dive height + speeds, max number of probes per point, tolerance(MM)
;M308 S2 P"e1temp" A"PINDA" Y"thermistor" T100000 B3950 ; configure sensor 2 as thermistor on pin e1temp
G31 K0 P1000 X-34.5 Y-13 Z0.18 ;H2 S27 T0.020 ; set Z probe trigger value, xy offset, z trigger height(higher=closer to bed)don't care, temp sensor number, reference temp, compensation coefficient mm/degree(higher more close when hot)

;Bed Levelling
M671 X4:233 Y170:170 S25 ;leadscrew/pivot locations and max allowable deviation
M557 X10:265 Y5:270 P6:6 ; define mesh grid

; Z Tool Length probe
M558 K1 P5 C"^zstop" T8000 F600 H2 A10 S0.01 R0.2 ;set second (K1) Z probe: pin in, travel speed to probe, probing speed, dive height, max number of probes, tolerance(MM), rest time
G31 K1 P500 X0 Y0 Z0.75 ;set second (K1) Z probe: trigger value (higher value = closer nozzle)

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 R1.028 C177.2 D6.82 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C

M308 S1 P"e0temp" Y"thermistor" T100000 B3950 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 R2.373 C103.0 D8.21 S1.00 V24.2 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

M308 S3 A"Chamber" P"exp.thermistor3" Y"thermistor" T100000 B3950 ; configure sensor 3 as "thermistor" type on pin "thermistor3" (Henry added for chamber monitoring)

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 C"Part cooling fan" ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T85 C"Heat Break Fan" ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency (Henry add chamber fan)
M106 P2 S0 H-1 C"Chamber fan" ; set fan 0 value. Thermostatic control is turned off

;LED Lights
M950 P0 C"e1heat"
M42 P0 C"LEDs"

; Tools
M563 P0 S"Dragon" D0 H1 F0:1 ; 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

; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M911 S21 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool