Trying to unattach OctoPrint from Robo repository, have issues.

I need to find someone who has more GITHUB knowledge than I do. I tried the following commands

Code:

cd Octoprint
git remote -v
git remote set-url origin https://github.com/foosel/OctoPrint.git
git pull
git reset --hard origin/master

After this I tried to do a clean and reinstall but it didn't actually update the local files.

Code:

python setup.py clean
python setup.py install

There must be something simple I am overlooking, but I can't seem to find what it is. My previous efforts at trying to build a slim version of RoboOS was thwarted as the LCD setup forces changes to OctoPrint and resets the git origin back to the Robo default. Since Robo is not really keeping up to date on any of the software if there was a way to detach these two parts we could keep OctoPrint current with whatever bug fixes and new features their community is developing.

 

Change the origin and forget about all the changes Robo made. Want to switch completely to official OctoPrint, not Robo's version without having to reinstall everything.

 

@sgomes The git log command does show that I am now linked to Gina's original source but now I am thinking that OctoPrint is installed in ~/oprint and not in ~/Octoprint. But ~/oprint is not a GIT clone. The whole image is a mess, nothing uses default directory structures, repositories are forked for no apparent reason. Not every repository is owned by Robo3D on GITHUB. It is very hard to keep track of what is current and what is just messing around with the code.

 

The problem is that RoboLCD messes up the whole install. they do too much in that setup. And I haven't yet figured out how they did the custom startup screen. Linux used to use Plymouth, but I am pretty sure it has been deprecated. I do have an image with everything loaded, OctoPrint, all the plugins, minus robotheme, kaa_printerevent and Lani. OctoPrint is even installed in a virtual environment as Gina recommends. As soon as you install the LCD python files the image is borked!

And there is a lot of stuff that is just version specific in the LCD code. I am running with Marlin 1.1.5 w/MESH and now I can't use the Offset Wizard as it just hangs after homing. The temperature readout for the hotend is not anchored to the bottom left corner of the screen properly, I don't know what else is broken.

 

It is not all doom and gloom. If you saw the original work on the RoboOS interface (before Robo forked the project) it is pretty spartan and it doesn't even look complete, so they did a lot of work on it that the original author hasn't done. But why fork Firmware Updater is you aren't going to improve it. All they did was detach it from any updates or feature improvements. The theme was forked from Voxel8, others from other locations. They did create the Alexis Plugin as far as I can tell. My image had all the OctoPrint plugins pointing back to the original authors, everything worked, then I installed the LCD files, everything is now broken. Based on my experience with their Marlin fork, I can't even trust the code to run on the printer in its current form.

The whole RoboOS whose concept I think is pretty innovative and good, needs a complete rewrite and streamlining.

 

This next statement will likely rile up a few here, but my opinion is this is what you get when you allow programmers to run a software project. It's a mess of code that exists just because a programmer thinks they can pull it off.

 

I don't disagree with any of your statements @Kilrah, but if you use OSS and actually improve or fix something you should at the very least offer it to the upstream developer(s) to include or not. That also is not happening. My biggest issue is forcing the dependencies and the haphazard way all the parts were assembled, that is the basic underlying root of my issues with RoboOS. I even mentioned this to Braydon, if you take, you should have some moral/ethical obligation to give back.

And I have said all along, even before you arrived on the scene, that this was designed as an appliance and marketed as an appliance, even though the tech isn't quite there yet.

 

He gets it.

 

They don't get it