FlappyBird_Python
FlappyBird_Python copied to clipboard
clear-code-projects
Bad file name
Case sensitive linux drops an error when trying to load 04B_19.ttf which is named 04B_19.TTF in the repo.
I did look at that page and have all those settings correct and I have some insulating tape on the pin of the usb cable to prevent 5V coming in. Not sure why this would be different for the new version - it's always worked fine with 1.3.5.
I tried that and the machine was OK with the Meatpack line commented out. I'm just going to rebuild with it back in again to prove that that is the issue.
Nope I uncommented it still works fine, so I put the downloaded release build back on and that works fine as well. I don't understand, maybe I disturbed the tape on the 5V wire. I'll close this anyway as all appears well.
For what it's worth, I am also having this issue with the exact same hardware. I did just identify then that powering up the printer with the OctoPi host disconnected and then plugging it in worked to "reconnect". I'm not sure how often this will work, but figured I'd let someone know that it may be related to the serial startup sequence?
Glad it's not just me. Getting the same M112 error on Ender 3V2 with Octoprint on power up. (5V pin was masked).
Update: I removed a number of plugins from Octoprint, reverting to a more basic operating system and then used the settings here and restarted Octoprint. Everything okay so far on the last three prints.
I have also been having this same issue and it also seems to be erratic and intermittent. It’s hard to prove but if I home all before I connect it “seems” like it does not happen as often.
I have the same problem ever since I upgraded to 2.01 firmware. I have these Octoprint settings already.
Anyone figured a solution other than downgrading ?
I have the same problem ever since I upgraded to 2.01 firmware. I have these Octoprint settings already.
Anyone figured a solution other than downgrading ?
I was having this issue recently. The steps I took to rectify it were:
- I removed any unused and unwanted plugins from Octoprint.
- I then Formatted the SD card and flashed the new firmware to the printer.
- I then systematically did a Reset to Default, followed by a Store Settings and followed by a Restore Settings to correctly initialise the EEProm.
- I also flashed the DWIN firmware to the display. Then followed the process in step 3.
I had the same issue with the 2.0.1 JyersUI... After 6-7 retries Octoprint connected to the printer.
Since I swapped out the display unit with a Creality touchscreen, I had to swap to the Creality-provided Firmware (also based on Marlin 2.0.1) and Octoprint is working as expected again.
