[Solved] Random USB / ftdi disconnection with Raspberry π 3 model B+


#1

Many disconnection tty disconnection "usb_serial_generic_read_bulk_callback"

Haphazardly, I have USB/TTY disconnection.

Jun 30 21:56:02 octopi kernel: [11817.708624] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Jun 30 21:56:02 octopi kernel: [11817.708737] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

After this message print is stoped.

I change Repetier server to Octoprint, π host, USB cable, boot parameters

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)

Raspberry π 3 model B+
OctoPrint version : 1.3.8
OctoPi version : 0.15.1
Tronxy 3D Printer : P802M_8_V1.6
Repetier firmware-0.91
Controller board : Melzi_3.0_V3

# octoprint.log
| Send: N10272 G1 X110.573 Y108.182 E675.68049*96
| Recv: ok 10270
| Recv: ok 10271
| Send: N10273 G1 X110.352 Y107.799 E675.69693*103
| Send: N10274 G1 X111.910 Y110.497 F7800.000*93
| Recv: ok 10272
| Send: N10275 G1 F4800*67
| Recv: Error:expected line 10273 got 10274
| Recv:
| Recv: Resend:10273
2018-06-30 19:54:10,536 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 20:09:10,537 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 20:24:10,539 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 20:39:10,540 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 20:54:10,543 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 21:09:10,544 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 21:24:10,547 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 21:39:10,558 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 21:54:10,559 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2018-06-30 21:57:01,729 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-06-30 21:57:31,740 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-06-30 21:58:01,771 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-06-30 21:58:31,790 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-06-30 21:59:01,824 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.

Parameters tested (one by one / each time have randomly failure):
dwc_otg.fiq_fix_enable=0
dwc_otg.fiq_fsm_mask=0x0
dwc_otg.lpm_enable=0
dwc_otg.speed=1
ftdi_sio.ndi_latency_timer=255
max_usb_current=1


#2

Replace π3 b+ with π3 model B v1.2

2 prints without error....


#3

Some prints latter, no errors :slight_smile:

Soo, if you have a π3 B+ and USB connexion loss. Replace it with lower model and your life can be more sweety :stuck_out_tongue:


#4

Hm... The more people get RPi3+, the more weird errors I hear about in that combination.

Starting to feel that that model has some issues still and seriously wondering if I should recommend against using it on the download page.


#5

I usually have really bad luck with tech, and have to tweak it in all sorts of random ways just to get it to work normally, and I'm probably jynxing myself for saying this, but, I must be have gotten the only functional B+ that the factory ever put out cuz, so far, the only issue mine has given me was that ONCE it locked up on a print, and that was when it was %99 completed during a power failure

Of course, now that I said that it'll start smoking...


#6

@OutsourcedGuru posted a link to a (very long) discussion in the official RPi forums. What I gathered from it was that you need to run "sudo rpi-update" on the Rpi3+ to get the latest firmware. Also running "sudo apt-get update", "sudo apt-get upgrade" is probably a good idea as well.


#7

I already did this,

As I say upper, I try many modules options.

I also think the change board controller, command new FTDI chip to change it (yes very hot unsold old and
sold new one SMD chip).

But if I only change the π and works, it’s done for me now.