Other Parts Discussed in Thread: C2000WARE
I created a custom project based on the Universal Motor Control Lab.
I copied files from the Universal Motor Control Lab into the custom project, so that I can make modifications there. These are local copies of the files within the custom project, and are no longer links to the original files in the original project at C:\ti\c2000\C2000Ware_MotorControl_SDK_4_02_00_00\solutions\universal_motorcontrol_lab
I have updated the custom project INCLUDES search paths to local paths within the custom project (and no longer pointing to the original project)
As an example of what I'm seeing, I modified MOTOR_Vars_t in the custom project to add a couple of data fields. The project builds without error, and I do not see compiler errors when accessing these data fields.
However, when running the custom project, <something> is still referring to the original MOTOR_Vars_t structure, so that data access is becoming offset. For example, if the original struct might have been:
typedef struct{
oldmember1,
oldmember2
} EXAMPLE_STRUCT_t
And the new struct might be
typedef struct{
oldmember1,
newmember,
oldmember2
} EXAMPLE_STRUCT_t
If I try to access newmember in, the compiler does not complain. But at runtime, if I try to access newmember, the data read is oldmember2.
This is what is happening with MOTOR_Vars_t from the universal motor control project. Runtime does not use the updated MOTOR_Vars_t struct from the custom project.
As a test, I deleted the .settings folder in the custom project. On opening the project, CCS created a new .settings directory, and populated it with settings from the original project. So there is still some link from the custom project to the original project.
My overall goal is that the custom project should use the custom/local MOTOR_Vars_t for runtime, and NOT use the MOTOR_Vars_t from the original project. Any suggestions on how I can break this link and get the custom project working correctly?
Thanks!
Thanks!
