3.4.0beta7+7 config.g and accelerometer bug

Dogma2k

Since the update to 3.4.0beta7+7 I have several problems.

If I made a change in config.g, save and then confirm that I want to restart, the Duet crashes during the execution of the first command (e.g. G32 or a macro). Then it only helps if I completely de-energize the Duet.
I can work around the problem if, after making a change and restarting the board, I first press the emergency stop symbol at the top right.
Then the board no longer crashes after the first command.
When I have an accelerometer connected to the daughterboard that also has a PT100 connected, the DWC shows a sensor error and the value N/A.
This always happens when I restart the board after making a change in config.g. If I immediately press the EMERGENCY OFF symbol again, the error no longer occurs.
The Duet crashes when I run the measurement with this command "G1 X-50 G4 S2 M956 P0 S1000 A0 G4 P10 G1 X50 F20000".
A csv file is created, but this cannot be opened because the board reports it as faulty.

Gixxerfast

@dogma2k HI, it would probably help if you tell which setup you have, Which boards, Pi etc?

Also, check firmware versions. Mismatched versions is known to have cused similar behaviour.

Dogma2k

@gixxerfast
My setup is 1x Duet 3 6HC (3.4.0beta7+7) standalone mode and a Duet 3HC (3.4.0beta7+4) somehow doesn't give a beta7+7 version for it.

mrwizzard

@dogma2k I've experienced #3, and gave up. i figure it was the connection even though it does detect it every time. when it doesn't a reboot fixes it. i got data points in some files but at the end of them say something like "failed to read from accelerometer." and locks up the whole board. if it's the cable i'll just have to try another time. too frustrating to deal with and re-crimp wires, lol.

Julian_Wicht

@dogma2k in your #3 I had the same issue. Then I cut a USB 3.0 cable and use this Cable, Problem fixed

There is also in the wiki a notice about this trick