Topics created by VirtualBrown

@VirtualBrown Looking back at the M122 report you posted, I see:

=== DDARing 0 === Scheduled moves 2526188, completed 2526188, hiccups 0, stepErrors 0, LaErrors 0, Underruns [302, 1, 1064], CDDA state -1

It's the Underruns [302, 1, 1064] that will have been causing pauses.

The first underrun number is the number of 'lookahead' underruns, i.e. there were not enough spaces available in the move queue to do full lookahead. This type of underrun causes movement to be slower when there are very many short decelerating segments in succession. This should not cause a pause/stutter.

The second figure is the number of 'prepare' underruns. This indicates that the step interrupt service routine wanted another move, but although there was one it had not been prepared for execution. If the SD card was struggling to supply the next move, the processor may not have had time to prepare it for when it was needed. This may cause a stutter.

The third figure is the number of "no move" underruns. This indicates that the step interrupt routine wanted another move but none was available. If the SD card couldn't supply the next move in time to even be prepared, this will cause a stutter.

To check everything is okay now, start a print job, send M122. This will clear any existing errors. At the end of the job, send M122 again and see if it reports any of the above errors.

Probably just reformatting your original card would have cured it; I expect it was just running out of space, and causing files to be fragmented and taking longer to read.

Ian

@dc42 I used a hot air station we have at work to remove the chip and the board works great now, thanks for all your help!

@virtualbrown said in Heightmap, fill in missing data and interpolation:

@fcwilt this is my M557 line in my config:

M557 X0:200 Y0:200 S10 ; define mesh grid

What will your macro do? Will it interpolate to missing data? Sorry, I’m only a couple weeks into all of this.

It will take the values you enter and set M557 to the best values it can given the limits of the area you can probe.

The code does make an assumption that your M208 command has specified the printable area of the bed. In some printers the M208 min/max values actually are outside the printable area to allow certain movements, such as changing a tool on a multi-tool printer.

Here is a version that allows for that:

Code_to_set_M557.g

As to interpolation I know of no reasonable and accurate way to do that.

There are some systems that have a probe that is in the exact same XY location as the nozzle. These, of course, don't have the issue of not being able to reach all points.

You can "probe" with the nozzle but the results are very unlikely to be accurate, and it would be tedious in the extreme.

Frederick

@virtualbrown said in Temperature chart has stopped showing live data:

DWC: 3.4.1
RRF: 3.4.0

You should update your firmware to match the DWC version. Both should be 3.4.1

@dc42 I found B0 and C500 work well.

Thank very much for all your help on this!