for slic3r look here
post send to printer

@dc42 does only apply to G32 or also to G29 mesh calibration?

@chanders https://www.thingiverse.com/thing:2469902

Hi
I thought to ask this as a reply on another question but I figured it could be a topic on its own since I see a lot of people that have offset problem etc with auto bed levelling
Just a quick question here: Are auto bed level(G32) and and mesh(G29) independend from each other? I see that M561 clears bed level whilst G29 S2 clears mesh....So can I do a M561 followed by a G32 to bed level using my 2 z motors and after that G29 S2 and G29?
And can these be used independently, i.e. can I clear M561 and only do G32 and keep using G29 S1 to reuse the mesh height map and vise-versa; can I use G29 S2 and measure a new mesh with G29 without clearing the G32 auto bed level for my motors

Another question regarding this : does the bed leveling using independent motors move the motors once and leave them there or is this like mesh compensation something that adjusts z dependend on the hotend position?

In general I think the relation between G32/G30/M561 vs G29 S1/S2 could be explaned better in the wiki. each is explained well in it self but the relation between the 2 is not very clear

Thanks

for cura there was a plug-in
cura print

I added M703 in start.g.so at the beginning of a print all filaments specifics are loaded

Hi
Is tehre a way to stop a marco from running whilst printing .Was 5 hours into a print a pressed by accedent the wrong marco ...and can now start again

Hi
One of the first things on my wishlist would be the actual print time from the last time a certain file was printed in the gcode file list... And a history of all print jobs with accumulated print time and used filament... And ability to reset it.... It is nice for maintenance to know how many hours the print has been running since the last maintenance.....

I also have this error for most of the time when doing it in the console.wil ltry upgrade to 1.22.2 and firmware 2.02beta

OK that is fine then when it is a warning 100C will trigger the fan

Hi
I'm using RRF3.1.1 on Duet2 wifi and have this in my config.g:
M308 S5 Y"drivers" A"Drivers"

But the reading are always 0.0C...it works fine for mcu-temp.....

Have I configured it incorrectly?
Cheers
Alex

was a bit hesitant to upgrade to an RC...but you would say that RC12 is more reliable than 3.0?

Hi
I recently upgraded from RRF 2 to 3 and after the necessary changes every works except when I pause and cancel a print and try to start a new one...I cannot home and the print will not start. I have to power up and down in order to be able to home and then start a new print.
Is there anything that changed in regard to pause and cancel a print?
start.g

G21        ;metric values
G90        ;absolute positioning
M107       ;start with the fan off
G29 S2
M703 ; config filament
G28
M376 H10 ;taper off bed level compensation

M204 P1200 T2000			;Set accelerations (mm/s^2)
G1 X15 Y5 Z5
G1 Z0.2 F3000 ;move the platform down 
G1 F3000
G1 X115 Y5 E10
G1 Z21.75 F3000 ;move the platform down

G29 S1

pause.g

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool on Sat Feb 24 2018 12:46:55 GMT+0100 (Central Europe Standard Time)
M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0

cancel.g
does nothing

stop.g

M104 S0                     ;extruder heater off
M140 S0                     ;heated bed heater off (if you have it)
G91                                    ;relative positioning
G1 E-1 F300                            ;retract the filament a bit before lifting the nozzle, to release some of the pressure
G1 Z+0.5 E-5 X-20 Y-20 F3000 ;move Z up a bit and retract filament even more
G90                         ;absolute positioning
G1 X0 Y0                              ;move X/Y to min endstops, so the head is out of the way

Cheers Alex

excellent!

thanks for the M558 comment..will remove that
But yes placing G31 after M558 helps. I cannot find where that is stated though......

Think I found the reason G31 before M558 seems to ignore the G31 setting. Placing it after M558 did the trick

Ok G31 returns
G31
Current reading 0, threshold 500, trigger height 0.70, offsets X0.0 Y0.0

so that explains..but where is the 0.7 coming from? I don't have it in my config.g or any other file..

If I manually perform this from the console and then home z it works

G31 X0 Y0 Z0 P100
M558 P5 I1 R0.9 F500 X0 Y0 Z0

Hi
I have my Orion quite a while now, but chang from having max z/u endstops to using the probe as z-min.I do this to save time homing.
I have this in my config.g
G31 X0 Y0 Z0 P100
M558 P5 I1 R0.9 F500 X0 Y0 Z0

and homez.g
;homing min using probe
G91 ; relative positioning
G1 S2 Z10 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X145 Y145 F6000 ; go to first probe point
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z10 F100 ; lift Z relative to current position
G90 ; absolute positioning

However after homing it z shows 15.7mm when probing G30 S-1 after homing it always shows 0.7mm..
I don't understand where the 0.7mm comes from
as result my prints start to close to the bed(0.6mm)
What do I do wrong?