background image

 

UG:309 

Page 6

The following information is intended to provide the user with a description of the various “soft” 

buttons and user menus available in the Buck GUI.

The “File” menu provides “Exit” as the only option available when left clicking on it. If the user chooses 

“Exit”, a dialog box will pop up to allow the user to confirm their selection. If “Yes” is chosen, the GUI 

will close and Buck GUI will terminate. If “No” is selected, the user will be returned to the main program 

without exiting the GUI.

The “Help” menu provides the current revision of the Buck GUI. There is no interactive user help or 

search utility provided at this time, although there may be expanded help facilities in the future build 

releases of the software.

The “Address” menu will produce a drop down dialog box for the user to be able to select the 

decimal address of the PI33xx‑xx determined by the ADR0 and ADR1 decodes in Table 1. For example, 

if the PI33xx‑xx unit has both ADR0 and ADR1 floating or not connected, the child address will be 

76 decimal or 4C. Configuring ADRO and ADR1 allow for eight addressable locations from 72d to 

79d or 48h to 4Fh.

The “FAULT” button allows the user to read the PI33xx‑xx fault telemetry information. The fault register 

is 8 bits wide with the most significant bit set to logic 0 always. The gray indicator panels for each fault 

on the Buck GUI display will illuminate bright red to indicate the decoded fault(s) for the user, so they 

don’t have to refer to Table 4 for the decoded value. In addition, the binary value of the register will be 

displayed in the “FAULT” window.

The PI33xx‑xx fault logging only occurs when the controller is in normal operation mode. After a fault 

is detected and assessed, the fault is latched into the register so long as the controller V

CC

 is active and 

above the minimum threshold. The controller will take the appropriate action to protect the PI33xx‑xx 

and system based on the type of fault. If for example, the input voltage is high enough to power the 

controller but below the minimum under voltage lock out threshold, the controller will prevent the unit 

from enabling and remain in a low‑power state. Since it has not entered operate mode, the UVLO fault 

will not be logged. If the input voltage is higher than the undervoltage lockout threshold but drops to 

zero, the fault will remain latched as long as there is V

CC

 to the controller. Once the controller V

CC

 dips 

below the minimum value, the fault data will not remain valid. The fault register will be cleared upon 

power on reset. If V

CC

 remains after a logged fault, the fault register must be cleared in order to log any 

new events. A description of the logged faults is as follows:

FLT[0] – VCC_UV:

 if this bit is set, it indicates that the internal power supply for the PI33xx‑xx has gone 

into undervoltage.

FLT[1] – UVLO:

 if this bit is set, the indication is that the input voltage decreased below the 

undervoltage lock outthreshold (UVLO) at some point while the unit was in operate mode. The UVLO 

threshold is defined as the minimum value required for a PI33xx‑xx to be able to meet all specified 

parameters of operation.

FLT[2] – OVLO:

 if set indicates that the input voltage exceeded the over voltage lockout threshold 

(OVLO) at some point while the unit was in operate mode. The OVLO threshold is that value where the 

input voltage is too high for a PI33xx‑xx to be able to meet all specified parameters of operation.

FLT[3] – VOUT_HI:

 if this bit is set, it indicates that the error amplifier input was higher than it should 

be for the programmed output voltage during operate mode, indicating that the output voltage 

may be too high.

FLT[4] – SLOW_IL:

 if this bit is set, it indicates that the error amplifier output was at the positive rail for 

more than 1 ms during operate mode. This means that the load current demand was higher than the 

maximum output current available from the PI33xx‑xx.

FLT[5] – FAST_IL:

 if this bit is set, it indicates that the peak current in the output inductor was higher 

than the maximum peak current allowed during operate mode. It is an indicator of output short circuit 

or inductor failure.

FLT[6] – OTP:

 if this bit is set, it indicates that the PI33xx‑xx internal temperature exceeded the 

maximum temperature for safe operation during operate mode and that the PI33xx‑xx shut down to 

prevent damage.

Table 4

 

Fault register assignments

FLT[7]

FLT[6]

FLT[5]

FLT[4]

FLT[3]

FLT[2]

FLT[1]

FLT[0]

0

OTP

FAST_IL

SLOW_IL

VOUT_HI

OVLO

UVLO

VCC_UV

Summary of Contents for PI33 EVAL1 Series

Page 1: ...ompatibility The PI33xx xx is hardware compatible with the NXP I2C bus specification Version 2 1 Standard Mode 100kHz January 2000 for all bus timing and voltage resistors levels up to 5 5V maximum The PI33xx xx is configured as an I2C child device with no internal bus pull up or pull down Interface Software Tool The Buck GUI software tool offered by Vicor allows quick access to the one time progr...

Page 2: ...ort The use of USB expansion ports especially those that are heavily loaded is not recommended The LinkM interface can be mounted directly to the PI33xx xx evaluation board using a straight 4 pin header see Figure 1 Users who wish to connect the LinkM in this manner will need to use a male to female USB extension cable This method works very well and is the preferred method Other users may wish to...

Page 3: ...ing of ADR1 and ADR0 A zero or one indicates the logic strength of the bit and NC indicates that the pin is floating or not connected The HEX column indicates the final address in hexadecimal while the DEC column is the decimal address value Table 1 Addressing options See Table 3 where VCC PI33xx xx fixed internal 5 1V bias rail PGND SGND SYNCO PGD Q1 Q2 ADR0 SDA VCC ADR1 EN SYNCI TRK EAO ADJ VS1 ...

Page 4: ...ttom half of Figure 4 Table 2 User accessible registers Table 3 I2C port specifications Figure 3 Error message due to missing LinkM upon software start Name Address HEX Bits Description TSTMDE 2 0 18 3 Test mode register used for burning bits into non volatile memory MRGN 3 0 19 4 Volatile register for output voltage margining FLT 7 0 1A 8 Fault Register read only FREG_CLR 1B 0 Register for cleari...

Page 5: ...be powered on using the proper input voltage value and enabled by the user Failure to apply input voltage will result in the error message shown in Figure 28 see Buck GUI error messages section upon pressing any of the soft buttons on the screen The LinkM should not be removed or installed with the power already applied to the PI33xx xx Always power down the PI33xx xx prior to installing or removi...

Page 6: ...in in a low power state Since it has not entered operate mode the UVLO fault will not be logged If the input voltage is higher than the undervoltage lockout threshold but drops to zero the fault will remain latched as long as there is VCC to the controller Once the controller VCC dips below the minimum value the fault data will not remain valid The fault register will be cleared upon power on rese...

Page 7: ...nges made to this register are dynamic and will change as soon as the command is sent The user simply enters the value they wish to margin and then clicks margin Any value sent to this register will be lost as soon as power is removed Note that margining down 20 or more in one step may cause a VOUT_HI fault which is a normal condition Fault Telemetry Command Structure The PI33xx xx command structu...

Page 8: ...are two bytes of data The first byte is the address of the FREG_CLR register The second byte is the data The next message is a read of the address This read is performed by the LinkM and is not needed to make the transaction complete This command could be sent by a generic I2C interface as START WRITE 98h 2 Bytes 1Bh 00h followed by STOP START WRITE 98h 2 bytes 1Ah 00 followed by STOP START READ 9...

Page 9: ...hird fault is OVLO Figure 11 shows the I2C bus capture of dynamically margining the PI33xx xx output voltage down 20 by entering 1100 in the MARGIN dialog box and clicking the MARGIN button Note that 0Ch is sent in the second data byte which is the margin value Figure 8 I2C bus capture input undervoltage fault register read using Buck GUI and LinkM Figure 9 Buck GUI capture of input undervoltage f...

Page 10: ...e the delay setting between a synchronizing signal rising or falling edge as selected applied to the SYNCI input and the SYNCO output rising edge applied as a fraction of the main system clock period MP The most significant bit SYN 3 determines which edge trigger occurs A 1 indicates rising edge and a 0 indicates falling edge As an example if the MP value is 1µs and the SYNC dialog box reads 1101 ...

Page 11: ... the output inductor to provide zero voltage switching The rising edge of SYNCO defines the beginning of T1 and can be observed in Figure 13 The rising edge of SYNCO is synchronized to SYNCI rising or falling edge as programmed plus any delay desired Figure 13 shows the timing relationship of SYNCO SYNCI and the phase node VS with default timing and phase delay Note that the node VS in the schemat...

Page 12: ...the PI33xx xx The KBIT2 register may only be written with a 1 entered into the dialog box This register can not be read it is write only Burning this register will prevent making any more changes to any register even if there are unused bits available to burn Start of T1 ZVS Turn on of high side MOSFET External sync pulse falling edge Start of T1 ZVS Turn on of high side MOSFET External sync pulse...

Page 13: ...UG 309 Page 13 Figure 14 PI33xx xx SYNC 1000 timing Figure 15 PI33xx xx SYNC 1111 1 4MP ...

Page 14: ...UG 309 Page 14 Figure 16 PI33xx xx SYNC 1110 1 3MP Figure 17 PI33xx xx SYNC 1101 1 2MP ...

Page 15: ...UG 309 Page 15 Figure 18 PI33xx xx SYNC 1100 2 3MP Figure 19 PI33xx xx SYNC 1001 3 4MP ...

Page 16: ...e each bit is burned correctly Users that write their own software or operate from a different GUI will need to consider this In addition power should not be removed from the PI33xx xx during the burn process The Buck GUI will prompt the user when to enable and disable the target Enabling and disabling is done using the EN pin One important note to consider is that if the enable polarity has been ...

Page 17: ...e user enables the PI33xx xx it should power up normally and the burned in changes shall take effect The user may read the register that was just programmed by clicking on the SYNC button Buck GUI should show the new burned in values read back from the SYN 3 0 register as shown in Figure 24 If an error message occurs or the incorrect results are obtained refer to the section titled PI33xx xx Error...

Page 18: ...able the target PI33xx xx It should be pointed out that the SYN 3 0 register had already been programmed to 0010 on the PI33xx xx target prior to the enable polarity change Note that the first two bus transactions occur when the target PI33xx xx is enabled and the final transaction occurs when it is disabled Failure to follow this exact sequence will prevent successful storage of the desired confi...

Page 19: ...leting this step no further changes can be made to the PI33xx xx It is very important to double check all settings before clicking the BURN button If the user makes a mistake in a setting after clicking on the BURN button the instructions for enabling and disabling the unit that are prompted by Buck GUI should be IGNORED by leaving the target enabled and clicking OK to each pop up dialog box This ...

Page 20: ...her the PI33xx xx or LinkM I2C interface is malfunctioning It will also occur during program execution if the PC to USB or LinkM USB hardware or software interface is malfunctioning If the USB portion of the interface is at fault Buck GUI can not recover and will continue to display this error even if the USB interface problem is corrected Buck GUI will need to be closed and restarted to reestabli...

Page 21: ... GUI to report the appropriate error If this error occurs after receiving the Missing or Malfunctioning I2C Interface Error it is critically important to ensure that you shut down power to the PI33xx xx and exit the Buck GUI prior to attempting to reprogram again Adhering to this step can possibly avoid programming the wrong register values Burn Skipped Error The error message shown in Figure 30 o...

Page 22: ...ns and products and to implement adequate design testing and operating safeguards for your planned application s and use s VICOR PRODUCTS ARE NOT DESIGNED AUTHORIZED OR WARRANTED FOR USE IN LIFE SUPPORT LIFE CRITICAL OR SAFETY CRITICAL SYSTEMS OR EQUIPMENT VICOR PRODUCTS ARE NOT CERTIFIED TO MEET ISO 13485 FOR USE IN MEDICAL EQUIPMENT NOR ISO TS16949 FOR USE IN AUTOMOTIVE APPLICATIONS OR OTHER SIM...

Reviews: