1. Got a question or need help troubleshooting? Post to the troubleshooting forum or Search the forums!

G36 Failure

Discussion in 'Troubleshooting' started by Colin, Dec 5, 2024.

Thread Status:
Not open for further replies.
  1. Colin

    Colin New Member

    Joined:
    Aug 5, 2013
    Messages:
    2
    Likes Received:
    1
    Long time lurker, first time poster. I've printed hundreds of items with my RoboR2 and been extremely happy with it overall, but this one has me scratching my head and I need help.

    I have had 2 recent (as of Monday) successful prints, the last one taking up the whole print bed, and I may have been a bit violent taking the print off (I don't know why this would cause the issue, but putting it in here for posterity). After this, each print I have tried has failed during startup, and I have traced it to the G36 command. When issued, it drives the z-axis down instead of up for some reason! Since it is at its home position, the motor stalls as it is driven into the printer base, and then the gantry performs its normal routine as if the bed is actually near it, but this inputs very bad offset data into the printer and I've had to power cycle the printer to stop it from grinding the print head against the base after the G1 Z15 command is issued. Commenting out the G36 command through Octoprint resolves this issue, but I will need to be a lot more careful on my manual bed leveling, and I like to be lazy, personally. Any ideas what could have caused this issue? Or how I can resolve it?

    Firmware: Marlin_1.1.6_RoboVersion_1.2.4
    Software: RoboOS 2.0.0-r2.6
     
  2. Lance Weston

    Lance Weston Active Member

    Joined:
    Jun 2, 2018
    Messages:
    686
    Likes Received:
    236
    Check the cable to to the ir board
     
  3. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    24,018
    Likes Received:
    7,347
    Make sure the z offset is a negative value in the EEPROM.
    That is what usually did it on my C2 -- they changed the firmware a bit in one release and it tended to NOT make the LCD value a negative value (and it must be -- it is the relative position of the nozzle to the bed and negative means "above" the bed)
     
  4. Colin

    Colin New Member

    Joined:
    Aug 5, 2013
    Messages:
    2
    Likes Received:
    1
    Hey Everyone, thanks for your patience with me, and thanks for the support! And I'm happy to report that the advice here solved my issue!

    Mark, I checked the EEPROM and can verify that it is negative.
    Lance, I admit, I was a bit skeptical at first that this could be the issue, but sure enough, the cable was completely disconnected on the IR board at the gantry. Plugging this back in completely resolved the issue. That is definitely a weird one, but thank you very much for the pointer!
     
    mark tomlinson likes this.
Thread Status:
Not open for further replies.

Share This Page