Intraship Integration Control Instructor: TV Prabakar

1. Intraship Integration ControlInstructor: TV Prabakar

2. Functional Requirement • 150 sensors are placed on turbine. • Sensors read Temperature and Pressure every 50 ms. • Monitoring System checks for threshold Bounds. • If unusual, gear of the turbine is changed. • Should respond to External Control signals . • Should balance load among all four Turbines.

3. Constraints • Should not effected by Electro Magnetic Interference. • Components should be ‘MIL’ standard. • Database updates are restricted.

4. Obvious Architecture Temperature Sensors Turbine Monitor Data Pressure Sensors Gear Controller

5. Architecture Evaluation • It is Block Diagram, not an Architecture. • What is Turbine monitor Black box? • Does Turbine Control Component is readily available? • Assumed that no component fails. • Using above diagram, can development be started? • How many Network interfaces Turbine Monitor should have?

6. Improved Block Diagram Mote 1 Concen- trator Turbine Monitor Data Mote 2 Mote 3 Concen- trator Mote 4 Mote 5 Gear Controller

7. Priority of Quality Attributes • Availability. • Performance. • Usability. • Testability. • Security. • Modifiability.

8. Quality Attribute Dependency • Performance ∞ Availability. • Performance ∞ 1/Security. • Performance ∞ 1/Modifiability. • Performance ∞ 1/Usability. • Availability ∞ Security. • Availability ∞ 1/Usability.

9. Availability Driven Design Apply Removal from service Tactic to every component.

10. Sensor Fault recovery Temperature sensor Active redundancy µP µP µP µP Pressure Sensor

11. Sensor Fault recovery µP µP µP

12. Fault Detection Tactics Applied When µP samples sensor, reads incorrect Value or no value. • Heartbeat. • voting • Active Redundancy • Spare • Shadow operation

13. µP Fault Recovery

14. Fault Detection Tactics Applied • Redundant µP informs the concentrator. • Concentrator doesn’t read data from mote. • Heartbeat. • voting • Exception. • Transaction. • Passive Redundancy. • Active Redundancy. • Spare. • State resynch.

15. Mote to Conc. Cable Fault Recovery Concen- trator

16. Mote to Conc. Cable Fault Recovery Concen- trator

17. Fault Detection Tactics Applied • µP senses the channel before sending, if not in operating voltage, chooses spare. • Similarly Concentrator does. • Heartbeat. • Spare. • Transaction

18. Concentrator Fault Recovery Concentrator Concentrator Concentrator Concentrator Concentrator Concentrator

19. Conc. To Monitor Cable Fault Recovery Concentrator Turbine Monitor Concentrator

20. Conc. To Monitor Cable Fault Recovery Concentrator Turbine Monitor Concentrator

21. Open the Turbine Monitor Black Box System Monitor Controller Slave processor Controller Heartbeat Shared Memory Slave processor Turbine Monitor

22. Slave Processor Fault Recovery Slave2 Slave1 Slave2 Slave1 Shared Memory Shared Memory Controller Controller

23. Fault Detection Tactics Applied • After Processing of operations each slave sets the their flag byte to one. • At end of deadline, controller checks the flag byte, if zero, respective slave failed. • Heartbeat. • Voting. • Active Redundancy. • Spare • Shadow operation.

24. Controller Fault Recovery Slave Slave Slave Shared Memory Shared Memory Shared Memory Controller Controller Controller Controller

25. Fault Prevention Tactics Applied • Each controller lives for fixed safe duration and initializes its spare as controller. • Removal from service. • Passive Redundancy. • Spare • State resynchronization.

26. Poor Resource utilization…. • Each processor can act as Controller and Slave. • Each removed Controller becomes spare of slave, acts as slave till it dies.

27. Turbine - Gear Cable Fault Recovery Turbine Monitor Gear Monitor

28. Turbine - Gear Cable Fault Recovery Turbine Monitor Gear Monitor

29. Open the Gear Monitor Black Box Slave processor Controller Shared Memory

30. Slave Processor Fault Recovery Slave2 Slave1 Slave2 Slave1 Shared Memory Shared Memory Controller Controller

31. Controller Fault Recovery Slave Slave Slave Shared Memory Shared Memory Shared Memory Controller Controller Controller Controller

32. Performance Driven Design

33. Current Architecture Mote Turbine Monitor Concentrator Contro ller Slave µP µP Shared Memory µP Gear Monitor Contro ller Slave Shared Memory

34. sense Bounds checking Raise Alarm Data send Check failures Data receive Glow LEDS Data receive Store threshold Data send Data send Data receive Data receive Data receive Data send Change gear Data send send ACK Get data From ROM Compute function Receive ACK

35. Concentrator Allocation view Mote Check failures Raise Alarm sense Bounds checking Data receive Data send Glow LEDS Store threshold Data receive Data send Data send Data receive Gear Monitor Turbine Monitor Change gear Data receive Data receive Data send Data send send ACK Get data From ROM Receive ACK Compute function

36. Simple Range checking program, choosing high speed hardware will give high performance.

37. Hardware Specifications • 8-bit µP on mote. • 1 KBps cable from mote to concentrator. • 16-bit µP on Concentrator. • 1MBps cable from concentrator to Monitor. • Pentium Processor on Turbine Monitor. • 1KBps cable from Turbine to Gear Monitor. • Pentium Processor on Gear Monitor. • Packet size from mote is 5 bytes.

38. Delay on mote. • To sense Temperature (ADC) = 1 ms • To sense Temp. thru spare (ADC) = 1 ms • To sense Pressure ( ADC ) = 1 ms • To sense Pressure thru spare = 1 ms • To sense channel (ADC) = 1 ms • To sense spare channel (ADC) = 1 ms • To send packet on channel (DAC)= 1 ms Total delay at mote = 7 ms.

39. Mote to Conc. Cable delay 1000 Bytes = 1 sec 5 Bytes = 5 ms In µP Active redundancy mode load is 10 bytes Total network delay = 10ms

40. Concentrator delay • To sense the channel (ADC) = 1 ms • To sense spare channel (ADC) = 1 ms • To read 300 packets (ADC) = 300 ms • To process and aggregate data = 2 ms • To sense other channel (ADC) = 1 ms • To sense other spare channel = 1 ms • To send 150 packets (DAC) = 150 ms Total delay at concentrator = 456 ms

41. Conc. To Monitor cable delay To transfer 1500 bytes = 1.5 ms Delay at Turbine Monitor Total delay = 150 + 25 + 150 = 325 ms.

42. Monitor to Concentrator cable delay To transfer 1500 bytes = 1.5 ms Delay at Concentrator Total delay = 456 ms Conc. to mote delay Total delay = 10 ms

43. Total processing delay Total delay = 7 +10 + 456 + 1.5 + 325 + 1.5 + 456 + 10 = 1256 ms (or 1260 ms approx)

44. Evaluation • Not satisfying functional requirements. • Sensitivity points are ADC and DAC. • Packet errors during transmission are not considered, may result in retransmissions. • EMI constraint is not taken considered.

45. Possible solutions • Increase redundancy in ADCs and DACs • Use checksum for transmission error detection.

46. Comments What is the redundancy number of ADC and DAC? 150 ADCs and 150 DACs may solve the Problem (infeasible). Checksum - increases network delay by 1 ms. - calculation takes 5 ms ( min. ). - checking takes 5 ms. Retransmissions are not decreased.

47. Effective solution • Data should be sent digitally ( elimination of ADC and DAC ) • No effect of EMI. • Retransmission free. • Use Fiber optic cable.

48. Poor Resource utilization…. • For efficient usage of bandwidth, connect all components in bus Architecture.

49. Modified Architecture mote Fibre optic cable Turbine Monitor Fibre optic cable µP Contro ller Slave Concentrator Shared Memory µP µP Gear Monitor µP Contro ller Slave Shared Memory

50. Need of Concentrator Acts as proxy Delay calculation Total delay = 7 + 0.3 + 2 + 0.015 + 25 + 0.015 + 2 + 0.03 = 36.615 ms (or 37 ms approx)