@Phaedrux
According to documentation M701 runs "filamanets/PLA/load.g" and you should run M703 to run "filamanets/PLA/config.g"

But when I load PLA it runs both filamanets/PLA/load.g and filamanets/PLA/config.g
(now I get unsure if it's the web-gui that does a M701 + M703 on filament change or if it's the M701 that does this undocumented behaviour)

@dc42
Yeah, v1.1

No problem, you guys found the issue in no-time, will contact support

@jay_s_uk
Bought it at 2022-03-09 from your official reseller https://hobby-store.pl/

@dc42
I got a file with numbers in v3.3, but it feels like it ends badly

(whole file: x.csv )

Sample,X,Y,Z
0,0.00,0.09,1.00
1,0.00,0.09,1.00
2,-0.02,0.02,0.98
3,-0.02,0.02,0.98
4,-0.02,0.02,0.98
5,-0.02,0.02,0.98
6,-0.06,0.08,1.00
.....
.....
661,0.11,0.03,1.09
662,0.11,0.03,1.09
663,0.11,0.03,1.09
664,0.08,0.22,1.02
Received mismatched data

@jay_s_uk
I think I identified the correct corner, it was easy to photograph for me. It's missing the diode, right?

@jay_s_uk I will double check, but I got a file with numbers in it, let me get back to you with a file

@gloomyandy yeah, and that also states that you should do a 703 to load specific config for the loaded filament.

Now that is done automatically. Which doesn't match the documented behaviour

@jay_s_uk I don't think so, didn't see any components on the underside. Which edge? It's currently mounted and a bit difficult to look at the underside.

But how does it explain why it works in 3.3 and not in 3.4?

Hi,

https://docs.duet3d.com/User_manual/Reference/Gcodes#m701-load-filament

Why is this command running the configure.g-script?
Is this a bug in firmware or a bug in documentation?

When called the firmware does the following:

Run the macro file "load.g" in the subdirectory of the given material (e.g. /filaments/PLA/load.g)
Change the filament name of the associated tool, so it can be reported back to Duet Web Control

I was planning on having M701 PLA more as an state.
And in my start g-code have a M703 to activate heaters

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0 (2022-03-15 09:00:04)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2624, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.4%,111) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,27) TMC(notifyWait,3.0%,67) MAIN(running,91.7%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:06:07 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 690.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 32, reads 48625, writes 5, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -5/6, peak Rx sync delay 211, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.4, current 24.4, max 24.4
MCU temperature: min 38.2C, current 38.5C, max 38.6C
Last sensors broadcast 0x00000002 found 1 78 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 7246, send timeouts 0, received 3270, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00, INT1 error!
I2C bus errors 0, naks 0, other errors 0

Works in 3.3.0, doesn't work in 3.4.0

M955 I14 P121.0

G91
G1 X-50
G4 S2
M956 P121.0 S1000 A0 
G4 P10
G1 X50 F20000
G90

Error: Failed to start accelerometer data collection: INT1 error