elma rugged microtca test

7/31/2019 ELMA Rugged Microtca Test

1/31

ELMA Trenew

Shock and

Vibration Tests

November 2007AS, FF


2/31

Ruggedized MicroTCAShock and vibration tests by ELMA Trenew Electronic

Ruggedized MicroTCA - 1 - AS, FF

Contents

1 Introduction .............................................................................2

2 Test equipment.........................................................................3

2.1 System ................................................................................ 3

2.2 Backplane............................................................................. 4

2.3 Shock absorber ..................................................................... 4

2.4 Load Board ........................................................................... 5

2.5 Mechanical Load Board ........................................................... 6

2.6 MCH .................................................................................... 72.7 Power Module........................................................................ 7

2.8 Module Fixing........................................................................ 7

2.9 Testing machines................................................................... 8

2.9.1 Shaker ....................................................................... 8

2.9.2 Shock test machine...................................................... 9

3 Test procedure........................................................................10

3.1 Sine Vibration (AC1 IED 61587-1)........................................10

3.2 Random Vibration (AC2 VITA 47) .........................................10

3.3 Shock (AC1 IEC 61587-1) ...................................................11

3.4 Shock (AC2 VITA 47)..........................................................11

4 Test results.............................................................................12

4.1 Sine Vibration ......................................................................12

4.2 Random Vibration.................................................................12

4.3 Shock test (AC1 IEC 61587-1) .............................................14

4.4 Shock Test (AC2 VITA 47)...................................................14

5 Conclusion ..............................................................................15

Appendix A Vibration profile (sinusoidal).................................16

Appendix B Vibration profile (random) ....................................18

Appendix C Shock profile (AC1 IEC 61587-1) ........................20

Appendix D Shock profile (AC2 VITA 47)...............................21

Appendix E MCH Log ................................................................22


3/31



1 Introduction

The MicroTCA system architecture is not only dedicated for the telecom

market, but also for industrial and even for rugged applications like

transportation and MIL/AERO applications.

The following tests should show the capabilities that the ELMA MicroTCA

systems can withstand shock and vibration tests that are required. To

meet these requirements, the system and daughter cards have to be

prepared.

The system that was used is a specially adapted ATR system with aMicroTCA card cage. The AMCs have to be modified with special screwable

front panels, so that they could be fixed with captive screws to the

extrusions. Other cards, like MCH and PM are fixed with screws and

washers.


4/31



2 Test equipment

2.1 System

The device under test is the ELMA Ruggedized MicroTCA system. The

system is an ARINC 404A full size ATR long. It includes a MicroTCA card

cage. The mechanic was designed according to meet the following MIL

standards:

MIL-STD 810 E for shock and vibration

MIL-STD 461 for EMI


5/31



2.2 Backplane

The backplane that was included into the system is the ELMA MicroTCA

Cube backplane for rugged environments. To withstand higher shock and

vibration values, the AMCs can be fixed on the extrusions. The backplane

can contain up to six AMC cards, one MCH and one Power Module.

2.3 Shock absorber

Shock absorber can be mounted below the system to decrease the force

to the system.


6/31



2.4 Load Board

The load boards that were used are ELMA full size load boards for

industrial application. The front panels are modified to be able to screw

them to the extrusions of the card cage.

The load boards are designed to be full compliant with the MicroTCA.0 1.0

specification and are capable to fulfill the complete management via IPMI.


7/31



2.5 Mechanical Load Board

The mechanical load boards are based on the ELMA load boards. To fit the

ruggedized MicroTCA specification, the resistive load was removed and

mechanical loads were fixed on the base plate. The mechanical loads are

according to the MicroTCA.1 D0.5 specification with a weight of 264g (Full-

Size, Single-Width; For multiple slot test). These load boads are full

functioning intelligent load boards.


8/31



2.6 MCH

The MCH that was used in the system was the NAT-MCH-GbE (one

tongue). This MCH was prepared by fixing the ribbon cable with silicon

material.

2.7 Power Module

The Power Module that was used was a CorEdge Networks PM

(CEN-MPWR-4840). It was also prepared by fixing higher devices like

aluminum electrolyte capacitors with silicon.

2.8 Module Fixing

The Modules that have no special front panel, which could be screwed to

the extrusions, are fixed with a screw and washers on the top and on the

bottom of the cards.


9/31



2.9 Testing machines

All tests were made at the ICT Fraunhofer institute in Berghausen,

Germany.

2.9.1Shaker

Inv.-nr: 612

Shaker RMS SW 6005

Charge Amplifier Bruel&Kjaer 2626

Accelerometer S/N 848930


10/31



2.9.2Shock test machine

Inv.-nr: 610

Shock Test Machine AVCO SM 110-3

Charge Amplifier Bruel&Kjaer 2626

Accelerometer S/N 848928

Inv.-nr: 030

Oscilloscope Hewlett/Packard 54 602A


11/31



3 Test procedure

After each test period, the system was completely checked for mechanical

and electrical damage. An electrical test was performed to ensure the

functionality of the system. For this reason, the system was switched on

with all slots populated with cards. The activation of any card should show

that the system was not damaged at any position.

3.1 Sine Vibration (AC1 IED 61587-1)

2-9Hz: Magnitude 9.2mm

9-200Hz: Acceleration 3g

Frequency change: 1 Octave per minute

Axis: 3

Duration: 10 Minutes per axis

3.2 Random Vibration (AC2 VITA 47)

Frequency range: 5-2000Hz

Effective value of the acceleration 8g

Axis: 3

Duration: 60 Minutes per axis


12/31



3.3 Shock (AC1 IEC 61587-1)

Shock form: Half sinus

Acceleration: 25g

Duration: 18ms

Axis: 6

Shocks per axis: 3

3.4 Shock (AC2 VITA 47)

Shock form: Half sinus

Acceleration: 20g

Duration: 11ms

Axis: 6

Shocks per axis: 3

X Y Z

+

-


13/31



4 Test results

4.1 Sine Vibration

Mechanical: No issues during this test

Electrical: All slots booted up without errors.

4.2 Random Vibration

X-axis: Test was performed with shock absorbers



Y-axis: Test was performed without shock absorbers

Mechanical: Some load resistors disassembled during tests.


Z-axis: Test was performed without shock absorbers

Mechanical: Some load resistors disassembled during tests.

Electrical: Two slots didnt boot up. After extraction and reinsertion they

booted up without errors.


14/31



X-axis: Test was performed with shock absorbers

System was booted up during this test

Test duration: 30min


Electrical: The MCH showed some error messages:

processMsg(0xc2):

Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded to hpid

pm_processEvent(50):

Power Channel Notification Event,

Sensor=0x0, Dir=0x6f, Data=0xa1 0x1b 0x01

Despite of this, the system worked fine, after the vibration test.

All cards were hot-swappable.


15/31



4.3 Shock test (AC1 IEC 61587-1)

All shocks without shock absorbers

X-axis: After 6 shocks (3 shocks +X-axis, 3 shocks X-axis)


Electrical: All slots booted up without errors

Y-axis: After 6 shocks (3 shocks +Y-axis, 3 shocks Y-axis)



Z-axis: After 6 shocks (3 shocks +Z-axis, 3 shocks Z-axis)



4.4 Shock Test (AC2 VITA 47)

All shocks without shock absorbers

X-axis: After 6 shocks (3 shocks +X-axis, 3 shocks X-axis)



Y-axis: After 6 shocks (3 shocks +Y-axis, 3 shocks Y-axis)



Z-axis: After 6 shocks (3 shocks +Z-axis, 3 shocks Z-axis)




16/31



5 Conclusion

By screwing the front panels of the AMCs to the extrusions, there were no

mechanical problems. Even weight loaded boards (264g) were held

correctly in the card cage.

The electrical tests after the shock and vibration tests showed that the

boards were not damaged during the tests and were functioning well.

Further research is required to check the plating of the AMC boards and

the backplane connectors.

These tests show that MicroTCA could also be used for rugged

environments for transportation and MIL/AERO applications. Only little

modification is needed on the standard AMC boards.


17/31



Appendix A Vibration profile (sinusoidal)

STATUS INFORMATION

FREQUENCY: 19.30 Hz

REFERENCE: 2.97 g pk

CONTROL ACCELERATION: 2.95 g pk

CONTROL VELOCITY: 0.24 m/s pk

CONTROL DISPLACEMENT: 3.94 mm pp


18/31



CONTROL PARAMETERS

CONTROL CHANNEL(S): 1

CONTROL TYPE: SINGLE

SWEEP TIME: 6 min, 38 sec

SWEEP TYPE: LOG

STARTING SWEEP DIRECTION: UP

STARTING FREQUENCY: 2.00 Hz

LOWER FREQUENCY: 2.00 Hz

UPPER FREQUENCY: 200.00 Hz

SERVO SPEED: 1K dB/s

INPUT CHANNEL PARAMETERS

Chan(#)

Sensitivity(mV/g)

Coupling(AC/DC)

Max.Range(g pk)

1 100.00 AC 100.00

2 10.00 AC 100.00

3 10.00 AC 100.00

4 10.00 AC 100.00

5 10.00 AC 100.006 10.00 AC 100.00

7 10.00 AC 100.00

8 10.00 AC 100.00

INPUT CHANNEL DESCRIPTION

Chan # Description

1 B&K 848930


19/31



Appendix B Vibration profile (random)

STATUS INFORMATION

TEST LEVEL: 0.0 dB

REFERENCE: 8.00 g rms

CONTROL: 8.81 g rms


20/31



CONTROL PARAMETERS

CONTROL CHANNEL(S): 1

CONTROL TYPE: SINGLE

FREQUENCY RANGE: 2000 Hz

NUMBER OF PSD LINES: 2000

FREQUENCY RESOLUTION: 1.000 Hz

DOF: 130

SIGMA DRIVE LIMITING: 2.00

INPUT CHANNEL PARAMETERSChan(#)

Sensitivity(mV/g)

Coupling(AC/DC)

Max.Range(g rms)

1 100.00 AC 10.00

2 100.00 AC 10.00

3 100.00 AC 10.00

4 100.00 AC 10.00

5 10.00 AC 50.00

6 10.00 AC 50.00

7 10.00 AC 50.00

8 10.00 AC 50.00

INPUT CHANNEL DESCRIPTION

Chan # Description

1 B&K 848930


21/31



Appendix C Shock profile (AC1 IEC 61587-1)

X-axis:

Y-axis:

Z-axis:


22/31



Appendix D Shock profile (AC2 VITA 47)

X-axis:

Y-axis:

Z-axis:


23/31



Appendix E MCH Log

**************************************************

**** Welcome to OK1 V2.0 for NAT-MCH ********------------------------------------------******** Core Release: V1.13 ******** BSP Release: V1.0 Beta ******** Build : Jun 25 2007 15:04:37 ******************************************************

initializing ... >H>sysMemInit: ram_addr=1400ec, ram_end=2000000M>I>mbinit()MB>T>C>S H>sysMemInit: ram_addr=18347c, ram_end=2000000M>I>mbinit()MB>T>C>S l2Main: L2 (MAC) startingL2M_init: initialize Ethernet device(s)L2M_Init: reading the onboard EthID !

*** N.A.T. FEC driver V1.4 Engineering (16:01:31 Jun 8 2007) ****** N.A.T. LXT972 driver V1.1 Engineering (16:01:32 Jun 8 2007) ***

found LXT972 Rev 2Initialize Multi-channel DMA API Alpha v0.3 (2004-04-26)L2M_Init(1): - completed successfully

l2Main: successfully finished - L2 runningtcpipMain: launching N.A.T. TCP/IP Rel. V1.12 cpipMain: (Jun 8 2007


25/31



16:01:37)

L2_AttProto: attaching new protocol=5 for Process=3 and family=2,ifcall=1307fe, a6stat=0 - OK, new protoID=5, used=1

tcpipMain: process 3 attached for ProtID 5

init_tcpip: initializing TCP/IPnatattach: nat0 attached

with ethernet id 00 40 42 0b 00 14loattach: lo attached

with ethernet id 00 40 42 0b 00 14L2_AddType: adding type 0800 to port 5L2_AddType: adding type 0806 to port 5L2_AddType: adding type 1001 to port 5L2_AddType: adding type 1002 to port 5init_tcpip: finished successfullytcpipMain: sucessfully finished - TCP/IP running

------------------------------------------------------------------

NAT-MCH - Firmware Release V1.7E Beta (17:08:25 Jun 12 2007)------------------------------------------------------------------

Carrier Manager starting ....

*** N.A.T. DSPI driver V1.2 Engineering (16:01:34 Jun 8 2007) ***ETH1 link DOWNTransmit task startedTimer task startedSEL: starting timestamp taskSEL: 1970.000 00:00:00 aliveifconfig_nat0: own IP 0x8493a086 smask 0xffffff00 brdcst 0x8493a0ffifconfig_nat0: ioctl(SIOCSIFNETMASK) o.k., 0xffffff00

ifconfig_nat0: ioctl(SIOCSIFADDR) o.k., 0x8493a086ifconfig_nat0: ioctl(SIOCSIFBRDADDR) o.k., 0x8493a0ff

*** HPID started ***local host: 132.147.160.134remote host: 132.147.160.70RMCP rx port: 623RMCP tx port: 7001session: auth 0x00 id 0x00000000 seq_no 0x00000000 (size 9)

SEL initialized:max entry num: 1024sizeof entry: 16

default operations: 0x0a (cur 0x0a)cancel reservation id: 0x0001timestamp task pid: 12

SDR_REP initialized:max entry num: 4096sizeof entry: 64default operations: 0x2acurrent reservation id: 0x0001

IPMI DB: pre-initialization done - 24 entriesVPGA V1.4

*** N.A.T. BCM5396 driver V1.1 Engineering (16:01:33 Jun 8 2007) ***hpid_cm_server: starting taskmsgTaskIpmi: Message Handler started !


26/31



msgTaskShelf: Message Handler started !mcmc(3): startedmcmc: Carrier FRU Info device found at 0xa4 - Header CRC okFRU size = 1127 bytesmcmc(3): active

mcmcTask: started management task for fru_id=3, i2c=0x10mcmcTask(3): State change M0->M1processMsg(3): Got Inventory Response, Inventory Size = 1127mcmcTask(3): have read 1127 bytes of fru datamcmcTask(3): mcmc has 2 sensors, reading ...ScanPM: found Power Module at I2C=0xc2pmTask(50): started management task for Power Module at i2c=0xc2 oni2cdev=13PM_S_task: found 1 power modules, waiting for negoiation complete ....ProcessMsg: No Request outstanding, ignoring Response.pmTask(50): State change M0->M1pmTask(0): Power Module Info:

Device Revision =0x80

Firmware Revision =0x00:0x00Manufacturer ID =0x38:0x60:0x00Product ID =0x00:0x00Aux Firmware Rev. =0x00:0x00:0x00:0x00

processMsg(50): Got Inventory Response, Inventory Size = 500.mcmcTask(3): found Hot Swap Sensor at=0x01processMsg(3): Got Sensor Reading Response, handle=0x01mcmcTask(3): State change M1->M2mcmcTask(3): State change M2->M3mcmcTask(3): State change M3->M4pmTask(50): have read 500 bytes of fru dataIpmiFru_PrintRecords: invalid FRU ID = 33056756pmTask(50): Power Module at 0xc2 provides 31.0 Amps payload power

pmTask(50): Power module has 4 sensors, reading .......pmTask(50): found Hot Swap Sensor num=0processMsg(50): Got Sensor Reading Response, handle=0x01pmTask(50): State change M1->M2pmTask(50): State change M2->M3pmTask(50): State change M3->M4pmTask(50): FRU active, state M4pmTask(50): PM module at ic2=0xc2 choosen as the primary PM !pmTask(50): heartbeat command completed with code = 0x80pmTask(50): detected new FRU 40, power channel=3, state=0x1b ***pmTask(50): channel 3 management power enabledpmTask(50): channel 3 #ENABLE assertedcuTask(40): started management task for Cooling Unit at i2c=0xa8 on

i2cdev=13pmTask(50): detected new FRU 5, power channel=5, state=0x01 ***cuTask(40): State change M0->M1pmTask(50): channel 5 management power enabled$ipmiSendReqMsg: PANIC - MpcI2c_Write to 0xc2 failed with code = -2$processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwardedto hpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x03 0x05PM_S: Set Flag FlagMngdPowerModules$ScanClock(60): ipmiDev=17, i2c=0x14Scanning: 0x14 - NOT FOUNDpmTask(50): channel 5 #ENABLE asserted

$ipmiSendReqMsg: PANIC - MpcI2c_Write to 0xa8 failed with code = -3mmcTask(5): started management task for i2c=0x72processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded to


27/31



hpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x0b 0x05pmTask(50): detected new FRU 6, power channel=6, state=0x01 ***ScanClock(60): ipmiDev=17, i2c=0x14

Scanning: 0x14 - NOT FOUND$$$$$ScanClock(60): ipmiDev=17, i2c=0x14Scanning: 0x14 - NOT FOUND$$$$$clockTaskS: no Clock module found !ScanHub(61): ipmiDev=17, i2c=0x16Scanning: 0x16 - NOT FOUND$$$$$ScanHub(61): ipmiDev=17, i2c=0x16Scanning: 0x16 - NOT FOUND$$$$$ScanHub(61): ipmiDev=17, i2c=0x16Scanning: 0x16 - NOT FOUND$ipmiSendReqMsg: PANIC - MpcI2c_Write to 0xa8 failed with code = -3mmcTask(5): State change M0->M1$processMsg(5): Got Inventory Response, Inventory Size = 96

mmcTask(5): reading 96 bytes of fru datammcTask(5): reading FRU Info.$..$..$mmcTask(5): AMC needs 3.3 Amps powermmcTask(5): AMC has 6 sensors, reading ...hubTaskS: no HUB module found !PwrAllocate(fru 3 chan 0): allocating 0.8 A granted (available 30.2 A)$$.$$$.$$.$$$.$$.$$$.$$.mmcTask(5): found Hot Swap Sensor num=1processMsg(5): Got Sensor Reading Response, handle=0x01$mmcTask(5): State change M1->M2mmcTask(5): State change M2->M3PwrAllocate(fru 5 chan 4): allocating 3.3 A granted (available 26.9 A)

-------------------------------------------PM(1): - primary(fru 50): budget 31.0 A (alloc 4.1 A avail 26.9 A)PM(2): - unknownPM(3): - unknownPM(4): - unknown-------------------------------------------Primary Power Module:---------------------chan fruId PS1 ENA MPwr PPwr Amps-------------------------------------------1 3 y y y y 0.82 4 - - - -3 40 y y y y 0.0

4 41 - - - -5 5 y - - -6 6 y - - -7 7 y - - -8 8 y - - -9 9 y - - -10 10 y - - -11 11 - - - -12 12 - - - -13 13 - - - -14 14 - - - -15 15 - - - -16 16 - - - -

-------------------------------------------$ipmiSendReqMsg: PANIC - MpcI2c_Write to 0xa8 failed with code = -3$$$$$$$$$$processMsg(0x72): Event: NetFn=0x04, cmd=0x02, SensorType=0x01


28/31



forwarded to hpid$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ipmiSendReqMsg: WARN - switchIPMB-A -> IPMB-BipmiSendReqMsg: PANIC - MpcI2c_Write to 0xa8 failed with code = -3$processMsg(0x72): Event: NetFn=0x04, cmd=0x02, SensorType=0x01 forwarded

to hpidprocessMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x1b 0x05$$$$$$$$$$$$$$$$$$$$$$$$ipmiSendReqMsg: PANIC - MpcI2c_Write to 0xa8 failedwith code = -3PM(50): Payload switched ON for FRU(5) !mmcTask(5): State change M3->M4mmcTask(5): FRU active, state M4$pmTask(50): channel 6 management power enabledpmTask(50): channel 6 #ENABLE assertedmmcTask(6): started management task for i2c=0x74

processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x0b 0x06pmTask(50): detected new FRU 7, power channel=7, state=0x01 ***pmTask(50): channel 7 management power enabledpmTask(50): channel 7 #ENABLE assertedmmcTask(7): started management task for i2c=0x76processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x0b 0x07pmTask(50): detected new FRU 8, power channel=8, state=0x01 ***

pmTask(50): channel 8 management power enabledprocessMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x0b 0x08pmTask(50): channel 8 #ENABLE assertedmmcTask(8): started management task for i2c=0x78pmTask(50): detected new FRU 9, power channel=9, state=0x01 ***pmTask(50): channel 9 management power enabledprocessMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x0b 0x09

pmTask(50): channel 9 #ENABLE assertedmmcTask(9): started management task for i2c=0x7apmTask(50): detected new FRU 10, power channel=10, state=0x01 ***pmTask(50): channel 10 management power enabledprocessMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x03 0x0apmTask(50): channel 10 #ENABLE assertedmmcTask(10): started management task for i2c=0x7cprocessMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,

Dir=0x6f, Data=0xa1 0x0b 0x0aipmiSendReqMsg: PANIC - MpcI2c_Write to 0xa8 failed with code = -3mmcTask(6): State change M0->M1


29/31



processMsg(6): Got Inventory Response, Inventory Size = 96mmcTask(6): reading 96 bytes of fru datammcTask(6): reading FRU Info....mmcTask(7): State change M0->M1.processMsg(7): Got Inventory Response, Inventory Size = 96

mmcTask(6): AMC needs 3.0 Amps powermmcTask(7): reading 96 bytes of fru datammcTask(7): reading FRU Info.mmcTask(6): AMC has 6 sensors, reading ........mmcTask(7): AMC needs 3.0 Amps powermmcTask(7): AMC has 6 sensors, reading .....mmcTask(8): State change M0->M1processMsg(8): Got Inventory Response, Inventory Size = 96mmcTask(8): reading 96 bytes of fru datammcTask(8): reading FRU Info.......

mmcTask(8): AMC needs 3.3 Amps power..mmcTask(8): AMC has 6 sensors, reading ...mmcTask(9): State change M0->M1.processMsg(9): Got Inventory Response, Inventory Size = 96..mmcTask(9): reading 96 bytes of fru datammcTask(9): reading FRU Info........mmcTask(9): AMC needs 3.0 Amps powermmcTask(10): State change M0->M1mmcTask(9): AMC has 6 sensors, reading ....mmcTask(6): found Hot Swap Sensor num=1..processMsg(6): Got Sensor Reading Response, handle=0x01processMsg(10): Got Inventory Response, Inventory Size = 96

mmcTask(10): reading 96 bytes of fru datammcTask(10): reading FRU Info.mmcTask(6): State change M1->M2mmcTask(6): State change M2->M3PwrAllocate(fru 6 chan 5): allocating 3.0 A granted (available 23.9 A)ipmiSendReqMsg: PANIC - no answer from fruID=40 after 3 retries forNetFn=0x2c, cmd=0x07cuTask(40): unable to communicate with CU, waiting for extraction.$.mmcTask(7): found Hot Swap Sensor num=1...processMsg(7): Got Sensor Reading Response, handle=0x01$mmcTask(7): State change M1->M2mmcTask(7): State change M2->M3PwrAllocate(fru 7 chan 6): allocating 3.0 A granted (available 20.9 A)

.$.$$.mmcTask(10): AMC needs 3.0 Amps powermmcTask(10): AMC has 6 sensors, reading ...$$.$$..$$.$$$$.mmcTask(8): found Hot Swap Sensor num=1.processMsg(8): Got Sensor Reading Response, handle=0x01$$mmcTask(8): State change M1->M2mmcTask(8): State change M2->M3PwrAllocate(fru 8 chan 7): allocating 3.3 A granted (available 17.6 A).$$$.$$$.$$$$$$.$$$.$$$.$$$.mmcTask(9): found Hot Swap Sensor num=1$processMsg(0x76): Event: NetFn=0x04, cmd=0x02, SensorType=0x01 forwardedto hpidprocessMsg(9): Got Sensor Reading Response, handle=0x01$$mmcTask(9): State change M1->M2

mmcTask(9): State change M2->M3PwrAllocate(fru 9 chan 8): allocating 3.0 A granted (available 14.6 A)$$$.$$$$processMsg(0x78): Event: NetFn=0x04, cmd=0x02, SensorType=0x01


30/31



forwarded to hpid$$$$$.mmcTask(10): found Hot Swap Sensor num=1$processMsg(10): Got Sensor Reading Response, handle=0x01$$PM(50): Payload switched ON for FRU(6) !mmcTask(6): State change M3->M4

mmcTask(6): FRU active, state M4$$$mmcTask(10): State change M1->M2mmcTask(10): State change M2->M3PwrAllocate(fru 10 chan 9): allocating 3.0 A granted (available 11.6 A)processMsg(0x76): Event: NetFn=0x04, cmd=0x02, SensorType=0x01 forwarded tohpid$$$$$$$$$$$$processMsg(0x7a): Event: NetFn=0x04, cmd=0x02, SensorType=0x01forwarded to hpidprocessMsg(0x7a): Event: NetFn=0x04, cmd=0x02, SensorType=0x01 forwarded tohpid$$$$$$$$$$$$$$$$$$$$processMsg(0x7c): Event: NetFn=0x04, cmd=0x02,SensorType=0x01 forwarded to hpid$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$PM(50): Payload

switched ON for FRU(7) !mmcTask(7): State change M3->M4mmcTask(7): FRU active, state M4$$$$processMsg(0x78): Event: NetFn=0x04, cmd=0x02, SensorType=0x01forwarded to hpid$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$PM(50): Payload switched ON for FRU(8) !mmcTask(8): State change M3->M4mmcTask(8): FRU active, state M4$$$processMsg(0x7a): Event: NetFn=0x04, cmd=0x02, SensorType=0x01 forwardedto hpid$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$PM(50): Payload switchedON for FRU(9) !

mmcTask(9): State change M3->M4mmcTask(9): FRU active, state M4$$processMsg(0x7c): Event: NetFn=0x04, cmd=0x02, SensorType=0x01 forwardedto hpid$$$$$$$$$$$$$$$$$$$$$$$$$PM(50): Payload switched ON for FRU(10) !mmcTask(10): State change M3->M4mmcTask(10): FRU active, state M4$pmTask(50): heartbeat command completed with code = 0x80

-------------------------------------------PM(1): - primary(fru 50): budget 31.0 A (alloc 19.4 A avail 11.6 A)PM(2): - unknownPM(3): - unknown

PM(4): - unknown-------------------------------------------Primary Power Module:---------------------chan fruId PS1 ENA MPwr PPwr Amps-------------------------------------------1 3 y y y y 0.82 4 - - - -3 40 y y y y 0.04 41 - - - -5 5 y y y y 3.36 6 y y y y 3.07 7 y y y y 3.0

8 8 y y y y 3.39 9 y y y y 3.010 10 y y y y 3.0


31/31


11 11 - - - -12 12 - - - -13 13 - - - -14 14 - - - -15 15 - - - -

16 16 - - - --------------------------------------------processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x1b 0x01processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x5b 0x01processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,

Dir=0x6f, Data=0xa1 0x1b 0x01processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x5b 0x01processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x1b 0x01processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x5b 0x01

processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x1b 0x01processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x5b 0x01processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpidpm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x1b 0x01

SEL: 1970.000 00:16:40 alive

processMsg(0xc2): Event: NetFn=0x04, cmd=0x02, SensorType=0xf3 forwarded tohpid

pm_processEvent(50): Power Channel Notification Event, Sensor=0x0,Dir=0x6f, Data=0xa1 0x1b 0x01

SEL: 1970.000 00:33:20 alive

elma rugged microtca test

Documents