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.

getting a f28069 control card to work with HVMTRPFC kit

Other Parts Discussed in Thread: TMDSHVMTRINSPIN, TMDSCNCD28069MISO, MOTORWARE, DRV8301, INSTASPIN-BLDC, TMDSCNCD28035ISO, TMDSCNCD28069ISO, CONTROLSUITE

hi team,

A customer, in cc of this post, wants to get the HVMTRPFC kit to work with  f28069 control card in place of the documented F28035.

we're stuck at the connection stage as the PC doesnt seem to recognize the xds100 connection on JP1, while all recommendation from userguide where followed.

Customer as ccs installed and did get xds100 connection with other ti kits on the same PC.


I would suspect a jumper setting specific to f28069 controlcard, maybe?

also the 2 crosshair guis (HVMTRPFCKIT-BLDC-GUI and HVMTRPFCKIT-PM-ACI-GUI) generate the same error:

"VCP auto-connection is enabled for this interface, but there was a problem retrieving COM ports from your system. This may be due to a WMI corruption" which makes sense if the XDS100 doesnt appear in windows control panel.

thanks for support

  • Hi Olivier,

    Can you let us know whether you are using a:

    • "F28069 controlCARD"
      or a
    • "F2806x ISO controlCARD"?

    It should say one of these two things on the primary-side silkscreen of the cCARD.


    Thank you,
    Brett

  • Hi bret, hope you're well !

    Good point, I guess it's an ISO as customer stated it had a XDS100 onboard. any chance for this conbination to work or are we better off ordering a regular control kit?

    Olivier

  • Olivier,

    The non-ISO cCARD will work more directly with the documentation.  However, since you already have the hardware we should be able to make it work (without too much trouble).

    Can you let me know which revision of the HVMTR kit you have?  I can then help you go through the steps.


    Thank you,
    Brett

  • Hello Brett,

    First of all, thanks a lot for your help !

    I am jumping in the conversation as I think there may have been a confusion with the kit used.

    The right kit is TMDSHVMTRINSPIN, which is provided with F28069 ISO and F28027 cards and embedds the xds100 either on the main board or on the daughter card.

    I think this is the root of the problem here but I will come back to you if we need further help !

    Thanks again !

    Best regards,

    PA

  • Pierre,

    If you have the yellow PCB, black enclosure HVKIT rev1.1

    and you have TMDSCNCD28069MISO controlCARD

    you need to download, install, and run the MotorWare.exe from MotorWare

    When using this CARD + HVKIT combo you need to disable the on-HVKIT emulation and only use the emulator built-in to the controlCARD.

    This is discussed in the QSG documentation which is easy to find through MotorWare.exe

  • Hi Brett,

    Sorry that I am just jumping in on this thread but I am having the same dilemma.  I have a F28069M with a DRV8301 Rev D and want to compare the differences in performance between FOC and BLDC.  I can't seem to get any of the BLDC GUI's to work with the control card.  Do you know how to build either the InstaSPIN-BLDC Code Composer Studio code for F28069M or to rebuild the GUI's for that control card?

    Thanks,

    Michael

  • Michael,

    The M version of the F28069 has the IQmath tables in a different section of ROM.

    In the InstaSPIN-BLDC project you can either pull in the .cmd file for F28069M from MotorWare, or you could pull in the IQmath.lib into the project and make sure it compiles using the .lib instead of using functions from the ROM.

    Or just purchase a different controlCARD

    TMDSCNCD28035ISO

    TMDSCNCD28069ISO

    and use the controlSUITE InstaSPIN-BLDC project as-is.

    The BLDC version will be much, much harder to tune, will have torque ripple, and be less dynamically stable. We introduced InstaSPIN-BLDC while we were developing IntsaSPIN-FOC....once -FOC was released there are very few reasons to use -BLDC on a C2000 class device.

  • Hi Chris,

    Thank you for the advice.  I got the code to successfully build and loaded on the device.  I left the lines in F28035_RAM_BLDC_Int.CMD commented out to force the IQ tables to be placed in RAM is this the correct way to do it?

    /* Uncomment the section below if calling the IQNasin() or IQasin()
    functions from the IQMath.lib library in order to utilize the
    relevant IQ Math table in Boot ROM (This saves space and Boot ROM
    is 1 wait-state). If this section is not uncommented, IQmathTables2
    will be loaded into other memory (SARAM, Flash, etc.) and will take
    up space, but 0 wait-state is possible.
    */
    /*
    IQmathTables3 : > IQTABLES3, PAGE = 0, TYPE = NOLOAD
    {

    IQmath.lib<IQNasinTable.obj> (IQmathTablesRam)

    }
    */


    I tried to do a Level 1 Build and the Graph 1 mod6 counter looked correct but the BemfA, BemfB, and BemfC did not look as specified in the Doc folder guide.  Any ideas what the problem could be?

    Thanks!

  • if you're using an F28069M card I wouldn't be using any files for the F28035
  • The entire InstaSPIN_BLDC project uses 2803x files

    DSP2803x_CpuTimers.c
    F28035_RAM_BLDC_Int.CMD
    f2803xpwm_cntl.h
    BLDC_Int-DevInit_F2803x.c

    just to name a few.

    Are there F2069M versions of all of those files? Is there a version of InstaSPIN-BLDC for the F28069? The motorware files only have the F28069M.CMD file from what I have found.

  • sorry, I guess I misremembered. It looks like for the DRV830x kit only the PM_Sensorless project was dual built with 03x/06x support. You can switch between the project builds inside CCS. I thought this was also done for IS_BLDC
  • So does that mean getting InstaSPIN-BLDC won't work for the F28069M control card? Is there a way I can build it for the 06x? Or is that something I would need additional TI support with?
  • you would need to port it yourself.
    you can see in
    C:\ti\controlSUITE\development_kits\DRV830x-HC-C2-KIT_v105\PM_Sensorless

    how this was done to manage support for 03x/06x in one project