-
Notifications
You must be signed in to change notification settings - Fork 30
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
Automation Enhancements #4
Comments
wow seems interesting ,Have u tried this? |
Does this mean that almost all motherboards can be automatically recognized and connected to the Android klipper system without compiling the kernel driver for a specific motherboard? If this is the case, I think it is a simple and feasible solution once and for all. How about the memory usage of octo4a APP? Is it a big burden on the system? |
How do you implement this? I am pretty new to linux, so I am might be missing something obvious. |
Did you mean octo4a? It's just an APP, just install it directly in Android. |
No, not octo4a. Right now I have 2 printers running Klipper using your tutorial and I am using octo4a for both. I mean where do I need to run these commands to have them make it so that I don't have to change my printer.cfg everytime my phone restarts. |
Is the MCU path generated every time the phone is restarted different? If that's the case, it's really not a good problem to solve. |
Yeah the MCU path goes from /dev/pts/0 to /dev/pts/1 or /dev/pts/4 those are what I have seen it go to on my phone, but others could be different. I was thinking that this line sudo unchroot readlink -f /data/data/com.octo4a/files/serialpipe /dev/printer would somehow create a link between whatever /data/data/com.octo4a/files/serialpipe reads, because that is how you find the /dev/pts/{number} and make it a variable or something that would be written into /dev/printer but I guess I was mistaken. My bad. |
This link was posted by @d4rk50ul1. I haven't delved into it. I thought he might have a better solution. |
So this is what i've done so far:
Issues as of now:
Approaches:
i'm currently assessing if it works. I'm very junior on bash scripting so if there's any better approach i think it would be highly appreciated by everyone! |
Edit: didn't work :S so if @gaifeng8864 could help us that would be awesome! |
Thank you @d4rk50ul1 for trusting me. But, unfortunately, I'm also a novice at bash scripting. |
Hey @gaifeng8864 i got a suggestion on my original version to apply this very simplistic enhancement and works like a charm! On MOUNTS section: and voilah |
Is this method equivalent to mounting the virtual serial port generated by octo4a directly inside centos through linuxdeploy? Then call it directly in printer.cfg? |
question 1: yes it's equivalent |
You really did a really great job. In this way, almost all motherboards can be easily connected to the Android phone klipper. Do I need to set octo4a to start automatically if I use this method? |
This worked great! I have an issue where octoprint wasn't starting on boot, but once I open that up and chmod 777 /home//octo4a/serialpipe it works! I would still like to get this figured out to, but this is still easier then changing the mcu everytime as well |
I'm glad to see that you and @d4rk50ul1 have used this solution at the same time, which shows that the feasibility of this solution has been recognized by more people. According to your and @d4rk50ul1's description, what we need to solve is the problem of octo4a booting up and changing /home//octo4a/serialpipe permissions. I figured this could be done automatically by changing a few things in my adapted script. Let's study the following together. |
I read here https://unix.stackexchange.com/questions/663399/restore-default-permissions-on-dev-pts that pts is ram based, so they suggest making a udev rule. I don't know anything about udev or if that's even a reasonable way to go, but I was trying it and this is the rule I was using KERNAL=="pts*", MODE="0666", ACTION=="add", RUN+="sh /home/print3DchangePermissionspts.sh" I think we could get away with not using the RUN but just a test I was using it. I wasn't able to get this to work. I think it has to do with the kernel. I just don't think it was running when a new device is plugged in and I don't know how to test it. |
Do you know how Octo4A can drive so many devices? If we can know how it works, maybe we can find a more streamlined way to drive the printer motherboard than using Octo4A. |
hope you can help me, now i am getting Klippy: Disconnected, I did what you said but it doesn't seem to work, I have some config files hope you can take a look and let me know where is it crashing :( |
Try reinstalling the klipper components, make sure the installation is complete. Often due to network reasons, dependent download failures lead to compilation problems. Then re-execute the script configuration_klipper_family |
|
On my last time installing it I have a had to install it using python 2.7 and not python 3. You can try that and see if that helps. |
I'm currently using version 3. let me reinstall all to see if it works |
I found this forum post. https://forum.3dprintbeginner.com/t/klipper-and-creality-box/736/5 I think your issue is now just a general klipper/moonraker issue. |
it worked, i flashed the .bin file for mks robin e3, i used the mks printer.cfg file for it and got these errors, what should i do next :( |
It looks like some configuration files are not set completely. Please post your printer.cfg too, and we will analyze the following problems together. |
You can now follow basic klipper installation procedures as You have almost done installing! |
You need to add this configuration item in printer.cfg: [include fluidd.cfg] |
Hey @gaifeng8864 more than an issue its a comment,
i got a PR from someone that suggested the following lines to Skip Termux usage + automatic selection of Serial Printer:
Termux is not really necessary. You can use unchroot.
Also we can have a permanent link for the serial port from octo4a.
sudo unchroot am start -n com.octo4a/.ui.InitialActivity
sleep 10
sudo ln -s
sudo unchroot readlink -f /data/data/com.octo4a/files/serialpipe
/dev/printerWhat do you think?
The text was updated successfully, but these errors were encountered: