Octopi will boot only when i disconnect TFT touch screen

kokoshig5 · April 1, 2020, 7:15pm

What is the problem?
Hi guyz, completely newbie here. i got my RPI4 with tft 3.2 inch RPI touch screen last week to use it with my 3d printer , so i have octoprint set up everything working good but just one problem , when i shutdown RPI and turn back on i have to remove the screen from the GPIO pins and put it back so that the system boots normally. when i just reboot from terminal it does not have any problem works fine. if i leave the screen on the RPI and power cycle , the screen will come on and stay white, the red and green leds also stay solid ON. Just when i remove the screen for a second and put it back it will boot normally and i can use my Screen. any reason for this? Thanks
What did you already try to solve it?
Got original power adapter ,
Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
im using everything updated to latest firmwares.

OutsourcedGuru · April 1, 2020, 7:40pm

It's a bad idea to hot-plug TFT screens. This isn't USB. Just don't.

OctoPrint -> System -> Shutdown
Wait for green LED to stop blinking
Remove power from the Pi

If you're shutting down Raspbian (the operating system) then nothing is going to work until you power-cycle the Pi.

But upon bootup with the TFT installed on the GPIO pins it should bootup without all this extra effort.

It would be nice to know which manufacturer provided this and if you installed their drivers.

Waveshare, for example

kokoshig5 · April 1, 2020, 8:00pm

Yes i always shutdown from the normal terminal or by going to shutdown from the octopi UI on the touchscreen. My problem is everything works perfectly once i plug the TFT after RPI booting. i used the installation from http://www.lcdwiki.com/3.2inch_RPi_Display. Its been almost 3 days that im trying anything and searching all over for a solution but still couldnt get it work.
This is frim my boot/config.txt
its goodtft driver.

#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
#max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
hdmi_force_hotplug=1
dtparam=i2c_arm=on
dtparam=spi=on
enable_uart=1
dtoverlay=tft9341:rotate=270

kokoshig5 · April 1, 2020, 8:05pm

if you need to see anything to check if i have installed everything in correct way please just send me the command line (just a newbie to raspberry world) and i will post it here just to make a solution for this since its almost my 3rd consecutive day non stop trying to figure out without a result.
P.S. Its good in this quarantine days im learning new things Thank you in advance

OutsourcedGuru · April 1, 2020, 9:29pm

From the Raspbian docs:

Setting hdmi_force_hotplug to 1 pretends that the HDMI hotplug signal is asserted, so it appears that a HDMI display is attached. In other words, HDMI output mode will be used, even if no HDMI monitor is detected.

They're enabling the UART so maybe they're using that on the GPIO pins for the touch portion of this as an input. If that's the case, I would recommend adding: dtoverlay=miniuart-bt to keep the Bluetooth hardware from using the good UART.

It's interesting that they've got both SPI and I2C turned on, making it difficult to tell which one the input device needs (if at all).

You might try adding bootcode_delay=3 to see if this is a race condition between the display adapter on the add-on board and Raspbian.

kokoshig5 · April 1, 2020, 9:36pm

About the SPI and I2C i did turn them on from raspi-config just trying things if they will make any change, but they did not. Anyway i added those 2 lines and i turned #hdmi_force_hotplug =1 , i will try in 30 mins since there is a file on my 3d printer needs 30 min to finish and i will get back to you. I reaaly appreciate the help. Hope we will get into a solution and about the SPI and I2C shall i disable them?

OutsourcedGuru · April 1, 2020, 9:39pm

You need to do what the manufacturer of your TFT indicates you should do.

neither you nor I know if they use SPI or I2C or a UART to talk to this beast
presumably they know and their script sets you up for success

I myself prefer buying from Adafruit because the quality of their installation scripts and their documentation/tutorials are top-notch.

kokoshig5 · April 1, 2020, 9:57pm

This is the manual . It seems its SPI. so i disable I2C?

kokoshig5 · April 1, 2020, 10:09pm

so it seems it didnt work. again power cycling and it will not boot when screen attached. and now it will not load the octopi UI , after re attaching it goes to the terminal .
Edit: so after removing the # from the hdmi_force_hotplug=1 again , now its loading normally to the Octopi Touch UI. so i dnt know what that has to do with it, But still no luck booting RPI screen attached.

Edit Edit: one more thing that maybe will help figuring out. When i shutdown RPI the screen still is on but White. It stays on until i unplug the usb power cable from it. I dont know if thats the way it should be.

OutsourcedGuru · April 1, 2020, 11:19pm

If you shutdown from the OctoPrint system menu then it's probably running sudo shutdown -h now or similar. It just shuts down Raspbian but doesn't remove power from the TFT screen in this case. So yes, it would in many cases display something (even if it's just a white blank screen).

Setting that attribute for forcing the HDMI sounds like what you need to do in your case. Normally, the expected behavior is for the Pi to ask the HDMI what it is, the display adapter responds appropriately and then Raspbian knows to use that port.

You realize that this is the first you've mentioned the TouchUI plugin in this thread, right? Out here, we can't see your setup. It's why we ask for the logs you didn't provide so we're literally "flying blind".

Read these:

kokoshig5 · April 2, 2020, 9:19am

My touch UI is working perfectly once RPI boots and i attach the TFT. can you tell me plese how can i send you my log file. I am trying /var/log/syslog but it says command line not found while trying to access this on Putty. Sorry im reaaly new to this world . and again i really appreciate your help.

OutsourcedGuru · April 2, 2020, 5:23pm

The word logs here is automatically converted into a link which includes how to get the content. There's an upload icon here in this editor, click that.

kokoshig5 · April 2, 2020, 6:35pm

i dont know if this is the way i should give you the log file. I copied the text inside my /var/log/syslog .
this is the Log

Apr  2 00:00:23 octopi rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="361" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Apr  2 00:00:23 octopi systemd[1]: logrotate.service: Succeeded.
Apr  2 00:00:23 octopi systemd[1]: Started Rotate log files.
Apr  2 00:00:24 octopi systemd[1]: man-db.service: Succeeded.
Apr  2 00:00:24 octopi systemd[1]: Started Daily man-db regeneration.
Apr  2 00:02:05 octopi systemd[1]: Started Session c3 of user pi.
Apr  2 00:02:31 octopi systemd[1]: Unmounting RPC Pipe File System...
Apr  2 00:02:31 octopi systemd[1]: Stopped target Multi-User System.
Apr  2 00:02:31 octopi systemd[1]: Stopping LSB: TouchUI daemon...
Apr  2 00:02:31 octopi systemd[1]: Removed slice system-bthelper.slice.
Apr  2 00:02:31 octopi systemd[1]: Stopped target Sound Card.
Apr  2 00:02:31 octopi systemd[1]: Stopping Regular background program processing daemon...
Apr  2 00:02:31 octopi systemd[1]: Stopping Session c2 of user pi.
Apr  2 00:02:31 octopi systemd[1]: Stopped target Bluetooth.
Apr  2 00:02:31 octopi systemd[1]: gldriver-test.service: Succeeded.
Apr  2 00:02:31 octopi systemd[1]: Stopped Check for v3d driver.
Apr  2 00:02:31 octopi systemd[1]: Stopping LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
Apr  2 00:02:31 octopi systemd[1]: Stopping LSB: Change pi's password via /boot/octopi-password.txt...
Apr  2 00:02:31 octopi systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Apr  2 00:02:31 octopi systemd[1]: Stopped target Timers.
Apr  2 00:02:31 octopi systemd[1]: apt-daily-upgrade.timer: Succeeded.
Apr  2 00:02:31 octopi systemd[1]: Stopped Daily apt upgrade and clean activities.
Apr  2 00:02:31 octopi systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Apr  2 00:02:31 octopi systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Apr  2 00:02:31 octopi systemd[1]: Stopping OpenBSD Secure Shell server...
Apr  2 00:02:31 octopi systemd[1]: Stopping rng-tools.service...
Apr  2 00:02:31 octopi systemd[1]: Stopping triggerhappy global hotkey daemon...
Apr  2 00:02:31 octopi systemd[1]: Stopping Configure Bluetooth Modems connected by UART...
Apr  2 00:02:31 octopi systemd[1]: Stopping LSB: Change pi's hostname via /boot/octopi-hostname.txt...
Apr  2 00:02:31 octopi systemd[1]: Stopping Session c3 of user pi.
Apr  2 00:02:31 octopi systemd[826]: run-rpc_pipefs.mount: Succeeded.
Apr  2 00:02:31 octopi systemd[1]: Condition check resulted in Turns off Raspberry Pi display backlight on shutdown/reboot being skipped.
Apr  2 00:02:31 octopi rngd[379]: stats: bits received from HRNG source: 60064
Apr  2 00:02:31 octopi systemd[1]: Stopping Session c1 of user pi.
Apr  2 00:02:31 octopi rngd[379]: stats: bits sent to kernel pool: 6656
Apr  2 00:02:31 octopi systemd[1]: Stopping Make remote CUPS printers available locally...
Apr  2 00:02:31 octopi rngd[379]: stats: entropy added to kernel pool: 6656
Apr  2 00:02:31 octopi systemd[1]: Stopping BluezALSA proxy...
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS 140-2 successes: 3
Apr  2 00:02:31 octopi systemd[1]: Stopping Save/Restore Sound Card State...
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS 140-2 failures: 0
Apr  2 00:02:31 octopi systemd[1]: man-db.timer: Succeeded.
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Apr  2 00:02:31 octopi systemd[1]: Stopped Daily man-db regeneration.
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS 140-2(2001-10-10) Poker: 0
Apr  2 00:02:31 octopi systemd[1]: logrotate.timer: Succeeded.
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS 140-2(2001-10-10) Runs: 0
Apr  2 00:02:31 octopi systemd[1]: Stopped Daily rotation of log files.
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS 140-2(2001-10-10) Long run: 0
Apr  2 00:02:31 octopi systemd[1]: systemd-rfkill.socket: Succeeded.
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS 140-2(2001-10-10) Continuous run: 0
Apr  2 00:02:31 octopi systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Apr  2 00:02:31 octopi rngd[379]: stats: HRNG source speed: (min=411.176; avg=445.295; max=499.125)Kibits/s
Apr  2 00:02:31 octopi systemd[1]: rpi-eeprom-update.service: Succeeded.
Apr  2 00:02:31 octopi rngd[379]: stats: FIPS tests speed: (min=11.899; avg=12.232; max=12.557)Mibits/s
Apr  2 00:02:31 octopi kernel: [  213.291006] Bluetooth: hci0: sending frame failed (-49)

OutsourcedGuru · April 2, 2020, 6:43pm

I formatted it for you. Next time, highlight the part you just pasted in and then click the icon above this which looks like this </>.

You might as well include the octoprint.log as well.

kokoshig5 · April 2, 2020, 7:02pm

|  hardware:
|      cores: 4
|      freq: 1500.0
|      ram: 969879552
|  os:
|      id: linux
|      platform: linux2
|  plugins:
|      pi_support:
|          model: Raspberry Pi 4 Model B Rev 1.1
|          octopi_version: 0.17.0
|  python:
|      pip: 19.3.1
|      version: 2.7.16
|      virtualenv: /home/pi/oprint
2020-04-02 17:51:50,080 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/webassets...
2020-04-02 17:51:50,100 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/.webassets-cache...
2020-04-02 17:51:50,172 - octoprint.plugins.octolapse - INFO - Octolapse is loading assets.
2020-04-02 17:51:50,789 - octoprint.server - INFO - Shutting down intermediary server...
2020-04-02 17:51:51,251 - octoprint.server - INFO - Intermediary server shut down
2020-04-02 17:51:51,253 - octoprint.events - INFO - Processing startup event, this is our first event
2020-04-02 17:51:51,253 - octoprint.events - INFO - Adding 0 events to queue that were held back before startup event
2020-04-02 17:51:51,256 - octoprint.server - INFO - Autoconnect on startup is configured, trying to connect to the printer...
2020-04-02 17:51:51,256 - octoprint.filemanager - INFO - Adding backlog items from all storage types to analysis queue...
2020-04-02 17:51:51,275 - octoprint.filemanager - INFO - Added 0 items from storage type "local" to analysis queue
2020-04-02 17:51:51,288 - octoprint.server - INFO - Trying to connect to configured serial port /dev/ttyUSB0
2020-04-02 17:51:51,320 - octoprint.server.util.watchdog - INFO - Running initial scan on watched folder...
2020-04-02 17:51:51,326 - octoprint.server.util.watchdog - INFO - ... initial scan done.
2020-04-02 17:51:51,334 - octoprint.plugins.discovery - INFO - Registered 'OctoPrint instance on octopi' for _http._tcp
2020-04-02 17:51:51,345 - octoprint.plugins.discovery - INFO - Registered 'OctoPrint instance on octopi' for _octoprint._tcp
2020-04-02 17:51:51,348 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial port"
2020-04-02 17:51:51,351 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2020-04-02 17:51:51,369 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-02 17:51:51,376 - octoprint.server - INFO - Listening on http://127.0.0.1:5000
2020-04-02 17:51:51,380 - octoprint.plugins.octolapse - INFO - Loading existing settings file from: /home/pi/.octoprint/data/octolapse/settings.json.
2020-04-02 17:51:51,511 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid
2020-04-02 17:51:52,244 - octoprint.util.pip - INFO - Using "/home/pi/oprint/bin/python2 -m pip" as command to invoke pip
2020-04-02 17:51:52,245 - octoprint.util.pip - INFO - pip installs to /home/pi/oprint/lib/python2.7/site-packages (writable -> yes), --user flag needed -> no, virtual env -> yes
2020-04-02 17:51:52,285 - octoprint.util.pip - INFO - ==> pip ok -> yes
2020-04-02 17:51:52,325 - octoprint.util.connectivity_checker - INFO - Connectivity changed from offline to online
2020-04-02 17:51:52,515 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid
2020-04-02 17:51:52,676 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.0.111
2020-04-02 17:51:52,932 - octoprint.plugins.pluginmanager - INFO - Loaded notice data from disk, was still valid
2020-04-02 17:51:53,142 - octoprint.plugins.HeaterTimeout - INFO - Starting up...
2020-04-02 17:51:53,204 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-02 17:51:53,265 - octoprint.plugins.navbartemp - INFO - Broadcom detected
2020-04-02 17:51:53,269 - octoprint.plugins.themeify - INFO - Themeify initialized.
2020-04-02 17:51:53,527 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.0.111) 93.93ms
2020-04-02 17:51:53,596 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.0.111) 25.61ms
2020-04-02 17:51:53,597 - octoprint.plugins.pluginmanager - INFO - Loaded notice data from disk, was still valid
2020-04-02 17:51:53,615 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.0.111) 6.42ms
2020-04-02 17:51:53,633 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.0.111) 6.81ms
2020-04-02 17:51:53,670 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.0.111) 6.26ms
2020-04-02 17:51:53,690 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.0.111) 7.40ms
2020-04-02 17:51:53,692 - octoprint.server.preemptive_cache - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://[::1]/'}
2020-04-02 17:51:53,712 - tornado.access - WARNING - 409 GET /api/printer (::ffff:192.168.0.111) 5.62ms
2020-04-02 17:51:53,721 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-02 17:51:53,727 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Operational"
2020-04-02 17:51:53,753 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-02 17:51:53,792 - octoprint.plugins.tracking - INFO - Sent tracking event startup, payload: {'python': '2.7.16', 'ram': 969879552, u'octopi_version': u'0.17.0', 'version': u'1.4.0', 'pip': '19.3.1', 'cores': 4, 'freq': 1500.0, u'pi_model': u'Raspberry Pi 4 Model B Rev 1.1', 'os': 'linux'}
2020-04-02 17:51:53,810 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin 1.1.9 (Github)"
2020-04-02 17:51:53,834 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2020-04-02 17:51:54,027 - octoprint.server.util.flask - INFO - Passively logging in user _admin from ::ffff:192.168.0.111
2020-04-02 17:51:54,029 - octoprint.access.users - INFO - Logged in user: _admin
2020-04-02 17:51:54,088 - octoprint.server.util.sockjs - INFO - User _admin logged in on the socket from client ::ffff:192.168.0.111
2020-04-02 17:51:54,134 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 6}
2020-04-02 17:51:54,503 - octoprint.plugins.tracking - INFO - Sent tracking event pong, payload: {'plugins': u'heatertimeout:0.0.3,slic3r:1.2,cancelobject:0.4.1,themeify:1.2.2,autoscroll:0.0.2,touchui:0.3.14,navbartemp:0.13,floatingnavbar:0.3.1,octolapse:0.3.4'}
2020-04-02 17:51:54,868 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {u'printer_baudrate': 115200, u'printer_port': '/dev/ttyUSB0', 'firmware_name': u'Marlin 1.1.9 (Github)'}
2020-04-02 17:52:03,627 - octoprint.server.preemptive_cache - INFO - ... done in 9.94s
2020-04-02 17:52:03,628 - octoprint.server.preemptive_cache - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://192.168.0.104/'}
2020-04-02 17:52:05,148 - octoprint.server.preemptive_cache - INFO - ... done in 1.52s
2020-04-02 17:52:05,149 - octoprint.server.preemptive_cache - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://192.168.0.100/'}
2020-04-02 17:52:06,692 - octoprint.server.preemptive_cache - INFO - ... done in 1.54s
2020-04-02 17:52:06,692 - octoprint.server.preemptive_cache - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://octopi.local/'}
2020-04-02 17:52:08,401 - octoprint.server.preemptive_cache - INFO - ... done in 1.71s
2020-04-02 17:52:33,991 - octoprint.server.util.sockjs - INFO - New connection from client: ::1
2020-04-02 17:52:34,066 - octoprint.server.util.flask - INFO - Passively logging in user _admin from ::1
2020-04-02 17:52:34,067 - octoprint.access.users - INFO - Logged in user: _admin
2020-04-02 17:52:37,083 - octoprint.server.util.sockjs - INFO - User _admin logged in on the socket from client ::1
2020-04-02 17:52:48,677 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.0.111
2020-04-02 17:52:48,941 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.0.111
2020-04-02 17:52:48,990 - octoprint.server.util.flask - INFO - Passively logging in user _admin from ::ffff:192.168.0.111
2020-04-02 17:52:48,991 - octoprint.access.users - INFO - Logged in user: _admin
2020-04-02 17:52:50,149 - octoprint.server.util.sockjs - INFO - User _admin logged in on the socket from client ::ffff:192.168.0.111
2020-04-02 18:06:48,178 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-04-02 18:06:54,495 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 890}
2020-04-02 18:10:31,553 - octoprint.filemanager.analysis - INFO - Starting analysis of local:Filter_Mask_v4.gcode
2020-04-02 18:10:31,557 - octoprint.filemanager.analysis - INFO - Invoking analysis command: /home/pi/oprint/bin/python2 -m octoprint analysis gcode --speed-x=6000 --speed-y=6000 --max-t=10 --throttle=0.0 --throttle-lines=100 /home/pi/.octoprint/uploads/Filter_Mask_v4.gcode
2020-04-02 18:10:37,449 - octoprint.filemanager.analysis - INFO - Analysis of entry local:Filter_Mask_v4.gcode finished, needed 5.90s
2020-04-02 18:10:41,412 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: Filter_Mask_v4.gcode, owner: _admin, user: _admin
2020-04-02 18:10:47,645 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2020-04-02 18:10:47,658 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Filter_Mask_v4.gcode, owner: _admin, user: _admin
2020-04-02 18:10:48,048 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {'origin': u'local', 'file': '3031d361a200731173401433a457bf4eb6cfe474'}
2020-04-02 18:10:49,728 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Cancelling"
2020-04-02 18:10:49,738 - octoprint.util.comm - INFO - Force-sending M108 to the printer
2020-04-02 18:10:49,773 - octoprint.printer.standard.job - INFO - Print job cancelled - origin: local, path: Filter_Mask_v4.gcode, owner: _admin, user: None
2020-04-02 18:10:49,855 - octoprint.util.comm - INFO - Changing monitoring state from "Cancelling" to "Printing"
2020-04-02 18:10:49,885 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-02 18:10:49,967 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Operational"
2020-04-02 18:10:50,558 - octoprint.plugins.tracking - INFO - Sent tracking event print_cancelled, payload: {'origin': u'local', 'file': '3031d361a200731173401433a457bf4eb6cfe474', u'elapsed': 2}
2020-04-02 18:10:50,901 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {'origin': u'local', u'reason': u'cancelled', 'file': '3031d361a200731173401433a457bf4eb6cfe474', u'elapsed': 2}
2020-04-02 18:11:03,259 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2020-04-02 18:11:03,275 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Filter_Mask_v4.gcode, owner: _admin, user: _admin
2020-04-02 18:11:03,310 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-02 18:11:03,335 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2020-04-02 18:11:04,022 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {'origin': u'local', 'file': '3031d361a200731173401433a457bf4eb6cfe474'}
2020-04-02 18:11:05,468 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2020-04-02 18:11:25,053 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2020-04-02 18:21:48,181 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-04-02 18:21:53,508 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 1790}
2020-04-02 18:36:48,182 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-04-02 18:36:55,210 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 2690}
2020-04-02 18:51:48,184 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-04-02 18:51:53,555 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 3590}
2020-04-02 18:58:54,935 - octoprint.server.util.sockjs - INFO - New connection from client: fe80::1075:1e9a:cdd8:caa9
2020-04-02 18:58:55,092 - octoprint.server.util.flask - INFO - Passively logging in user _api from fe80::1075:1e9a:cdd8:caa9
2020-04-02 18:58:55,094 - octoprint.access.users - INFO - Logged in user: _api
2020-04-02 18:58:55,112 - octoprint.server.util.sockjs - INFO - User _api logged in on the socket from client fe80::1075:1e9a:cdd8:caa9
2020-04-02 18:58:57,943 - octoprint.server.util.sockjs - INFO - Client connection closed: fe80::1075:1e9a:cdd8:caa9
2020-04-02 19:06:48,185 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-04-02 19:06:53,520 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 4490}
2020-04-02 19:07:29,395 - octoprint.server.util.sockjs - INFO - New connection from client: fe80::1075:1e9a:cdd8:caa9
2020-04-02 19:07:30,168 - octoprint.server.util.flask - INFO - Passively logging in user _api from fe80::1075:1e9a:cdd8:caa9
2020-04-02 19:07:30,171 - octoprint.access.users - INFO - Logged in user: _api
2020-04-02 19:07:30,213 - octoprint.server.util.sockjs - INFO - User _api logged in on the socket from client fe80::1075:1e9a:cdd8:caa9
2020-04-02 19:07:32,548 - octoprint.server.util.sockjs - INFO - Client connection closed: fe80::1075:1e9a:cdd8:caa9

OutsourcedGuru · April 3, 2020, 1:07am

Here, I would guess that something is trying to remotely ask OctoPrint for the printer status but isn't configured properly. It might need the API key set for that to work. I'd like to say that it might be TouchUI but you'd think that it's IP address would be more like 127.0.0.1 instead.

Perhaps someone else knows what's going on with this. Or perhaps the manufacturer or their forum might have more answers.