g32 reporting

tracar

is it normal for the Duet2 wifi to report this more than 1 time when only one G32 is done ?

9/29/2020, 9:00:27 PM M98 P"0:/macros/BLTouch/G32 to level bed"
Leadscrew adjustments made: 0.079 0.082, points used 2, (mean, deviation) before (0.080, 0.001) after (0.000, 0.000)
9/29/2020, 9:00:27 PM M98 P"0:/macros/BLTouch/G32 to level bed"
Leadscrew adjustments made: 0.079 0.082, points used 2, (mean, deviation) before (0.080, 0.001) after (0.000, 0.000)
9/29/2020, 9:00:27 PM M98 P"0:/macros/BLTouch/G32 to level bed"
Leadscrew adjustments made: 0.079 0.082, points used 2, (mean, deviation) before (0.080, 0.001) after (0.000, 0.000)

Phaedrux

What firmware version are you running?
How did you initiate the g32?
Where is the report showing up multiple times?

tracar

@Phaedrux

3.1.1
g32 was initiated ftom the web interface terminal
in the console

What firmware version are you running?
How did you initiate the g32?
Where is the report showing

fcwilt

Hi,

Could you post your bed.g file?

Thanks.

Frederick

tracar

@fcwilt

; bed.g
; called to perform automatic bed compensation via G32
;
M400 ; Finishes all current moves and clears the buffer
G4 S1 ; wait 1 second
M280 P0 S160 I1 ; Alarm Release and Push-Pin UP
G4 S1 ; wait 1 second
M402 ; Retract probe just in case it's down
M400 ; Finishes all current moves and clears the buffer
M561 ; clear all bed compensation
G28 ; home all axis
G90 ; absolute positioning
G30 P0 X440 Y291.5 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X0 Y291.5 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
G1 X220 Y318 F8000 Z10 F800 ; move probe to center of the bed
G30 ; set Z0 position with the probe
M402 ; retract probe

; uncomment as needed to probe a height map after an auto bed level OR not and use an old map
;G29 S0 ; Probes and makes a new probed height map
;G29 S1 ; loads a previously saved height map

fcwilt

@tracar said in g32 reporting:

; bed.g
;
> M400 ; Finishes all current moves and clears the buffer
G4 S1 ; wait 1 second
M280 P0 S160 I1 ; Alarm Release and Push-Pin UP
G4 S1 ; wait 1 second
M402 ; Retract probe just in case it's down
M400 ; Finishes all current moves and clears the buffer
M561 ; clear all bed compensation
G28 ; home all axis
G90 ; absolute positioning
G30 P0 X440 Y291.5 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X0 Y291.5 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
G1 X220 Y318 F8000 Z10 F800 ; move probe to center of the bed
G30 ; set Z0 position with the probe
> M402 ; retract probe

JOOC why did you include the commands in bold? I have nothing like them and everything seems to work.

Thanks.

Frederick

tracar

console posts.png

here is the problem:

i mean to say when i do a bed level ( only once ) i get many reports back at the same time.

Phaedrux

The macro you're running in your screenshot is not bed.g

tracar

@Phaedrux said in g32 reporting:

The macro you're running in your screenshot is not bed.g

it was a G32 from a macro containing only this:
G32 ; level bed

the above screen shot is what the duet posts back, it is not all the time, like every tenth g32..

Phaedrux

Alright, so to recap, occasionally running G32 will output the results multiple times to the console and the DWC popup.

Do you happen to have any leveling code in your homeall? Just asking because it gets called in bed.g

tracar

@Phaedrux said in g32 reporting:

homeall

No leveling code in Homeall..

you answered it, if it occasionally does this then all is ok.

thanks for the reply

Phaedrux

I wonder if it's a firefox thing. Is that windows 7?

tracar

@Phaedrux said in g32 reporting:

r if it's a firefox thing. Is

yes win7