UCD90160 sequencing stipulations

Hi Aaron,

UCD90160 starts monitoring and controlling all rails as soon it is powered up. For example, when turn-on conditions of certain rails are met, UCD90160 will assert the Enable signals of the corresponding rails, then the rails will be turned on. If for any reason a rail is not successfully turned-on, UCD90160 can raise a user-configurable Max Turn On timeout fault. The fault response can be also configured by user, including ignore, shut down, re-sequence, etc.

There are many documents under Fusion GUI -> Help ->  Documentation & Help Center.

Thanks,

Zhiyuan

So I read a help note that said to look under the Other Tab for re-sequencing options and changed it to unlimited and got better results. But, I was adjusting (talked my way out of) the fault responses under the Fault Response Tab and I am right back to where I started. Toggling Rail One does not change the enable on Rail Two.

What is the definition of re-sequence and restart? I was looking for a document that would explain the difference and maybe a step by step example to look at.

Nathan,

Restart means turning off a rail and turning it back on. Restart does not involve other rails. Restart is also called Retry.

Resequence means turning of a rail and its Fault Shutdown Slaves, and then turning back on the rails according to user-defined sequence (time delay, rail sequence-on dependency, GPI sequence-on dependency, etc.)

Ok, so I think I am on the right track now. 

What does Time Between Re-Sequences do? I set it to 96ms for rail 1 and rail 2 is the Fault Shutdown Slave and rail 1 shuts down Rail 2 as expected. When I change the time to 1ms rail 1 does not shutdown rail 2. Why?

Re-sequence is a series of actions that shut down a rail and its Fault Shutdown Slaves, and then re-enable the rails according to sequence-on delay times and dependencies.

Time Between Re-Sequence defines the delay time from a fault shutdown to the following attempt to re-initiate the sequence. The Time Between Re-Sequences period will start to count when all the relevant rails are given Not Power Good statuses. When the time period elapses, a Re-sequence will start. The Enable Re-Sequence Abort checkbox, when checked, will abort Re-sequence if any relevant rail triggers a Max Turn Off warning. However, the Max Turn Off warning will not stop an ongoing Re-sequence.

Fault Shutdown Slaves will only be shut down when the master rail exhausts its Restart attempts. If the master rail is configured to Restart continuously, its slaves will never be shutdown because Re-sequence is only triggered after Restart is exhausted.

You may also go to the Status tab to see if there is any fault raised.

Thanks,
Zhiyuan