For me, as a driver developer, I find the HT I2C interface generally easier to use but the MS one usually has more features.
From a user perspective, the MS NXT-G blocks tend to be less refined than the HT ones.
HT is not always as forthcoming with publishing all of the specs of a sensor, like MS is. I may have an NDA with HT but that doesn't get me an access all areas pass either
The MS sensors do tend to have the "tinkerer" in mind more than the HT ones, there's usually not as much to tweak with them (see first point)
The HT sensors are LEGO certified, which covers many aspects of the sensor, including the NXT-G blocks they provide
I have a great relationship with both these companies and I know how much effort they both put into their development.
- Xander
| My Blog: I'd Rather Be Building Robots (http://botbench.com)
| RobotC 3rd Party Driver Suite: (http://rdpartyrobotcdr.sourceforge.net)
| Some people, when confronted with a problem, think, "I know, I'll use threads,"
| and then two they hav erpoblesms. (@nedbat)
mattallen37 wrote:Yes. Xander's first comment was right, it is indeed an NXTPortal.
I've written a driver for this thing about a 100 times now. The trouble is, each time I activate it, I get transported back to a moment in time where the driver hasn't been written yet. It's getting a bit tedious.
- Xander
| My Blog: I'd Rather Be Building Robots (http://botbench.com)
| RobotC 3rd Party Driver Suite: (http://rdpartyrobotcdr.sourceforge.net)
| Some people, when confronted with a problem, think, "I know, I'll use threads,"
| and then two they hav erpoblesms. (@nedbat)
| My Blog: I'd Rather Be Building Robots (http://botbench.com)
| RobotC 3rd Party Driver Suite: (http://rdpartyrobotcdr.sourceforge.net)
| Some people, when confronted with a problem, think, "I know, I'll use threads,"
| and then two they hav erpoblesms. (@nedbat)
mattallen37 wrote:Yes. Xander's first comment was right, it is indeed an NXTPortal.
I've written a driver for this thing about a 100 times now. The trouble is, each time I activate it, I get transported back to a moment in time where the driver hasn't been written yet. It's getting a bit tedious.
- Xander
Just insert a *-1 in somewhere and transport to a moment in the future when the driver is already done.
mightor wrote:I think HT and MS have different pros and cons:
For me, as a driver developer, I find the HT I2C interface generally easier to use but the MS one usually has more features.
From a user perspective, the MS NXT-G blocks tend to be less refined than the HT ones.
HT is not always as forthcoming with publishing all of the specs of a sensor, like MS is. I may have an NDA with HT but that doesn't get me an access all areas pass either
The MS sensors do tend to have the "tinkerer" in mind more than the HT ones, there's usually not as much to tweak with them (see first point)
The HT sensors are LEGO certified, which covers many aspects of the sensor, including the NXT-G blocks they provide
I have a great relationship with both these companies and I know how much effort they both put into their development.
- Xander
Matt wrote:This is one thing you almost definitely WOULD use, and really like.
Thanks guys, I have previously looked very little at Mindsensors, and you have now brought them to my undivided attention. Now I have quite a desire to purchase a number pad . I believe that I have missjudged Mindsensors, and no longer believe that just because they lack a plastic shell, that they are not professional. But looking back at them, I realize that the circuitry is quite concealed, and that the only reason is that they're just not shaped the way that LEGO and HiTechnic sensors are. Thank you for showing the light in an area which I was previously oblivious.
Last edited by haydenstudios on 11 Mar 2011, 21:47, edited 2 times in total.