during Print Starts M32 showing Errors

NeueKlasse

@Phaedrux OK, i'll try that, Thanks

Phaedrux

Error: Bad command: --------------------------69765c7ee65a6614
Error: Bad command: Content-Disposition: form-data
Error: Bad command: Content-Type: application/octet-stream

That seems like HTML meta data that might be getting sent along with the curl upload.

Veti

@NeueKlasse said in during Print Starts M32 showing Errors:

where do you get the E5LeftRight.gcode? i didn't find it in the gcode, that's the name another file...

its the name in your first post.

NeueKlasse

@Phaedrux

That's possible, I uploaded the gcodefile via Upload File on DWC, and started it
without an Error....

with curl that's the only Script that works.... at least a little bit, 5 of 10 Times it doesn't
do anything.... when i try it with S3D

NeueKlasse

@Veti Jup, i've seen it 1min Later

Phaedrux

Perhaps do some forum searching for previous examples of the CURL script.

https://forum.duet3d.com/topic/20374/browser-must-be-open-to-upload-from-s3d?_=1610987947656

for instance

NeueKlasse

@Phaedrux
i tested a few examples posted here in the forum, that one i currently
use was the first one that worked a certain degree...

Thank you for that Post, that could help me.

in Case of the M376 Command,
i tested it again with taper off (H0)

the Problem is that the Nozzle (if you look at the Gcode files) drops to the Start Z-Height after the Purgeline, my thought is that the Bed heightmap isn't involved at
that moment, because the Nozzle drops to far down after the Purgeline and scrapes a little bit (~40mm till the bed gets deeper..) to the Beginning coordinates (XY) in the middle of the bed (Bed is approx. 0,15mm higher on the outline as in the middle... (best leveling i could do with
the Chiron 400x400 Glass Bed)

Phaedrux

Not sure what you mean. The mesh will be active once G29 S1 is called. The M376 H2 will diminish the amount of compensation applied though, so it would make the problem you describe worse.

NeueKlasse

@Phaedrux
M376 is disabled (H0)
yes, Normally the G29 S1 should enable to heightmap.csv as the current Bed Mesh.
that means 0,1mm are everywhere the same on the bed, but in my case the Nozzle
crashes into the Bed on the Border after the Purgeline when the Start Z Height is setted
in the Slicer...

not sure how to explain that...
=> Bed Z=0 are in the middle of the bed.
=> the saved Heightmap shows that the Bed is like a cup (outer Edges Higher than the middle of the bed ... about 0,15mm)

Normally when G29 S1 is called the current height map are loaded.
in my case when the Nozzle goes to 0,16mm(first layer height) after the Purgeline (from Z0,4 to Z0,16) (after the G29 S1 command) it scrapes on the
edges of the bed into the Build Platform, after that the nozzle goes in the middle of the Bed to it's first gcode coordinate and the Nozzle height is visible higher there!!(that's the heightmap in reality...), Normally that should be compensated.

Phaedrux

@NeueKlasse said in during Print Starts M32 showing Errors:

but in my case the Nozzle
crashes into the Bed on the Border after the Purgeline when the Start Z Height is setted
in the Slicer...

Is this area within the probed area, or is it outside the area the probe can reach physically? If it's outside, the firmware will use extrapolation to guess what the height adjustment would be, but it's not always going to be accurate.