RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
Octoscreen was abandoned a quite a while back.
Change over to OctoDash. It's a big step forward and has current support and development.
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
>Octoscreen was abandoned a quite a while back.
Um, no, it's not. @morphias why did you post this?
Jeff (the developer who IS working on OctoScreen)
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
So any ideas on the extended cable to reach from the rear to the front or can several smaller cables be plugged together?
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
@jeff-15
I apologize and this is news to me. It certainly was abandoned up until the middle of this year, but I see it was handed over from Aleksei to Jeff in late July.
Glad to see the torch has been passed on and good luck with it. 👍
It's a case of "too little, too late" for me. It had a lot of issues with no hope (at the time) of them ever being fixed, so I moved on to OctoDash.
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
Same here. If i remember i’ve had problems with shifting lcd (to the right) and at the time it seems that noone really cared... so i found octodash, which is nicer look, too (but that’s only my personal opinion). What’s really good is that installation is not that complicated as with octoscreen - one file is needed to run, that’s all.
BTW... on octoscreen’s github it still says latest version 25.dec 2019...?
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
@pingu
How did you ruin it? I have mine connected and it works fine.
--------------------
Chuck H
3D Printer Review Blog
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
@raptor72
I think most people plug their GPIO display directly into their Raspberry Pi, and then connect their Raspberry Pi to their printer with a USB cable. What you're looking for might be a speciality cable. You might try DigiKey - they might have one, or you might have to buy some ribbon cable and connection headers. Before you do though, contact the manufacturer of your display. I think (but not positive about this) that displays can typically run only up to a certain length of cable. Measure the length and contact the manufacturer and ask them first before buying a cable (or making one using ribbon wire and female header connectors)
Jeff
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
It's a case of "too little, too late" for me. It had a lot of issues with no hope (at the time) of them ever being fixed, so I moved on to OctoDash.
No worries. Yea, there are a lot of good options out there, like OctoDash, TouchUI, and Big Tree Tech has some displays with an integrated control panel.
Jeff
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
Same here. If i remember i’ve had problems with shifting lcd (to the right)
Yea, that was a problem. The issue is that OctoScreen requires a minimum display of 548 x 348 pixels, but many of the 3.5" displays are only 480 x 320. There's a way to get the screen to scale and get it to work, but there wasn't a good setup guide. I created a step by step guide and posted it to https://github.com/Z-Bolt/OctoScreen/wiki/Installing-OctoScreen-with-a-3.5%22-480x320-TFT-screen, and hopefully this resolves the issue with all those 3.5" 480 x 320 displays. (it works with the 480x320 display that I have, and several others have reported that the instructions work, so we'll see)
Jeff
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
BTW... on octoscreen’s github it still says latest version 25.dec 2019...?
Yea, December 2019 was the last release I think. I started volunteering and working on it sometime in the Summer. It's taken a while but I'm about to release the next version.
Jeff
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
@jeff-15
This may be a sort of dumb question, but, once octoscreen is installed, is there anything necessary to get the touchscreen and graphics to actually work?
I have spent the last several days trying to get this going and it seems to be close, but I just can't find the magic key to get it finally up and running.
Here's the status:
I have installed and re-installed octopi/octoprint several times. Octoprint is working with my MK3S. I have only tested it, but it can do all the usual stuff--heat the bed and nozzle, move the motors, home the machine, etc., so I'm confident this part is in order. (RPi 3B+, by the way)
The display I'm trying to get to work is the UCTRONICS 3.5" LED that runs over the SPI bus, so it connects directly to the GPIO connector on the RPi. The UCTRONICS driver doesn't seem to install properly (tries to load a file that doesn't exist) so I have also tried the waveshare driver.
When I go through the process in your instruction document, it all seems to occur without any errors. And, at the end, the display does, in fact, seem to work except that there is no touchscreen and none of the octoscreen graphics. Rather, it just looks like a terminal with a lot of lines that get printed during startup and then the octopi prompt once everything is up and running. (So, things like the raspi-config change to boot directly is clearly active.)
Although most of my effort has been done without it physically connected to the printer, I have also connected it and tried booting the RPi but got the same exact result--a working display with an octopi prompt. No indication of touchscreen or octoscreen.
Is there some way to check the octoscreen installation to see if something is missing? I'm definitely not a Linux guru, so most of what I do is obviously "cookbooking". However, the systemctl command shows octoprint.service to be loaded, active and running, but shows octoscreen.service to be loaded, inactive and dead. rc.local.service is also loaded, active and running.
I have tried this multiple times, never successfully, and generally all with the same result, so if there is something to try to determine what's wrong, I'd appreciate knowing about it.
RE: 3.5" GPIO Touchscreen+RPI 3B+and Octoscreen
Here's a brief update.
I installed the drivers for the UCTRONICS display and there was no change. However, I then issued the systemctl command to start octoscreen since it shown to be inactive, and, this caused the graphical screen to appear and the touchscreen to be active. I then connected to the printer and restarted, and once again issued the systemcl command to start octoscreen.
It did start, and the touchscreen is active, but, the display is shifted severely to the right. However, this is progress.
And, by the way, the version that is installed is 2.7.0