search

gaifeng8864 / klipper-on-android

Run klipper, moonraker, fluidd, KlipperScreen one-click configuration script on androidOS.
GNU General Public License v3.0
144 stars 29 forks source link

Help, TCP - UART problem #27

Open HelioNM opened 3 weeks ago

HelioNM commented 3 weeks ago

I follow the steps and I cant connect to my printer, the usb serial is not present at the deploy, also I cant use the octo4a method. So I tried with the TCP-UART app. At the first try it works!! klipper was runnig and without errors. Then restarted my phone and... Nothing works again.

The problem is... when I put the socat command this is what happen:

$ socat -d -d pty,link=/tmp/tcpserial,raw,echo=0,waitslave tcp:localhost:8080 2024/10/29 19:41:17 socat[16715] N PTY is /dev/pts/7 2024/10/29 19:42:30 socat[16715] N opening connection to AF=2 127.0.0.1:8080 2024/10/29 19:42:30 socat[16715] N successfully connected from local address AF=2 127.0.0.1:45489 2024/10/29 19:42:30 socat[16715] N starting data transfer loop with FDs [5,5] and [6,6]

Also at the app I can see bytes transfered at the USB_UART -> TCP and TCP -> USB_UART

capture_1

The problem is... At the moment I enter the mainsail web and try to start the connection with my printer the connection fail...

2024/10/29 19:49:29 socat[16789] N read(5, 0x82813000, 8192): Input/output error (probably PTY closed) 2024/10/29 19:49:29 socat[16789] N socket 1 (fd 5) is at EOF

capture_2

Cant understand why it works so fine the first time I tried this method and after a phone reboot it never works again.

Log: klipy.log

The phone is in SELinux Permissive btw however I cant no see any diference between permissive and enforcing. Octa4a is active with the service stopped, also tried to uninstall octa4a however same results.

Also at the TPC/UART app after the problem start at the moment that klipper try a connection, I can see the USB_UART -> TCP is still transfer bytes, it looks like the TCP -> USB_UART is stoped with no activity

If anyone can help me...

BTW: the printer connects with no issues to octa4a in this smartphone when the firmware is marlin and right now with the klipper firmware it also works with no issue at my computer with debian. Also it worked fine the first time I tried the method with tcp/uart until I rebooted my phone.

HelioNM commented 3 weeks ago

Ok, I found a behavior...

If I stop moonmaker and klipper services, start it again, and then and only then (with the mainsail web open) use the socat command... Then it works.

If the socat command is executed with the klipper or moonraker actives, it will not work.

I can't figure out how to do a script that run when the system start because rc.local and systemctl are blocked in this kind of deploy and I don't know how to activate it or if there is an alternative.

This is a problem, if I close the ssh connection, my PC goes down, the ssh connection pauses due to inactivity, etc... The printer STOP...

Any idea? How can I tell to debian to execute the socat command after the klipper is loaded with no ssh connection? And what happens if I need to restart the firmware due a change in config? Is it possible to create a script that runs the socat only after stop klipper and moonraker and start they again? Also, the script should monitor if klipper or moonraker restart by any reason (like editing things at the printer.cgf), then the socat command need to be closed and started again...

I need help xD

Milliw commented 1 week ago

Have you gotten any further?

EDIT: And can you explain in short how to use that app? Installed it and run that socat command. Then tried to connect tcp client within the app but got connection refused.