Problem with duet 3 mainboard as an expansion board

mike_b

Hi everyone, new user here. I have a quick question regarding how to make changes in my config.g file to propagate to my second Duet 3 Mini 5+ board that I am using as an extension board for some stepper drivers. My problem is this: when I make a change in my config.g file that effects a stepper driver on the second board, that change is not reflected until I power cycle both boards. For example, when I try to change the direction of the motor on the expansion board, that change in direction is not reflected until I power cycle both boards. Is this normal/expected behavior? Thanks in advance!

EDIT: I am posting in the "duet web control" section because I just assumed that the "reset main-board" option in the web control would accomplish what I'm after. So just wondering if there is something obvious I am missing.

dc42

@mike_b do you have a G4 command early in the main board config.g to give the expansion board time to start up and set its CAN address before it receives CAN commands?

Phaedrux

How are you editing the config.g?

What firmware version?

dc42

@mike_b do you have a G4 command early in the main board config.g to give the expansion board time to start up and set its CAN address before it receives CAN commands?

mike_b

@dc42 That fixed it, thank you! I was building my config.g file one section at a time, by copying and pasting the text via the Show G-code preview option in RRF config tool. Although the G4 command does show up in the config.g file at the end, none of the section themselves contain it, hence why I missed it. Anyway, thanks again. I'm extremely happy with my Duet 3 Mini 5+ purchase, in fact, the entire ecosystem is just plain fantastic. Thank you!

mike_b

@Phaedrux thanks for the reply, appreciate it! Turns out I was missing the G4 command at the top of my config.g file