• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 713 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.

HVMTRPFCKIT GUI Connection Problems

Nicholas David
Prodigy 60 points
Other Parts Discussed in Thread: CONTROLSUITE

C2000 Support,
I have been having connection problems while using the TMDSHVMTRPFC development kit with the provided GUI.  The GUI is v1.0, available from ControlSUITE v7 and v8.  I am not sure what the board revision is; we ordered them a few months ago.  The flash image on the F28035 ControlCARD is v1, as provided in ControlSUITE v7 and v8.
I have tried two different kits on two different computers.  One runs Windows 7, and the other is Windows XP 2002.  I have only run the GUI with the PMSM motor that the kit is tuned for.  I have re-flashed the cards multiple times.
When I open the GUI, I can connect to the board.  I know it is connected because the status shows "connected" and the DC Bus voltage updates.  Sometime, the connection is immediately lost; not even enough time to start the motor.  When this occurs, I can still click "disconnect" and it disconnects.  I can then reconnect by clicking connect, but this doesn't always result in actually being able to run the motor.  I have also noticed that changing any setting in the GUI, such as the the slider for the set speed, the graphs, etc., seems to make the connection fail.  Overall, operation is very unpredictable.  In the morning, when running the system for the first time for the day, there doesn't seem to be any problems.  But after running for several minutes, it is very difficult to get the motor to even start turning, let alone change speed.
There is no consistency as far as a specific routine of operations which will cause the connection to fail.  Sometimes it works, and sometimes it doesn't.  
I have changed Windows firewall settings to allow the GUI, installed the latest drivers, and verified the USB serial port configuration.  I have also checked the regional language settings as described in another post.
Sometimes I get a message that port "ComX" is unavailable.  Sometimes there is a message that the "Target Code is incompatible with GUI".  Sometimes there is a message that the GUI encountered a critical error and is forced to close. 
Attached is a document containing screenshots of the errors we are receiving, with some notes about when they occurred.
I am not aware of software updates other than what is available in ControlSUITE v8.  From what I have searched on the internet, this is not a problem for other people.  Both computers I am using are connected to our university network; maybe there are network configurations which could be causing the inconsistent connection.
Thank you for your help,
Nick
  • 0
    TI__Mastermind 43730 points

    Nick,

    It does seem you have checked for all the right things, the v1 is the only version of the GUI, we have had some issues with the GUI on different machines, however most have been linked to the regional language settings. Few things to keep in mind when using this GUI are

    1. If you use the sliders, don't keep the left mouse clicked and vary the speed. Just vary it quickly to the new position and release the button. When clicked the GUI constantly tries to update the values which may cause the connection to fail.

    2. We only tested the GUI with XP and did not use Windows 7, so i am not sure if this could be causing any problems.

    3. GUI does require .Net framework installed on the machine, did you check if you have an updated version of the .Net

    4. The Gui is constructed to be connected from a power start, so i will recommend powering off the board completely once the connection is lost and then reconnecting.

    5. I would also recommend that you start looking at the CCS projects and use them to start spinning the motors in the meanwhile. The GUI is just meant for a visual demo and i will not recommend spending a lot of time getting it working on your machine.  

    Also just as a note for future kits we are moving to a more robust GUI development platform, to avoid such situations.

    I apologize for the inconvenience.

    Regards

    Manish Bhardwaj