fischertechnik community forum

RDS 4 Beta
http://www.microsoft.com/robotics/
Fischertechnik is a partner is the MS-RDS project.

Hello Carel,

Fischertechnik is a partner is the MS-RDS project

But from what fact do we know this? From the fact that their RDS service is lousy and outdated, so that *you* had to write a better one? Isn't fischertechnik totally inactive regarding RDS?

Greetings,
Stefan

Hi Stefan,
Nice point for discussion during the FT-Convention at coming weekend .

What is your analysis of the development of the TX-C firmware and interface API?
The quality of TX-C the I2C connectivity (only 2 bytes or 2 words)?
The camera, the upwards compatibility with the FtLib API?

What is your analysis of the development of the RoboPro not extendable software?
If I compare the graphic presentation (GUI) in RoboPro with MS-RDS VPL than RoboPro is a little bit out dated.

I guess that the North America market will not be so happy with the long delay in the growth process of the TX-C firmware.
With the closed TX-C internal software Msc Germany does not really left his visiting card in the market.

LEGO does a much better job in the I2C smart sensor and actuator area and also in the Labview and MS-RDS area. National Instruments is making use of their good relation with LEGO during the NIDays in Europe now.

If you want to play with I2C why don't you get a µC (AVR,ARM,whatever...) like everyone else? This way you can have full control over your Hardware.

@Defiant
You remark is not so clear to me. I am using the Microchip range if you don't mind.
But that is not the issue here.
The issue is the TX-C (microcontroller system) and the specification as describt in the User Manual.

fischertechnik did promiss I2C connectivity but does not deliver.
For the off line use of the TX-C this is an important issue: connecting the TX-C with smart actuators and smart sensors.
LEGO has implemented I2C too and LEGO knows a nice range of smart actuators and smart sensors.
A lot of people are making use of the LEGO I2C connectivity (byte array and not a limitation to 2 bytes or 2 words).

@Stefan

But from what fact do we know this? From the fact that their RDS service is lousy and outdated, so that *you* had to write a better one? Isn't fischertechnik totally inactive regarding RDS?

That fischertechnik and Studica partners are in this "research" project, could we know from the Microsoft MS-RDS website.

I created some prototype for that project (TX-C, TX-L and RoboInterface family) as kind of hobby and in collaboration with fischertechnik. I also develop a simulation of a FT-bot for Studica Canada; this also as kind of hobby.
This work is time consuming and because of a change in my professional live I am not able to spend enough time to this project to bring the output on a better and more consistent level anymore. I have not the budget and means for that developing work on the moment.

The biggest bottleneck is the missing of a native dotNet framework version of the FtMscLib and the FtLib.

The prototype for the TX-C has a nice layered structure which enable me to deal with the a general purpose interface inside the MS-RDS philosophy.

The I2C connectivity is for the MS-RDS integration not important. I am developing a I2CService that integrates I2C devices directly in MS-RDS by using I2C to USB interface.