Motor brake not working on expansion board

mike_b

@dc42 quick question: do you recommend testing 3.6.0-alpha at this point? Or just waiting for the 3.5.3?

dc42

@mike_b we recently released 3.5.3-rc.1 so I suggest you try that.

mike_b

@dc42 Thank you! This is fantastic. I'll try it out tomorrow and report any bugs in the beta channel. Thanks again!

mike_b

@dc42 apologies up front if I'm missing something obvious here. However, in your dropbox, I don't see the Duet3_SBCiap32_Mini5plus.bin file which, I assume, I would a 3.5.3-rc.1 version off to test if this bug has been resolved? Or, is it safe to test with Duet 3 Expansion Mini5plus running at 3.5.2?

jay_s_uk

@mike_b https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.3-rc.1

mike_b

Hi @jay_s_uk, unfortunately I don't see Duet3_CANiap32_Mini5plus.bin in the link provided. Am I missing something?

jay_s_uk

@mike_b DSF should handle the SBC IAP file, they aren't part of a normal release

mike_b

@jay_s_uk When you say "DSF should handle the SBC IAP file" do you mean that I'll be able to find the .bin file in the DSF git repo?

jay_s_uk

@mike_b when you sudo apt update/upgrade, everything gets pulled down and automatically updated. so I suppose I should say the DSF repository (not git)

mike_b

@jay_s_uk ah, Ok, got it, thank you! So I guess that mean I'll have to figure out my second issue https://forum.duet3d.com/post/344169, for some reason, despite switching to the unsteady deb repo (i.e deb https://pkg.duet3d.com/ unstable-3.5 armv7 in my sources, running apt update/upgrade doesn't get me 3.5.3-rc

p8blr

@dc42 How do we update to this if we're running in SBC mode? The M997 commands don't work.

jay_s_uk

@p8blr you can't at the moment

mike_b

Hey @jay_s_uk when you say "you can't at the moment" do you mean you can't at the moment because of a bug? Or do you mean you can't update to an -rc release in SBC in general? I ask because there does seem to be a version 3.5.3-rc1 in the repo here so I'm not really sure what the issue is. Could you help me understand?

jay_s_uk

@mike_b just wait for @chrishamm to respond. You can usually upgrade to RC versions but it's obviously not working so be patient

mike_b

Hey @jay_s_uk Thanks for your feedback! I truly appreciate everyone’s input and am happy to wait for a response Thanks again!

chrishamm

@mike_b It's now available via the package feeds, apologies for the delay.

mike_b

Thanks @chrishamm, my entire system is now running 3.5.3-rc.1 as shown here

Unfortunately @dc42 I'm getting the same bug as before:

05/09/2024, 14.02.03 -Error in start-up file config.g line 156: M569.7:
05/09/2024, 14.02.03 -Error: M569.7:

Interestingly, I don't see these errors after power cycling the board and the SBC. That error only shows up when I do an emergency stop or chose "restart mainboard" or "run config file" after editing the config file. Although I guess I'm not getting those messages after a power cycle because DWC starts up only after the error, so doesn't show up in the console?

@dc42 also, I just realized that my particular issue was never mirrored on github - or mentioned in the release notes - so now I'm wondering if this issue got confused with this one?

Looking through the changelogs of previous releases, I see this limitation mentioned for 3.4.0RC1 but it's never mentioned again:
M569.7 (configure driver brake port) is supported, initially on the main board only

dc42

@mike_b M569.7 is supported on expansion boards too, since version 3.5.0 AFAIR.

mike_b

Hey @dc42, hmm, ok, I'm now very confused... this entire thread is about fixing this issue, since, as you yourself said at the very top of this thread:

@mike_b this is a known issue, fixed in 3.6.0-alpha and in the forthcoming 3.5.3 release.

Or am I missing something?

mike_b

Hey @dc42 in case it's helpful, I am reiterating the issue here:

in 3.5.2 and 3.5.3-rc.1 this command fails:

 M569.7 P40.0 C"40.out5" S25

while a similar command on the main board works fine:

M569.7 P0.0 C"out5" S25