3.5 B3 Toolboard stepper intermittently running backwards

Exerqtor

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

@ctilley79 @tas @Argo I have found a possible cause of this issue. It will indeed give the appearance of randomness because whether it happens will depend on the history of moves done. It is most likely to occur either segmentation is enabled. It is unlikely to occur unless pressure advance is in use, although it might possibly occur on a delta printer even when pressure advance is not used.

Are you able to test a new build of the firmware that should correct this? If so, which boards do you need firmware for?

I've had a much similar issue on my Duet 3 @ 1LC and would love to test out a possible fix ✌️

tas

Hi dc42,

I just need firmware for Duet2wifi and I can test immediately.

I do have pressure advance enabled in my config.

dc42

@tas please try the file at https://www.dropbox.com/sh/in0t2j68ic66oa8/AADv_6WzRy07H6MhBOrkDt23a?dl=0. Caution: this is untested because I no longer have a Duet 2 machine to test it on.

@Exerqtor I will test the new tool board firmware on my machine before I make it available.

dc42

@Exerqtor my test print was OK so I have put the new binaries for tool board and 6HC at https://www.dropbox.com/sh/in0t2j68ic66oa8/AADv_6WzRy07H6MhBOrkDt23a?dl=0. The tool board binary should be all you need to fix this issue.

ctilley79

@dc42 I’m using an SBC Duet 3 6HC and Toolboard. Is there a process to update without the package manager?

dc42

@ctilley79 if you are already running 3.5.0-beta.3 then it should be OK to just upload the new files via DWC.

tas

@dc42 Yes that has fixed the problem.

I tried extrude and retract from the paneldue three times rebooting the printer each time. All ok.

I then tried a print and the prime did push out filament. I see no issues with the print so far.

So you have fixed the issue and my Duet2Wifi machine did not blow up.

Many thanks.

Argo

@dc42

I can confirm the issues are gone with Duet 3 Mini 5 + Toolboard 1LC

dc42

@Argo @tas thanks for the feedback! This gives us more confidence to release 3.5.0-beta.4.

ctilley79

@dc42 Worked for me too. Thank you.

dc42

@ctilley79 thanks.

Exerqtor

@dc42
Seems to be working here too!

It's off-topic but happened after moving too b3+ so i'll drop it here and open another thread if it's more than a one line reply to fix it. Now I'm having some issues with the new neopixel assignement, it won't accept M950 E0 C"DO" T2 and returns:

M950 E0 C"DO" T2
Error: M950: Unknown pin name 'do'

This is on the Duet 3 Mini.

dc42

@Exerqtor the configuration of LED strips has changed for 3.5 beta4. See the new E parameter of the M950 command and the updated M150 description in the GCode dictionary.

Exerqtor

@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?).

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?