-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mcu: "Unable to connect" error #27
Comments
Hi! glad you found us, we're trying to do our best here! |
Hi again, thank you for your fast response! Sorry I didn't notice until now.
|
Ok so after almost 3 months of testing, this morning I finally managed to get it to communicate correctly haha, klipperscreen showing and fluidd on browser. I can confirm Android 11 works for this method on my Lenovo M10 plus (3rd gen, Magisk rooted). So I replaced 'ttyACM0' with ''/home/print3D/octo4a/serialpipe/serialpipe", and the klipper family bash ran perfectly. Still, I had to 'sudo chmod 777 /dev/pts/0' manually from ssh after that because the fluidd web interface just prompted failure to connect on the logs. On the [mcu] header at printer.cfg, I used ''/home/print3D/octo4a/serialpipe/serialpipe". Right now, my lectures are good, and the board info is displaying on the browser, but I still get the 'Internal Server Error' when trying to save modifications of the printer config files directly from the fluidd web interface (i modified them externally transfering them using FileZilla), any suggestions on what I'm still missing? Also, is it normal to get the 'fluidd-config', 'moonraker', and 'klipper' under software update with an error 'No valid, Recover' buttons? |
I manage to get it to work too. Everything is working except I have to run
|
There is a problem when I reboot the android, there are many prompts of apps that aren't running well right after the reboot, then the android reboots itself again and enters into a recovery screen: 'Can't load into Android system. Your data may be corrupt'. Then a 'try again' or 'factory data reset' menu is below. |
Hi! I was impressed with your work on this topic so I tried to power a setup the octo4a way (using a Lenovo Tab M10 plus 3rd gen and a BTT SKR2 board), I selected the CH341 driver on the app, changed the mcu serial in printer.cfg to "/home/android/octo4a/serialpipe" and set a 250k baudrate. Klipperscreen is launching, fluidd is accessible through browser but I still get the mcu: "Unable to connect" error. I already factory reseted 2 times and I'm still stuck at this point. Also, I get "Internal server error" on fluidd when trying to save changes on any .cfg file. Any suggestions on what to look for? Greetings.
The text was updated successfully, but these errors were encountered: