search

donovan6000 / M33-Fio

The ultimate OctoPrint plugin
GNU General Public License v3.0
125 stars 38 forks source link

Can't Connect to Printer #172

Closed Alaric323 closed 7 years ago

Alaric323 commented 8 years ago

Greetings Donovan,

After updating to the latest version of OctoPrint (1.2.14) and M33 Fio (1.2), I can no longer connect to the printer. The log given when attempting to connect is as follows:

Changing monitoring state from 'Opening serial port' to 'Connecting' Send: N0 M110 N0_125 Recv: ok 0 Changing monitoring state from 'Connecting' to 'Operational' Send: N0 M110 N0_125 Recv: ok 0 Send: M21 Recv: ok Recv: wait Send: N0 M110 N0*125 Recv: ok Send: M117 Unexpected error while writing to serial port: TypeError: 'unsupported operand type(s) for +=: 'int' and 'NoneType'' @ comm.py:_do_send_without_checksum:2039 Recv: PROTOCOL:RepRap FIRMWARE_NAME:iMe FIRMWARE_VERSION:00.00.01.06 MACHINE_TYPE:Micro_3D SERIAL_NUMBER:BK16041502050017 Connection closed, closing down monitor Changing monitoring state from 'Operational' to 'Offline: TypeError: 'unsupported operand type(s) for +=: 'int' and 'NoneType'' @ comm.py:_do_send_without_checksum:2039' Closing down send loop

The printer was running with the latest iMe Firmware (00.00.01.06), but just to make sure it wasn't the firmware, I used M33 Manager to install the official M3D firmware, version 2016040401. Same error occurred.

Any advice?

donovan6000 commented 8 years ago

I didn't even notice a new version of OctoPrint got released. Let me try it out and see what's causing this.

donovan6000 commented 8 years ago

It's all fixed now in M33 Fio V1.3.

Alaric323 commented 8 years ago

Thanks for the speedy resolution. Once the update is pushed to OctoPrint's plugin repository, I'll get back to you on how it performs.

Alaric323 commented 8 years ago

The connection problem is indeed fixed, however while in the middle of an automatic full calibration, when adjusting the levels of the corners, it seems to lose connection to the printer. The only fix is a reboot of both the printer and the OctoPrint server. Sadly, it doesn't give an error of any type, and the logs don't mention anything.

donovan6000 commented 8 years ago

Someone just reported something similar on M3D's forum. Seems like something changes in how OctoPrint handles communication timeouts. I'm looking into it now.

donovan6000 commented 8 years ago

Just released M33 Fio V1.4 that fixes this.

Alaric323 commented 8 years ago

Nice changelog. :P Testing it out now.

Alaric323 commented 8 years ago

Froze in the middle of a print. Here's the log for when it happened. octoprint (2).txt

Sorry for bringing up so many issues.

donovan6000 commented 8 years ago

The log doesn't show any reason why it froze, so it was probably a firmware issue. If your using M3D's V2016040401 firmware then downgrade to M3D's V2016010812 firmware since the former has been known to cause this issue occasionally. The newest version of iMe firmware hasn't been tested much, so it could also potentially have caused it to freeze.

Alaric323 commented 8 years ago

Was on iMe 1.06, downgraded to the January 2016 firmware and am printing again. I'll update what happens.

donovan6000 commented 7 years ago

It's been a while since anyone has responded to this issue, so I'll probably close it in a couple of days. Let me know if you still have any interest in testing/fixing this issue.