Test case for the FtMscLib I2C connectivity.
Verfasst: 16 Apr 2011, 21:41
I am looking forward to the I2C bus connectivity on the TX-C and of course the I2C specification in the FtMscLib.
One and a half year ago I already develop a test case for this connectivity.
I choose an AMIS stepper controlle. This because it is fully covering the old fischertechnik stepper motor.
So this test case serves a very practical objective and it has a direct relation with fischertechnik.
Hereby a nice example of a I2C device that is very useful to connect with the TX-C
This will be a fine test case for the upcoming I2C connectivity of the TX-C.
See also my stepper project.
How to receive or send the data from/to this I2C stepper controller with the FtMscLib API/TA (or RoboPro)?
See the I2C section in the AMIS steppercontroller datasheet, it is very complete.
Although the I2C protocol does not limit the number of bytes for sending or receiving, this stepper example shows that atleast a number of bytes will be needed. In this case 8 -10 bytes.
A limitation as far as only one or two bytes is not in accordance with the I2C bus specification (2007).
An example of a good set of I2C operations that is covering the I2C standard
http://ww1.microchip.com/downloads/en/D ... 20v2-4.pdf
For LEGO Mindstorm experts I heard that the LEGO API is covering an array of bytes.
One and a half year ago I already develop a test case for this connectivity.
I choose an AMIS stepper controlle. This because it is fully covering the old fischertechnik stepper motor.
So this test case serves a very practical objective and it has a direct relation with fischertechnik.
Hereby a nice example of a I2C device that is very useful to connect with the TX-C
This will be a fine test case for the upcoming I2C connectivity of the TX-C.
See also my stepper project.
How to receive or send the data from/to this I2C stepper controller with the FtMscLib API/TA (or RoboPro)?
See the I2C section in the AMIS steppercontroller datasheet, it is very complete.
Although the I2C protocol does not limit the number of bytes for sending or receiving, this stepper example shows that atleast a number of bytes will be needed. In this case 8 -10 bytes.
A limitation as far as only one or two bytes is not in accordance with the I2C bus specification (2007).
An example of a good set of I2C operations that is covering the I2C standard
http://ww1.microchip.com/downloads/en/D ... 20v2-4.pdf
For LEGO Mindstorm experts I heard that the LEGO API is covering an array of bytes.