Topics created by MikeGeppert

@mikegeppert I think you must be using the Duet in SBC mode. Expressions in array parameters are not yet supported in SBC mode, but support is coming in RRF 3.4beta2.

I only use hardware debugging aids to debug startup and bootloader issues, and then I use a Atmel ICE and Atmel Studio.

@dc42 said in Error building RepRapFirmware 3.3-dev:

I suggest you install this https://xpack.github.io/windows-build-tools/ if you haven't already, then adjust your PATH so that the version of make.exe from that installation is picked up before any other. You can type "where make" at the Windows command prompt to find out where make is being fetched from.

Yah... I tried several combinations (starting with the ones in the instructions) and finally gave up on Windows.

I installed a Virtual Box with a Ubuntu distribution and got it all working. Just avoided the whole make/rm command line length issue all together.
Thanks

@MikeGeppert said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

@Phaedrux said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

@MikeGeppert said in Extruder issues with 3.2-beta 3.2 - Duet 3 MB6HC:

My homing macros try and set stealthchop and sensorless homing. To do that I have to cut the current to 30% using the M913 command. So if I cut to 80% at first in the config file, do I then cut to 80% * 30%? Then set back to 80% when done?

This is exactly why I leave M906 as the full rated current and then adjust with M913. That way I know that M913 80 is 80% of rated. And 30% is 30% of rated. It's just more direct. No percentage of a percentage.

Mathematically I want the 80%*30%. My intention was that once Variables get implemented I would make a MAX_MOTOR_LDO that has the 2000mA value. And another variable that would have the percentage MAX_RUN_PERCENT to be like 80%. Then set the M906 to the multiplication of the two. Then I can use percentages of that MAX_RUN_VALUE.

Seems needless when M913 already exists, but it would work either way.