@jay_s_uk we will try, i'll keep you in touch
Best posts made by Krohm Koala
-
RE: [3.3.0-rc2] M3-M5 gcode action
-
RE: load unload macro with endless loop and cancel condition
@garethky I use a macro, it show at the first page btw it's universal in one file (i just had to separate the purge loop to be able to cancel it) and i also like to be guide, i've done everything to be as simple and explicit as possible for the ease of use but i admit that it can be nice to use the built-in solution
also it detects if there's a filament, if not it skip the unload
@OwenD wow it's a nice approach ! A bit too complicated for me but man, it's nice work -
M291 S3 E suggestion
Hi, i was thinking about how it could be useful to add an E parameters at the M291 command as, when i use my unload filament macro, sometimes, a ball of filament stay under the extruder gear and i need to open all the extruder to get this out or cancel the macro and retract more with the interface. So, with this i could add control to the extruder in the macro
Have a nice day !
-
RE: [3.3.0-rc2] M3-M5 gcode action
@educatingsavvas Have you tried to do a G1 Xxxx Sxxx to try if it turn on with a mouvement? it work for us, i assume it'll work for you. Even if it doesn't stay On, you can engrave
Latest posts made by Krohm Koala
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@chrishamm Here it is :
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.3+pre (2023-03-27 16:33:18) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: RBLWU-5096U-D65J0-40KMQ-K513Z-HRUJH Used output buffers: 1 of 40 (17 max) === RTOS === Static ram: 102980 Dynamic ram: 105380 of which 0 recycled Never used RAM 30840, free system stack 206 words Tasks: SBC(ready,5.9%,464) HEAT(nWait,0.0%,359) Move(nWait,0.0%,360) CanReceiv(nWait,0.0%,941) CanSender(nWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(nWait,0.6%,114) MAIN(running,78.0%,549) IDLE(ready,14.7%,30) AIN(delaying,0.8%,273), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:02 ago, cause: software Last software reset at 2023-04-02 09:29, reason: AssertionFailed, Gcodes spinning, available RAM 30456, slot 1 Software reset code 0x4923 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000087d BFAR 0xe000ed38 SP 0x2003fe74 Task MAIN Freestk 62331 ok Stack: 0000019f 000bf718 0009b5ed 00000002 0009c775 00000000 00000000 2003b728 2000302c 2002c2c0 200165fc 00000000 00000000 00000000 00000000 20032738 000993f3 20018758 2003fee0 200327c0 00000000 00000000 00083cd1 20018758 20032738 00000000 00086275 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 2169, completed 2169, timed out 0, errs 0 MCU temperature: min 22.9, current 23.3, max 23.3 Supply voltage: min 24.5, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/19, heap memory allocated/used/recyclable 2048/224/8, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 86, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 86, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 25, reads 85, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 144, read errors 0, write errors 1, ifcnt 34, reads 84, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 144, read errors 0, write errors 1, ifcnt 34, reads 85, writes 14, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-04-02 09:29:29 Cache data hit count 3995363 Slowest loop: 144.04ms; fastest: 0.00ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, 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 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP* is doing "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 doing "M81 C"PS_ON"" in state(s) 0 0, running macro 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 12, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 11/0/0 Tx timeouts 0,0,10,0,0,0 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 6579/779 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0dd14 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.0-beta.2 (2023-02-08 11:47:09) Trigger: >> Finishing macro config.g, started by system Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 56.24, max time between full transfers: 42.1ms, max pin wait times: 868.7ms/2.6ms Codes per second: 3.23 Maximum length of RX/TX data transfers: 4656/912
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@chrishamm Why not, if it can resolve the problem, i'm OK with that
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@chrishamm So i've tried without the USB on the duet, same behavior, can it be something about the fact that i run SBC ?
Here's the config.g :
;Duet 3 Mini MK3S Bear ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Network ;M550 P"Kroma3D-MK3S" ; Set machine name ;M551 P"Krohm" ; Set password ;M552 S1 ; Enable network ;M586 P0 S1 ; Enable HTTP ;M586 P1 S0 ; Disable FTP ;M586 P2 S0 ; Disable Telnet ; Global Var Creation global Zcal = 0.1 global XTrav = 250 global YTrav = 210 global daemon = 0 global XDrive = 4 global YDrive = 3 global Z1Drive = 0 global Z2Drive = 1 global E0Drive = 2 global PrintFilament = "NONE" global homing = 0 global IdleTimer = 0 global ETempPLA = 215 global BTempPLA = 50 global ETempPETG = 250 global BTempPETG = 90 global ETempTPU = 220 global BTempTPU = 60 ; Drives M569 P{global.Z2Drive} S0 D2 ; Z2 Drive M569 P{global.Z1Drive} S0 D2 ; Z1 Drive M569 P{global.E0Drive} S0 D2 ; E0 Drive M569 P{global.YDrive} S1 D3 V10 ; Y Drive M569 P{global.XDrive} S0 D3 V35 ; X Drive ; Set drive number M584 X{global.XDrive} M584 Y{global.YDrive} M584 Z{global.Z1Drive, global.Z2Drive} M584 E{global.E0Drive} ; Set drive parameters M92 X200.00 Y200.00 Z400.00 E830 ; Set steps per mm M350 X32 Y32 Z32 E16 I1 ; Configure microstepping with interpolation M205 X10 Y10 Z0.5 E10 ; Set maximum instantaneous speed changes (mm/s) M203 X15000.00 Y15000.00 Z2400.00 E4200.00 ; Set maximum speeds (mm/min) M201 X1400.00 Y1400.00 Z80.00 E3000.00 ; Set accelerations (mm/s^2) M906 X500 Y500 Z800 E850 I50 ; Set motor currents (mA) and motor idle factor in per cent M84 S60 ; Set idle timeout M564 H0 S1 ; Temp Sensor M308 S0 P"temp0" Y"thermistor" T100000 B4100 ; Set thermistor + ADC parameters for heater 0 M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 ; Set thermistor + ADC parameters for heater 1 M308 S20 Y"mcu-temp" P"dummy" A"MCU" ; Axis Limits M208 X0 Y-5.4 S1 ; Set axis minima M208 X254 Y210 Z210 S0 ; Set axis maxima ; Endstops M574 Z1 S2 M574 X1 Y1 S3 ; Set endstops controlled by motor load detection ; Filament Sensor M591 D0 P2 C"io3.in" S1 ; Set filament sensor ; Z-Probe M558 P5 C"^io1.in" A2 H2.5 F2000:500 T9000 ; Set Z probe type to switch and the dive height + speeds G31 P999 Z0 ; Set Z probe trigger value, offset and trigger height G31 X23 Y-4 ; Set Z probe offsets M557 X25:245 Y5:200 P5:4 ; Define mesh grid ; Heaters M950 H0 C"out0" Q30 T0 ; Define bed heater M950 H1 C"out1" T1 ; Define E0 heater M140 H0 M307 H0 B0 S1.0 ; Disable bang-bang mode for the bed heater and set PWM limit M143 H0 T0 S120 ; Set temperature limit for heater 0 to 120C M143 H1 T1 S285 ; Set temperature limit for heater 1 to 285C ;M307 H1 A358.6 C148.2 D5.5 B0 ; Set PID for heater 1 ; Fans M950 F0 C"out3" Q62.5 ; Set print fan M950 F1 C"out4" Q500 ; Set dissipator fan M950 F2 C"out6" Q500 ; Set case fan M106 P0 S0 H-1 C"Print Fan" ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 H1 T45 C"Head Fan" ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on M106 P2 S1 H20 T35:40 L0.5 C"Case Fan" ; LEDs M950 F3 C"out5" Q25000 ; Set LEDs M106 P3 S0 C"LEDs" B0 ; Tools M563 S"E3D MiniRevo" P0 D0 H1 ; 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 ; Automatic power saving M911 S23 R23.8 P"M913 X0 Y0 G91 M83 G1 Z0.2 E-5 F1000" ; Set voltage thresholds and actions to run on power loss ; Arduino COM / Paneldue M575 P1 S1 B57600 ; Custom settings are not configured ; Miscellaneous T0 P0 ; Select first tool M501 ; Load config overrides M81 C"PS_ON" ; Make sure PSU is off ;good old PID M307 H1 R1.969 K0.403:0.000 D3.40 E1.00 S1.00 B0 V24.5
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@chrishamm it is this command, I have a USB cable on the duet to provide power, but there's no data on it. I'll post my config.g when I'll be at home.
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@jay_s_uk Sure, here are all you need :
Home-config.gif global.homing == 1 M80 G4 S0.5 M400 M569 P{global.YDrive} S1 D3 V60 ; Y Drive 1 goes forwards M569 P{global.XDrive} S0 D3 V60 ; X Drive 2 goes forwards M915 X S-15 H400 F0 R0 M915 Y S4 H400 F0 R0 M574 X1 Y1 S3 M913 X60 Y60 echo "homing..." if global.homing == 0 M569 P{global.YDrive} S1 D3 V2 ; Y Drive 1 goes forwards M569 P{global.XDrive} S0 D3 V2 ; X Drive 2 goes forwards M915 X Y S8 F0 R1 M501 echo "homing done"
Homeall.g
set global.homing=1 M98 P"home-config.g" G91 G1 H2 X5 Y5 Z5 F3000 G1 H1 X-325 Y-325 F3000 M913 X100 Y100 G90 G1 X{(global.XTrav/2)-sensors.probes[0].offsets[0]} Y{(global.YTrav/2)+sensors.probes[0].offsets[1]} F12000 M400 G91 G1 H1 Z-300 F600 G1 Z5 F600 G90 G30 set global.homing=0 M98 P"home-config.g"
daemon.g
while global.daemon == 0 G4 S1 if state.status == "idle" set global.IdleTimer={global.IdleTimer+1} if global.IdleTimer>= 250 && heat.heaters[1].avgPwm <= 0.1 && heat.heaters[0].avgPwm <= 0.05 M81 else set global.IdleTimer=0 while boards[0].vIn.current < 23 if {heat.heaters[1].active >= 60 && heat.heaters[1].state == "active"} || {heat.heaters[0].active >= 30 && heat.heaters[0].state == "active"} M80 break else break if boards[0].vIn.current > 5 && fans[3].actualValue < 0.04 M106 P3 S255 if move.currentMove.requestedSpeed > 0 && boards[0].vIn.current < 23 M80 if global.Zcal = 1 && boards[0].vIn.current < 23 set global.Zcal=0
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@chrishamm @Phaedrux Here is the logs with the level debug :
Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Finished code G1 H1 X-325 Y-325 F3000 Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Finished code M913 X100 Y100 Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Finished code G90 Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Finished code G1 X{(global.XTrav/2)-sensors.probes[0].offsets[0]} Y{(global.YTrav/2)+sensors.probes[0].offsets[1]} F12000 Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] Requesting update of key inputs, seq 17 -> 18 Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] Updated key inputs Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] Requesting update of key move, seq 45 -> 48 Mar 12 07:45:27 MK3S-BEAR DuetControlServer[24468]: [debug] Updated key move Mar 12 07:45:28 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Finished code M400 Mar 12 07:45:28 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Finished code G91 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [warn] HTTP: Aborting orphaned macro file homeall.g Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Failed to flush codes on stage Firmware for set global.homing=0 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [info] Aborted macro file homeall.g Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Cancelled code set global.homing=0 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [warn] HTTP: ==> Cancelling unfinished starting code: G28 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Cancelled code M98 P"home-config.g" Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Cancelled code G28 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [warn] Daemon: Aborting orphaned macro file daemon.g Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] Daemon: Failed to flush codes on stage Firmware Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] Evaluating If block Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [info] Aborted macro file daemon.g Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] Daemon: Cancelled code G4 S1 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] Evaluating state.status == "idle" on channel Daemon Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Cancelled code G1 H1 Z-300 F600 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Cancelled code G1 Z5 F600 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] IPC#16: Connection closed Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Cancelled code G90 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] HTTP: Cancelled code G30 Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] Finished codes from macro file homeall.g Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [debug] Finished codes from macro file daemon.g Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [warn] SPI connection has been reset Mar 12 07:45:29 MK3S-BEAR DuetControlServer[24468]: [info] Starting macro file config.g on channel Trigger
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@chrishamm Here it is :
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5beta2 (2023-02-08 15:27:32) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: RBLWU-5096U-D65J0-40KMQ-K513Z-HRUJH Used output buffers: 1 of 40 (17 max) === RTOS === Static ram: 103012 Dynamic ram: 103320 of which 0 recycled Never used RAM 32524, free system stack 206 words Tasks: SBC(ready,6.7%,446) HEAT(notifyWait,0.0%,376) Move(notifyWait,0.0%,359) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.6%,114) MAIN(running,82.1%,604) IDLE(ready,9.7%,30) AIN(delaying,0.9%,272), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:01 ago, cause: software Last software reset at 2023-03-12 07:31, reason: AssertionFailed, Platform spinning, available RAM 28536, slot 2 Software reset code 0x4120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000087d BFAR 0xe000ed38 SP 0x2003fe74 Task MAIN Freestk 62331 ok Stack: 0000019f 000be780 0009a7ed 00000002 0009b975 2001cfd0 2003b838 2003b998 2000302c 2002c2e0 20016604 00000000 00000000 00000000 00000000 20032758 000985eb 20018760 2003fee0 200327e0 00000000 00000000 000831a1 20018760 20032758 00000000 00085709 Error status: 0x00 MCU revision 3, ADC conversions started 1492, completed 1492, timed out 0, errs 0 Step timer max interval 1490 MCU temperature: min 23.8, current 24.2, max 24.2 Supply voltage: min 24.5, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/15, heap memory allocated/used/recyclable 2048/168/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 24, reads 50, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 24, reads 50, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 22, reads 50, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 114, read errors 0, write errors 1, ifcnt 30, reads 49, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 134, read errors 0, write errors 1, ifcnt 30, reads 50, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-03-12 07:31:07 Cache data hit count 2919629 Slowest loop: 3.27ms; fastest: 0.00ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, 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 no step interrupt scheduled === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, null HTTP* is doing "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 0, running macro 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 7, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 7/0/0 Tx timeouts 0,0,6,0,0,0 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 2469/604 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0dcf4 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.0-beta.2 (2023-02-08 11:47:09) File+ProcessInternally: > Busy Trigger+ProcessInternally: >> Macro config.g: Executing global BTempPETG = 90 (15 more codes pending) Trigger: >> Doing macro config.g, started by system Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 5 Full transfers per second: 38.82, max time between full transfers: 920.5ms, max pin wait times: 865.1ms/49.3ms Codes per second: 0.79 Maximum length of RX/TX data transfers: 4448/1588
and here are the logs :
Mar 12 07:34:25 MK3S-BEAR DuetControlServer[19220]: [info] Starting macro file homeall.g on channel HTTP Mar 12 07:34:25 MK3S-BEAR DuetControlServer[19220]: [info] Starting macro file home-config.g on channel HTTP Mar 12 07:34:26 MK3S-BEAR DuetControlServer[19220]: [info] homing... Mar 12 07:34:26 MK3S-BEAR DuetControlServer[19220]: [info] Finished macro file home-config.g Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [warn] HTTP: Aborting orphaned macro file homeall.g Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [info] Aborted macro file homeall.g Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [warn] HTTP: ==> Cancelling unfinished starting code: G28 Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [error] HTTP: Failed to find corresponding state for code M98 P"home-config.g", cancelling it Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [warn] Daemon: Aborting orphaned macro file daemon.g Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [info] Aborted macro file daemon.g Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [warn] SPI connection has been reset Mar 12 07:34:32 MK3S-BEAR DuetControlServer[19220]: [info] Starting macro file config.g on channel Trigger
-
RE: RRF 3.5.0b2 SPI Connection has been reset
@Phaedrux i've check the section you sent, there's no problems here, it really only occurs when i send this command "G1 H1 Z-300 F600" i'll check when i have the time, what's going on in the logs.
-
RE: RRF 3.5.0b2 SPI Connection has been reset
The problem occurs when executing this command
G1 H1 Z-300 F600
i use it to probe the bed first and do a g30 after -
RRF 3.5.0b2 SPI Connection has been reset
Hi,
I just installed the new update on my duet 3 mini on SBC, but everytime i wanna launch a print i get the message "SPI connection has been reset", i use the sensorless homing and it reset at the moment it wants to home the Z axis.
Have a nice day.