This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I am use the MotorWare GUI with the HV Kit Rev1.1 to identify my custom motor and spin it with InstaSPIN. I'm using the F2806xM ISO target with the kit. When I select "Automatic ID" in the Identification Method, then click "Identify Motor", it works great and ID's my motor by spinning it, and then I can spin it freely with the other menu options such as "Speed or Torque." However, after ID'ing my motor once, I want to enter it into user.h settings to avoid having to "Automatic ID'ing" my motor by spinning every time I use the MotorWare GUI tool. Therefore, I tried to edit the "user.h" file under the HV Kit InstaSPIN-FOC files as instructed to add my motor and parameters, and the updated the #define to use my motor settings. When I re-run the GUI, select "user.h settings" as Identification Method, and then click "Identify Motor", the parameters that get populated in the green "Identified Motor Parameters" block are not my motor parameters. Instead I see they are USER_MOTOR == Anaheim_BLY172S parameters. I searched everywhere these motor parameters were defined and changed them to my motor parameters to try to trick the software, but this did not work. The parameters that are being pulled into the green block are nowhere to be found in the Motorware HV kit source code as I have commented them out of the code. It's interesting how they are still being pulled into the green block. I feel like this may be a bug in the Motorware GUI.
If you have experience with Motorware, please let me know how you were able to add your motor to user.h and be able to ID it without the tool spinning it the motor.
Thank you in advance!
-Nick Smith
Are you using the InstaSPIN Universal GUI or another tool? If you are using the Universal GUI, can you confirm that after you've rebuilt your project with the updated user.h you've moved and renamed the new .out file into the GUI folder as instructed in the readme?
Whitney
I reread your post and answered my own question about which GUI you're using. What application are you using with the GUI? You may want to switch to the Universal GUI. It has similar functionality with more flexibility in which labs are compatible with it.
Whitney
Thank you Whitney for your reply. I installed the Universal GUI and compiled "Lab2a" - first time Motor ID project in CCS and copied the .out file to the correct directory and changed the name to appProgram.out as instructed in the readme. I tried the "Release" and "Flash" compile. However, it did not spin my motor with the Universal GUI as it does with the original GUI when trying to ID the motor. It tries to measure the resistance but does not get the correct value. Then it tries to measure the inductance and flux, but since the motor never turns, it does not measure these values correctly either. I tried compiling "Lab3a" - load motor parameters with user.h, and when I check the "run" box, my motor parameters are populated in the appreciate boxes. However, it proceeds to measure resistance but as mentioned doesn't measure it correctly and updates the box with the wrong value. I'm not sure which project to load to actually spin my motor as the Universal GUI is not as intuitive as the original GUI. I tried to switch back to the original GUI, but ever since I installed the Universal GUI, I get an error when trying to run the original GUI saying the execute file is not found. I searched for the original GUI in Windows Explorer, and I cannot find it. Please let me know the next steps. Thanks again for your support!
Do you have success running the labs without the GUI, loading the labs through CCS and turning on the enable flags through the Expressions window as described in the lab guide?
Not sure why installing the Universal GUI would remove the other one. The should be able to coexist in the C:\ti\guicomposer\webapps. Are you able to reinstall it?
Whitney