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.

Is there a script/source mismatch (char vs int) experienced on the GMotorVars.Flag* scripting console window declarations on lab02a

Other Parts Discussed in Thread: MOTORWARE, DRV8312

I am using

F28069M controlCARD

DRV8302-HC-EVM Rev D

controlSUITE3.4.0

motorware_1_01_00_16

CCS 6.2.0.00050

C2800 Compiler Tools 16.6.0

Concern:

 these 4 vars:

  • GMotorVars.Flag_enableSys  
  • GMotorVars.Flag_Run_Identify
  • GMotorVars.Flag_enableForceAngle
  • GMotorVars.Flag _enablePowerWarp

these are showing as unsigned char in the scripting console

as opposed to the page 36 info on lab 2a showing as   unsigned int

I get red LEDs on GPIO31 (flashing) and GPIO34 (steady)

Is there some undocumented fix required in the source or a setting?

I am using a BLDC motor (assumes many PMSM settings)

We get errors trying to runGMotorVars.Flag_enableSys  =1 and GMotorVars.Flag_Run_Identify =1

thanks

Jim

  • I would like to know if MotorWare "17" that Chris Clearman had listed a goal date to release by Friday 10/28 could regression test this? thanks

  • we will take a look to see if we can replicate this issue. I rarely use the scripting (I use the GUI inside CCS) but I've never seen it reported. If anything it may have to do with CCSv6.2 which we haven't been using. The CCS releases usually have a surprise or two for us....

  • Chris - what version of CCS have you been using in regression? Is it a specific 5.? or 6.1.5 ? I saw your earlier post about CCS 6.1.3, i.e. e2e.ti.com/.../519654

    thanks
    Jim (ex TIer 1982-1997)
  • Jim,
    6.1.1

    I'm going to see if we can test 6.2.0 before the release
  • Jim,

    I'm unable to reproduce your issue on my end. Here's my testing setup:

    CCS Version: 6.2.0.00050
    MotorWare 16 base install
    F28069M ISO ControlCard
    DRV8312 EVM rev D
    Running proj_lab02a
    JavaScript file: C:\ti\motorware\motorware_1_01_00_16\sw\solutions\instaspin_foc\src\proj_lab02a.js

    When I press "Resume" with Expressions "Continuous Refresh" enabled, I'm able to manipulate both Flag_enableSys and Flag_Run_Identify with no errors being thrown.

    As to your point about unsigned char in the expressions window and unsigned int in the lab manual - it doesn't make a difference whether the expression has been declared an int or a char. On C2000 architecture, both int and char are 16bit variables, per page 106 of this document: www.ti.com/.../spru514j.pdf

    While it would make a difference on a device like MSP430, char and int are interchangeable on C2000 due to its architecture.

    Have you tried with a different CCS install? Also, please try manually add gMotorVars.Flag_enableSys and gMotorVars.Flag_Run_Identify to the expressions window and see if execution happens as expected when manipulating them that way.

    Sean
  • Sean:

     I was instructed to attempt rollback to ccs v6.0.1 (but I am running into a JVM startup issue now). Please advise

  • Jim,


    I was able to correctly load the JavaScript file on v6.2, which you had indicated you had tried initially. I use v6.1.1 for my day-to-day usage, but you should be able to use any version aside from v6.1.3. With v6.2 being largely untested by the team, rolling back could be a good idea. I'm not sure how to clear up a JVM startup issue, I would need more information from your end to figure out if this is an issue I can help with or if we need to get help from the CCS team themselves.


    Sean