I am bumping it up (a little), as I have just had a couple of mysterious stops.

How about writing check results to CSV file?
Every 3 millimeters by default, only current 'percent' value.

It can be then analyzed in Excel (eg.).
If it proves useful, we can think again about 'live' chart.

I am bumping it up (a little), as I have just had a couple of mysterious stops.

How about writing check results to CSV file?
Every 3 millimeters by default, only current 'percent' value.

It can be then analyzed in Excel (eg.).
If it proves useful, we can think again about 'live' chart.

Hi,

I am using Creality coated glass bed, 330x330 mm (Ender 5 Plus).
It is great in many ways, but not especially flat, probably due to additional coating.
The maximum deviation is -0,14 / 0,07, works fine with mesh compensation, very poorly without. And my mesh is 240 points (15 x 16) , which takes a lot of time.

From time to time I need to re-calibrate, usually there is some skew probably related to dualZ, maybe one stepper moves slightly while the printer is off.

But the bed is generally the same all the time, only slightly tilted, so why to probe it again and again?

If after homing Z axis we check four key points, preferably near leveling screws, it should be possible to calculate temporary height map for each print? It would be fast and precise, and could be easily a start of every print.

BTW, how can I check these four key points offset without running mesh compensation and overwriting existing heightmap.csv?

My current workflow looks like this:

1 mesh compensation with four points (near the screws), read the Z offsets, manually readjust the bed, repeat until all offsets are around 0,010, usually takes three to four passes
2 run full mesh calibration, 240 points, mainly because it is overwritten during first step

Maybe I could make my manual correction a little more precisely and retain original height map for a little longer.

I have just realized that in gcode there is no explicit "extrusion rate", like in "mm/s"
but it is perfectly possible to calculate it for each move separately (?)

I am in the middle in diagnosing the cause of clogging in new hotend, and it would be extremely useful to have this information

with all-metal it is possible (at least i have read so) to experience heat creeping up the radiator, so low extrusion rate in some parts of the model could be problematic, and maybe also avoided by changing slicer settings

on the other hand, if it proves not to be the source of the problem, I can focus on other tests

hence the chart idea

BTW, maybe it could be also implemented in the slicer (Cura plugin?)

@infiniteloop, you are absolutely right - cleaning is the best way to go. just now I use two nozzles, one is printing, the other one bathing in acetone

on the other hand, just recently I have had one irritating print which clogged three times in a row at exactly the same spot - so maybe there was some additional problem with slicer - BTW, it was Cura 5 early beta, so...

the simulated extrusion chart should help with indicating such problems (to many thin walls etc.)

and who knows, maybe when we have the chart, there will be some indication of coming nozzle clog?

using M591manually definitely doesn't realize full potential of MFM

Hi,

I am looking for a way to better utilize magnetic filament sensor, and let it live up to the official "monitor" part of the name

I have bought MFM because of recurring problems with some prints - hotend clogging (all-metal), always at the same stage. Probably slicer&nozzle problem with restricted extrusion, resulting in overheating and eventual total clog.

I would love to have a chart similar to "Temperature chart", but displaying extrusion rate - both "theoretical" (from gcode) and measured by MFM:

• preferably every 3 mm (configurable?) and not averaged from the beginning of the print
• maybe also log file for later analysis
• it would be perfect as separate tab - plugin?

Probably the most useful way would be to display "theoretical" vs measured extrusion rate as separate lines on the same chart, with percentage thrown in as an option (or all three selectable?).

"Theoretical" chart would be also useful with simulation, to identify potential problems, even without MFM.

If there is any chance for official or community plugin, I will gladly give my input in planning and testing. Too complex for my mediocre programming skills

I am not sure if this post belongs to "DWC Wishlist" or "Filament Monitor", so I start in "General Discussion"

Alas, no joy.

I have tried 57600, 115200 and 250000 baudrate, crossed and straight RX-TX, nothing but startup creality logo.

It is a shame, I really like the flush mount of the original screen.

Already ordered Panelduer 4.3''.
For now, it is going to be strictly DWC and old iPad.

thanks for the clarification

so, I just connect it (resistors and all), and it either works, or it doesn't
and I have to check the firmware, upgrading it if necessary
Rx-Tx crossover is safe, and there are only two ways to connect it, no poroblem

It greatly simplifies matters

I will post the result here

@Veti

The dimensions offset doesn't look too bad, a little of careful filing should do the trick

I will probably try to upgrade and use original screen.
If I brick it in the process - welcome paneldue 4,3''.
The only caveat is the availability, it is not very popular and I will probably have to wait for it a bit.

@dc42

thanks for reply
I have some further questions:

1. how and where do I install the firmware? on the touchscreen? what is the procedure?

EDIT: I have checked the procedure for original Paneldue - can I use it?
Only my display doesn't have usb port, so I probably should connect USB directly to TX/RX/5VB/GND? Again with resistors on RX/TXfor safety? What if I reverse RX and TX by mistake, is it safe for my computer?

2. what is the chance that I will get full functionality of Paneldue?

Hi

I am just installing Duet 2 Wifi in Creality Ender 5 Plus, and I wonder if I can retain original 4,3'' touchscreen?

It has similar specs to older/smallest Paneldue, and is really nicely mounted in the chassis. Upgrading to 5'' or 7'' Paneldue means additional enclosure and I would gladly avoid that.

I am using 12864 on Maestro&Ender3, and it is ok for simple tasks - I use Webcontrol for complicated stuff anyway.

So 4,3'' touchscreen seems quite reasonable.
At least for a start.
Since it is already there.

I have a fear of small currents in me, and don't want to fry my new shining Duet - can somebody look into it, or maybe share a success story?

Here is the specification of very similar display (02WT instead of 06WT):
https://www.datasheetarchive.com/whats_new/f461dd15e005b2a27f4b985dece87d8b.html

Only I have newer version: DMT48270C043 _06WT.

Original board is connected with the screen by 4-wire (5V, GND, Tx, Rx).
Onboard SD port is not functional (there are additional Rx and Tx for that, not connected).

I don't have a clue about firmware etc. on these displays.