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
The SpinTAC components that make up InstaSPIN-MOTION need to be configured for your specific application. This is a simple process. The specific configuration details of the SpinTAC components in InstaSPIN-MOTION will be covered in subsequent sections of this document. The spintac_velocity.h and spintac_position.h header files provide a singular interface to include the SpinTAC components in your project. These files contain the macro definitions, type definitions, and function definitions required to setup the SpinTAC components. Including these files in your project is the first step to using the SpinTAC components that make up InstaSPIN-MOTION. The file that should be included is dependent on the type of control. If the application is a velocity application, spintac_velocity.h should be included. If the application requires position control, spintac_position.h should be included.