Octoprint Serialexception: 'device Reports Readiness to Read but Returned No Data

This topic has been deleted. Only users with topic management privileges can see it.

I am using Octoprint to talk to my controller running 2.03Beta1.

I consistently get disconnects very soon later on connecting.
"SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)"

I don't remember getting these when running Marlin with the same hardware.

The raspi is continued to the +5VFSB on an ATX PSU, the controller switches the PSU on via PS_ON pin.

The webcam and controller are plugged into the USB ports on the raspi.

I have tried the things in the octoprint faq- https://faq.octoprint.org/serialerror

Here are my logs -
Octoprint
https://pastebin.com/2iMmYxSJ

Serial Log-
https://pastebin.com/dYb1Dg37

Volition using M555: Set compatibility help me?

M555 P2

to force Marlin input and output?

At that place are some options that I can configure for communication with the controller. I am tryng to RTFM but its tedious going.
The only RRF specific one is SD carte du jour relative file selection, merely it does non apply to me.

Practise any of these settings or GCODES wait similar they can assist?

Thanks in advance

Dennis

The firmware defaults to Marlin compatibility for responses sent to the USB port; and so unless yous take a dissimilar M555 command in config.m, adding M555 P2 is unlikely to help.

You don't need to flag M0 or M1 as commands to block or pause on, simply you may wish to specify them equally long-running.

Nosotros're sending Gina (the creator of Octoprint) a Duet, then she may be able to help soon.

PS - I know that we have a number of users running Duet + Octoprint with no trouble; but from the logs I see that you are using the LPC1769 port. So I think this result may be specific to that port.

I realize that I am pretty much on my ain with the bleeding edge LPC port, and there is a high likelihood there might be an consequence there. But the consequence only happens when I am trying to print via Octoprint.

The various options in the screenshots I posted are the default settings from Octoprint.

If the upshot IS the LPC port, I feel it would be appropriate for me to exercise my best to endeavour and identify the issue and contribute that fashion.

Part of my reason to try the LPC port was there were many times I felt that Octoprint was bottlenecking things. The printer would stutter while printing like information technology was waiting for a command and I'd get oozing / warts on prints. If I ran the same gcode from SD card - I'd get perfect prints. This happened when sending prints both nether Marlin 1.1.x, ii.0 and now with the LPC port. I have tried all the recommended fixes but no luck I have even swapped out cables, raspi's and SD cards.

Where might I network with the folks using Octoptint + Duet? I'd exist curious to see what their experiences were, both good and bad. I am also interested how DWC and Octoprint play together.

Best regards,

Dennis

I think most people end up switching to using the DWC completely.

What exactly are you getting from Octoprint that you tin't get from the DWC or through some other implementation?

Streaming a print over USB is always going to be problematic.

@phaedrux
the trouble with the lpc port is that most boards do not have a network connection. hence him trying to use octoprint.

The Octoprint logs signal that the USB CDC port driver reported that data was available, yet when Octoprint asked to read that data, none was provided. I am not familiar with the LPC code, but I tin can retrieve of a few possible reasons:

1. A bug in the low-level USB/CDC driver used in the LPC port. If that aforementioned commuter is being used for other firmwares, this seems unlikely.

2. A bug in how the LPC port of RRF uses the API to that driver.

3. It could exist that when Octoprint asks whether data is bachelor, in that location is some; but by the time Octoprint asks for the data, RRF has timed out the buffer because it has been sitting effectually not being fetched for too long (peradventure it was about to time out when Octoprint asked whether data is bachelor). RRF times out buffers of data destined for USB, because otherwise the printer would stall when in that location is no USB client or the client isn't reading messages fast enough. The code that does this is in office Platform::FlushMessages(). You might want to endeavor increasing the value of SERIAL_MAIN_TIMEOUT, which is currently 1000ms.

Still, unless the LPC port does things differently, then at that place is some other buffer in the USB commuter itself. The status returned by the driver should indicate whether there is data in that buffer, regardless of whether or not the main RepRapFirmware code has whatsoever buffers of data ready to send to USB.

We're sending Gina (the creator of Octoprint) a Duet, and then she may be able to help presently.

Brill, I cannot expect.
Struggled trying to setup a timelapse on my Pi, but I appreciate the info the person who did the write up on this forum.

Hopefuly they will exist able to interrogate the Duet over TCP/IP as opposed to USB!
I do like the DWC and my Panel Due, simply OctoPrint is handy for other things too.

@paulhew I recall on linux you can create virtual series port from TCP via socat

@dragonn I am certain someone could!!! I am not a Linux pro, it took me 2-iii days just trying to go Stretch working with a Pi photographic camera and then installing Python3 etc.
I would rather donate to someone or purchase, at least information technology will work and accept the head scratching element out of it!

@dc42 THANK YOU for the lead! I will blindside away at it and communicate this with sdavi too.

I know that the LPC port is teetering on the bleeding edge. I know that its challenged for retentiveness and processes. But I am hopefull that it can be figured out. I know that information technology has reduced MTU/MSS/buffers and only supports ane client at a time, no sliding windows, all this from sdavi.

@Phaedrux yes, I am notwithstanding west/o network still. trying to get my hands on Ethernet module for ReArm in the concurrently. alternative is generic LAN8720 module to try. To my knowledge, the ReArm has a daughter board, X5 has wifi built in, the SKR, MKS boards only have TX/RX on UARTs. So they need a host via USB or an LCD to be functional.

Octoprint to me is more than virtually printer management. I think of DWC as printer control- and I will freely admit that I have but witnessed it on a friend's printer and don't merits much beginning hand knowledge.
The things I like well-nigh it are the plugins for Tempgraphing over time, Heater timeout plugin (non sure if the idle timeout volition control heaters even so), PSU control with ATX power supply which requite me +5VFSB to power controller and Pi and then turn on the 12V chief power via gcode or the LCD panel. Filament managment and inventory by impress is overnice too.

Delight don't take this as me complaining for features, I acknowledge and respect that RRF was not built for some of these tasks, and that some of them need a proper, full diddled processor and subsystem to function. To my knowledge, Duet and RRF were not congenital to provide those things, and that is OK.

Thanks to all for your help so far.

@sinned6915 said in Octoprint Serial Exceptions:

Ethernet module for ReArm in the concurrently.

Ah, sorry almost that. Didn't click for me that you were on ReArm. My bad.

I was but genuinely curious what you find missing from DWC that Octoprint does. When I switched over I missed a few plugins besides, merely by and large they weren't all that important. So thank you for your breakup.

I hope that Octoprint and the Duet can begin to part together more finer. A lot of the ability of Octoprint comes from the fact information technology'south running on more fully featured hardware. The future looks brilliant in that regard.

@phaedrux timelapse, spaghetti detector, and the ability to cancel individual items during a print are my top 3 reasons for using octoprint with my duet.

@antlestxp cool. Makes sense. The only reason I utilise it at present is for the Pallette 2

wilbankscoperfell.blogspot.com

Source: https://forum.duet3d.com/topic/10411/octoprint-serial-exceptions/7

Share this post