My default theme from OctoBTT unfortunately is white text on white background. This is not readable and makes no sense. I try to change it somewhere in the configuration, but have no success. Also the Octodash plugin for Octoprint does not work together with OctoBTT. Do you have an idea, how to change the theme?

It appears that instead of keeping the users existing config, you guys back it up, and copy a new one in place of it. This can be bad for someone that has spent days getting their OctoPrint install setup and dialed in to how they want it. Instead, you guys should be adding the required lines to the config, if any that are needed to enable OctoBTT to work.

You can use this command to get additional info on how to set configs via CLI.

~/oprint/bin/octoprint config --help

And here is some info on what is in the config.yaml file.

https://docs.octoprint.org/en/master/configuration/config_yaml.html

When there will be a new version to Octopi 0.18?

I'm a newb when it comes to programming/coding, but i had a look at the c++ code and noticed that the word "BAN" related to something to do with the Filament...But the word does not make sense in this context. looking further it looks like its the connection / printer status.

can we get a more appropriate label for the status rather than the word "BAN"?

Thanks

I have used OctoBTT for about a month, and have just migrated my Ender with BTT Mini E3 1.2 from Marlin to Klipper. When OctoBTT is active, OctoPrint is unable to connect to Klipper's virtual printer /tmp/printer. Octoprint seems to be forced to connect to /dev/tty/ACM0. I have changed the Octoprint setting for the default printer to /tmp/printer, but this is ignored.

When I kill OctoBTT, Octoprint can immediately connect to /tmp/printer.

I disabled the autostart of OctoBTT, and Klipper is now running fine with Octoprint.

I recently received the PI TFT50. when i connect my Raspberry PI 4 to the screen I am unable to connect to any WIFI connections. if i unplug it from the screen, no problem connecting to my network. I have went through all the resolution settings on PI to see if that would help. no luck. do you have any suggestions on how to fix this issue?

Why don't you get support? I already have the second display of the company btt which cannot be started. Then I have another tft35 which does not boot because of a bootloader bug. And one of my skr 1.4 turbo is also defective. If neither detected on the PC nor can it read sd cards. I think it's a naughty thing that you paid this company over 200€ for hardware that doesn't work! You should be sued!

when I connect the screen the wifi does not connect to the network
if I turn off the screen wifi works

Hi!

I wonder if BTT is going to release the schematics for the PCB of PITFT50 and the source code for the onboard STM32.
That would help a lot in reprogramming it for custom application.

I just got my screen yesterday, and all day, I've been trying to get this wifi on both of my raspberry Pi 3B+ and 4B 2GB working with the screen attached. Whenever the screen is plugged in, the wifi just stops working entirely. I have reflashed the pis multiple times, only ever getting them to connect once before the issue came back again. This is really frustrating

--Update--
Just discovered that the screen itself is causing interference with the wifi antenna when mounted like so

Clearly a major design flaw.. this seriously needs to be fixed because I ended up buying another pi thinking my original one had something defective on it

As it is this will not work with an Artillery Sidewinder X1 or any other printer with a 250000 baud rate. This really needs to be a configuration option at install.

To fix:
change:
mainwindow.cpp: _ConnectJson.insert("baudrate",115200);
to this:
mainwindow.cpp: _ConnectJson.insert("baudrate",250000);
do a make clean; make; qmake OctoBTT.pro;

Please remove all OctoDash assets from this repository (like https://github.com/bigtreetech/OctoBTT/blob/master/assets/icon/icon-alt.svg). Since you haven't kept the original LICENSE you are not allowed to use them within your "inspired by OctoDash" program.

I would also advise you to remove the other icons you copied as well, since you also need to mention the auther / origin of them as indicated by their license from thenounproject.

@bigtreetech You guys could've just contacted me and we could've worked something out so you could use OctoDash with custom branding and stuff - I'm still happy to talk to you guys about that, so just let me know. But please do remove the copied assets, which you don't have a license for.

There is no deinstallation script. As workaround I have to backup Octoprint, make a new install and restore from the backup file. a simple deinstallation script would be better.

OctoBTT doesn't appear to support PSU Control plugin, thus the web interface must be used to start the 3D printer.

My Raspberry Pi 3A+ randomly reboots multiple times while trying to install OctoBTT.
After first reboot I waited almost 1.5 hours, but nothing happened. It just crashed. Second till fifth reboot same, but waited shorter. Last reboot it was almost at 90%, but then reboot and could start on.
Power Supply is standard 5V/2.5A, so, nothing wrong there.
Video of the steps I took to get here:
OctoBTT.zip

When pressing the camera icon opens a blank page .can see camera output on web page of Octoprint. Any help

Hi,

Is there a way to configure the screen to turn off itself after 30 minutes of inactivity? If not, it will be a great feature to have inside OctoBTT, it will save the life of the screen. I don't think a screen open 24/7 will have a long life.

Thank you

octobtt high cpu usage in idle. around 40% in idle

My issue is as per the image attached. Prior tohis i see white screen, then the color pallete, then the console print out s, and then boots to this with a small cursor on top left it seems. I followed instructions, saw no issues where can i look to troubleshoot the issue? Bjust got my v 1 BTT PITFT50

Okei image didnt play ball just imagine a black screen with this in the top left corner: _

most of the icon svg files are now missing causing install.sh to fail

Wifi doesnt work via file with google mesh. If i goto the config menu in the gui i see nothing and it freezes. Cannot exit wifi menu

I tried to install, it fails with complaints about missing files for assets/icon/BingoTouch_Logo_B.svg and assets/icon/BingoTouch_Logo_H.svg, which I cannot find in the repo (even in older versions). Was this perhaps something a developer was tinkering with and forgot to check in?

--
Download OctoBTT ...
Cloning into 'OctoBTT'...
remote: Enumerating objects: 724, done.
remote: Counting objects: 100% (348/348), done.
remote: Compressing objects: 100% (263/263), done.
remote: Total 724 (delta 162), reused 222 (delta 82), pack-reused 376
Receiving objects: 100% (724/724), 10.97 MiB | 2.28 MiB/s, done.
Resolving deltas: 100% (299/299), done.
Done.
Installing OctoBTT ...
Info: creating stash file /home/pi/OctoBTT/.qmake.stash
RCC: Error in 'assets.qrc': Cannot find file 'assets/icon/BingoTouch_Logo_B.svg'
RCC: Error in 'assets.qrc': Cannot find file 'assets/icon/BingoTouch_Logo_H.svg'
rm: cannot remove 'OctoBTT': No such file or directory
rm -f qrc_assets.cpp
rm -f moc_predefs.h
rm -f moc_accesscontrol.cpp moc_cameradialog.cpp moc_configuration.cpp moc_controlpanel.cpp moc_customdialog.cpp moc_filedialog.cpp moc_gcodedialog.cpp moc_inputdialog.cpp moc_mainwindow.cpp moc_materialctrlpanel.cpp moc_terminaldialog.cpp moc_wlanconfig.cpp
rm -f ui_cameradialog.h ui_configuration.h ui_controlpanel.h ui_filedialog.h ui_gcodedialog.h ui_inputdialog.h ui_mainwindow.h ui_materialctrlpanel.h ui_terminaldialog.h ui_wlanconfig.h
rm -f accesscontrol.o cameradialog.o configuration.o controlpanel.o customdialog.o filedialog.o gcodedialog.o inputdialog.o liblog.o main.o mainwindow.o materialctrlpanel.o mylineedit.o octonetwork.o terminaldialog.o wlanconfig.o qrc_assets.o moc_accesscontrol.o moc_cameradialog.o moc_configuration.o moc_controlpanel.o moc_customdialog.o moc_filedialog.o moc_gcodedialog.o moc_inputdialog.o moc_mainwindow.o moc_materialctrlpanel.o moc_terminaldialog.o moc_wlanconfig.o
rm -f *~ core *.core
/usr/lib/qt5/bin/uic cameradialog.ui -o ui_cameradialog.h
/usr/lib/qt5/bin/uic configuration.ui -o ui_configuration.h
/usr/lib/qt5/bin/uic controlpanel.ui -o ui_controlpanel.h
/usr/lib/qt5/bin/uic filedialog.ui -o ui_filedialog.h
/usr/lib/qt5/bin/uic gcodedialog.ui -o ui_gcodedialog.h
/usr/lib/qt5/bin/uic inputdialog.ui -o ui_inputdialog.h
/usr/lib/qt5/bin/uic mainwindow.ui -o ui_mainwindow.h
/usr/lib/qt5/bin/uic materialctrlpanel.ui -o ui_materialctrlpanel.h
/usr/lib/qt5/bin/uic terminaldialog.ui -o ui_terminaldialog.h
/usr/lib/qt5/bin/uic wlanconfig.ui -o ui_wlanconfig.h
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o accesscontrol.o accesscontrol.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o cameradialog.o cameradialog.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o configuration.o configuration.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o controlpanel.o controlpanel.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o customdialog.o customdialog.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o filedialog.o filedialog.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o gcodedialog.o gcodedialog.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o inputdialog.o inputdialog.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o liblog.o liblog.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o main.o main.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o mainwindow.o mainwindow.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o materialctrlpanel.o materialctrlpanel.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o mylineedit.o mylineedit.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o octonetwork.o octonetwork.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o terminaldialog.o terminaldialog.cpp
g++ -c -pipe -O2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem /usr/include/arm-linux-gnueabihf/qt5/QtSvg -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem /usr/include/arm-linux-gnueabihf/qt5/QtWebSockets -isystem /usr/include/arm-linux-gnueabihf/qt5/QtNetwork -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -I. -I. -I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o wlanconfig.o wlanconfig.cpp
/usr/lib/qt5/bin/rcc -name assets assets.qrc -o qrc_assets.cpp
RCC: Error in 'assets.qrc': Cannot find file 'assets/icon/BingoTouch_Logo_B.svg'
make: *** [Makefile:582: qrc_assets.cpp] Error 1
make: *** Waiting for unfinished jobs....

Hi,
OctoBtt runs permanently at 100% Cpu level and blocks everything. Also crashes the print because of blocking.

My last installation step from install.sh is:

g++ -Wl,-O1 -o OctoBTT accesscontrol.o cameradialog.o configuration.o controlpanel.o customdialog.o filedialog.o gcodedialog.o inputdialog.o liblog.o main.o mainwindow.o materialctrlpanel.o mylineedit.o octonetwork.o terminaldialog.o wlanconfig.o qrc_assets.o moc_accesscontrol.o moc_cameradialog.o moc_configuration.o moc_controlpanel.o moc_customdialog.o moc_filedialog.o moc_gcodedialog.o moc_inputdialog.o moc_mainwindow.o moc_materialctrlpanel.o moc_terminaldialog.o moc_wlanconfig.o -lQt5Svg -lQt5Widgets -lQt5Gui -lQt5WebSockets -lQt5Network -lQt5Core -lGLESv2 -lpthread -latomic

After this step installation stops, RPI reboots and I'm still in console with errors from XORG:

modprobe: FATAL: Module g2d_23 not found in directory /lib/modules/5.10.17-v7l+ xinit: Connection to X server lost

I have followed this step by step guide: https://www.youtube.com/watch?v=EQiSkXKjplQ (and some others after encountering above issue).

Dont have the option to set hot end temperature.
Latest version of Octoprint on Raspberry pi 4 with BTT PITFT50
3d Printer is an Ender 3 V2.
i am able to set bedtemp for preheat but not hot end temp.

I just get the new BIGTREETECH PI TFT50 V1.0 TFT-display, it work really well, buuuut, when I have it attached to a Raspberry Pi 4 with the mounting screws, the Wifi drops or work really bad, if I detach the Screen from the Pi (still attached to the pi via the cable), the Wifi start working Again, any sugestión?, I read that HDMI signal can interfiere with 2G and 5G networks this can explain this behavior.

Thx!

Hi,

First, thank you for your work.

I previously had OctoBTT installed on a Raspberry Pi running octoprint until about a week ago, when I had to restore the sdcard to its former state. When it was running on the pi, it worked very well and performed great, no problems overall.
I have just got to reinstalling it tonight & when the ui appears, the font & all icons displayed are very small. I don't think it's the display I'm using. Any chance you know what's going on? More than happy to provide information to help. :)

I figured I should ask here, before doing anything else...

The assets are downloaded from raw.githubusercontent.com which has valid SSL certificates; if a certificate error occurs that means there is something wrong.

Or is the "Great Firewall" damaging your connections? Because those in the rest of the world can probably omit that command line parameter safely.

Using the Pi TFT50 V2.0 with a RasPi 3b, Wifi does not work when the screen is attached. I'm using the standoffs provided with the screen , with a Pi 3B. Router is just a few feet away. Unplugging the screen Wifi works again.

Hi,

I just installed OctoBTT on a Raspberry Pi 3B+. OctoBTT open but I have "error" in the lower right of the screen. I can not control the printer at all. The screen doesn't seem to detect OctoPrint. Octoprint (1.4.2) run on the same Raspberry Pi and is working great with my CR-10s.

Is there any log I can look at to know what this error is about?

Thank you

hello, I don't know raspberry pi and following the guide to install OctoBTT I was stuck as shown in the image, could someone explain me how to solve? thank you

Hi,

I have a strange problem with my OctoBTT. I use the screen with a raspberry pi 4, 4 GB.
I installed it with lan cable connected, with no problems. All ran good, touchscreen showed up and OctoPrint is accessable via network. The I changed configuration to wifi. Network didn't start at next reboot. Ok, removed raspberry from screen and layed it beside the screen and gave power to the raspberry (I used a longer ribbon cable). It booted up and wifi connected. Oh, my fault, screwed all together and booted the raspberry. Again, no wifi. Removed raspberry from screen => wifi. Hmmm ... then I placed a sheet of alu-foil (in a pastik bag) between raspberry and screen and booted up. Now I got wifi on the raspberry, but so low that commands via putty needed 1-2 seconds to show. Has everyone the same problem? Maybe a faulty screen, or what can I do? Please help!

Bye

Björn ...

a non issue misspell that bugs I guess just me lol
When ever I need to Cancel out I Laughed a bit at this misspell not sure if its intentional

https://imgur.com/pQjV3kr

I am trying to install OctoBTT on your 5" TFT for Rasp... and it fails completely. Here are the steps I followed from the 'Readme' on this page.
Download and install Octoprint on a 32gb class 10 sd.
Access the Pi via ssh
Executed: 'sudo apt upgrade' then 'sudo apt update' both executed without errors.
Reboot the Pi
Access and setup Octoprint , performed required Octoprint updates.
Reboot the Pi, It now shows Octoprint Version 1.6.1 and Octopi Version 0.18.0
Access the Pi via ssh and run your command to install 'rm -f startup.sh ... "
The script reboots at the end and I get this

I examined the /etc/rc.local file and found this reference to OctoBTT 'su -l pi -c "cd /home/pi/OctoBTT && ./OctoBTT -platform eglfs" '
I ran it with sudo and got this response "-bash: ./OctoBTT: No such file or directory "
That is where I am now, it appears the is no executable for OctoBTT.
Where do I go from here.

I have an error on the right bottom part of the screen and no command is working.

My octoprint is/was working already

How to connect octobtt to octoprint ?

I received one of the production models and attached a Raspberry Pi Model 3 B+ to the main board. I only seem to get connection to the printer functions if I run a USB cable from the Pi to the front USB port in the printer. In the previews published on YouTube (e.g. by Teaching Tech) it seems that the Pi would connect directly with the printer through the internal serial port.

What is the problem with my model?

I'm trying to install OctoBTT per the guide on a Raspberry Pi 3B+ running OctoPi 0.15.1 , Octoprint version 1.4.2

The install gets to the following point and then quits, I've tried to reboot the RPI and it just comes back to a console shell.

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@octopi:~ $ /usr/include/arm-linux-gnueabihf/qt5/QtCore/qbytearray.h:361:16: note: candida te expects 0 arguments, 1 provided
-bash: /usr/include/arm-linux-gnueabihf/qt5/QtCore/qbytearray.h:361:16:: No such file or directory
pi@octopi:~ $ Makefile:677: recipe for target 'filedialog.o' failed
-bash: Makefile:677:: command not found
pi@octopi:~ $ make: *** [filedialog.o] Error 1
-bash: make:: command not found
pi@octopi:~ $ make: *** Waiting for unfinished jobs....
-bash: make:: command not found

Did a 6 hour print over night no issue.. Started a 10 hour print.. 4 hours in and octobtt crashed to console.. printer is still running as octoprint is still running but on the screen what I see is the octoprint console..

In a file;
sudo service octoprint stop
cp OctoBQPi/config.yaml .octoprint/config.yaml
sudo service octoprint start
cp OctoBQPi/.xsession .xsession
the path is incorrect.

Hi,
I've just gt the OctoBTT up and running and I have a small black square on the home screen just before the "-*C" text at the bottom of the screen in the centre. Also when clicking on the control icon there is a larger square black area i the top right corner.

What are these black squares?

Thanks

Just installed OctoBTT on a new Rass Pi 4b now, followed your guide and after ". install.sh" is finish, i have full control of the printer
on the 5" screen.
But, after i do a restart of the Pi, the OctoBTT do not start. It just loads up to command line, and thats it.

Is there something im doing wrong or what.??