What is STorM32 NT about?: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* The possibility to replace individual NT modules may reduce costs in case of damage. | * The possibility to replace individual NT modules may reduce costs in case of damage. | ||
* The concept simplifies integration of technological advances: If you need encoders, build and code a FOC motor driver module, if you need a high-quality ultra-low drift IMU module, build and code a high-quality ultra-low drift IMU module, if you need a CHDK camera controller, build and code a CHDK camera controller, and so on. | * The concept simplifies integration of technological advances: If you need encoders, build and code a FOC motor driver module, if you need a high-quality ultra-low drift IMU module, build and code a high-quality ultra-low drift IMU module, if you need a CHDK camera controller, build and code a CHDK camera controller, and so on. | ||
The scheme below shows what could be a typical, fully NT-ized configuration. | |||
One further cool thing about the NT concept is that one can continue to use the widely and cheaply available conventional STorM32 boards. The NT concept is fully compatible with them! Technically this becomes possible because the microcontroller pins available on the I2C port can also be configured as UART pins, turning them into the NT bus. Even though one doesn't need a new controller board, one nevertheless needs new hardware, at minimum one NT IMU module. | One further cool thing about the NT concept is that one can continue to use the widely and cheaply available conventional STorM32 boards. The NT concept is fully compatible with them! Technically this becomes possible because the microcontroller pins available on the I2C port can also be configured as UART pins, turning them into the NT bus. Even though one doesn't need a new controller board, one nevertheless needs new hardware, at minimum one NT IMU module. | ||
The | However, it is pointed out that all one needs to start with is only one NT IMU module to replace the "old" camera IMU. All other modules are optional, and not using them doesn't incur any restrictions in functionality. The rule is simple: Whenever a NT module is found it is used, and when not the conventional hardware is used. For instance, if a 2nd NT IMU module is not on the NT bus, then the on-board IMU or a I2C-based IMU connected to the I2C#2 port is used. Similarly you can continue to use the STorM32's motor driver outputs M0, M1, and M2, or the IR led, and so on. | ||
[[File:Storm32-nt-wiring-scheme-v2x docu.jpg|none|900px|center]] | |||
[[File:Storm32-nt-wiring-scheme-docu-02.jpg|none|900px|center]] | [[File:Storm32-nt-wiring-scheme-docu-02.jpg|none|900px|center]] | ||
Revision as of 14:59, 13 January 2017
One of the major drawbacks of the conventional STorM32 is the reliance on the I2C bus for communicating with the IMU(s), because of it's sensitivity to disturbances from e.g. the motor signal wires (see the I2C Error Compendium). The STorM32 NT provides an ultimate solution by replacing the I2C bus with the NT bus, which hardware-wise is nothing else than just a standard serial TTL UART, but at a quite high baudrate. Since the UART is low resistance and push-pull the disturbance sensitivity is very much lower than for I2C, making it practically error free. Furthermore, even if a transmission error should occur, the controller has no difficulties to recover from it, unlike with I2C.
The additional cool thing about the NT concept is that it does not stop here. As with any bus also the NT bus allows one to not only connect one IMU module but also further modules, such as e.g. a 2nd IMU module, motor driver modules, a camera controller module, and so on. This provides us with a number of further advantages:
- The NT modules can be replaced easily, resulting in extraordinary flexibility in the configuration. For instance, if one needs higher motor power, one just needs to install a NT motor module with higher amperage.
- The NT modules can be daisy-chained, which can result in quite clean wiring, and helps tremendously with e.g. slip rings.
- The possibility to replace individual NT modules may reduce costs in case of damage.
- The concept simplifies integration of technological advances: If you need encoders, build and code a FOC motor driver module, if you need a high-quality ultra-low drift IMU module, build and code a high-quality ultra-low drift IMU module, if you need a CHDK camera controller, build and code a CHDK camera controller, and so on.
The scheme below shows what could be a typical, fully NT-ized configuration.
One further cool thing about the NT concept is that one can continue to use the widely and cheaply available conventional STorM32 boards. The NT concept is fully compatible with them! Technically this becomes possible because the microcontroller pins available on the I2C port can also be configured as UART pins, turning them into the NT bus. Even though one doesn't need a new controller board, one nevertheless needs new hardware, at minimum one NT IMU module.
However, it is pointed out that all one needs to start with is only one NT IMU module to replace the "old" camera IMU. All other modules are optional, and not using them doesn't incur any restrictions in functionality. The rule is simple: Whenever a NT module is found it is used, and when not the conventional hardware is used. For instance, if a 2nd NT IMU module is not on the NT bus, then the on-board IMU or a I2C-based IMU connected to the I2C#2 port is used. Similarly you can continue to use the STorM32's motor driver outputs M0, M1, and M2, or the IR led, and so on.
