[3.4-b5] Expansion Board - Driver does not exist

[TechNi]

After upgrading from 3.4-b2 to 3.4-b5 on my mainboard and from 3.3 to 3.4-b5 on my expansion boards, the drivers on my expansion boards don't seem to work anymore correctly. During the very first boot, there is no error message but even then I notice something's wrong during homing (e.g. wrong motor speed). When I reboot with M999, I then get the following error message:

After that error message, the motors in question don't turn anymore. I have a Duet 3 attached to an SBC and 3 expansion boards.

Is there any easy way to downgrade to 3.4b2 for the mainboard and 3.3 for the expansion boards? Or should I wait for beta 6?

[T3P3Tony]

@techni do you have a delay in the start of your config.g of a couple of seconds to allow the expansion boards to start up before running config.g the startup speeds might have changed slightly from b2 to b5 (not sure about this). Also try sending M98 P"config.g" to see if you get the same errors because you can obviously communicate with all the expansion boards.

[Marcossf]

@t3p3tony @TechNi

Same in our post:

https://forum.duet3d.com/topic/25633/connection-error-to-1xd-boards-after-reset-but-ok-at-power-on/9

Still unsolved. Meanwhile we reset the boards with M112 + M999 after config modifications and they back online again. Not ideal but it works.

[TechNi]

@t3p3tony

I didn't have a delay in my config.g but I added one at the beginning for testing purposes and it does not make any difference (well except that it takes longer ofc).

Sending M98 P"config.g" does not generate any errors.

@Marcossf

When I send M112, there are actually no errors and the homing works fine, just like pre 3.4-b5 (even the thing with the different motor speed, might have been a one-time thing)

When I send M999, I get the errors. Also when I change the config.g and reset the board (which probably is also M999?).

[Marcossf]

@techni Same here. M999 cause inmediate lost of the 1XD boards.

Doing a M112 start up it right but after this command we need to send a aditional reset with M999 to get it back.

In previous beta4 didn't happened.

[T3P3Tony]

@marcossf @TechNi just to confirm we are looking at this issue.

[TechNi]

@t3p3tony Is there a fix for this in beta 6?

[T3P3Tony]

@techni @Marcossf neither @dc42 or I have been able to replicate this yet so there is nothing specifically in b6 that addresses this issue. That said it would still be helpful if you could try 3.4b6 to see if the issue is still present.

Also can you post your config.g and let me know if you are running in stand alone or SBC mode so I can setup a test setup as similar as possible to try and reproduce the problem. Thus far with 1 3HC and 2x 1XDs i have not yet seen the "error Driver does not exist" issue

[dc42]

@techni please post your config.g file.
EDIT: Tony asked already,

[Marcossf]

@t3p3tony @dc42 Sorry for late reply, we are involved in other projects.

We will update to 3.4.0 beta6 now and see if it's gone. By the way, we use SBC mode.

EDIT UPDATE: with the 3.4.0beta6 the missing boards when M999 is still there:

9/11/2021 13:26:47	PRINTER READY, TRY HOMING ALL
9/11/2021 13:26:46	extruder driver:  2
9/11/2021 13:26:42	Error: M584: Driver 40.0 does not exist
Driver 41.0 does not exist
Driver 42.0 does not exist
Driver 43.0 does not exist
Driver 44.0 does not exist
Driver 45.0 does not exist
9/11/2021 13:26:27	CORS disabled
9/11/2021 13:26:27	CORS disabled