Stephan3 / dwc2-for-klipper

A translator between DWC2 and Klipper
GNU General Public License v3.0
160 stars 38 forks source link

Error: 'dict' object has no attribute 'get_float' #72

Closed brycedjohnson closed 4 years ago

brycedjohnson commented 4 years ago

klippy.log

New dwc2 install coming from an octoprint/octopi. Got that error when adjusting speed factor

image

alfrix commented 4 years ago

Yeah i just updated and yes, Klipper changed a lot stuff since i'm not in the mood of debugging i just reverted back to May 4

if you need help:

sudo systemctl stop klipper
cd ~/klipper
git reset --hard 9a92b346fd81386c54464b45d8310dab972b6bbd
cd ..

gcode=$(sed 's/self.bytes_read = 0/self.bytes_read = 0\n        self.respond_callbacks = []/g' klipper/klippy/gcode.py)

gcode=$(echo "$gcode" | sed 's/# Response handling/def register_respond_callback(self, callback):\n        self.respond_callbacks.append(callback)/')

gcode=$(echo "$gcode" | sed 's/os.write(self.fd, msg+"\\n")/os.write(self.fd, msg+"\\n")\n            for callback in self.respond_callbacks:\n                callback(msg+"\\n")/')

echo "$gcode" > klipper/klippy/gcode.py
cd ~/klipper
make clean
make 
make flash FLASH_DEVICE=yourdevicename
sudo systemctl start klipper
brycedjohnson commented 4 years ago

Thanks @alfrix that appeared to fix it. I'll leave the issue open for now unless someone wants me to close it?

dw-0 commented 4 years ago

+1 on that issue. Something is broken when updating to the newest commit of klipper.

Sending a heater command via DWC2 to my printer gives me the following error:

G10 P0 S120
Operation failed (Reason: 500: Internal Server Error)

What's really weird is, a G10 is usually a retract, so something is really broken when issuing a heating command.

Heating the bed give another error:

M140 P0 S50
Operation failed (Reason: 500: Internal Server Error)

Homing does work, but when moving the axes manually via the buttons in the interface the following error messages occur: Error: 'dict' object has no attribute 'get_commandline' Error: 'dict' object has no attribute '_params'

manu7irl commented 4 years ago

Try to upgrade the dwc2 server files from duet web control website. I am on latest one everything is ok.

On Fri, May 8, 2020, 6:06 PM th33xitus notifications@github.com wrote:

+1 on that issue. Something is broken when updating to the newest commit of klipper.

Sending a heater command via DWC2 to my printer gives me the following error:

G10 P0 S120 Operation failed (Reason: 500: Internal Server Error)

What's really weird is, a G10 is usually a retract, so something is really broken when issuing a heating command.

Heating the bed give another error:

M140 P0 S50 Operation failed (Reason: 500: Internal Server Error)

Homing does work, but when moving the axes manually via the buttons in the interface the following error messages occur: Error: 'dict' object has no attribute 'get_commandline' Error: 'dict' object has no attribute '_params'

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Stephan3/dwc2-for-klipper/issues/72#issuecomment-625860738, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWT4RBAM6LJAFRDLUHVZPTRQQNY3ANCNFSM4M2U7WQA .

BlackStump commented 4 years ago

G10 with Reprap Firmware for which Duet Web Control is design for is for Temperature Control, You need to remember Duet Web Control was never design for klipper. fyi @th33xitus https://duet3d.dozuki.com/Wiki/Gcode#Section_G10_Tool_Offset_and_Temperature_Setting

pluuuk commented 4 years ago

75 might fix this too.

manu7irl commented 4 years ago

G10 with Reprap Firmware for which Duet Web Control is design for is for Temperature Control, You need to remember Duet Web Control was never design for klipper. fyi @th33xitus https://duet3d.dozuki.com/Wiki/Gcode#Section_G10_Tool_Offset_and_Temperature_Setting

Hi man I made a new patch for your script. It is in my forked folder. https://github.com/manu7irl/dwc2-for-klipper You could have a look at it.

BlackStump commented 4 years ago

Thanks, I have done the update

manu7irl commented 4 years ago

all in all @pluuuk got so far that the need for a patch is obsolete! I will test that in the next coming hours

Stephan3 commented 4 years ago

fixed