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.

CCSTUDIO: CCS20 Watch Window Missing Import/Export Feature from CCS12.5 Expressions Window

Part Number: CCSTUDIO

Tool/software:

It seems that you cannot import or export watch window variables in CCS20, so you can't import files like "universal_lab_level1.txt". Also if you somehow lose the variables you have entered, then they have to be entered manually. In CCS12.5 you can right click on the expressions window and you get the option to import and export the variables. Is there a workaround / am I missing something? 

  • Hi Ted,

    CCS20 should preserve the "Watch" expressions that you have entered in the "Watch" view the next time the IDE is opened.

    Do you mean that CCS Eclipse allow you to import/export watch expression? I am not able to find how to do this in Eclipse.

    Regards,
    Patrick

  • Hi Patrick. I also have this same issue, so maybe I can add some info.

    For CCS Eclipse... I first saw a reference to this feature in the universal motor control lab (section 3.1.5.2 Setup Debug Environment Windows).

    Sure enough -- if you right click in the Expressions window in CCS 12, you can select "import" or "export" as your options.

    The expressions text file internally (I just did a test export) is basically an XML file that looks like this:

    Also have not seen any way to import this into CCS 20 for debugging.

  • Hi Tyler,

    Thanks for the info, I wasn't able to see the two import/export context menu items until I started a debug session.

    I have filed a jira to track this enhancements for CCS v20, CCSNXT-2326.

    Regards,
    Patrick

  • Thanks Patrick, I appreciate it for the enhancement request!

    As for disappearing watch window items, not entirely sure how to recreate that one or what Ted had seen originally, but from our side seems like it may be tied to the debugger crashing or something that causes a weird program exit path. Will let you know if I can re-create it.