• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 609 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F2806: SpinTAC/GUIComposer values not setting

Mathew Maher49
Expert 2125 points

Part Number: TMS320F2806
Other Parts Discussed in Thread: MOTORWARE

When running the InstaSpin GUI Composer, I'm getting repeated failures on the SpinTAC 1: Startup Inertia identification (2004). The user guide suggests increasing ramp time, which is default to 10: however, whenever I increase it (eg 25), the length of time taken to fail remains the same and 10 is re-inserted back into the GUI. 

It looks like the settings are not adjustable on this screen: is this correct, or is there an updated version which would correct this?

Mat

  • 0
    TI__Guru** 116880 points
    Did you use lab02b to identify motor parameters, and use lab12a to identify the inertia first before you run SpinTAC for motion control? Or would you like to follow the Quick Start Guide of InstaSPIN-Motion GUI to implement automatic ID to identify these parameters of motor. The guide can be found in motorWare folder if you have installed it on your PC.
  • 0 in reply to Yanming Luo
    Expert 2125 points
    I'm struggling to find lab02b: although its mentioned frequently in the documentation, when I check the sw resources they all start at lab05c upwards (I'm using the HV Kit).
  • 0 in reply to Mathew Maher49
    TI__Genius 17175 points
    Sounds like you're investigating the projects in the "instaspin_motion" sub-folder of the "solutions" directory. You'll want to also investigate the "instaspin_foc" sub-folder, you will find previous labs in that directory. For devices with an 'M' suffix, both "instaspin_foc" and "instaspin_motion" projects are relevant to the device as 'M' (which denotes InstaSPIN-MOTION) is a superset of 'F' (InstaSPIN-FOC) devices. In short, 'M' devices can run all of the InstaSPIN projects in both "solutions" directories

    Sean
  • 0 in reply to Sean Bigley
    TI__Guru** 116880 points
    Just wanted to check in and see if there is any update from your side, I haven’t heard from you for a week, so I’m assuming you were able to resolve your issue. Please let me know if you have any questions. We would like to close this thread if no any further questions. Thanks.
  • 0 in reply to Yanming Luo
    Expert 2125 points
    Apologies for the lack of respsonse - currently covering two peoples jobs so it's fits and starts...

    This 'kind of' resolves the issue: I found the lab02a bits. However, it'd be really useful if you guys could spend another 1/2day on the GuiComposer application: it's a good starting point (and much better to show the management an easy interface), but basic usability issues are really limiting it. For eval purposes, its good not to need CCS!

    cheers

    Mat