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
SpinTAC Velocity Plan does not have a maximum number of elements that can be configured. The limit is based on the amount of memory that you would like to commit to the configuration of SpinTAC Velocity Plan. This is done in order to be both efficient as to how SpinTAC Velocity Plan is using the system memory and be flexible to allow for custom configurations of the element. Each element of SpinTAC Velocity Plan has a different memory foot print. These are collected in Table 14-3.
Plan Element | SpinTAC Velocity Plan (double words) | SpinTAC Position Plan (double words) |
---|---|---|
Actions | 5 | 5 |
Conditions | 3 | 3 |
Variables | 2 | 2 |
Transitions | 5 | 7 |
States | 4 | 7 |
This additional flexibility requires you to declare a configuration array whose address needs to be passed into SpinTAC Velocity Plan. This configuration array needs to be sized according to how many elements are in your Plan. Table 14-3 provides the memory requirements for each element. It is a best practice to declare enumerations for the Plan elements that you wish to use. This makes it simple to calculate the amount of memory that is required for the configuration array.