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.

LAUNCHXL-F2800137: Universal Motor control lab 1

Part Number: LAUNCHXL-F2800137
Other Parts Discussed in Thread: BOOSTXL-DRV8323RH, TMS320F2800132, SYSCONFIG

Hello TI experts, 

I'm running Universal Motor Control Lab 1 and following the tutorial on below page:

https://www.ti.com/video/series/motor-control-SDK-universal-project-and-lab.html

I'm using LaunchXL-F2800137 and boostxl-DRV8323RH kit to run the BLDC motor with sensorless FOC method.

In the expressions window, I'm getting an error under systemVars.fastype "member 'fastType' not found at (systemVars).fastType". Screenshot is attached. 

I'm using motor control sdk version 5_00_00_00. 

When I change the variable "flagEnableRunAndIdentify" from 0 to 1, nothing happens. Instead, the variable changes value to 0 again. I'm expecting PWM output to be at 50% at this stage according to lab 1. 

Could you please advise on this issue? 

Thanks. 

  • Hi Rahul,

    Did you connect motor in build level 1? Please disconnect the inverter with motor for build level 1. 

    When I change the variable "flagEnableRunAndIdentify" from 0 to 1, nothing happens. Instead, the variable changes value to 0 again.

    This variable changed back to 0 as there is a fault indicated by "motorVars_M1.faultMtrUse.all".

    Thanks,

    Jiaxin

  • Hello Jaixin, 

    Motor is not connected. 

    Thanks. 

  • Hello Jiaxin, 

    1. As informed earlier motor is not connected. 

    2."motorVars_M1.faultMtrUse.all" had overcurrent issue. After Changing S2 position it is cleared. I enabled flag "motorVars_M1.flagEnableRunAndIdentify" and I can see PWM at 50%. 

    3. There are 3 issues (and possibly more) as of now: 

    a. systemVars.fastype "member 'fastType' not found at (systemVars).fastType": this error is still present

    b. Voltage offset are not near to 0.5V.

    c. PWM values are different than indicated in lab manual.

    Could you please advise the solution? 

    Thanks. 

  • Hi Rahul,

    "motorVars_M1.faultMtrUse.all" had overcurrent issue. After Changing S2 position it is cleared. I enabled flag "motorVars_M1.flagEnableRunAndIdentify" and I can see PWM at 50%. 

    Glad that you have cleared the issue.

    systemVars.fastype "member 'fastType' not found at (systemVars).fastType": this error is still present

    For the issue a, You don't have to worry about this variable. This variable is not available in the F280013x example code.

    For the issue b, what is the source of ADC reference voltage?

    For the issue c, the manual is just an example with another device. As long as you are getting 50% PWM, the PWM should function properly.

    Thanks,

    Jiaxin

  • Hello Jiaxin, 

    Thanks for your reply. 

    I have not made any other changes to code or kit apart from S4 and S2 configuration. After going through a similar topic here

    As I see in "hal.c" ADC reference is set to 3.3V internal. However, the bus voltage is being read correctly as 24V. 

        // LAUNCHXL-F2800137 based kits
        ADC_setVREF(obj->adcHandle[0], ADC_REFERENCE_INTERNAL, ADC_REFERENCE_3_3V);
        ADC_setVREF(obj->adcHandle[1], ADC_REFERENCE_INTERNAL, ADC_REFERENCE_3_3V);

    I have not mounted 47nF at C9, C10 and C11. Is it related to this issue? 

    Thanks again, 

    Rahul. 

  • Hello Jiaxin, 

    I mounted capacitors C9, C10, and C11 as 47nF. I see that voltage offsets are showing the correct value now. 

    Lab 1 is completed. I have one last question. 

    Finally, we have to migrate this project to TMS320F2800132 (F2800132RHBR) 32 pin device which is cheaper an smaller. 

    I'm following these video tutorials here. But it starts with having a .sysconfig file, which is absent in the current project. Snapshot attached. 

    Could you please advise how we migrate the project to another device? 

    Thanks. 

  • Hi Rahul,

    You may notice there are two different folders within the solutions folder, one is "universal_motorcontrol_lab" and another one is "universal_motorcontrol_syscfg". The syscofig tool that the video talked about is a GUI can be used to configure the peripherals and select the motor control methods, now it only supports F28002x and F28003x devices. Please use the example code in "universal_motorcontrol_lab" and configure through "hal.h" according to your customized hardware for your case. 

    Thanks,

    Jiaxin

  • Thanks Jiaxin for your support!!