• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 124 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

UCD3138ALLCEVM150: UCD3138ALLCEVM150:

UCD3138ALLCEVM150: Help understand the LLC code

Zihang Xie
Prodigy 31 points
Part Number: UCD3138ALLCEVM150

Tool/software:

I'm using UCD3138ALLCEVM150 this board, I may need this document explaining how the LLC code works, can you send it to me? In addition, the LLC firmware I downloaded contains many kinds. X0 file, I want to know which one I need to burn for this board I'm using. X0 file, looking forward to your reply, good luck!

  • 0
    TI__Expert 6200 points

    Hello Zihang,

    We do not have a detailed document that explains exactly how the UCD LLC firmware works. Most of the firmware is just configuring the peripherals since the control algorithm is relatively simple. However, you can view this E2E post on an example on how the ADC works in the LLC firmware.

    Please see this E2E post on instructions on how to set up the UCD firmware using Code Composer Studio and Fusion Studio GUI. The instructions will explain how to select the correct .x0 file that you will flash.

    Regards,

    Jonathan Wong

  • 0 in reply to Jonathan Wong
    Prodigy 31 points

    Hello Jonathan,

    What I want to know is the relationship between the digital and analog quantities of these parameters in the code, I think this will help to modify the parameters for debugging later, and I would appreciate it if you could provide an explanation or a link to it.

    Best wish,

    Zihang Xie

    #define VOUT_0 				(6144)
#define VOUT_OV_FAULT_LIMIT (7168)
#define VOUT_OV_WARN_LIMIT 	(6656)
#define VOUT_UV_FAULT_LIMIT (1536)
#define VOUT_UV_WARN_LIMIT 	(5632)
#define IOUT_OC_FAULT_LIMIT (40)
#define IOUT_OC_WARN_LIMIT 	(30)
#define TEMP_OT_FAULT_LIMIT (110)
#define TEMP_OT_WARN_LIMIT 	(90)
#define VIN_OV_FAULT_LIMIT 	(430)
#define VIN_OV_WARN_LIMIT 	(400)
#define VIN_UV_FAULT_LIMIT 	(320)
#define VIN_UV_WARN_LIMIT 	(350)
#define IIN_OC_FAULT_LIMIT	(7)
#define IIN_OC_WARN_LIMIT	(4)
#define PGOOD_ON_LIMIT		(5888)
#define PGOOD_OFF_LIMIT		(5632)
#define VIN_ON_LIMIT		(320)
#define VIN_OFF_LIMIT		(310)
#define TON_RISE 			(30)
#define VOUT_0_TRAN 		(0x9B33)
#define DEADTIME1			((int)(DT1 / TDPWM + 0.5))
#define DEADTIME2			((int)(DT2 / TDPWM + 0.5))
#define DEADTIME3			((int)(DT1SR / TDPWM + 0.5))
#define DEADTIME4			((int)(DT2SR / TDPWM + 0.5))
#define SAMPLERATE 			((int)(TSAMP / TDPWM / 16 + 0.5))
#define MINPER				((int)(TH / TDPWM / 16 + 0.5))
#define MAXPER				((int)(TL / TDPWM / 16 + 0.5))
#define TSRMAX	 			((int)((TSR - DT2SR) / TDPWM / 16 + 0.5))

  • 0 in reply to Zihang Xie
    TI__Expert 6200 points

    Hello Zihang,

    I will respond by tomorrow.

    Regards,

    Jonathan Wong

  • 0 in reply to Jonathan Wong
    TI__Expert 6200 points

    Hello Zihang,

    The E2E post that I mentioned above goes through an example of how the IIN_OC_WARN_LIMIT is used. You will need to read the entire E2E thread to understand how a measurement of the primary side current leads to the IIN_OC_WARN_LIMIT being used. The other variables in the list are used in similar ways. Many of them are used in the Fusion Studio GUI and can be changed in the Fusion Studio GUI.

    Regards,

    Jonathan Wong

  • 0 in reply to Jonathan Wong
    Prodigy 31 points

    Ok, thank you for your patience in explaining.