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

Upgrade to Marlin 1.1.9 UBL + Extras (Work in progress)

Discussion in 'Projects' started by CdRsKuLL, Oct 20, 2018.

  1. WheresWaldo

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

    Joined:
    Feb 18, 2015
    Messages:
    5,814
    Likes Received:
    3,538
    So, you didn't look at the spoilers in the above message?
     
  2. CdRsKuLL

    CdRsKuLL Member

    Joined:
    Sep 27, 2018
    Messages:
    81
    Likes Received:
    34
    I did, but I couldn't find the updates\roboos_20.sh and the setup.py doesn't exist in my folder, must only be in the package. I've been working off the default image that came with my Robo.

    Thanks,
     
  3. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    21,321
    Likes Received:
    7,032
  4. WheresWaldo

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

    Joined:
    Feb 18, 2015
    Messages:
    5,814
    Likes Received:
    3,538
  5. mark tomlinson

    mark tomlinson ༼ つ ◕_ ◕ ༽つ
    Staff Member

    Joined:
    Feb 21, 2013
    Messages:
    21,321
    Likes Received:
    7,032
  6. CdRsKuLL

    CdRsKuLL Member

    Joined:
    Sep 27, 2018
    Messages:
    81
    Likes Received:
    34
    Morning,

    I'm not currently looking for the update script on Git, I am looking for the code currently on the SD card inside the R2 that holds the URL so it knows where to look on GIT. It was in the update_system folder before it was updated but I can't find where it's currently stored now.

    I did wonder why you kept post git urls when its the procedure that calls this that I'm after, sorry for the confusion.
     
  7. WheresWaldo

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

    Joined:
    Feb 18, 2015
    Messages:
    5,814
    Likes Received:
    3,538
    I believe the current update erases itself, it is in the code somewhere within the update scripts. You can't always look at the final result because you have to make assumptions on how Robo got to the end result. The update routine in roboLCD/lcd calls the updater that then does the work, deletes itself then RoboLCD just rereads the settings to tell you what is now there.
     
    Geof likes this.
  8. WheresWaldo

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

    Joined:
    Feb 18, 2015
    Messages:
    5,814
    Likes Received:
    3,538
    The whole point, you cannot look at the individual parts in a vacuum, they are all moving at the same time. You are looking at the final result and then assuming you know how it was done. It just doesn't work that way.
     
  9. CdRsKuLL

    CdRsKuLL Member

    Joined:
    Sep 27, 2018
    Messages:
    81
    Likes Received:
    34
    I understand what you're saying but somewhere in the current code on my SD card must have 1. Present version number. 2. Link (URL) to check for an update.

    I just need to find it..... I've loaded all the PY scripts and scanned it for an http link but all I'm getting is json_pack = requests.get('http://127.0.0.1:8888/state', timeout=0.5) .. thinking it now might reside somewhere else other than the RoboLCD folder
     
  10. WheresWaldo

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

    Joined:
    Feb 18, 2015
    Messages:
    5,814
    Likes Received:
    3,538
    There are other files Robo writes. Most hidden
    /home/pi/.update.txt
    /home/pi/.octoprint/ssh_marker.txt

    There is a whole directory where everything is controlled from
    /home/pi/.octoprint/data/RoboLCD

    This is the entire reason I sent you to the GITHUB and Amazon repositories, you would see where stuff goes, but working from the final result to the beginning is much harder. You know the saying, 'Give a man a fish or teach a man to fish....'
     
  11. CdRsKuLL

    CdRsKuLL Member

    Joined:
    Sep 27, 2018
    Messages:
    81
    Likes Received:
    34
    Waldo.... You legend! :)

    So, I had a look in those suggested folders and you were spot on :)

    The file that holds the current installed version is in /home/pi/.octoprint/data/RoboLCD/roboOS.txt

    To test, I edited it to..
    1.0.0-r2.6 and went to the update screen at got this..
    [​IMG]

    Then I edited it to..
    4.0.0-r2.6 and it said I was all up to date.
    [​IMG]

    So, by simply changing this txt file will stop the R2 running the update I hope.

    Sorry for the late reply, works getting in the way of fun sadly.

    Thanks again,

    Steve
     

Share This Page