Artillery Sidewinder not connecting to OctoPrint

What is the problem?
I want to connect an Artillery Sidewinder X1 to octoprint but I only managed to do it once until it would refuse to connect because of this error:

Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0xaf9bce50, open=True>(port='/dev/ttyUSB0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=30.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Send: N0 M110 N0*125
No answer from the printer within the connection timeout, trying another hello
Send: N0 M110 N0*125
There was a timeout while trying to connect to the printer
Changing monitoring state from "Connecting" to "Offline"
Connection closed, closing down monitor

What did you already do to try to solve it?
I have tried changing baud rates and ports and I have updated the Artillery printer firmware.
Logs

OctoPrint log:
https://drive.google.com/file/d/1VduV87TToyTFBKT_VtPStXn4Elsz1hU0/view?usp=sharing

Terminal output:

Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0xaf9bce50, open=True>(port='/dev/ttyUSB0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=30.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Send: N0 M110 N0*125
No answer from the printer within the connection timeout, trying another hello
Send: N0 M110 N0*125
There was a timeout while trying to connect to the printer
Changing monitoring state from "Connecting" to "Offline"
Connection closed, closing down monitor

Additional information about your setup
I have tried on macOS High Sierra (version 10.13 ), Windows 10, and Debian 10 (Buster).
I am slicing with Ultimaker Cura 4.6
and I have Octoprint version OctoPrint : 1.4.0.
Pi is Raspberry pi 1 model B
Printer is Artillery Sidewinder X1 (Evnovo)
Marlin firmware version 2.0.5.3 (stable)

I have also tried connecting the printer directly to a PC using Cura's printer control and it worked perfectly. USB and SD printing works fine as well.

Not a solution but you should really switch to newer model.
The pi 1 and Zero are not recommended since severe performance issues were observed

Log into your pi via ssh then disconnect your printer, connect it again, enter dmesg | tail -n 20 and post the output here.

If you need help with the ssh part


Scroll down and start with the Connecting to Your Raspberry Pi over SSH part.
The first part is already done for you in the octopi image.

Got that. I am ordering a raspberry pi 4 from element14 so I will see if it works with that when it comes.

I have the same problem with Artillery Sidewinder X1 and Raspberry 3B+
Serial connection is simple failing. Same Raspberry Pi connects to other Prusa printers without problem.

Artillery X1 USB port is caught by the TFT Screen Module. To allow USB connection to it you must disconnect the TFT ribbon cable from the Artillery mainboard or cut the Power USB line in the USB cable.(this last I read about but I not tested myself, I test disconnect the ribbon and its work fine).

1 Like

Has anyone verified this? Is this the only way to get OctoPrint working on a Sidewinder X1 V4?

I just got my X1 5 days ago and am surprised that I can't find anything on setting up OctoPrint for it.

1 Like

Hello,

I have this problem since some time now :cry: . I tried several USB cables, octopi 0.18, and I even just tried a new Raspberry Pi 3 B+, same issue, it always fails with no connection to serial port !!!

So, I just tried to downgrade to 1.4.2 and guess what it works now :grinning:, I got my SideWinder X1 back in Octoprint :smiley:

Commands to execute are the next ones:

~/oprint/bin/pip install https://github.com/OctoPrint/OctoPrint/archive/1.4.2.zip
sudo service octoprint restart

From my point of view, there is an issue with 1.5.x being not compatible with SideWinder X1 :confused: . Until they could fix the issue, I'll stay with this version :slight_smile:

Well, if with "they" you mean me (hi, I'm OctoPrint's maintainer), I will not be able to fix any issues if you don't report them properly (which means opening and completely filling out a bug report, and standing by to answer questions and test out stuff).

In general there are no changes in 1.5.x that would explain some printer no longer working that did before, but you never know with all these horrid firmware and electronics in circulation.

Hello, very sorry, not wanted to point any issue and surely not someone at all :confounded: .... This work is amazing !

I fought a long time to have my Sidewinder on Octoprint because this is the perfect tool for 3D printer management. :grinning:
Last update, after I downgraded and the connection to the serial port got back, I just updated Octoprint back to 1.5.3 and I have it working by now. I'll test it later with my other Raspberry. I really don't understand the issue :confused:
In their on other topic where I can put some feedback ?

Was there ever a resolution for this? I just loaded a fresh load of .18 onto a labists pi 4, works fine on sovol, refuses to see sidewinder at all. i even unplugged touchscreen completely and that also did not work.

Run the lsusb command and see if the printer is listed.

If the printer is not listed, unplug it, plug it back in and run dmesg | tail -n 20 and post the output here.

Both of the above need to be performed from the terminal of the Pi, over SSH or connected keyboard & monitor.

pi@octopi : ~ $ sudo lsusb

[sudo] password for pi:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 004: ID 1bcf:28c4 Sunplus Innovation Technology Inc.

Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@octopi : ~ $ sudo lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 004: ID 1bcf:28c4 Sunplus Innovation Technology Inc.

Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@octopi : ~ $ sudo dmesg | tail -n 20

[ 196.342262] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0

[ 196.342301] ch341 1-1.3:1.0: device disconnected

[ 199.710755] usb 1-1.3: new full-speed USB device number 5 using xhci_hcd

[ 199.846999] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[ 199.847022] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[ 199.847041] usb 1-1.3: Product: USB Serial

[ 199.851798] ch341 1-1.3:1.0: ch341-uart converter detected

[ 199.857211] usb 1-1.3: ch341-uart converter now attached to ttyUSB0

[ 541.247615] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

[ 541.249051] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

[ 541.479038] usb 1-1.3: USB disconnect, device number 5

[ 541.479500] usb 1-1.3: failed to send control message: -19

[ 541.480482] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0

[ 541.480525] ch341 1-1.3:1.0: device disconnected

[ 614.243574] usb 1-1.3: new full-speed USB device number 6 using xhci_hcd

[ 614.379621] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64

[ 614.379631] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[ 614.379639] usb 1-1.3: Product: USB Serial

[ 614.385964] ch341 1-1.3:1.0: ch341-uart converter detected

[ 614.389709] usb 1-1.3: ch341-uart converter now attached to ttyUSB0

here is the lsusb with/ then without/ then the dmesg output. it works just fine on the prusa and sovol

i have tried marlin 1.1.9 and 2.0.5.3
to flash you need to disconnect the touchscreen, so i tried starting the sidewinder without touchscreen and connecting pi but i get the exact same behavior whether the touchscreen is on there or not

i am also seeing this in the terminal window

WARNThe received line contains at least one null byte character at position 0, this hints at some data corruption going on

so i smelled a rat in the software. I tried 2 versions of marlin, 4 usb cables, the root cause was......BigTreeTech crappy software, OctoBTT. If i do a clean load of .18 octoprint is just fine. no display on the touch screen but it works without issue
I just confirmed that installing OctoBTT onto a working octoprint server running on a raspi4 w/ 8G Ram will break it and make it no longer work on the artillery yet it does work on my other printers. So this is one bug that is 100% their fault. They have know about it since at least October 2020, it stems from their software trying to default to 115200 baud no matter what. Other than recompiling the software to fix their poor coding not sure there is a fix. they do not seem motivated to fix their problem.