homing problems
-
Can you send M122 and M98 P"config.g" in the gcode console tab of DWC and copy and paste the results here? That will give us some needed information.
Can you also check the setup page of the Panel Due and let us know the firmware version?
-
the panel due firmware is 3.5.0
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.5 (2022-11-30 19:41:16) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: BWP0W-7196U-D65J0-40KM6-KV03Z-HD87J
Used output buffers: 1 of 40 (19 max)
=== RTOS ===
Static ram: 103652
Dynamic ram: 97972 of which 108 recycled
Never used RAM 39980, free system stack 196 words
Tasks: SBC(ready,1.2%,446) HEAT(notifyWait,0.0%,367) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,348) TMC(notifyWait,0.7%,106) MAIN(running,97.2%,530) IDLE(ready,0.0%,30) AIN(delaying,0.8%,263), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:43:35 ago, cause: power up
Last software reset at 2023-09-12 22:08, reason: User, GCodes spinning, available RAM 39692, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 2615791, completed 2615790, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 34.4, current 34.6, max 37.9
Supply voltage: min 24.0, current 24.0, max 24.1, 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 0, read errors 0, write errors 0, ifcnt 11, reads 6575, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 6575, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 6574, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 6574, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 6575, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-09-13 01:12:30
Cache data hit count 4294967295
Slowest loop: 3.40ms; fastest: 0.09ms
=== Storage ===
Free file entries: 10
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
=== 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 -1 -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 23492, received 52107, lost 0, boc 0
Longest wait 3ms for reply type 6026, peak Tx sync delay 258, free buffers 18 (min 17), ts 13079/13078/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 35656/35656
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0f1bc
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.6
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 32.75, max time between full transfers: 52.3ms, max pin wait times: 30.5ms/9.0ms
Codes per second: 0.02
Maximum length of RX/TX data transfers: 3296/740
9/13/2023, 12:33:02 AM m115 b121
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04)
9/13/2023, 12:29:36 AM m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-11-30 19:41:16 -
@Phaedrux
Sorry but i don't understand the m98 command -
here is a screenshot of the print failure.
-
@spfxshane said in homing problems:
@Phaedrux
Sorry but i don't understand the m98 commandIn SBC mode it probably won't say much of anything unless there are configuration syntax errors.
-
Can you share the complete gcode file you're trying to print?
-
-
@spfxshane
sorry took me a minute to figure out how to send this. I was just taking a swing at slicing something in prusa slicer and get it to work on this machine. Getting information on setting up a slicer profile for this machine is defiantly been hard; and I'm just starting that journey after building the hardware and wading through the software for the machine. -
G1 H1 X-625 Y605 F1800 ; Move quickly to X and Y axis endstops and stop there (first pass) G1 X3 Y-3 F600 ; Go back a few mm G1 H1 X-625 Y605 F360 ; Move slowly to X and Y axis endstops once more (second pass) G1 H1 X-625 F360 ; Move slowly to X and Y axis endstops once more (second pass) G1 H1 Y605 F360 ; Move slowly to X and Y axis endstops once more (second pass)I think the problem is that your initial homing moves are incomplete for a corexy. You're moving both X and Y axis together, but as soon as one of the endstops is hit, the homing move ends, so one axis will be left unhomed. Then the short move to back off the endstop is throwing the error because it's trying to move an unhomed axis.
Your second pass is correct though, it moves both axis at once, then each axis individually to ensure they are both actually homed.
So if you just duplicate your second pass moves to the first pass, you'll be good to go I think.
-
That fixed it on the panel due!
I will give the print a try. I'm hopeful -
@spfxshane
success!
Now i have to figure out how to deal with the next problem. Maybe you can help point me in the right direction. Is there a way to configure one tool into the config file. this time the print failed because i did not choose a tool. The bed heated, then the machined homed, then faulted because i didn't choose a tool. I then put tool zero on standby started the print again and the bed heated and it immediately started the print with a cold extruder. i was hoping would heat theebed and then wait for the hotend to heat up and start the print. -
Uncomment
T0in your config.g to have the first tool selected at startup. Your slicer should also choose the tool before the print, but you may need to add that to your slicer start gcode.@spfxshane said in homing problems:
;Select default tool
;T0
