Thanks. i missed it
Posts made by joe92
-
RE: extruder config.g
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode) Board ID: 08DJM-9P63L-DJ3S0-7J1F8-3SD6N-TVJV9 Used output buffers: 1 of 40 (20 max) === RTOS === Static ram: 152760 Dynamic ram: 67196 of which 108 recycled Never used RAM 130608, free system stack 200 words Tasks: SBC(ready,0.6%,487) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.6%,91) MAIN(running,91.7%,923) IDLE(ready,0.1%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:14:25 ago, cause: power up Last software reset at 2023-02-19 21:08, reason: User, GCodes spinning, available RAM 130032, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 133 MCU temperature: min 28.1, current 33.2, max 35.1 Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 8, reads 49775, writes 14 timeouts 0 Driver 1: standstill, SG min 0, mspos 8, reads 49775, writes 14 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 49775, writes 14 timeouts 0 Driver 3: standstill, SG min 0, mspos 8, reads 49775, writes 14 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 49776, writes 14 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 49776, writes 14 timeouts 0 Date/time: 2023-02-19 21:26:16 Slowest loop: 2.33ms; fastest: 0.03ms === 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 === DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by 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 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 === CAN === Messages queued 7712, received 17045, lost 0, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 7, free buffers 50 (min 49), ts 4326/4325/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 34142/34142 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad48 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.5 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 34.76, max time between full transfers: 52.2ms, max pin wait times: 39.8ms/11.8ms Codes per second: 0.06 Maximum length of RX/TX data transfers: 3032/588
m122 b121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.4 (2022-10-14 11:46:33)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2592, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,57) MAIN(running,91.9%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:14:56 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 420.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 54923, writes 11, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -3/2, peak Rx sync delay 214, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.0, current 24.0, max 24.1
MCU temperature: min 34.6C, current 35.1C, max 35.4C
Last sensors broadcast 0x00000002 found 1 85 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 17692, send timeouts 0, received 8000, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0 -
extruder config.g
hello I'm almost done with my config and have only one problem. when i want to use the extruder z1 moves instead. i only have this error in connection with the extruder, otherwise g32 and g29 run without problems
; Configuration file for Duet 3 MB 6HC (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.15 on Sat Feb 04 2023 18:22:06 GMT+0100 (Central European Standard Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M669 K1 ; select CoreXY mode G4 S1 ;wait for expansion boards to start ; Drives M569 P0.0 S0 ; physical drive 0.0 goes backwards M569 P0.1 S0 ; physical drive 0.1 goes backwards M569 P0.2 S1 ; Z1 goes goes forwards M569 P0.3 S0 ; Z2 goes goes backwards M569 P0.4 S1 ; Z3 goes goes backwards M569 P0.5 S0 ; Z4 goes goes forwards M569 P121.0 S1 ; physical drive 121.0 goes forwards M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 E121.0 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X21000.00 Y21000.00 Z4000.00 E8000.00 ; set maximum speeds (mm/min) M201 X3600.00 Y3400.00 Z4000.00 E850.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout M584 R0 X0 Y1 Z0.2:0.3:0.4:0.5 E2 ; motor bindings ; Axis Limits M208 X0 Y-15 Z0 S1 ; set axis minima M208 X350 Y350 Z300 S0 ; set axis maxima ; Endstops M574 X1 S1 P"121.io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin 121.io2.in M574 Y1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M558 P8 C"^121.io0.in" H15 F500 T6000 ; set Z probe type to switch and the dive height + speeds G31 P1000 X0 Y0 Z6.190 ; set Z probe trigger value, offset and trigger height M557 X55:295 Y30:270 S30 ; S30 for high density, S40 for testing M671 X410:410:-60:-60 Y350:-80:-80:350 S20 ; belts in all 4 corners ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out1" T0 ; create bed heater output on out1 and map it to sensor 0 M307 H0 B0 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"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin 121.temp0 M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C M308 S2 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin temp1 M950 H2 C"out3" T2 ; create chamber heater output on out3 and map it to sensor 2 M307 H2 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit M141 H2 ; map chamber to heater 2 M143 H2 S280 ; set temperature limit for heater 2 to 280C ; Fans M950 F0 C"121.out1" Q500 ; create fan 0 on pin 121.out1 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"121.out2" Q500 ; create fan 1 on pin 121.out2 and set its frequency M106 P1 S1 H1:2 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"out7" Q500 ; create fan 2 on pin out7 and set its frequency M106 P2 S1 H1:2 T20 ; set fan 2 value. Thermostatic control is turned on M950 F3 C"out8" Q500 ; create fan 3 on pin out8 and set its frequency M106 P3 S1 H1:2 T20 ; set fan 3 value. Thermostatic control is turned on ; Tools M563 P0 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 M150 x1 Q4000000 M150 W255 P255 S10 F0 ; Allow Movement of Axis that have not been homed M564 H0 ; Custom settings are not defined
`; bed.g
M561 ; Clear any existing bed transform
G28 ; home
M98 P"/macros/klickyprobe/klickyprobe_attach.g"
; Probe bed at these 4 points:
G30 P0 X290 Y290 Z-99999
G30 P1 X290 Y60 Z-99999
G30 P2 X60 Y60 Z-99999
G30 P3 X60 Y290 Z-99999 S4M98 P"/macros/klickyprobe/klickyprobe_dock.g"
G28 Z ; Home Z Axis`` -
RE: 1LC Toolboard
I adjusted the config and the toolboard is now responding. Thanks to all
-
RE: 1LC Toolboard
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3S0-7J1F8-3SD6N-TVJV9
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67452 of which 68 recycled
Never used RAM 130320, free system stack 144 words
Tasks: SBC(ready,259.2%,468) HEAT(notifyWait,5.5%,322) Move(notifyWait,0.9%,259) CanReceiv(notifyWait,9.5%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,2.5%,339) TMC(notifyWait,3567.3%,57) MAIN(running,41023.7%,923) IDLE(ready,10.0%,30), total 44878.5%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:35:39 ago, cause: power up
Last software reset at 2023-02-14 06:40, reason: User, GCodes spinning, available RAM 130608, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 134
MCU temperature: min 15.1, current 28.7, max 29.0
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 792, reads 32278, writes 19 timeouts 0
Driver 1: standstill, SG min 0, mspos 248, reads 32278, writes 19 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 32278, writes 19 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 32281, writes 16 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 32281, writes 16 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 32281, writes 16 timeouts 0
Date/time: 2023-02-14 20:10:20
Slowest loop: 33.14ms; fastest: 0.04ms
=== 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 ===
DMs created 125, segments created 3, maxWait 29244ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 40, completed 40, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 25], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by 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
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
=== CAN ===
Messages queued 51586, received 114539, lost 0, boc 0
Longest wait 2ms for reply type 6026, peak Tx sync delay 278, free buffers 50 (min 49), ts 28698/28697/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 30205/30205
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 4.82, max time between full transfers: 491.8ms, max pin wait times: 80.7ms/11.7ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 3116/1380 -
RE: 1LC Toolboard
@jay_s_uk Well, a klickyprobe is planned later, so I thought that the temp 1 should also fit because it's just a simple switch, but later I just set it to io2. I'll send the m122 and m98 later because I'm not at home right now. I'll just copy them in and won't send any photos
-
RE: 1LC Toolboard
@jay_s_uk the 1lc is on and connected to the duet 3 but the hotend thermistor is not working and none of the fans spin up. the x stop is not connected according to m119. So the main problem is that the canbus signal doesnβt forward the signals, but if I swap the H L cables, the error message comes up at startup that board 121 is not connected
-
1LC Toolboard
hello I've checked the wiring and config since yesterday, but I don't see any errors in general. the board seems to be connected but nothing works. does anyone recognize the problem? I have the command m122 b121 here.
-
RE: Error: Probe already triggered at start of probing move
found the fault in the cable to the z switch. a broken wire has trigged the z stop
-
RE: Error: Probe already triggered at start of probing move
@phaedrux I can take the photos after work
-
RE: Error: Probe already triggered at start of probing move
@phaedrux
Yes, home all is the first thing I do, but I have now installed the duet from the other printer and everything works. I completely erased the board with the defect and wrote it with the latest software, but the error is still there in the other printer -
RE: Error: Probe already triggered at start of probing move
; homez.g
; called to home the Z axis
;; Lift Z relatively to current position
G91
G1 H2 Z5 F2000 S2; Back to absolute positioning
G90; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z SwitchG30 Z-99999 ; Probe Z Switch
G0 Z5
M98 P"/macros/probe_scripts/goto_nozzle_scrubber_and_scrub.g" ; Scrub Nozzle
; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z SwitchG30 Z-99999 ; Probe Z Switch
G0 Z20
M98 P"/macros/probe_scripts/activate_z_probe.g" ; Activate Z Probe
-
RE: Error: Probe already triggered at start of probing move
bed.g
; called to perform automatic bed compensation via G32
; setup for quad belt gantryM561 ; Clear any existing bed transform
G28 ; homeM98 P"/macros/probe_scripts/activate_z_probe.g" ;activate inductive z-probe
; Probe bed at these 4 points:
G30 P0 X290 Y290 H0 Z-99999
G30 P1 X290 Y60 H0 Z-99999
G30 P2 X60 Y60 H0 Z-99999
G30 P3 X60 Y290 H0 Z-99999 S4G28 Z ; Home Z Axis
; homeall.g
; called to home all axesG91 ; Relative
G1 H2 Z5 F2000 S2 ; Lower bed 15mm
G1 H1 X-300 Y-300 F2000 S1 ; Coarse home X and Y
G1 H1 X-300 S1 ; Coarse X in case Y homed first
G1 H1 Y-300 S1 ; Coarse Y in case X homed first
G1 H0 X5 Y5 F2000 ; Move away from the endstops
G1 H1 X-300 F360 S1 ; Fine home X
G1 H1 Y-300 F360 S1 ; Fine home YM98 P"/macros/print_scripts/xy_current_high.g" ; Restore motor currents
G90 ; Absolute positioning; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z SwitchG30 Z-99999 ; Probe Z Switch
G0 Z5
M98 P"/macros/probe_scripts/goto_nozzle_scrubber_and_scrub.g" ; Scrub Nozzle
; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z SwitchG30 Z-99999 ; Probe Z Switch
G0 Z20
M98 P"/macros/probe_scripts/activate_z_probe.g" ; Activate Z Probe
-
RE: Error: Probe already triggered at start of probing move
Error: Pin 'zstop' is not free
Is something broken on the board or is it a config setting? -
RE: Error: Probe already triggered at start of probing move
@phaedrux M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Pin 'zstop' is not free
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 558C -
RE: Error: Probe already triggered at start of probing move
@phaedrux m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJ3S0-7JKFJ-3SD6M-1TFHG
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75852 of which 28 recycled
Never used RAM 14660, free system stack 174 words
Tasks: NETWORK(ready,12.9%,237) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) DUEX(notifyWait,0.0%,24) MAIN(running,86.5%,443) IDLE(ready,0.4%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:59 ago, cause: power up
Last software reset at 2022-01-25 19:19, reason: User, GCodes spinning, available RAM 11676, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 31.8, current 37.5, max 37.7
Supply voltage: min 24.1, current 24.1, max 24.2, 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: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-01-26 05:40:12
Cache data hit count 4294967295
Slowest loop: 6.95ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Autopause is idle in state(s) 0
Code queue is empty.
=== DueX ===
Read count 1, 0.33 reads/min
=== Network ===
Slowest loop: 15.91ms; fastest: 0.00ms
Responder states: HTTP(2) 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.23
WiFi MAC address 8c:aa:b5:d5:7e:45
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23968
WiFi IP address 192.168.0.67
WiFi signal strength -39dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
RE: Error: Probe already triggered at start of probing move
@phaedrux at the moment only x and x are homing. at z comes the error message but then tried g30 s-1 and the probe works normally. I also disconnected the probe from the board but the value on the web control remains at 1000
-
RE: Error: Probe already triggered at start of probing move
can nobody help me ? the probe is active all the time even if i disconnect the cables. I loaded the config on my second print for testing and I can't find any errors there (both prints are voron 2)