I cannot make this work :-(

dank0

gixxerfast what do you mean by this? "but when do you do the run G32 QGL" . you are asking when i am calibrating the bed?

also to be honest i believe that my configs are not correct/sloppy, that is why i am asking you guys who knows duet boards well. I am learning.

I got tired of the coarse surface and i turned the PEI surface to the other side, and it prints ok( still not great quality), i need to figure out the pressure advance settings. But i will be definitely buying new bed.

Also one thing is still question for me. I tried Cura and Simplify3D for slicing with Reprap gcode flavour and it prints slow, how do you guys setting the speed of your prints?

fcwilt

@dank0 said in I cannot make this work :

bed.g G30 are 4 points, repeated 3 times each.

Since you seem to be using firmware 3.3 you can make use of it's features to avoid duplicating those sets of 4 points and always running 3 leveling passes even if they are not needed.

Now the points in the G30s below are for my printer by the approach works for any printer just by changing the points.

What it does is run a pass (4 points in this example) and check the results. If the results are not within the specified range (0.02 in this example) it runs another pass. It will run up to 5 passes trying to get the result within the specified range. On my printer it most always finishes in 2 passes.

Just FYI.

while true
  ; run leveling pass

  G30 P0 X-140 Y-90 Z-99999    ; LF
  G30 P1 X-140 Y90  Z-99999    ; LR
  G30 P2 X140  Y90  Z-99999    ; RR
  G30 P2 X140  Y-90 Z-99999 S3 ; RF 

  ; check results - exit loop if results are good

  if move.calibration.initial.deviation < 0.02
    break

  ; check pass limit - abort if pass limit reached

  if iterations = 5
    M291 P"Bed Leveling Aborted" R"Pass Limit Reached"
    abort "Bed Leveling Aborted - Pass Limit Reached"

dank0

@fcwilt Thanks for the bed.g example - it works nicely

fcwilt

@dank0 said in I cannot make this work :

@fcwilt Thanks for the bed.g example - it works nicely

Glad to hear that is worked.

Frederick

Gixxerfast

@dank0 Sorry, I don't mean that your config is sloppy. I mean that I read them not thorugh enough.

No, what I am asking is when are you doing bed leveling -> G32 which uses the bed.g macro and when do you do a bed mesh G29 that uses the mesh.g macro. To me, I could be wrong here, it seems like those are mixed in your config.

On the Voron 2.4 the routine is always (very roughly) G28, G32, G28 (G28 Z)and sometimes a G29 depending on how large the print is. That converts into macros as homeall.g, bed.g homeall.g (maybe homez.g) and then maybe a mesh.g.

Anyone who knows anything different may please correct me

dank0

Hey guys, thanks for the help - I am finally printing

I have one more thing that bothers me. CURA
it prints the first 4 bottom and top 4 layers (solid ones) in proper speed, but areas where is just walls and infill are terrible slow. all my speeds in the Cura are set way higher, but the print is slow. Maybe someone had same issue before and know the solution. I also tried Simplify3D with same results.

My G-code flavor is Reprap
My Cura start code is

M140 S50
M190 S50
M116
G28
M400
T0 ; Select the tool
G29 S1 ; Load Mesh coordinates
M82 ; Absolute extrusion mode
M140 S{material_bed_temperature_layer_0}  ;Start heating bed
M190 S{material_bed_temperature_layer_0}  ;Wait for bed to reach temp before proceeding
M104 S{material_print_temperature_layer_0} ;Start heating extruder
M109 S{material_print_temperature_layer_0} ;Wait for extruder to reach temp before proceeding
M98 P/sys/start_print.g

thanks for your time

T3P3Tony

@dank0 check the feed rates in the gcode file for infil and walls in a normal layer - are the feedrates what you expect (e.g. F3600 = 60mm/s). If the top and bottom layers are printed as expected.

From the config.g you set above your maximum speeds are set to 500mm/s, are the travel moves on those layers slow or just the print moves?

dank0

@t3p3tony oh, so if i want the speed 100mm/s it must be 6000 in cura to translate for reprap correctly?

T3P3Tony

@dank0 no i think cura takes mm/s in the configuration box, but then changes it to F6000 in the gcode - you can check that in the print file.

dank0

@t3p3tony ah, ok i got it, thanks