@jay_s_uk awesome, I guess I'll pull the plug and go for it. Thanks!

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?

Hey @droftarts, thanks for the heads up, and @dc42, enjoy your holiday! I just wanted to take a moment to express how impressed I am with the incredible hardware and software you guys create. My experience with the Mini 5+, 1LC, and magnetic filament monitor has been fantastic! The documentation is top-notch, and the forum is always such a helpful and well-organized place to find support. I know it can be tough and disheartening when all you hear are problems, so I wanted to share my appreciation for all your hard work and dedication. It really shows!

Hey @droftarts and @dc42 - FYI this issue is fixed in the alpha firmware linked by Andy Everitt in the github issue for this bug: https://github.com/Duet3D/RepRapFirmware/issues/1039 Thanks again for all your help on this!

droftarts created this issue in Duet3D/RepRapFirmware

closed [Bug]: Motor brake reports error when configured on mainboard used as expansion board #1039

@dc42 the most useful thing I have printed on my 3D printer is....another 3D printer, of course! And then with that new 3D printer, I plan to make all the plastic parts required for build a PrintNC CNC router.

@droftarts thanks for this very detailed write up, and thanks again for putting so much effort into this! I realy appreciate it. Unfortunately I'm dealing with some health issues at the moment but should be able to test in a week or two. Thanks again!

@dc42 thank you for the update and the heads up! Very much appreciate it.

@droftarts Ok, thanks! I'll repeat here what I posted on github, because I think it's important: I really don't want to come across as overly demanding - I fully appreciate how challenging it is to allocate resources in an open-source project. That said, the safety implicating of this particular issue are significant. I do have brakes on my z-stage motors but brakes clearly don't help in this situation. Although I guess you could argue a belted z-stage is a terrible idea in the first place anyway, again, I deeply respect the effort it takes to maintain an open-source project, so please don't take this as an entitled complaint - just a genuine concern I felt was worth sharing.

All that siad, I’m more than happy to take a more active role in debugging this issue, whether it involves hardware (I have multimeters, oscilloscopes, etc.) or software troubleshooting.

Hey @droftarts - just noticed this issue has been closed in github. Was this by mistake? Or has there been some resolution I'm not aware of?

@droftarts said in Motor current idle factor not working over canbus?:

Sorry, senior moment,

LOL, no worries, I know the feeling!

Could you test without stallguard and with the drivers in spreadCycle?

Just tried it, unfortunately no luck, problem still persists.

Otherwise I'll try and test early next week

Thank you! And please do let me know if there is anything I can do on my end to help with the debugging.

Hey @droftarts, I shared the configurations for both boards just a few days ago - you can find them here

I need to include the M906 I90 command in the config.g file for the expansion board; otherwise, the motors default to the default idle current, which causes my print plate to drop. For testing purposes, I remove that line. So, when I say the issue persists, I mean the problem still occurs when the M906 command is omitted from the expansion board’s config.g file. This was a workaround recommended by @dc42 himself here. Sorry, I know this is all a bit confusing, happy to jump on a quick voice call, to explain everything, if you think it could help?

EDIT: fixed links

Hey @droftarts, I hope this doesn’t make me sound crazy (though I wouldn’t blame you if it does!), but I just tested it in standalone mode, and the problem is still happening. I was sitting right next to the printer, with my hand under the print plate ready to catch it as soon as the low idle motor kicked in ... thankfully, I managed to catch it in time. I repeated the test several times with the same result. Anyway, I really don’t know what to do next. At this point I'm wondering if it's a hardware issue?

@kevinallen1902200 I'm planning to build a PrintNC router this winter and power it using duet closed-loop steppers. You might be interested in joining the printnc discord, I know a few people there that are discussing milling machines

@droftarts yup, running in SBC mode. Is our current running hypothesis that this could be an SBC-related issue? If so, would you like me to test without SBC mode on my end?