Issues after prime
-
Is the same
-
your video is very short and a little confusing to me. It looks like it goes into slow motion? Is that to show the stuttering? Can you upload a new video that's a bit longer and doesn't go to slow mo? Describe for us exactly at what point each piece of gcode is executing from the time you hit print to the time you see the problem.
-
This Video is without slow motion and with Sound.
G90 M83 M106 S0 M140 S50 M190 S50 M104 S240 T0 M109 S240 T0 T0 M98 P"startGcode" G92 E0.0 ; process CR3D 0.4 ; layer 1, Z = 0.200 T0 G1 E-0.6000 F1200 ; if I comment out this line then the error is not there. ; feature skirt ; tool H0.200 W0.440 G1 Z0.200 F600 G1 X19.489 Y53.567 F12600 G1 E0.6000 F1200 G1 X280.511 Y53.567 E8.9768 F1800 ; layer end T0 M98 P"endGcode"
G32 G29 S1 P"heightmap.csv" G1 X5 Y5 Z30 F6000.0 G1 E40 F600 G1 E40 F200 G1 Y20 F2000 G1 Y50 Z0.2 F2000 G1 Y90 E20 F300 G1 Y120 F1200
-
@phaedrux
Is that video better? -
Yes I think so. At what point in the gcode stream does the video start?
It looks like it's just finished homing, or is that it finishing G32?, moves to the corner, purges some filament, then draws a purge line, and moves to start another line across the bed.
What is in M98 P"startGcode" ?
Is it this?
G32 G29 S1 P"heightmap.csv" G1 X5 Y5 Z30 F6000.0 G1 E40 F600 G1 E40 F200 G1 Y20 F2000 G1 Y50 Z0.2 F2000 G1 Y90 E20 F300 G1 Y120 F1200
@heartleander81 said in Isusses after prime:
G28Z
What do you have in homez.g?
-
@phaedrux
Yes that is my startcodeThe video start after finish G32.
After the the Purge line goes X to 110 and from ther Point start the slicing Part with G1 E-0.600 F1200 and on the next move to print Point start ist the issuse.
I think I See at dwc Motor E run to Zero and back without 0.6mm
From E100 to E0 to E99.4; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Aug 26 2020 16:14:58 GMT+0200 (Mitteleuropäische Sommerzeit) ;G91 ; relative positioning ;G1 Z5 F600 ; lift Z relative to current position ;G90 ; G1 X129.4 Y139.4 F3000 ; M401 G30 ; Do a single probe to home our Z axis M402 ;G90 ; Uncomment the following lines to lift Z after probing ;G1 X0 Y0 F6000 ; lift Z relative to current position ;G1 Z5 F600
-
My homez is old. I know i must clean it.
-
By the way, when using a BLtouch you do not need to use M401/M402 explicitly. The G30 commands will deploy and retract as needed.
The only thing I can think of for the extrusion move is that your E speeds may be a bit aggressive?
M566 X1250.00 Y1250.00 Z200.00 E1000.00 ; set maximum instantaneous speed changes (mm/min)
M203 X30000.00 Y30000.00 Z600.00 E16000.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z200.00 E2000.00 ; set accelerations (mm/s^2)
Perhaps F1200 is too much for the extruder? It seems fairly low speed though for retraction, so I'm not sure.
I'm kind of at a loss. Is the problem causing any actual detriments?
-
Any other Propeller use 50-70mm/s retract speed. There is my 20 very slow.
Without filament I can speed the extruder high. With optimal print Temp and filament can I extrude ~20mm/s.
I have this 20mm/s use the last 6-8 month without Problem.
Any time I have step lost on X and Y
-
If you look at this video you can see how the car brakes hard by braking and starting again and then continues jerking, and the belts wobble a lot. Depending on how it vibrates, the motors lose steps and I no longer print in the middle. In the long run, the jerking is not healthy for the whole mechanics
-
But the question is why run the extruder to 0 and back to 99.4 when M83 is Configured?
When I All write to M82 and slice M82 is the same problem. At this one Point reset the firmware not the extruder.
-
That Video is with a another Purge line.
There is with step lost on X and Y. The print must start on the middle on x150 Y150 but is in the left back corner.
-
Have you tested in standalone mode yet without the SBC?
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Running_in_standalone_mode
-
@phaedrux no. I dount have standalone configured
-
As process of elimination it may help to know if the problem still presents in standalone mode.
You can copy your current config files onto a fresh SD card that has the folder structure and DWC files present and use that SD card in the Duet. That link describes in more detail.
-
@Phaedrux
Ok have I do. -
@phaedrux
The same on standalone -
That came after 2 weeks after I have install the toolboard 1lc V1.1
-
Should I reset the toolboard?
By pressing both buttons on the toolboard when starting.
Reload the board firmware and then test it again?
After install the Bus change to 20. -
Thanks for testing in standalone mode. Before you do anything to the toolboard, let's let @dc42 have a look and see what he thinks.