I am looking for a solution to reach the serial interface of a 3D printer in a debian chroot linux deploy.
My devices is Samsung A3 2015, rom: resurrection remix 7.1
During my tests, I can communicate with the printer (I sent gcode commands correctly) with a simple serial port application on the playstore.
I deployed the octoprint server in Debian Arm of Linux Deploy. In the octoprint configuration an automatic search of the periphery (usually /dev/ttyUSB) does not work; no port found.
In addition, when I navigate with a terminal in the android system, there is no /dev/ttyUSB file.
But where does Android map the periphery?
Here is the result of the dmesg when connecting the printer:
[85207.609290] usb 1-1: full-speed USB device number 10 using msm_hsusb_host
[85207.737337] usb 1-1: New USB device found, idVendor = 1a86, idProduct = 7523
[85207.737475] usb 1-1: New USB device strings: Mfr = 0, Product = 2, SerialNumber = 0
[85207.737514] usb 1-1: Product: USB2.0-Serial
An lsusb, gives me my printer:
Bus 001 Device 014: ID 1a86: 7523 QinHeng Electronics HL-340 USB-Serial Adapter
Hello
I am looking for a solution to reach the serial interface of a 3D printer in a debian chroot linux deploy. My devices is Samsung A3 2015, rom: resurrection remix 7.1
During my tests, I can communicate with the printer (I sent gcode commands correctly) with a simple serial port application on the playstore.
I deployed the octoprint server in Debian Arm of Linux Deploy. In the octoprint configuration an automatic search of the periphery (usually /dev/ttyUSB) does not work; no port found. In addition, when I navigate with a terminal in the android system, there is no /dev/ttyUSB file.
But where does Android map the periphery?
Here is the result of the dmesg when connecting the printer:
An lsusb, gives me my printer:
Bus 001 Device 014: ID 1a86: 7523 QinHeng Electronics HL-340 USB-Serial Adapter
I aim on getting problem ..