• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 492 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.

TMDSSOLARPEXPKIT: F28035

Roger Bell
Intellectual 440 points
Part Number: TMDSSOLARPEXPKIT


I took the hardware used in the solar EMU and designed hardware for 250W.  The hardware uses a Piccolo LaunchPad.  I have loaded the code from the Solar Explorer Kit into the LaunchPad.  I checked the PWM signals the the power stage and they are what I expect.  My question is how can I continue to test the code in the LaunchPad to verify the signals are on the correct pins:

1.  When I added the LaunchPad to the hardware one of my drivers on my hardware shorted and failed.  I did some test of the hardware before adding the LaunchPad to my hardware.  I was planning to us the 3.3V and 5V from my hardware to power the LaunchPad.  This may not be the best approach.

2.  Is it possible to change the duty cycle for the code in the LaunchPad using an external source?

3.  Is it possible to run the code open loop at a fixed duty?

Thanks for the help,

Roger

  • 0
    TI__Mastermind 43730 points

    Roger,

    I would recommend you can start with understanding the code. 

    In the Main.c file you will notice the net terminal connection

    // PWMDRV_BuckBoost block connections
    PWMDRV_BuckBoost_Duty1=&Duty1; //Duty1;

    the duty1 is coming from the controller..

    if you want to operate it in open loop, you will need to create a new variable and point that to the PWM Duty net terminal

    rest you will need to debug and test..