during Print Starts M32 showing Errors
-
@NeueKlasse said in during Print Starts M32 showing Errors:
Error: Bad command: Content-Type: application/octet-stream
download the file and look at it.
-
Yes, please share the file here.
-
i didn't see anything Strange there
Prusa Mini, Chiron @ BMG X2
Metal SLS Printer Development -
How are you uploading the file? Directly from S3D with a script? Or just sliced with S3d and uploaded with DWC?
Are you actually using M32 to start the print?
Please post the results of M122 and check the general tape to see if DWC is actually at 3.2.
-
yes, you can see the Script in the top comment section of the gcode file.
i'm starting the print over "Left Click on the Job, and start print"
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S4-6J1FL-3SD6R-1S5YF
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 94036 of which 24 recycled
Never used RAM 114984, free system stack 180 words
Tasks: NETWORK(ready,193) ETHERNET(blocked,118) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,349) TMC(blocked,50) MAIN(running,1123) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:02:14 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 8.5, current 22.9, max 22.9
Supply voltage: min 25.2, current 25.4, max 25.5, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 29810, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 29810, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 29810, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 29810, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 29810, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 29811, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-01-18 17:44:41
Slowest loop: 16.98ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 205.99ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
Extruder 1 sensor: no filament
=== CAN ===
Messages queued 536, send timeouts 1205, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 47
Prusa Mini, Chiron @ BMG X2
Metal SLS Printer Development - Ethernet -
-
@NeueKlasse said in during Print Starts M32 showing Errors:
YamahaPSS11Knob.gcode
E5LeftRight.gcode
those names do not match
-
i only noticed that the Bed Mesh didn't take advantage....
=> Activated with:
G29 S1
M376 H2
but after the Primeline the Nozzle goes down onto the bed and scraping a little bit
to it's start Coordinates (middle of the bed, approx. 0,15 mm deeper (bed is like a cup)Prusa Mini, Chiron @ BMG X2
Metal SLS Printer Development -
@Veti it's the same on all other files, i just uploaded the latest one
here the gcode from the topic:
Prusa Mini, Chiron @ BMG X2
Metal SLS Printer Development -
@NeueKlasse said in during Print Starts M32 showing Errors:
M376 H2
H2 is a very short taper height. That means it's going to compress the amount of adjustment so that by the time it's at 2mm height, no compensation is done. Try H20 if you must use taper, or turn it off entirely with H0.
-
; postProcessing,curl -F "file=@[output_filepath]" "http://192.168.178.182/rr_upload?name=gcodes/[output_filename].gcode",,, ,I'm not a S3D user and not really familiar with using curl to get it to upload, but can you try by just uploading the file with DWC itself?
-
@Phaedrux OK, i'll try that, Thanks
-
Error: Bad command: --------------------------69765c7ee65a6614 Error: Bad command: Content-Disposition: form-data Error: Bad command: Content-Type: application/octet-streamThat seems like HTML meta data that might be getting sent along with the curl upload.
-
@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.
-
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 -
@Veti Jup, i've seen it 1min Later
-
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
-
@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) -
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.
-
@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. -
@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.
