Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Chris, Thanks Chris. Yes, I saw it, and actually the normal flow is when we start with ENTRY_PRI which from there we can go to detection of the primary. Going to detection_pri from IDLE_PRI (due to errors that brings us back to IDLE_PRI) which in this case is pending on if secondary is already powered due to the fact that before primary
gone to IDLE_PRI, all 4 pairs where powered etc. So, all is good now. Yair From: Chris Bullock (bullock) [mailto:bullock@xxxxxxxxx]
EXTERNAL EMAIL Hi Yair, The existing logic is intentional. The idea is that you should only end up in IDLE_PRI if there is an error condition or power is intentionally removed
from the primary alternative…..in which case, you should exit back to Main IDLE unless power is applied to the secondary alternative. Thanks, Chris From: Yair Darshan [mailto:YDarshan@xxxxxxxxxxxxx]
Hi guys, I find issue here, please verify. Thanks Yair --------- From IDLE_PRI to START_DETECT_PRI (145.2.5.7, Page 141 line 10)
Comment The condition:
!pwr_app_pri * pwr_app_sec doesn’t make sense that only if the secondary is powered we can go to START_DET_PRI.
The conditions should allow to move to
START_DET_PRI in the following conditions:
i.e. the condition should be:
!pwr_app_pri + !pwr_app_sec
Proposed remedy: !pwr_app_pri * pwr_app_sec
To: !pwr_app_pri + !pwr_app_sec
Darshan Yair Chief R&D Engineer Analog Mixed Signal Group Microsemi Corporation 1 Hanagar St., P.O. Box 7220 Cell: +972-54-4893019
E-mail: <mailto:ydarshan@xxxxxxxxxxxxx>. |