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

Solved Can't update Printer EPRROM

Discussion in 'Troubleshooting' started by 0ryanx, Sep 22, 2016.

  1. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    New problem. I installed a new E3D V6 hotend, installed the updated firmware, and thought ask was well. The problem it's when i adjust the Z-Step in the EPRROM to calibrate the extruder, it won't stay. I've used Matter Control to try updating it, hit Save to EPRROM, abd it looks good. Next day, it reverts back to stock settings. Repeat the steps, and add the M500 command to force the save. Everything looks good until it's turned off, then reverts to stock. Any ideas on how to make it stay?


    Printer: Robo3D R1+Plus
    Firmware: V2 w/ E3D V6 update
    Slicer: Matter Control & Cura
    Stock Setting: Z-Step 723.38
    Desired setting: Z-Step 765
     
  2. Geof

    Geof Volunteer Moderator
    Staff Member

    Joined:
    Nov 9, 2015
    Messages:
    6,757
    Likes Received:
    2,339
    If it were me id just update and flash the firmware. I personally do not like eeprom for that reason.
     
  3. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    I would, except I'm not sure how to do that; my programming skills are non existant.
     
  4. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    ==== EEPROM GCodes ====

    M500 Store current settings in EEPROM for the next startup or M501.
    M501 Read all parameters from EEPROM. (Or, undo changes.)
    M502 Reset current settings to defaults, as set in Configurations.h. (Follow with M500 to reset the EEPROM too.)
    So after firmware is fixed you need the M502 and an M500 at some point for them to work.
     
  5. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    If you are using the stock firmware writing to EEPROM is not enabled
     
  6. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    I didn't have a problem writing to the EEPROM before the firmware update. Is that a change in the V2 firmware?
     
    #6 0ryanx, Sep 22, 2016
    Last edited: Sep 22, 2016
  7. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    V2 has EEPROM writing enabled, I just checked, Mattercontrol should be using standard gcodes to write settings to EEPROM. That code is M500 just as @mark tomlinson mentioned above. If they are not doing that, then it is a Mattercontrol issue. You can always go to the terminal windows and issue the command yourself.
     
    Geof likes this.
  8. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    What are the commands to do that through the Terminal? I know I can look it up, but I don't want to mess my printer up any more than it already is.
     
  9. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    See post #4 in this thread
     
  10. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    I've tried those in my first post; they still didn't work.
     
  11. Geof

    Geof Volunteer Moderator
    Staff Member

    Joined:
    Nov 9, 2015
    Messages:
    6,757
    Likes Received:
    2,339
    Try downloading cura and try from there. Matter control is an odd bird that things just dont work *normal* in.
     
  12. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
  13. Geof

    Geof Volunteer Moderator
    Staff Member

    Joined:
    Nov 9, 2015
    Messages:
    6,757
    Likes Received:
    2,339
    Many members would suggest not running the r1+v2 firmware. I have been for about 2 months to see what happens but i believe its got some bad code. @WheresWaldo or @danzca6 could possibly elaborate more.
    Anyway the leadscrew firmware is the perferred robo firmware for most.
     
  14. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    Ok, so dumb question: which file is the lead screw firmware? I see the R1+ and the R1 (which says not to use if you have the R1+), or is it gotten from somewhere else?
     
  15. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
  16. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    And that firmware is ok to use on the R1+? I ask only because it warns not to use it on the R1+.
     
  17. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    23,912
    Likes Received:
    7,338
    Because they have the "R1+ Firmware V2"

    but if you want the original R1+ firmware ... that is it.

    The leadscrew update was for R1 users who applied the leadscrew update and basically ended up with an R1+
     
    0ryanx and Geof like this.
  18. 0ryanx

    0ryanx New Member

    Joined:
    Aug 11, 2016
    Messages:
    28
    Likes Received:
    3
    Ah, I see. Thank you. I did a print of the quick-release plate the E3D V6 hotend needs, and it came out pretty nice. Thanks for all the help, everyone!
     
    mark tomlinson likes this.
  19. WheresWaldo

    WheresWaldo Volunteer ( ͠° ͟ʖ ͡°)
    Staff Member

    Joined:
    Feb 18, 2015
    Messages:
    5,905
    Likes Received:
    3,593
    All of the firmwares @Mike Kelly posted in that thread are pretty old and none of them have EEPROM enabled. As I suspected that was the problem to begin with.
     

Share This Page