3NTR A4V4 Serial Connectivity

Get Help
1

What is the problem?

I am not getting a serial connection. I did a search and only found one instance from 4 years ago that mentions this printer. This user did mention it worked as it should.

What did you already try to solve it?

I tried the wait on start to connect setting, no change
I also increased both time out settings by 50%

Have you tried running in safe mode?

No I am not running any plug ins, straight install

Did running in safe mode solve the problem?

Unknown

Systeminfo Bundle

I have the file but do not see a facility to attach it or upload it. I also have a dmesg file with the printer plugged and unplugged for comparison

Last lines of dmesg with printer connected.
[ 5220.090520] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd
[ 5220.236775] usb 1-1.1: New USB device found, idVendor=0403, idProduct=6001, b cdDevice= 6.00
[ 5220.236799] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber =3
[ 5220.236811] usb 1-1.1: Product: FT232R USB UART
[ 5220.236821] usb 1-1.1: Manufacturer: FTDI
[ 5220.236830] usb 1-1.1: SerialNumber: A505CLRW
[ 5220.243460] ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected
[ 5220.243595] usb 1-1.1: Detected FT232R
[ 5220.247727] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUS B0

lsusb -v command

Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6001 FT232 Serial (UART) IC
bcdDevice 6.00
iManufacturer 1 FTDI
iProduct 2 FT232R USB UART
iSerial 3 A505CLRW
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 FT232R USB UART
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)

Additional information about your setup

OctoPrint version is Version 1.9.3, chrome, octopi is latest on raspberry pi imager 1.0.0

2

Hello @Kevin_Vallelunga !

So you got a used setup?

You can upload the systeminfo bundle with the upload feature of the forum editor:

Upload

3

octoprint-systeminfo-20240402154251.zip (30.7 KB)

4

There are these messages in the log:

2024-04-02 15:33:28,702 - octoprint.util.comm - WARNING - Received line:
2024-04-02 15:33:28,703 - octoprint.util.comm - WARNING - | áqìðÕHt(.8B6«H™HaQΔ=0á;”m&‡~.0Ylôü]qÒ&(AÓjR^Ð~ÂJ=\x00¸M&p¯J%éì]p$obò^aƒ6Ù7ž>/Ÿš77ðMI/NBÁ+zm>¸JújaÿJa%JBh59³l´ú8ÈÿŽÓL´}(Ȕÿ59§l´]8ÈÁÿ[Žtš>ü>»M67ûQzM˜Z Jr¢ìQIþkBÂKA‚ÈMamˆÐ%ÿH”	x]$
2024-04-02 15:33:28,703 - octoprint.util.comm - WARNING - The received line contains at least one null byte character at position 55, this hints at some data corruption going on
2024-04-02 15:33:28,765 - octoprint.util.comm - WARNING - Received line:
2024-04-02 15:33:28,765 - octoprint.util.comm - WARNING - | œ8’zM>˜Z\x00Áÿ’zm>ü\x00é+þM`Šl´]4ü[Bâ[Bâ%!ÿ%!l´ú4¼8%!l´ú4œ8%!l´]$¼8Hrœ¹é\”~R6§ˆ6’MsâjO.äš>˜J\x00AQˆÐAQˆ|Q>˜J\x00‚üH”xú4¼ˆTJl´]$œ%!ˆ|Q˜J\x00aüˆTJl´]“laƒ&"ñ·¨w(`QÈ;6 aÛHHûQìÙMá/>XÑ(2гl*,^Ð(p“Ð}Tp{&2Mƒ&alTzM>˜zjBòjBÂJB‚ÿJA‚jCÒ!l´]$¼8kBl´ú4œkBx}$¼ŽtMÑ8‹60$L´}$
2024-04-02 15:33:28,765 - octoprint.util.comm - WARNING - The received line contains at least one null byte character at position 11, this hints at some data corruption going on
2024-04-02 15:33:28,767 - octoprint.util.comm - WARNING - Received line:
2024-04-02 15:33:28,767 - octoprint.util.comm - WARNING - | <ŽOIBLY"ÈM>Ñ_AÒ«›h8l´útœ(jBâjBâjBx}d¼(jbâZa%jÂl´útœ(júˆ[Q%jBl´]d¼jBâjBòjBl´]ìpMa°M.:œ>ø%\x00ÁOãzm>øJ\x00Oã;MaíˆÐJOã;š>ø%\x00ÁG“:M> Ma;}ùl´ú4ZA‚þjBÂ
2024-04-02 15:33:28,767 - octoprint.util.comm - WARNING - The received line contains at least one null byte character at position 109, this hints at some data corruption going on

Either

  • The USB cable is broken
  • There is a massive EMI source nearby
  • The baud rate is wrong (try with manually setting to 128000)
5

No EMI that I know of
The cable works with the native software but is slow, so there might be something to that, I'll try to find another one.
And I'll try the baud rate, later today and report back

Thanks for the input.

Kevin

6

Ewald,

I tried a new cable and all of the various baud rates presented in octoprint.

I'm getting " State: Offline after error" Is there any other log files to submit or tests you'd like me to perform?

K.

7

Would it help if I put a usb port sniffer on the pi or on my windows computer to see what traffic is occuring?