Will not connect to SV04

What is the problem?

I am trying to connect my new Sovol SV04 to Octoprint. Everyone that I have spoken to who has one of these and connected said they plugged in the cable and connected right away. I keep getting Offline After Error .

This is a brand new installation of Octoprint on a Rasp Pi 3b+.

The firmware on the printer and screen are up to date.

I have a USB webcam connected and it works on all the USB ports.

I have tried 3 usb cords, 2 of which were brand new. All heavier cords.

One person told me to set the serial to: /dev/ttyUSB0 and the baudrate to 115200 . I tried those and Auto for all 3 cords.

I am not sure how to proceed.

What did you already try to solve it?

I asked on the Facebook group - no one has told me they have experienced this issue.
I asked the manufacture but did not hear back yet.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

no

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
Here is the system Information
SV04 Sys Invo.zip (35.9 KB)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Here are what I think are the relevant logs
SV04 Serial.log (296 Bytes)
SV04 Log.log (114.9 KB)

I turned on Serial Log and tried again. I don't know if this will have more info but here it is just in case.
SV04 Serial.log (3.8 KB)

I rebooted a number of times, just in case.

You purchased the new ones as data cables?

Yes. I also ordered a new one that is sold as a data transfer cable.
I have another PI 3 that is connected to my other printer. I tried to get it to connect to this one and again it fails.

Try the Pluggable Device Differ and reply with the results.

Got it to produce a log. I used PuTTY. But I can't figure out how to get the log. Or copy/paste it.

or use WinSCP/FileZilla to copy the file.

Got it. Not sure why site is not allowing me to upload a text doc.

---Generated - Tue  8 Mar 16:34:03 CST 2022

===DEV PATHS:
/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
/dev/serial/by-path/platform-3f980000.usb-usb-0:1.1.2:1.0-port0
/dev/ttyUSB0
/dev/char/188:0
/dev/char/189:6
/dev/bus/usb/001/007



===DMESG:
[  589.328442] usb 1-1.1.2: new full-speed USB device number 7 using dwc_otg
[  589.461618] usb 1-1.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54
[  589.461646] usb 1-1.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[  589.461709] usb 1-1.1.2: Product: USB2.0-Serial
[  589.463961] ch341 1-1.1.2:1.0: ch341-uart converter detected
[  589.467538] usb 1-1.1.2: ch341-uart converter now attached to ttyUSB0



===UDEV MONITOR:

KERNEL[589.464681] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2 (usb)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/007
DEVTYPE=usb_device
PRODUCT=1a86/7523/254
TYPE=255/0/0
BUSNUM=001
DEVNUM=007
SEQNUM=1362
MAJOR=189
MINOR=6

KERNEL[589.466164] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=1a86/7523/254
TYPE=255/0/0
INTERFACE=255/1/2
MODALIAS=usb:v1A86p7523d0254dcFFdsc00dp00icFFisc01ip02in00
SEQNUM=1363

KERNEL[589.467013] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0 (usb-serial)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0
SUBSYSTEM=usb-serial
SEQNUM=1364

KERNEL[589.469999] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0/tty/ttyUSB0
SUBSYSTEM=tty
DEVNAME=/dev/ttyUSB0
SEQNUM=1365
MAJOR=188
MINOR=0

KERNEL[589.470649] bind     /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0 (usb-serial)
ACTION=bind
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0
SUBSYSTEM=usb-serial
DRIVER=ch341-uart
SEQNUM=1366

KERNEL[589.471050] bind     /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
ACTION=bind
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
DRIVER=ch341
PRODUCT=1a86/7523/254
TYPE=255/0/0
INTERFACE=255/1/2
MODALIAS=usb:v1A86p7523d0254dcFFdsc00dp00icFFisc01ip02in00
SEQNUM=1367

KERNEL[589.471949] bind     /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2 (usb)
ACTION=bind
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/007
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=1a86/7523/254
TYPE=255/0/0
BUSNUM=001
DEVNUM=007
SEQNUM=1368
MAJOR=189
MINOR=6

UDEV  [589.533188] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2 (usb)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/007
DEVTYPE=usb_device
PRODUCT=1a86/7523/254
TYPE=255/0/0
BUSNUM=001
DEVNUM=007
SEQNUM=1362
USEC_INITIALIZED=589532577
ID_VENDOR=1a86
ID_VENDOR_ENC=1a86
ID_VENDOR_ID=1a86
ID_MODEL=USB2.0-Serial
ID_MODEL_ENC=USB2.0-Serial
ID_MODEL_ID=7523
ID_REVISION=0254
ID_SERIAL=1a86_USB2.0-Serial
ID_BUS=usb
ID_USB_INTERFACES=:ff0102:
ID_VENDOR_FROM_DATABASE=QinHeng Electronics
ID_MODEL_FROM_DATABASE=HL-340 USB-Serial adapter
MAJOR=189
MINOR=6

UDEV  [589.535751] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=1a86/7523/254
TYPE=255/0/0
INTERFACE=255/1/2
MODALIAS=usb:v1A86p7523d0254dcFFdsc00dp00icFFisc01ip02in00
SEQNUM=1363
USEC_INITIALIZED=589535050
ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
ID_VENDOR_FROM_DATABASE=QinHeng Electronics
ID_MODEL_FROM_DATABASE=HL-340 USB-Serial adapter

UDEV  [589.537144] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0 (usb-serial)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0
SUBSYSTEM=usb-serial
SEQNUM=1364
USEC_INITIALIZED=589537012

UDEV  [589.550517] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty)
ACTION=add
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0/tty/ttyUSB0
SUBSYSTEM=tty
DEVNAME=/dev/ttyUSB0
SEQNUM=1365
USEC_INITIALIZED=589549713
ID_VENDOR=1a86
ID_VENDOR_ENC=1a86
ID_VENDOR_ID=1a86
ID_MODEL=USB2.0-Serial
ID_MODEL_ENC=USB2.0-Serial
ID_MODEL_ID=7523
ID_REVISION=0254
ID_SERIAL=1a86_USB2.0-Serial
ID_TYPE=generic
ID_BUS=usb
ID_USB_INTERFACES=:ff0102:
ID_USB_INTERFACE_NUM=00
ID_USB_DRIVER=ch341
ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
ID_VENDOR_FROM_DATABASE=QinHeng Electronics
ID_MODEL_FROM_DATABASE=HL-340 USB-Serial adapter
.ID_PORT=0
ID_PATH=platform-3f980000.usb-usb-0:1.1.2:1.0
ID_PATH_TAG=platform-3f980000_usb-usb-0_1_1_2_1_0
MAJOR=188
MINOR=0
DEVLINKS=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0 /dev/serial/by-path/platform-3f980000.usb-usb-0:1.1.2:1.0-port0
TAGS=:systemd:

UDEV  [589.557013] bind     /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0 (usb-serial)
ACTION=bind
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/ttyUSB0
SUBSYSTEM=usb-serial
DRIVER=ch341-uart
SEQNUM=1366
USEC_INITIALIZED=589556571

UDEV  [589.561876] bind     /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
ACTION=bind
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
DRIVER=ch341
PRODUCT=1a86/7523/254
TYPE=255/0/0
INTERFACE=255/1/2
MODALIAS=usb:v1A86p7523d0254dcFFdsc00dp00icFFisc01ip02in00
SEQNUM=1367
USEC_INITIALIZED=589535050
ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
ID_VENDOR_FROM_DATABASE=QinHeng Electronics
ID_MODEL_FROM_DATABASE=HL-340 USB-Serial adapter

UDEV  [589.598338] bind     /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2 (usb)
ACTION=bind
DEVPATH=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/007
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=1a86/7523/254
TYPE=255/0/0
BUSNUM=001
DEVNUM=007
SEQNUM=1368
USEC_INITIALIZED=589532577
ID_VENDOR=1a86
ID_VENDOR_ENC=1a86
ID_VENDOR_ID=1a86
ID_MODEL=USB2.0-Serial
ID_MODEL_ENC=USB2.0-Serial
ID_MODEL_ID=7523
ID_REVISION=0254
ID_SERIAL=1a86_USB2.0-Serial
ID_BUS=usb
ID_USB_INTERFACES=:ff0102:
ID_VENDOR_FROM_DATABASE=QinHeng Electronics
ID_MODEL_FROM_DATABASE=HL-340 USB-Serial adapter
MAJOR=189
MINOR=6


You might need to manually build the updated drivers for ch34x.

x40:updatech340 [] seems like a decent guide but you'll likely need to adjust.

Before I get that far into it I tried to attach my laptop to the printer using Pronterface. It did not work.

I am not so sure anymore that this is an Octoprint issue.

Did you install the drivers from the vendor?

Yes. It has the latest vender supplied firmware for both the printer and the screen. (yes, you have do both. It's dumb).

Not firmware, drivers. Are you on Windows? This seems to be the latest driver for the CH34x on Windows.

Ok, I am confused. I looked at the earlier article it seemed to be about updating the driver on the Pi. I hooked the laptop up to the printer and used Pronterface to try to connect to it. No Pi or octoprint used.

Did I misunderstand? Was that driver supposed to be installed on the printer itself?

Right. The goal would be to update the driver on the Pi if it's the problem but since you tested on your laptop I assume you are on Windows which would be easier to try a new driver. If it works with the newer driver on Windows then it should on Linux.

Yes.
Is that driver for the printer itself? Does it get installed on the printer?

If not, and forgive my ignorance, does it matter if I am not using the Pi or octoprint at all? When I say I tried to use my laptop to connect to the printer I mean I removed the USB from the Pi, installed Pronterface, attached the USB cord to the laptop, and tried to connect.

I am just trying to understand a little more.

The driver tells windows or linux how they can connect to the usb port of your printers mainboard [simplified]

That means every device that wants to connect to your printer needs a driver to do so.

It's easier to install that driver on windows and test if it works at all than on linux.

Ok.
That makes sense. Will install and report back.

Installed on windows.
Started up Pronterface again.
Tried all the baudrates.
No dice

just to be sure - did you restart after you installed the driver?

Yep. Restarted laptop and then pronterface