Error: bad Command XXX W/RRF 3.2 and leveling issue
-
@3DPrintingWorld said in Error: bad Command XXX W/RRF 3.2 and leveling issue:
M92 X100.00 U100.00 Y100.00:100.00 Z1096:1096:1096 E415.00:655.00
z does not allow for more than one value
remove them from M566 M92 M203 M201 and M906
what i did for the bed leveling to see if the adjustments were correct is look at the heightmap before and after a g32.
-
Anyway, the manual says it will take the first one, so no problem. Also as stated it was working fine before the firmware update.
What G32 has to do with the heightmap, that is made with g29 probing. G32 just levels the bed on 3 pointsMuldex IDEX Duet2+Duex5
Custom CoreXY 600x400 Hemera , Duet3
Sapphire Pro with Duet2 , with closed-loop motors
voron v0.1,2.4 ,cr10s all running klipper; stock Bambu X1CC, X1C and P1P,A1,A1 mini
custom high temp E3D toolchanger with Duet2+Duex -
@3DPrintingWorld said in Error: bad Command XXX W/RRF 3.2 and leveling issue:
Also as stated it was working fine before the firmware update.
I have no idea if this is related but it might be.
On my 3 Z stepper printer each Z stepper has it's own end stop sensor. The Z steppers are on the Duex 5 board.
I home Z using the end stop sensors which have been carefully adjusted to result in the bed being very nearly level.
I then use G32 to perform the final bed leveling.
Under 3.1.1 everything worked fine for months and months of use. I recently upgraded to 3.2.0.
Under 3.2.0 Z homing frequently failed as one of the Z steppers would fail to stop when it's end stop sensor was triggered.
Since I could not rely on the Z homing I never moved on to the next step of using G32 so I cannot say if that would have worked or not.
Frederick
-
@martin7404 said in Error: bad Command XXX W/RRF 3.2 and leveling issue:
Anyway, the manual says it will take the first one, so no problem.
I'll take them out to neaten it up anyways.
Agreed, the height map should not have anything to do with it. Right now the height map is cleared and I'm just trying to get the bed level to the nozzle.
-
I played a little with G32 . Strange
After initial tramming twice with G32
Here is 5 more made one after other2/8/2021, 12:50:52 PM g32 Leadscrew adjustments made: 0.007 -0.004 -0.028, points used 3, (mean, deviation) before (-0.008, 0.010) after (-0.000, 0.000) 2/8/2021, 12:36:06 PM G32 bed probe heights: 0.003 -0.006 -0.020, mean -0.008, deviation from mean 0.009 2/8/2021, 12:35:43 PM g32 Leadscrew adjustments made: -0.000 -0.007 0.017, points used 3, (mean, deviation) before (0.003, 0.008) after (-0.000, 0.000) 2/8/2021, 12:32:41 PM G32 bed probe heights: 0.008 -0.006 0.013, mean 0.005, deviation from mean 0.008 2/8/2021, 12:32:18 PM g32 Leadscrew adjustments made: -0.008 -0.007 0.018, points used 3, (mean, deviation) before (0.000, 0.009) after (0.000, 0.000) 2/8/2021, 12:31:32 PM G32 bed probe heights: 0.009 -0.006 0.014, mean 0.005, deviation from mean 0.008 2/8/2021, 12:31:09 PM g32 Leadscrew adjustments made: 0.092 -0.021 -0.039, points used 3, (mean, deviation) before (0.018, 0.044) after (-0.000, 0.000) 2/8/2021, 12:29:59 PM G32 bed probe heights: 0.060 -0.013 -0.019, mean 0.010, deviation from mean 0.036 2/8/2021, 12:29:36 PM g32 Leadscrew adjustments made: -0.110 -0.019 0.009, points used 3, (mean, deviation) before (-0.046, 0.038) after (0.000, 0.000) -
post a picture of the mesh bed leveling
-
-
So I roll back to 3.1.1 and the heatmap is consistent, the tramming is working kind of. the deviation can be due to magnetic mat + steel sheet
-
@martin7404 said in Error: bad Command XXX W/RRF 3.2 and leveling issue:
So I roll back to 3.1.1
Surprised that made a difference, it didn't do anything for me when I reverted.
The leveling seems very consistent, just not level. I'm gong to try putting incorrect locations into the M671 to see if I can trick it into leveling properly. The front right corner is high so I'm going to move that point out further in the X until the bed is level. If I adjust just this motor by hand it seems to fall into level so it should work.
-
The two front motors are aligned in the X axis so I physically swapped motors, and switched the rotation direction in the config so they run in the correct direction. Now when it corrects for level it should be backwards, but it levels it exactly the same! Left back corner low, right front corner high.
I also moved the front right motor location in the M671 over as much as 350mm, but it has no effect and levels exactly the same! Left back corner low, right front corner high.
How can making these changes have no effect on level? The results should be all jacked up but nothing I do seems to have any effect on the outcome. At the same time, I don't understand how its correcting to the same bad plan every time even though I've giving it bad information.
-
@3DPrintingWorld said in Error: bad Command XXX W/RRF 3.2 and leveling issue:
I don't understand how its correcting to the same bad plan every time even though I've giving it bad information.
Are the files you are editing the actual files being used? Occasionally someone will edit a macro file in the macros folder without realizing the file they should be editing is actually in the sys folder. Could it be something like that happening here?
-
@Phaedrux Ha, you got to give me more credit then that. Yes, I'm modifying the config file in my systems folder. I know because I also swapped the left and right stepper motors and if I don't update the directions in the config one of the motors will be rotating in the wrong direction. Speaking that, like it says here. When I swap the X motors it should be leveling the opposite but I swapped the motors but its still identically off level.
-
I had to ask. It happens sometimes.
-
Is its possible that the firmware is corrupt? I tried reverting to 3.1 but it did not fix any of the issues. Is there a way to remove it and do a fresh install?
-
I manually adjusted the bed so it was out of level and I swapped a front motor with the back motor. It still levels at the same off level point? No matter what I do changes nothing, It makes no sense.
-
Can you report your current file set?
Also the results of M98 P"config.g"? -
-
@Phaedrux said in Error: bad Command XXX W/RRF 3.2 and leveling issue:
Can you report your current file set?
I'm not sure I understand, can you explain?
-
Sorry, meant to type repost. As in, upload your current files so we can see what's up.
-
@Phaedrux said in Error: bad Command XXX W/RRF 3.2 and leveling issue:
current files
Not sure what you mean "current files", I've already been asked to post config.g and bed.g. I would think the only other one that would pertain would be homeall.g.
; homeall.g ; X,U,Y Homing T0 P0 G91 ; relative positioning G1 H2 Z5 F2000 ; lift Z relative to current position G1 H1 X-475 U475 F7500 ;Rough home X and U axis G1 H1 X-475 ; home X axis G1 H1 U475 ; home U axis G1 H2 X5 U-5 F7500 ; go back a few mm G1 H1 Y500 F6000 ; move quickly to Y axis endstop and stop there (first pass) G1 Y-5 F6000 ; go back a few mm M584 Y1 ; Y-axis right side M574 Y2 S1 P"ystop" ; Y-axis right side endstop Active G1 H1 Y15 F360 ; move slowly to Y axis endstop once more (second pass) M584 Y2 ; Y-axis Left side M574 Y2 S1 P"zstop" ; Y-axis left side endstop Active G1 H1 Y15 F360 ; move slowly to Y axis endstop once more (second pass) M584 Y1:2 ; Combine Y-Axis M574 Y2 S1 P"ystop+zstop" ; Y Double max active high endstop switch G1 Y-5 F6000 ; go back a few mm G1 H1 X-25 F360 ; move slowly to X axis(second pass) G1 H1 U25 ; move slowly to U axis(second pass) G1 H2 X2 U-2 F7500 ; go back a few mm ; Z Homing T0 P0 G90 G1 X219 Y150 F6000 ; Move to the center of the bed M558 F500 ; Fast probing speed G30 ; First probe M558 F50 ; Slow probing speed G30 ; Second probe G32 ; Level the bed G90 G1 X219 Y150 F7500 ; Move to the center of the bed G30 ; Bed Deviation probe G90 G1 X-16 ; Park x-axis
