Mini 5 (with toolboard) and leveling using X2 Motors

JayJay

I had an issue with miss-matched firmware earlier in the week which left me with a heater issue, the toolboard update took but the mainboard firmware didnt.

I had updated it (or so i thought) but the update hadnt taken, until it was done manually again, that updated evertything fully to the latest release candidates.

the final G30 in my bed.g was the result of a thread here on the forum which recommended a final G30 to re-set the Z datum in the middle of the bed after the leadscrews had carried out their compensation actions.

i commented it out the final G30, and the G29 that made no difference .

Although im puzzled why it would be a problem to load the height map aftwards when everything worked perfectly well on my Duet-2 with the same firmware and same bed.g .

i will make up a loom to remove the toolboard from the equation to see how that works

Veti

@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

the final G30 in my bed.g was the result of a thread here on the forum which recommended a final G30 to re-set the Z datum in the middle of the bed after the leadscrews had carried out their compensation actions.

best to do that in a macro.

JayJay

@Veti

what difference does it make where it is done ?

Veti

@JayJay
so it makes things like this
https://forum.duet3d.com/topic/20598/bed-g-repeated-execution-based-on-deviation-results
easier

JayJay

@Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:

@JayJay
so it makes things like this
https://forum.duet3d.com/topic/20598/bed-g-repeated-execution-based-on-deviation-results
easier

Thanks but i dont need that, and doesnt actually help me with the issue i am encountering.

i wired the Bl touch directly to the mini 5 and the problem still exists, i tried my IR probe direct to the board too and it too encounters the issue, really considering putting my Duet 2 back in at least i know it works.

EDIT

I just tested the probe(s) in all the other IO ports and the probes dont work in io0 or io4 dont know if that is relevant or not.

Veti

@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

I just tested the probe(s) in all the other IO ports and the probes dont work in io0 or io4 dont know if that is relevant or not.

io0 and io4 are not pwm capable.

see
https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Hardware_overview#Section_IO_port_pin_capabilities

JayJay

ok.

i tried homing Z at the points where my bed.g would probe to level the leadscrews and that works.

so its only when G32 is requested that the probe is not being seen

Veti

i am running bed leveling on my mini 5 fine using an ir probe.

only difference i see is that i have the M671 after the M208, but that should not matter

so its only when G32 is requested that the probe is not being seen

could that be a problem with the wiring?
maybe at the probing position the wires are not making a good contact

JayJay

@Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:

i am running bed leveling on my mini 5 fine using an ir probe.

only difference i see is that i have the M671 after the M208, but that should not matter

so its only when G32 is requested that the probe is not being seen

could that be a problem with the wiring?
maybe at the probing position the wires are not making a good contact

if it was a wiring issue then when i home at the probe points that would fail too, its only when G32 is requested, the probes work fine on the toolboard too when requsted to home at those points which rule out the wiring.

As i said in my post about the heaters which turned out to be the firmware, im confident in my wiring

Veti

@JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

G30 P0 X50 Y170 Z-99999
G30 P1 X350 Y170 Z-99999 S2

can you issue those commands manually? whats the output in the console

JayJay

@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 S2

can 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 move

but i can physically see the probe operate and the Z axis react and the head lifts back up

Veti

and a g29 across the bed works?

JayJay

@Veti

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

Veti

@JayJay

neither can i. and the probing working sometimes is not something you can configure.

JayJay

@Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:

@JayJay

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

Phaedrux

Firmware version? Can you post the results of M122?

JayJay

@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

Phaedrux

@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?

JayJay

@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

dc42

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!