DUET3 1XD M569 issues

too

Hello,

I have issues with configuring custom pulse timing on the 1XD boards.
On startup i get a Error: M569: Response timeout: CAN addr 40, req type 6018, RID=9 message from each 1XD board, is this feature already implemented or what am I doing wrong?

here is the part of the config.g that causes the issue:

M569 P44.0 T5:5:10:0 ; X driver 44 requires an active high enable, 5us minimum step pulse, 5us minimum step interval, 10us DIR setup time and 0us hold time
M569 P43.0 T5:5:10:0 ; X driver 43 requires an active high enable, 5us minimum step pulse, 5us minimum step interval, 10us DIR setup time and 0us hold time
M569 P42.0 T5:5:10:0 ; X driver 42 requires an active high enable, 5us minimum step pulse, 5us minimum step interval, 10us DIR setup time and 0us hold time
M569 P41.0 T5:5:10:0 ; X driver 41 requires an active high enable, 5us minimum step pulse, 5us minimum step interval, 10us DIR setup time and 0us hold time
M569 P40.0 T5:5:10:0 ; X driver 40 requires an active high enable, 5us minimum step pulse, 5us minimum step interval, 10us DIR setup time and 0us hold time

dc42

If you re-run config.g using M98 P"config.g", does it give the same errors?

If not, and the main board and the 1XD boards are powered from the same PSU, it could be that the 1XD boards are taking a little longer to power up than the main board. If that's the reason, you can use a G4 delay command in config.g before the first command that refers to a 1XD board.

too

~~The issue seems to have solved itself - I went ahead and moved the whole Duet3 assembly into the control box of an actual machine - and it seems to work now without issues..~~

Yes, they are all running from the same PSU. I will add a G4 delay in the beginning of the config.g just to be sure.

EDIT: The issue is back on startup. It also shows up when I re-run the config.g with M98:

dc42

"m569 p40.0 t5:5:10:0" works for me.

Have you established that you can communicate with those 1XD boards? Send e.g. M115 B40 to check.

Have you fitted the CAN termination jumpers on the last board in the chain, and not on any of the other boards?

too

Yes, the boards work fine. I can control the axes that are connected to the individual boards even with this error coming up.

I did in fact not have any termination resistor in the boards - I added them on the last one and would you look at that, the error is gone, thanks!