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
This should be done with the rest of the MACRO defines. In the Lab 13d example project this is done at the top of the main source file. Typically it is a best practice to use enumerations to define and label the states in your Plan. This allows you to easily size the configuration array to meet your application requirements. In the Lab 13d example project this step is done for you. Sizing the configuration array for your motion sequence is covered in Section 14.4.2.
#define ST_POSPLAN_CFG_ARRAY_DWORDS ((ST_POS_PLAN_ACT_DWORDS * 4) + \
(ST_POS_PLAN_COND_DWORDS * 6) + \
(ST_POS_PLAN_VAR_DWORDS * 6) + \
(ST_POS_PLAN_TRAN_DWORDS * 6) + \
(ST_POS_PLAN_STATE_DWORDS * 5))