having problems finishing one print starting next
-
I have 2 printers doing strange things after finishing or canceling a print and starting the next print.
printer 1 will not deploy BLtouch until the printer is rebooted.... if I deploy the test probe, then hit the emergency stop the probe will deploy prior to stopping and resetting.
printer 2 finishes the print when I start the next it homes all axis then goes slightly left and lifts Z pushed plastic then moved to X Y home and pushes plastic to fast while raising Z I hit emergency stop and print the same file with no issues.
-
@codfish124 for the first issue, try adding
M280 Px S160
to reset the probe at the beginning of your homez.g (with x being replaced by your servo number, usually this is P0).For your second issue this sounds like you're stuck in relative move mode after homing. Make sure to have a
G90
at the end of your homing files/beginning of your gcode start section to make sure your printer is in the right mode. -
For us to really understand what is going on we need to see the gcode that is actually being executed, so please share with us your config.g, homing files, slicer start and end gcode (an example sliced gcode file would be best). It would also help to know what firmware and duet you are using. Sending M122 and M98 P"config.g" in the gcode console and copy pasting it here would be good.
-
@oliof duh!!!!
thank seems to have fixed printer #2 thank you
-
this one has been doing this for some time though it was wireing but I have rewired it a few times
here is the M122
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NWNS4-7JKF0-3S46J-KV0VM Used output buffers: 3 of 24 (12 max) === RTOS === Static ram: 23868 Dynamic ram: 74860 of which 0 recycled Never used RAM 13352, free system stack 184 words Tasks: NETWORK(ready,129.4%,226) HEAT(notifyWait,2.2%,332) Move(notifyWait,0.1%,364) MAIN(running,147.8%,448) IDLE(ready,1.3%,30), total 280.8% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 27:25:41 ago, cause: software Last software reset at 2022-05-03 13:49, reason: User, GCodes spinning, available RAM 13208, 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 Step timer max interval 0 MCU temperature: min 35.2, current 36.3, max 37.7 Supply voltage: min 24.1, current 24.3, max 24.4, 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 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2022-05-04 17:15:28 Cache data hit count 4294967295 Slowest loop: 33.88ms; fastest: 0.19ms 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 26.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 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0 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 Autopause is idle in state(s) 0 Code queue is empty === Network === Slowest loop: 15.40ms; 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.26 WiFi MAC address 98:cd:ac:20:60:d8 WiFi Vcc 3.45, reset reason Power up WiFi flash size 4194304, free heap 25352 WiFi IP address 192.168.1.31 WiFi signal strength -66dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0``` and the M98 P
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled -
what else is needed this is most frustrating