• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 30 subscribers
  • Views 735 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.

CCS/BOOSTXL-DRV8323RS: GraphicalUserInterface

Thomas Hecht
Expert 1080 points
Part Number: BOOSTXL-DRV8323RS
Other Parts Discussed in Thread: DRV8323, DRV8305, DRV8320, C2000WARE

Tool/software: Code Composer Studio

Hello,

In my design, I use a Picolo F28027F in conjunction with the DRV8323RS, and I use InstaSPIN software. As a user interface, I have the GUI InstaSPIN_UNIVERSAL, which works quite well together.

Now it comes, the GUI does not support the DRV8323 what I would like to customize. Can I use the current GUI (InstaSPIN_UNIVERSAL) as a basis and import it into the GUI composer V2 or is there another way to start? I would like to keep the current setting options and layout of InstaSPIN_UNIVERSAL.  Can I add the DRV8323 as a registration page to the current InstaSPIN_UNIVERSAL, much like the DRV8305 SPI does? Or do I have to start from scratch, if so, are there any tutorials that you would recommend? The latest version of the GUI composer is only a cloud version isn't it?

In case I want to modify the current GUI do I have stick on the version 1? How can I use this GUI version, do I need to install CCS 5.5 therefore?

Best regads

Thomas

  • 0
    TI__Guru 53745 points

    If you zip up the GUI folder you should be able to import it into GUI Composer v1 and edit it to add a new DRV8323 page. CCS 6.2 was the last version of CCS to support the GCv1 designer tool, so you'll have to use that or older. Unfortunately there's no way to migrate a GUI built with GUI Composer v1 to v2. You're correct about GCv2 being one of our cloud tools at dev.ti.com.

    The other option you could consider is to take the new MotorControl SDK-based Universal GUI (search for InstaSPIN in the Gallery--https://dev.ti.com/gallery/) that was created using GCv2 and use it as a starting point (it has a page for supporting DRV8320). The variable names associated with the fields will be different than the MotorWare-based version you're working with, but it may be better than starting completely from scratch if you wanted to try GCv2?

    Whitney

  • 0 in reply to Whitney Dewey
    Expert 1080 points

    Thank you

    have nice weekend

  • 0 in reply to Thomas Hecht
    Expert 1080 points 
    Hello again,

I tried Version2.
    So I added a number box and linked it to the engine variable (gMotorVars.VdcBus_kV). 
    When I run the application (GUI ver2) then gMotorVars.VdcBus_kV is displayed as an integer value in the number field. 
    Whereas when using GUI Composer, gMotorVars.VdcBus_kV is displayed as Q24 value multiplied by 1000? 
    Where is the conversion done in version1 (Q24 value multiplied by 1000)?
    best regards
    Thomas
  • 0 in reply to Thomas Hecht
    TI__Guru 53745 points

    In the version 1 GUI there's a app.js file that contains some conversion functions. One of these functions (DivideQ24_multiply1000) is set as the pre-processing function for the box containing gMotorVars.VdcBus.kV.

    You can do something similar in version 2. If you look at the index.js file in the Gallery GUI I mentioned above, there are a few examples of number boxes that required some extra calculations. There's also a tutorial video that explains custom data processing: https://youtu.be/tqpZ47vhKaM

    Whitney

  • 0 in reply to Whitney Dewey
    Expert 1080 points

    Thanks,

    where are this functions set in version 1?

    Best regards

    Thomas

  • 0 in reply to Thomas Hecht
    TI__Guru 53745 points

    The code is in app.js. It's mapped to the number box by going to the "Binding" setting and then clicking the "..." button in the Value row and filling in the "Pre Processing Function" box.

    Whitney

  • 0 in reply to Whitney Dewey
    Expert 1080 points

    thank you Whitney

    Best regards Thomas

  • 0 in reply to Thomas Hecht
    Expert 1080 points

    Hello Whithney,

    I'm still trieing to convert the GUI V1 (that come with the Lunchpad TMS320F28017 + DRV8305) to GUI V2 (as a base I use the C2000Ware_MotorControlSDK_InstaSPIN_GUI from the galellery ).

    First I tryed to display th Bus voltage, As you suggested erlier I tried manipulate the displayed value in the index.js file.

        gc.databind.registry.bind('widget.ti_widget_numberbox_busvoltage.value',
            {
             BusVoltage: 'my_xds.gMotorVars.VdcBus_kV'
            },
            function(values) {
              var toQ24 = values.BusVoltage/(Math.pow(2,24));
              var result = Math.round(toQ24 * 1000);
              return (result);
              
            }
        );

    but I can't see anny effect on the value.

    I fiddelt with the binding of the gMotorVars.VdcBus_kV in the gaphical interface of the compose binding/leafing binding. but I don't get a result that makes sense.

    Do I have to keep the binding in the graphical Interface or is the binding done later in the index.js file? I tried to keep it in the graphical interface but than I only get a 0 displayed.

    Do I leave the binding, I only get the row value displayed (convertion is missing)?

    Have you got an idea were to look at?

    best regards

    Thomas

  • 0 in reply to Thomas Hecht
    TI__Guru 53745 points

    I just left the value binding in the properties box blank (or set to the default 0) for the things I was calculating in .js. I'm not spotting any issues in your code. I think opening the developers tools in your browser (l hit F12 in Chrome) when you run the application can sometimes display error messages that might be helpful for tracking down issues. See if there are any hints in there?

    Whitney