KlipperScreen VS OctoScreen

[server] host: 0.0.0.0 port: 7125 klippy_uds_address: /home/biqu/printer_data/comms/klippy.sock [authorization] trusted_clients: 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 FE80::/10 ::1/128 cors_domains: *.lan *.local *://localhost *://localhost:* *://my.mainsail.xyz *://app.fluidd.xyz [octoprint_compat] [history] [update_manager] channel: dev refresh_interval: 168 [update_manager mainsail-config] type: git_repo primary_branch: master path: ~/mainsail-config origin: https://github.com/mainsail-crew/mainsail-config.git managed_services: klipper [update_manager mainsail] type: web channel: stable repo: mainsail-crew/mainsail path: ~/mainsail [update_manager crowsnest] type: git_repo path: ~/crowsnest origin: https://github.com/mainsail-crew/crowsnest.git install_script: tools/install.sh # Sonar update_manager entry [update_manager sonar] type: git_repo path: ~/sonar origin: https://github.com/mainsail-crew/sonar.git primary_branch: main managed_services: sonar install_script: tools/install.sh [update_manager timelapse] type: git_repo primary_branch: main path: ~/moonraker-timelapse origin: https://github.com/mainsail-crew/moonraker-timelapse.git managed_services: klipper moonraker [update_manager KlipperScreen] type: git_repo path: ~/KlipperScreen origin: https://github.com/jordanruthe/KlipperScreen.git env: ~/.KlipperScreen-env/bin/python requirements: scripts/KlipperScreen-requirements.txt install_script: scripts/KlipperScreen-install.sh managed_services: KlipperScreen

The project I'm trying to run is this one: https://github.com/jordanruthe/KlipperScreen, it's a plugin for a 3D printing firmware, to have a screen connected to a raspberry where the firmware runs.

That sounds like a Klipperscreen bug. You should probably report it.

It won’t work (at least I don’t think it will) with the built in screen but you can alway setup Klipperscreen

cp sample-android-adb.sh launch_KlipperScreen.sh and there was no error viola! Follow by this line : chmod +x launch_KlipperScreen.sh  And the : sudo reboot Then go to moonraker and enter: under [authorization]trusted_clients:  127.0.0.1 And also add in moorraker update script: [update_manager KlipperScreen] type: git_repo path: ~/KlipperScreen origin: https://github.com/jordanruthe/KlipperScreen.git env: ~/.KlipperScreen-env/bin/python requirements: scripts/KlipperScreen-requirements.txt install_script: scripts/KlipperScreen-install.sh hit save and reboot   Using pixel 2 us a touch screen! Everything is working fine so far!

Fluidd and Mainsail are frontends for Moonraker. Moonraker is an API server for Klipper. There are other frontends for Moonraker too, such as KlipperScreen.

git clone https://github.com/jordanruthe/KlipperScreen.git

Used: https://klipperscreen.readthedocs.io/en/latest/Installation/ and the following Github: https://github.com/jordanruthe/KlipperScreen

I would like to use a screen, and install Octoscreen in a Raspberry 2 in fact is working but every time that reboot the Octoscreen run automatically, I wanna to use the normal desktop of my Raspberry to another purposes and only I see Octoscreen, how can I install Octoscreen like an app to my raspberry with run after every reboot.

Octoprint has a built-in API server too which is documented here. There are several alternative frontends that use the API. Most popular being probably OctoDash and OctoScreen, and several mobile apps. But also the "Send to printer" button in your slicer uses that API, and of course OctoPrint's UI itself.

For the printer controls i would recommend OctoScreen for ease of use.

OctoDash or OctoScreen.

I've been using OctoPi/OctoPrint and OctoScreen with a Pi 4 and a small 3" PiTFT 480x240 screen.

OctoScreen: https://github.com/Z-Bolt/OctoScreen

For the front display, I bought a 5" touchscreen and installed octoscreen on it: https://github.com/Z-Bolt/OctoScreen

wget https://github.com/Z-Bolt/OctoScreen/releases/download/v2.7.3/octoscreen_2.7.3_armhf.deb

It’s Octoscreen. I use that to have touch controls for when I’m here. Octoprint / spaghetti detective for when I’m away. It all works seamlessly together with the CR-10. You can use any device to control the unit. octocscreen

well having a screen probs would not have save you really because there is just a delay in the gcode the machine gets so when it receives that stop command the damage is done best to rip the power cord instead, but as for connecting look at this https://github.com/Z-Bolt/OctoScreen it may not be what your looking for but just google octoprint display and you can find what your looking for