@dc42 I think I understand the problem...
If I make a movement of 0.5mm from the dashboard the M425 code does its job very well, if I make movements of 0.05mm the machine does not make any corrections.
@dc42 I think I understand the problem...
If I make a movement of 0.5mm from the dashboard the M425 code does its job very well, if I make movements of 0.05mm the machine does not make any corrections.
@gloomyandy I measured the distance with 0.45 using the movement buttons on the dashboard page +0.05 -0.05, when I reverse the direction of rotation I measure about 0.45mm before the dial indicator moves...
Thanks so much for the support.
I tried with M425 Z2 S10 and M425 Z5 S10 but it doesn't work.
I detected an error of approximately 0.45mm on the z axis with the comparator.
Honestly, I read it wrong, and I thought it was microstep.
Now I try to put like 2mm as a value.
I have a centesimal comparator placed on the Z axis
M584 X0.0 Y0.1 Z0.2 ; set drive mapping
M350 X16 Y16 Z16 I0 ; configure microstepping without interpolation
M92 X8533.33 Y8533.33 Z3675 ; set steps per mm
M425 Z2500 S5
(
Good evening everyone, I kindly ask for clarification on the use of the M425 Code to use it on a small milling machine equipped with a Duet 3d 6HC v1.02 (Firmware version 3.5.0-rc.1)
I'm modifying the milling machine to be able to use it with CAM software.
The X and Y axes do not need a recovery with M425, while the Z axis does.
I tried to put a line with M425 Zxx Sxx in the config.g file but it doesn't change anything?
Can anyone tell me where I'm wrong?
@dc42 The result of the M122 that I posted above was the tenth of the session since it was on.
Today I tried unplugging everything and keeping the card on for hours.
This is the result.
25/7/2023, 21:22:03 m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.0-beta.4 (2023-06-08 23:41:30) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6J1F8-3SN6S-TV3BB
Used output buffers: 3 of 40 (31 max)
Error in macro line 33 while starting up: Response timeout: CAN addr 40, req type 6018, RID=0
=== RTOS ===
Static ram: 155012
Dynamic ram: 121896 of which 0 recycled
Never used RAM 66228, free system stack 208 words
Tasks: NETWORK(1,ready,41.5%,153) ETHERNET(5,nWait,0.0%,321) HEAT(3,nWait,0.0%,329) Move(4,nWait,0.0%,332) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,343) TMC(4,nWait,8.1%,59) MAIN(1,running,50.4%,444) IDLE(0,ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 06:56:47 ago, cause: power up
Last software reset at 2023-07-24 16:54, reason: User, Gcodes spinning, available RAM 65140, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU temperature: min 38.6, current 38.9, max 39.6
Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 0.6, current 12.1, max 12.3, under voltage events: 2
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/64/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a, mspos 8, reads 7823, writes 11 timeouts 0
Driver 1: standstill, SG min n/a, mspos 0, reads 7824, writes 11 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 7824, writes 11 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 7824, writes 11 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 7824, writes 11 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 7823, writes 11 timeouts 0
Date/time: 2023-07-25 21:22:03
Slowest loop: 5.19ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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 3 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 41222, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 22901/0/0
Tx timeouts 0,0,22901,0,0,18321 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 4.03ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 2
= WiFi =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0
I bought the board in Italy from COMPASS DHM PROJECT on 03/23/2023, this is the replacement for the first defective one that was delivered to me in May 2023 after a warranty replacement procedure.