Posts made by jchodakowski

Just want to sanity check before I get too deep. Will run dedicated 5v supply for the pi5 but other than that, just wondering if someone sees an issue I don't.

Thanks

Is there any access to the printed mount parts for the Z sensor? I've seen the spacer for the tb but nothing else.

No joy on the reflow

@droftarts
I should have mentioned that with regards to the sd card media, I've tried nearly everything you describe including using a brand new card I "just happened to have". I use the branded sd card formatter, and all the media inspects fine on any PC or Mac I check it on, but never seems to work appropriately when inserted into the board.

RepRapFirmware for Duet 3 Mini 5+ version 3.2.2
Warning: Cannot initialise SD card 0: Card is unusable
WiFi is disabled.
RepRapFirmware for Duet 3 Mini 5+ is up and running.

And from the M122

=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 0.2MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0

I see in the link you provided the following:

If the socket or processor is faulty but the card is detected, it usually drops to 0.2MB/sec.

So yeah

As the subject suggests, I have a Mini5+ and I've had it since they were released. The printer this board is attached to was set up, worked great (well enough to get a Voron serial number) and then life took over and the printer sat on a shelf, un-powered until this weekend. The printer never arrived on the network so after attaching a serial terminal, I can see the complaint in real time, the board is not initializing or reading from the sd card. There doesn't seem to be any good way to change the situation. The FW is at 3.2.2 if I recall.

What are my options here?

I don't have a direct 1:1 action->result yet, just something that occurs intermittently.

When uploading firmware via DWC, any connected serial terminal application (Pronterface, SerialTools) will crash with a verbose stack/IO error related to the app (so, not especially informative). This behavior is inconsistent and I've been trying to update to a non-beta 3.2 firmware to eliminate this as a cause but have been unable to (see posting in firmware).

It's not a fatal problem, subsequent application start and connection will succeed. Since the HW is new, seemed worth reporting. Let me know if I can collect more data.

The uploads succeeds but the version of 3.2 remains the beta that shipped on the board. Updates to 3.2 on other Duet boards do not bear this beta label.

Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.2-beta3.2+1 (2020-11-15)

@CaLviNx thanks!

Is there a board DXF available for creating a mount?

By "a bit of a process" I meant you'll need to activate your google-fu.
The firmware is in github and you need a pogo-pin firmware loader - the rest should be not unlike loading firmware on other simple rt devices.

I have never seen "a documented process".

100% all day

@T3P3Tony said in Magnetic sensor dead?:

@jchodakowski we will replace the sensor under warranty. Are you ok with swapping out the PCB only from the housing? That will be quicker as we don't have housings in stock right now.

What's my next step?

Yeah, that works fine

After a power cycle it behaves "normally" in that it flashes green, starts communicating with the duet. A M591 D0 asap yields this:

Duet3D magnetic filament monitor on input 3, enabled, sensitivity 25.20mm/rev, allow 70% to 140%, check every 3.0mm, version 3, mag 132 agc 89, no calibration data

However when a print actually starts (warmups done) the system will immediately report an error from the sensor and the print never starts. Filament never even moves.

It flashes green three times, there are no error flashes

Yes, it is updateable although it's a bit of a process.

So, was working last night. Woke up this morning, started a print and it immediately paused, with a sensor error. M591 D0 yielded this:

Duet3D magnetic filament monitor on input 3, enabled, sensitivity 25.20mm/rev, allow 70% to 140%, check every 3.0mm, version 3, mag 132 agc 89, error 4

I power cycled and the error 4 went away but the monitor still pauses the print. I've disassembled the monitor and it looks mechanically sound. Led flashes seem normal - I've not checked for error codes specifically.

Thoughts?

If I'm not mistaken that unit has older firmware on it? Should ideally be version 3 to start... the report will then tell you more about "how" sensitive it is:

Duet3D magnetic filament monitor on input 3, enabled, sensitivity 25.20mm/rev, allow 70% to 130%, check every 3.0mm, version 3, mag 133 agc 93, no calibration data

(mine hasn't gone anywhere today) what's important there are the mag and agc values. Knowing those lets you know if you're in a good bracket to start with (I had to modify my sensor housing a little) and once I got in a good reading realm, the data was more accurate and I had fewer if any false stops

I did have to sand it in the end but was able to, after a couple of sand/check/sands to get the agc to 92. Measurements are less rangy now. Thanks.

From time to time my prints will pause early on because I get a "no response received from filament sensor" (or somesuch message). When I try a M591 D0 it always responds and has data so I resume the print and everything is fine.

My mag is 132 and my agc is 106 - I understand the agc should normally be a little lower. Should I open this up and try to improve tension on the grub or are these numbers ok?