SPRUHJ1I January 2013 – October 2021 TMS320F2802-Q1 , TMS320F28026-Q1 , TMS320F28026F , TMS320F28027-Q1 , TMS320F28027F , TMS320F28027F-Q1 , TMS320F28052-Q1 , TMS320F28052F , TMS320F28052F-Q1 , TMS320F28052M , TMS320F28052M-Q1 , TMS320F28054-Q1 , TMS320F28054F , TMS320F28054F-Q1 , TMS320F28054M , TMS320F28054M-Q1 , TMS320F2806-Q1 , TMS320F28062-Q1 , TMS320F28062F , TMS320F28062F-Q1 , TMS320F28068F , TMS320F28068M , TMS320F28069-Q1 , TMS320F28069F , TMS320F28069F-Q1 , TMS320F28069M , TMS320F28069M-Q1
Our example state machine features the following elements:
This will require 83 double words of configuration space. This value is calculated from the above number of elements and the memory usage contained in Table 14-3.
4 Actions * 5 Double Words = 20 Double Words
3 Conditions * 3 Double Words = 9 Double Words
3 Variables * 2 Double Words = 6 Double Words
6 Transitions * 5 Double Words = 30 Double Words
3 States * 4 Double Words = 12 Double Words
Adding this together
20 + 9 + 6 + 30 + 12 = 83 Double Words
The declaration of the SpinTAC Velocity Plan configuration array should be as follows
uint32_t stVelPlanCfgArray[83];
An additional example can be found in the project Lab 6c, Motion Sequence Real World Example: Washing Machine. This also provides an excellent example of how to use enumerations in order to simplify the sizing of the SpinTAC Velocity Plan configuration array.
To size the configuration array for SpinTAC Position Plan you would need to follow the same procedure as outlined above, but use the memory usage for SpinTAC Position Plan.