Tetrix/HiTechnic Motor/Servor Controller driver misbehaves.

[GoogleCodeExporter]

I thought I'd respond to:

https://code.google.com/p/nxt-python/issues/detail?id=18

As I have such hardware.

First run: http://sprunge.us/FRJI (motor controller first in chain) (set_power 
worked as expected)

Second run: (motor controller second in chain) http://sprunge.us/fjaA 
(set_power worked, but nothing else)

I thought I might mention as of something like 10 days ago, the lejos SVN has 
100% working drivers for these controllers. I don't have an encoder, so I can't 
test that functionality, but aside from that, I'd be happy to work with any 
improvements you might consider making for this.

Original issue reported on code.google.com by zbuh...@gmail.com on 27 Jul 2012 at 12:48

[GoogleCodeExporter]

Sorry it took a while to get back to you. I've looked at this and, not knowing 
much about the hardware in question, all I can say is that whatever this 
"chain" is, it sounds like a good idea to put the sensor first in it. As for 
debugging, I'd suggest that you refer to the protocol information in the Issue 
18 attachments and try to adjust things yourself, since me trying to work 
without the hardware would be very inefficient. The first thing to do would be 
to make sure I've gotten the addresses right and to check whether the 
identification strings appear to be correct. Take a look at this and let me 
know whether you'd like to work on it or not.

Original comment by marcus@wanners.net on 24 Aug 2012 at 3:27

• Added labels: OpSys-All, Component-Sensors, Series-2.x, Usability