I prefer LAN cable over WiFi, and so after receiving my beautiful A350 yesterday, I attached an USB to Ethernet adapter to the USB port of the controller. This was an immediate success, it receives an IP via DHCP and I can connect successfully via Luban.
I suppose that any Linux kernel supported Ethernet chip should work, since Android is based on the Linux kernel. The adapter I used uses the Realtek R815x family chipset, namely the R8153.
When connecting, Snapmaker will still ask you to confirm the connection as WiFi connection.
To the Snapmaker team: Please please leave the support for such adapters in the machine in future releases! Where my machine in the end will live, I do not have WiFi reception, and cable is more stable then WiFi anyhow (as you can see from several posts in the Facebook group).
I guess itĀ“s a bit of trial and error. I suppose if you find a reference somewhere that a device workes with raspberry Pi, chances are high it will work with Snapmaker 2 also, but nothing is guaranteedā¦
The touchscreen controller is ARM based, just like the Raspberry Pi. But I guess thatĀ“s more or less the end of similarities, apart from perhaps that Android and Linux are close relatives. Doing a 10 seconds research, I hit this link: Reddit - Dive into anything It says that Octoprint somehow can run on Android, so in theory your idea would be feasible, and I would immediatly agree that it would be nice.
However, in the way to this stands that the touchscreen is not really open to modifications without a bit of ado. Paths to follow would be to see if a remote shell is somehow exposed via USB or over the network, or if behind the small plastic cover on the top back theeĀ“s a JTAG, UART or whatever debugging port. If so, there might be a way.
Personally, IĀ“ll just go for a classic Raspberry Pi when I set up my OctoPrint.
Octopi (the Raspbian OS) would not work on the controller. However, Octoprint is just Python, so an Android-based controller should be able to handle it easily.
I agree that it seems to make a lot of sense to offer octoprint as an interface on the touch screen. We have yet to see the source for that, though there are decompilations of it since it was embedded in the controller firmware.
Since the Touchscreen runs on Android, Iād not be surprised if thereās no real need to understand the Touchscreen controller software - all thatās needed is to understand how to install Apps on the Controller and how to perhaps disable the Snapmaker app(s), because if octoprint would take over, it would interfere with the Snapmaker native controls.
As to my knowledge nobody yet has found a way to make the controller accessible - connecting it to an USB-C port on a PC does not yield anything (it does not even start), and the case is not easy to open, so you canāt look for a JTAG/UART/ICSP connector.
Hopefully Snapmaker will release more information at some pointā¦
Iām trying to use a usb to ethernet adapter, just hooked it up today. It wonāt even pretend to connect. I get the following error: Request has been terminated. Possible causes: the network is offline. Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc. Can anyone help?
On first connect, youāll need to authorize the connection on the touchscreen.
To make your life easier, Iād create a DHCP reservation on your router for the Snapmaker so that the IP will stay the same even after power cycling the Snapmaker.
If the āAbout machineā page says āNot connectedā, this unfortunately can mean anything, starting from the USB-Ethernet-Adapter is not compatible, the printer did not get a DHCP lease, the network cable is not OK or anything else that is faulty.
Works with 1.16.7 - did not yet upgrade to 1.17 - currently travelling and away from machine. In case it does not work with 1.17 anymore, Iāll report here. If you do not read anything here in two weeks, it still works
