G33 RO. FOUND??

---> G33 L0

20:27:00.318 : G33 X10.00 Y10.00 Z0.000
20:27:00.318 : G33 X10.00 Y354.98 Z0.000
20:27:00.318 : G33 X10.00 Y699.97 Z0.000
20:27:00.318 : G33 X354.98 Y10.00 Z0.000
20:27:00.333 : G33 X354.98 Y354.98 Z0.000
20:27:00.333 : G33 X354.98 Y699.97 Z0.000
20:27:00.333 : G33 X699.97 Y10.00 Z0.000
20:27:00.333 : G33 X699.97 Y354.98 Z0.000
20:27:00.333 : G33 X699.97 Y699.97 Z0.000

---> G33 RO  

20:28:29.316 : Info:Resetting Z correction
---> G33 L0
20:29:53.338 : G33 X10.00 Y10.00 Z0.000
20:29:53.338 : G33 X10.00 Y354.98 Z0.000
20:29:53.338 : G33 X10.00 Y699.97 Z0.000
20:29:53.338 : G33 X354.98 Y10.00 Z0.000
20:29:53.353 : G33 X354.98 Y354.98 Z0.000
20:29:53.353 : G33 X354.98 Y699.97 Z0.000
20:29:53.353 : G33 X699.97 Y10.00 Z0.000
20:29:53.353 : G33 X699.97 Y354.98 Z0.000
20:29:53.353 : G33 X699.97 Y699.97 Z0.000

ALL CORRECTIONS TO 0 ?????NOOOOOOO

Comments

  • PRINTER CARTESIAN./bl touch
    tools BED HEIGHT MAP
    steps:
    1) G1 Z10
    NO MENSURE
    2) BOTON: MENSURE HEIGHT
    3) BOTON COPY PASTE:
    4) G33: CORRECTION
    1) G1 Z10

    CORRECTION MENSURE
    2) BOTON: MENSURE HEIGHT

    ???,
    IT'S OKAY
    ?

  • Z-OFFSET,
    HOW ARE THE STEPS FOR A SMALL SPACE BETWEEN THE BED AND THE EXTRUSER, TO BE ABLE TO PRINT?

  • z-probe measured THE REFERENCE  ??

  • #include

    void setup() {
    // initialize the LED pin as an output.
    pinMode(13, OUTPUT);

    /***
    Iterate through each byte of the EEPROM storage.

    Larger AVR processors have larger EEPROM sizes, E.g:
    - Arduno Duemilanove: 512b EEPROM storage.
    - Arduino Uno: 1kb EEPROM storage.
    - Arduino Mega: 4kb EEPROM storage.

    Rather than hard-coding the length, you should use the pre-provided length function.
    This will make your code portable to all AVR processors.
    ***/

    for (int i = 0 ; i < EEPROM.length() ; i++) {
    EEPROM.write(i, 0);
    }

    // turn the LED on when we're done
    digitalWrite(13, HIGH);
    }

    void loop() {
    /** Empty loop. **/
    }

    I have tried this code to erase the memory .... and what happened? , everything remains the same. I do not understand Anything. it keeps appearing the same values of the matrix
  • Sorry, but all your description are so confusing that I do not even see what you are doing and what your problem is.

    It is G33 R0 btw, not RO. Always use digits after the first letter in gcode. This is supposed to set all G33 corrections to 0, so why so surprised it does. Deleting eeprom also does not give you these back, how should it? Just call G33 after G32 S2 to get them back.
  • SORRY, ..NO found.. 


    13:51:04.409 : Info:Resetting Z correction   >>> G33 R0
    13:51:09.962 : Info:Resetting Z correction   <<< G33 RO
    13:51:14.611 : Info:Resetting Z correction    <<<G33 R

    G33 L0  >><<  G33 L  
    13:51:25.531 : G33 X10.00 Y10.00 Z0.000
    13:51:25.531 : G33 X10.00 Y329.98 Z0.000
    13:51:25.531 : G33 X10.00 Y649.97 Z0.000
    13:51:25.547 : G33 X329.98 Y10.00 Z0.000
    13:51:25.547 : G33 X329.98 Y329.98 Z0.000
    13:51:25.547 : G33 X329.98 Y649.97 Z0.000
    13:51:25.547 : G33 X649.97 Y10.00 Z0.000
    13:51:25.547 : G33 X649.97 Y329.98 Z0.000
    13:51:25.547 : G33 X649.97 Y649.97 Z0.000





  • AH, I BELIEVE THAT I UNDERSTOOD. IT ONLY PUTS THE CORRECTION TO ZERO AND NOT TO THE VERIFICATION POINTS

  • G33 L0 outputs the grid you measured and contains the corrections against the "normal" zero point without g33. So if it is set correctly it should swing around 0 with z values.
Sign In or Register to comment.