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?
Best posts made by mike_b
-
RE: Motor brake not working on expansion board
-
RE: Motor brake not working on expansion board
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!
-
RE: Motor brake not working on expansion board
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!
Latest posts made by mike_b
-
RE: 6hc as expansion
Hey @Zseven, I use an mini5+ as an expansion board, let me know if there is anything I could help you with
-
RE: Motor brake not working on expansion board
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!
-
RE: Motor current idle factor not working over canbus?
@dc42 Great question! Unfortunately, I can’t give a definitive answer at this point without conducting more thorough testing, I’m not entirely sure about the exact sequence of events. Let me get back to you this weekend
-
RE: Motor brake not working on expansion board
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!
-
RE: Procedure for testing an alpha release
Hey @jay_s_uk, awesome, it worked, thanks for your help!
-
RE: Motor brake not working on expansion board
Hi @droftarts and @dc42, not sure if this is helpful or not, but just wanted to come here to say that this bug is also present in the latest alpha release I'm testing:
Product Short Name Version Duet 3 Mini 5+ Mini5plus 3.6.0-alpha.5+1 Duet 3 Expansion Mini5plus Mini5plus 3.6.0-alpha.5+1 Duet 3 Expansion TOOL1LC TOOL1LC 3.6.0-alpha.5 Duet Software Framework DSF 3.6.0-alpha.2 Duet Web Control DWC 3.6.0-alpha.2
-
RE: Motor current idle factor not working over canbus?
Hi @dc42 running the following setup:
Product Short Name Version Duet 3 Mini 5+ Mini5plus 3.6.0-alpha.5+1 Duet 3 Expansion Mini5plus Mini5plus 3.6.0-alpha.5+1 Duet 3 Expansion TOOL1LC TOOL1LC 3.6.0-alpha.5 Duet Software Framework DSF 3.6.0-alpha.2 Duet Web Control DWC 3.6.0-alpha.2
And unfortunately this does not resolve the bug. I am still unable to set a custom idle current on the expansion board; i.e. the idle current remains at the default value, irrespective of what I set in my
M906
command. Here are some extra bits of info that might be helpful:- first, despite the idle current actually being set to the default initially -- I can tell this because my build plate drops; I have a belt driven z-axis with brakes -- running M906 without any parameters reports the desired idle current:
11/09/2024, 07.42.26 M906 Motor current (mA) - X:1200, Y:1200, Z:1200, E:500, idle factor 75%
- second, the interesting part is that despite the idle factor being set to the default initially, it appears as thought eventually, the motors do enter the desired 75% idle current, I can tell this because the build plate wont crash again. I'm not sure exactly how to verify this, I guess I could use my voltmeter to test current into the motor?
-
Procedure for testing an alpha release
Hi everyone, I’m looking to test the latest
3.6.0-alpha
release and would appreciate any general advice from the community on how to do this properly. I want to avoid making any mistakes and thus causing unnecessary work for the developers.For context, my setup:
- two Mini5+ boards (the first as the main board and the second as an expansion)
- one 1LC toolboard, and
- all in SBC mode.
When I tested the 3.5.3-beta release, I followed the official procedures by switching to the unstable repo, modifying
/etc/apt/sources.list.d/duet3d.list
, and then runningsudo apt update && sudo apt upgrade
.However, I'm unsure about the correct steps for testing the
-alpha
release. Should I simply download the firmware files to the SBC and the expansion board's SD card? And if I do that, will I also need to update the Duet Control Server or Duet Web Server as part of the process? Thanks in advance!EDIT: I edited the
duet3d.list
file to point tounstable-3.6
but runningapt list -a duetruntime
seems like only3.6.0~alpha.2
is available:$ sudo apt list --upgradable Listing... Done duetcontrolserver/unstable-3.6 3.6.0~alpha.2 arm64 [upgradable from: 3.5.3~rc.1] duetpimanagementplugin/unstable-3.6 3.6.0~alpha.2 arm64 [upgradable from: 3.5.3~rc.1] duetpluginservice/unstable-3.6 3.6.0~alpha.2 arm64 [upgradable from: 3.5.3~rc.1] duetruntime/unstable-3.6 3.6.0~alpha.2 arm64 [upgradable from: 3.5.3~rc.1] duetsoftwareframework/unstable-3.6 3.6.0~alpha.2 arm64 [upgradable from: 3.5.3~rc.1] duettools/unstable-3.6 3.6.0~alpha.2 arm64 [upgradable from: 3.5.3~rc.1] duetwebcontrol/unstable-3.6 3.6.0~alpha.2 all [upgradable from: 3.5.3~rc.1] duetwebserver/unstable-3.6 3.6.0~alpha.2 arm64 [upgradable from: 3.5.3~rc.1] libcamera-ipa/stable 0.3.1+rpt20240906-1 arm64 [upgradable from: 0.3.1+rpt20240829-1] libcamera-tools/stable 0.3.1+rpt20240906-1 arm64 [upgradable from: 0.3.1+rpt20240829-1] libcamera0.3/stable 0.3.1+rpt20240906-1 arm64 [upgradable from: 0.3.1+rpt20240829-1] reprapfirmware/unstable-3.6,unstable-3.6 3.6.0~alpha.2-3 all [upgradable from: 3.5.3~rc.1-1]
-
RE: Motor current idle factor not working over canbus?
Hi @dc42, I realize this is an old thread, but I was wondering if the fix for this bug (commit here) is included in
3.5.3-rc.1
? If it is, I can confirm that the issue persists, as I still can't change the idle current on motors connected to my Mini5+ board, which I'm using as an expansion board. Would you like me to test this on the 3.6 alpha release?" -
RE: Motor brake not working on expansion board
Hi @droftarts thanks for the suggestion. Unfortunately getting the same error message:
9/7/2024, 6:16:58 PM M569.7 P40.3 C"out6" Error: M569.7:
EDIT: also, is the CAN address in the port name was optional? Snippet from the docs:
The CAN address does not need to be specified in the port name, but if it is then it must be the same as the driver CAN address