Dynamixel Driver Crash: unsupported operand type(s) for &: 'float' and 'int'

[GoogleCodeExporter]

I'm not sure the correct way to reproduce this, but I believe the error is 
actually a problem with one of our machines somehow, as I have only experienced 
this one one machine. Anyhow, the issue is in the exception_on_error function, 
and I believe this is a bug regardless of what is actually throwing us into the 
function...

The following is the python stack trace: 

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 505, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/opt/ros/electric/stacks/dynamixel_motor/dynamixel_driver/src/dynamixel_driver/dynamixel_serial_proxy.py", line 205, in __update_motor_states
    state = self.dxl_io.get_feedback(motor_id)
  File "/opt/ros/electric/stacks/dynamixel_motor/dynamixel_driver/src/dynamixel_driver/dynamixel_io.py", line 801, in get_feedback
    self.exception_on_error(response[4], servo_id, 'fetching full servo status')
  File "/opt/ros/electric/stacks/dynamixel_motor/dynamixel_driver/src/dynamixel_driver/dynamixel_io.py", line 835, in exception_on_error
    if not error_code & DXL_OVERHEATING_ERROR == 0:
TypeError: unsupported operand type(s) for &: 'float' and 'int'

Let me know if there's anything more I can do to give you more information, 
although I'm still investigating the cause of this, I'm currently thinking 
something wrong at a device driver level of my USB controller chip... 

Original issue reported on code.google.com by haro...@gmail.com on 26 Mar 2012 at 5:30

[GoogleCodeExporter]

Hi, I am not sure how to reproduce this. I can't really how error_code can be 
float, it's just a byte straight from the serial port. Have you encountered 
this issue since reporting?

Original comment by areb...@gmail.com on 17 May 2012 at 6:15

• Changed state: Started

[GoogleCodeExporter]

I have not encountered this problem again. It looks like the problem only arose 
when the kinect was on the same USB controller as the dynamixel stuff. In fact, 
it looks like there's some sort of cross talk of the Kinect w/ any device that 
wants to share the same bus. 

Original comment by haro...@gmail.com on 23 May 2012 at 10:00

[GoogleCodeExporter]

Ok, then I will close this issue as invalid. Thanks for getting back on this!

Original comment by areb...@gmail.com on 23 May 2012 at 10:17

• Changed state: Invalid