search

hellerbarde / OctoPrint-Network-Printing

35 stars 2 forks source link

'write_timeout is currently not supported' using pyserial #2

Open Insertion-git opened 3 years ago

Insertion-git commented 3 years ago

Probably an issue unique to my setup.

Connection fails. Terminal returns 'write_timeout is currently not supported' when connecting to my RFC device hosted via pyserial. Commenting out the following resolved my issue:

"write_timeout": 0,

Otherwise works great with my setup, thanks for the plugin!

jdfalk commented 2 years ago

Not just you. I had the same error.

redPanther commented 1 year ago

Otherwise works great with my setup, thanks for the plugin!

I couldn't resolve the issue. I commented out the "write_timeout" in the plugin. Then octoprints comm.py throw the error ... then I uncommented "write_timeout" in octoprint, but this did not work too. It connects, but more or less nothing happens:

on pi rfc2217_server.py

INFO:root:Connected by 192.168.178.140:33248
INFO:rfc2217.server:client accepts RFC 2217
INFO:rfc2217.server:NOTIFY_MODEMSTATE: 17
INFO:rfc2217.server:client accepts RFC 2217
INFO:rfc2217.server:NOTIFY_MODEMSTATE: 16
INFO:rfc2217.server:set baud rate: 250000
INFO:rfc2217.server:set data size: 8
INFO:rfc2217.server:set parity: N
INFO:rfc2217.server:set stop bits: 1
INFO:rfc2217.server:changed flow control to None
INFO:rfc2217.server:changed DTR to active
INFO:rfc2217.server:changed RTS to active
INFO:rfc2217.server:purge in
INFO:rfc2217.server:purge out
INFO:rfc2217.server:set baud rate: 250000
INFO:rfc2217.server:set data size: 8
INFO:rfc2217.server:set parity: N
INFO:rfc2217.server:set stop bits: 1
INFO:rfc2217.server:changed flow control to None
INFO:root:Disconnected

on octoprint terminal:

Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to port rfc2217://xxxx:9999, baudrate 250000
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0x7fa0af563eb0, open=True>(port='rfc2217://xxxx:9999', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
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
prfiredragon commented 1 year ago

I have the same issue on octoprint. I chage the

"write_timeout": 10,

on the plugin and on octoprint

busy protocol support detected to 10

Temperature interval (polling) 10 s When printing or idle

at the moment is working

I am using a esp8266 26MHZ Crystal