3.5 B3 Toolboard stepper intermittently running backwards

ctilley79

@Exerqtor said in 3.5 B3 Toolboard stepper intermittently running backwards:

@dc42
Yeah I allready have the GCode dictionary for M150 & M950 up trying to figgure out what i'm doing wrong.

The reason i "had" to look into it now is that it threw Error: LED strip #0 has not been configured . And when i try to configure it it won't let me lol. (Or do i have to wait for b4 for it to work again?).

If I'm reading the M950 G-code section correctly, some of those parameters aren't available until 3.5.0-beta.4. I'm just living with the error at the moment.

Exerqtor

@ctilley79 said in 3.5 B3 Toolboard stepper intermittently running backwards:

@Exerqtor said in 3.5 B3 Toolboard stepper intermittently running backwards:

@dc42
Yeah I allready have the GCode dictionary for M150 & M950 up trying to figgure out what i'm doing wrong.

The reason i "had" to look into it now is that it threw Error: LED strip #0 has not been configured . And when i try to configure it it won't let me lol. (Or do i have to wait for b4 for it to work again?).

If I'm reading the M950 G-code section correctly, some of those parameters aren't available until 3.5.0-beta.4. I'm just living with the error at the moment.

Yeah that's how i'm interpreting it to, Same here even though it's flooding DWC & PD at the start / end of a print lmao.

dc42

@ctilley79 the new commands for configuring and controlling LED strips are implemented in the 3.5.0-beta.3+ binaries that I posted. They have been tested on Duet 3 Mini and 6HC.

@Exerqtor please post the M950 and M150 commands you used.

wieman01

Hello, @ctilley79,

I generally have these issues when there is a problem with the wiring or the connectors. Manual extruding via DWC works fine, but then the motor needs higher currents, it move backwards because the wires only let through so much current.

I would check every wiring the in particular the soldering joints and connectors. This solves this particular problem for me every time.

wieman01

Exerqtor

@dc42 said in 3.5 B3 Toolboard stepper intermittently running backwards:

@ctilley79 the new commands for configuring and controlling LED strips are implemented in the 3.5.0-beta.3+ binaries that I posted. They have been tested on Duet 3 Mini and 6HC.

@Exerqtor please post the M950 and M150 commands you used.

That's weird, since i'm quiiiite sure i'm using the right command set (for a Duet3 Mini).

I TRY to send M950 E0 C"DO" T2, but i get the error mentioned above.

The M150's have been changed to this (for example):

M150 E0 R150 U150 B150 W150 S1 F1
M150 E0 R150 U150 B150 W150 S2 F0

gloomyandy

@Exerqtor Is "DO" a valid pin name on the mini? I had a quick look and couldn't find any pins with that name. Is this for the neopixels in a display attached via the exp headers?

oliof

@Exerqtor Are you sure DO is right and not D0?

Exerqtor

@oliof I copied it from the docs since I was unsure about the exact same thing 😆 So unless it's written wrong there as well it should be correct.

gloomyandy

@Exerqtor Which docs? I've just checked the source and there is no pin called either D0 or DO as far as I can tell. What pin are you trying to drive the neopixels from?

Exerqtor

@gloomyandy said in 3.5 B3 Toolboard stepper intermittently running backwards:

@Exerqtor Which docs? I've just checked the source and there is no pin called either D0 or DO as far as I can tell. What pin are you trying to drive the neopixels from?

The only pin that supports it on a Duet 3 Mini, which from what I can see lacks a proper explanation on what the "DO" pin is actually called. "ctrl+f" search for DO here and look at the 14th entry. Thats the only mention of it (that i'm able to find) in all the docs / schematics.

It's also just called "DO" in the schematics:
alt text

dc42

@Exerqtor the dedicated LED port is known as "led" in the firmware. This needs to be added to the documentation.

Exerqtor

@dc42 Then i bet a beer on the problem being solved for both me and @ctilley79 now that we know that. Thx!

ctilley79

This post is deleted!

ctilley79

@Exerqtor said in 3.5 B3 Toolboard stepper intermittently running backwards:

@dc42 Then i bet a beer on the problem being solved for both me and @ctilley79 now that we know that. Thx!

Does the M150 P parameter to work for you on this firmware build? I'm also using RGBW neopixels. The P parameter does nothing right now.

Exerqtor

@ctilley79 said in 3.5 B3 Toolboard stepper intermittently running backwards:

@Exerqtor said in 3.5 B3 Toolboard stepper intermittently running backwards:

@dc42 Then i bet a beer on the problem being solved for both me and @ctilley79 now that we know that. Thx!

Does the M150 P parameter to work for you on this firmware build? I'm also using RGBW neopixels. The P parameter does nothing right now.

I don't use the P parameter, only the R/G/B/W component "amount", it should yeld the same result although you would have to play around with the values to get the same effect.

dc42

@ctilley79 you are correct, the P parameter doesn't work for Neopixels. I will correct this before we release beta4.

hestiahuang

@dc42 said in 3.5 B3 Toolboard stepper intermittently running backwards:

@ctilley79 you are correct, the P parameter doesn't work for Neopixels. I will correct this before we release beta4.

May I know how to define M950 for Duet2Wifi? It can use M150 directly before, however it is failed and need definition first now. But not pin name found...

hestiahuang

@hestiahuang said in 3.5 B3 Toolboard stepper intermittently running backwards:

@dc42 said in 3.5 B3 Toolboard stepper intermittently running backwards:

@ctilley79 you are correct, the P parameter doesn't work for Neopixels. I will correct this before we release beta4.

May I know how to define M950 for Duet2Wifi? It can use M150 directly before, however it is failed and need definition first now. But not pin name found...

Add the source code to confirm my finding.

hestiahuang

so don't miss Duet2Wifi...

dc42

@hestiahuang thanks, this is now fixed ready for 3.5beta4.