Mini 5 (with toolboard) and leveling using X2 Motors
-
@Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:
@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:
G30 P0 X50 Y170 Z-99999
G30 P1 X350 Y170 Z-99999 S2can you issue those commands manually? whats the output in the console
i issued both manually
G30 P0 X50 Y170 Z-99999 completes fine (shows green in the console)
G30 P1 X350 Y170 Z-99999 S2 shows: Error: Z probe was not triggered during probing movebut i can physically see the probe operate and the Z axis react and the head lifts back up
-
and a g29 across the bed works?
-
yes it does.
I re-installed my Duet-2 all is working again with the same bed.g file.
i have compared my Duet-2 & mini-5 config's and i can see nothing wrong with the mini-5 config
-
neither can i. and the probing working sometimes is not something you can configure.
-
@Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:
neither can i. and the probing working sometimes is not something you can configure.
Thank for the help, i will just wait and see what any of the duet team have to say , this board was a christmas gift so i will ask my uncle where he bought it
-
Firmware version? Can you post the results of M122?
-
@Phaedrux said in Mini 5 (with toolboard) and leveling using X2 Motors:
Firmware version? Can you post the results of M122?
The Board is removed so the M122 will show some errors i think.
i installed the board (and toolboard) in my core-xy , which normally has a duet-3-6hc fitted and the mini-5 runs fine in there, so im not sure why it doesnt like being in my hacked up i3, and even stranger that my Duet-2 wifi runs fine when i put it back into the i3, both printers sit side by side so its not a location related issue.
i have been racking my brains with this one as it makes no sense at all.
M115:
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.2-RC2 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2020-12-24
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.2-RC2 running on Duet 3 Mini5plus WiFi (standalone mode)
Used output buffers: 3 of 40 (11 max)
=== RTOS ===
Static ram: 98732
Dynamic ram: 107196 of which 496 recycled
Never used RAM 38792, free system stack 140 words
Tasks: NETWORK(ready,192) HEAT(blocked,316) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,360) TMC(blocked,123) MAIN(running,444) IDLE(ready,20) AIN(blocked,267)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:54 ago, cause: power up
Last software reset at 2020-12-30 22:53, reason: User, GCodes spinning, available RAM 38752, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00451000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Supply voltage: min 0.0, current 0.9, max 0.9, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
Date/time: 2021-01-01 15:00:52
Cache data hit count 222524317
Slowest loop: 5.31ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.2ms, 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, chamberHeaters = -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
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.
=== Network ===
Slowest loop: 10.70ms; 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.25beta0
WiFi MAC address f4:cf:a2:6f:bd:af
WiFi Vcc 3.37, reset reason Power up
WiFi flash size 2097152, free heap 25264
WiFi IP address 192.168.0.115
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages queued 1015, send timeouts 1012, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
- WiFi -
-
@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:
the mini-5 runs fine in there, so im not sure why it doesnt like being in my hacked up i3
That is confusing. An intermittent short in something connected?
-
@Phaedrux said in Mini 5 (with toolboard) and leveling using X2 Motors:
@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:
the mini-5 runs fine in there, so im not sure why it doesnt like being in my hacked up i3
That is confusing. An intermittent short in something connected?
its the exact same wiring between the mini-5 and the Duet-2 and i thought about that and have been probing for shorts and found nothing
-
Some thoughts:
- Is the tool board definitely running 3.2RC2 as well?
- Try adding a settling delay parameter (R) to the M558 command, e.g. R0.2 or R0.5
- You said the probe doesn't register as triggered, yet you don't get a head crash. That means either the dive height is too low to probe deep enough, or the probe trigger is being registered for the purpose of stopping the Z move but not for the purpose of recording the stop height. So try increasing the dive height - very carefully!
-
Well I finally fixed it....
My homeall.g had G30 S-3 in the script.
I removed that and changed it to single G30 command on its own and now it completes the G32 action with no errors, I dont know why it works fine on my Duet-2 with the S-3 switch in my homeall but the mini 5 doesnt like it
-
@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:
Well I finally fixed it....
My homeall.g had G30 S-3 in the script.
I removed that and changed it to single G30 command on its own and now it completes the G32 action with no errors, I dont know why it works fine on my Duet-2 with the S-3 switch in my homeall but the mini 5 doesnt like it
Perhaps your Duet 2 is running old firmware that doesn't support the S3 parameter?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in Mini 5 (with toolboard) and leveling using X2 Motors:
@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:
Well I finally fixed it....
My homeall.g had G30 S-3 in the script.
I removed that and changed it to single G30 command on its own and now it completes the G32 action with no errors, I dont know why it works fine on my Duet-2 with the S-3 switch in my homeall but the mini 5 doesnt like it
Perhaps your Duet 2 is running old firmware that doesn't support the S3 parameter?
The Duet-2 was/is on Release 3.2-RC1
And to confirm
Duet-2 WOULD complete the action with G30 S-3
Duet-3 Mini-5+ WOULD NOT complete the action G30 S-3
The Mini-5+ would only complete after i removed the S-3 switch
