Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when running without heated bed #399

TopherMan opened this issue Mar 2, 2014 · 2 comments


None yet
2 participants
Copy link

commented Mar 2, 2014


I'm working on a new printer, and since I use PLA, I've neglected to attach a heated bed. However, Octoprint will not connect when the heated bed is disabled or disconnected. I get the following error:

2014-03-01 18:16:15,490 - octoprint.util.comm - ERROR - Something crashed inside the serial connection loop, please report this in OctoPrint's bug tracker:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.1.0_dev-py2.7.egg/octoprint/util/", line 618, in _monitor
    self._callback.mcTempUpdate(self._temp, self._bedTemp)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.1.0_dev-py2.7.egg/octoprint/", line 444, in mcTempUpdate
    self._addTemperatureData(temp, bedTemp)
  File "/usr/local/lib/python2.7/dist-packages/OctoPrint-1.1.0_dev-py2.7.egg/octoprint/", line 359, in _addTemperatureData
    "actual": bedTemp[0],
TypeError: 'int' object has no attribute '__getitem__'

This seems to occur when either a heated bed is not defined (and M105 returns only hotend temp) or is defined and not connected (and M105 returns B:inf for the bed portion).

For reference: this is with the devel branch on Raspbian, and my firmware is Smoothie.

foosel added a commit that referenced this issue Mar 3, 2014

Changed handling of bed temperatures
Will now be left unset if not detected (instead of dying a horrible death), modified frontend to not display bed settings in such cases. While at it also (hopefully) fixed "Target: off" for bed issue.

TODO: Support repetier's "TargetBed:", "TargetExtr%n" syntax

Fixes #399, partially solves #360

This comment has been minimized.

Copy link

commented Mar 3, 2014

This should be fixed now in devel, please test and confirm.


This comment has been minimized.

Copy link

commented Mar 4, 2014

Yup, works perfectly. Thanks again!

@TopherMan TopherMan closed this Mar 4, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.