3.2.0-beta4 - Extruder skips stepps since update

Chriss

Hi *,

I upgraded to 3.2.0-beta4 for debugging my problems with the filament sensor. My extruder skips now steps during the extrusion. More detailed behind the facts:

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.0-beta4
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2-beta4 (2020-11-26)

pi=yes

M906 X2000 Y2000 Z1000 E800 I30					; set motor currents (mA) and motor idle factor in per cent -- E600

I upgraded to 3.2.0-beta4 right after the last print, so nothing so the hardware was the same. I started a test print after the update and saw that no filament left the nozzle. So I touched the filament and realized that the stepper skipped steps. (vibrating filament)
The extruder is a Bondtech Upgrade Kit for Prusa i3 MK3S & MK2.5S Mosquito Fit from Bondtech. I loosened the screw from the extruder nearly completely and the extruder was able to transport a little bit of filament, but with a lot os skipping. The transport stopped completely as soon as I added a bit of friction with my fingers to the filament.
So I gave the motor some more current (from 600 to 800mA) but the behavior has not changed. Bondtech mentioned 800mA as max. So I do not want to go further if possible.

And ideas?

Cheers, Chriss

Phaedrux

That's an odd one. Have you gone back to 3.1.1 to confirm it works properly there? (sorry for having to jump through so many hoops!)

If you send M98 P"config.g" in beta 4 do you see any error messages?

Can you send M906 by itself when the motor is skipping to verify what the current is actually set to at that time?

Chriss

@Phaedrux said in 3.2.0-beta4 - Extruder skips stepps since update:

That's an odd one. Have you gone back to 3.1.1 to confirm it works properly there? (sorry for having to jump through so many hoops!)

Can you send M906 by itself when the motor is skipping to verify what the current is actually set to at that time?

let's talk about that later, the M98 first.

If you send M98 P"config.g" in beta 4 do you see any error messages?

02/12/2020, 05:31:15	Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 512C
02/12/2020, 05:31:15	Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 245C
02/12/2020, 05:31:14	Error: M591: Response timeout: CAN addr 1, req type 6046, RID=5
02/12/2020, 05:31:14	Connection to Duet established
02/12/2020, 05:31:14	Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
02/12/2020, 05:31:14	Warning: Discarded msg src=1 typ=4510 RID=4095 exp 5
02/12/2020, 05:31:13	Error: M906: Response timeout: CAN addr 1, req type 6043, RID=4
02/12/2020, 05:31:12	Error: M92: Response timeout: CAN addr 1, req type 6042, RID=3
02/12/2020, 05:31:12	Warning: Discarded msg src=1 typ=4510 RID=4095 exp 4
02/12/2020, 05:31:11	Error: M350: Response timeout: CAN addr 1, req type 6042, RID=2
02/12/2020, 05:31:11	Warning: Discarded msg src=1 typ=4510 RID=4095 exp 3
02/12/2020, 05:31:10	Error: M584: Response timeout: CAN addr 1, req type 6042, RID=1
02/12/2020, 05:31:10	Warning: Discarded msg src=1 typ=4510 RID=4095 exp 2
02/12/2020, 05:31:09	Warning: Discarded msg src=1 typ=4510 RID=4095 exp 1
02/12/2020, 05:31:09	M98 P"config.g"

Hardware is a Duet 3 MB6HC (MB6HC) and a Expansion 3HC. The extruder is on "1.0".

M584 X0.0 Y0.2 Z0.3:0.4:0.5 E1.0

I had a problem with the update which I reported here.

I'm sure that the firmware in the 3HC is broken. The diag led flashes "2x" pause "4x". So the firmware is invalid and the board can not load the correct firmware from the MB6HC.

So I switched back to 3.1.1 this morning.

02/12/2020, 07:58:21	M115 B0
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-05-19b2
02/12/2020, 07:58:00	M115 B1
Board EXP3HC firmware 3.1.0 (2020-05-15b1)

The tool board is still on "3.1.0"? And it remains at "3.1.0" after a "M115 B1", should that be the case?

I think that a lot of things went horrible wrong during the upgrade to 3.2.

Back to your question, I tested the extrusion now while the board is on 3.1.1. The extrusion is fine, I tested at 5mm/s for 100mm, it starts skipping when I ask for a faster extrusion. But I think that this is the "old" behavior and fine for a 0.4mm nozzle.

Cheers, Chriss

jay_s_uk

yes, 3.1.0 is the latest stable versions for the toolboard and expansion boards

Chriss

@jay_s_uk

Thanks... that explains that.

Chriss

@Phaedrux said in 3.2.0-beta4 - Extruder skips stepps since update:

That's an odd one. Have you gone back to 3.1.1 to confirm it works properly there? (sorry for having to jump through so many hoops!)

If you send M98 P"config.g" in beta 4 do you see any error messages?

Can you send M906 by itself when the motor is skipping to verify what the current is actually set to at that time?

So, 3.2 works now as expected! I bet that the problem I reported here was caused by the missing update of the 3HC. I simply did not see the error message. Sorry, my bad.

BUT there is a good point here too, I learned a lot and I think that I found the problem of the filament sensor thingy from my other thread which was the reason for the upgrade to 3.2-beta4.

02/12/2020, 13:37:16	M98 P"config.g"
Error: M591: Filament monitor port must be on same board as extruder driver
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 245C
Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 512C

Cheers. Chriss

dc42

RepRapFirmware 3.2beta4.1 is now released. This fixes the problem with updating firmware on tool and expansion boards when the Duet has an attached SBC. Please try that version, and start a new thread if the problems continue.

Chriss

@dc42

Well, I used the version from your dropbox in the meantime. I wanted to get rid of my filament sensor problem first. That was really a pain in my ass to run frequently to the printer to check how many filament is left.

I will try that update later, anyway.