Data Networks

1
Data Networks Interfaces Working Group

• Development of high speed Mil-Std-1553B

2
Data Networks Interfaces Working Group

• Background
• Current situation
• QinetiQ Study
• ASSC Involvement
• Conclusions

3
Data Networks Interfaces Working Group

• Background
• 1 Mbit/sec bit rate of 1553B known to be limiting
• New Network Centric systems require higher
  bandwidth
• Legacy systems suffer bus loading problems
• Problem recognised by SAE back in 1999
• Next Generation task group set up and worked on
  various solutions
• (NG) 1553 (target 100 Mbit/sec)
• (EBR) 1553 (target 10 Mbit/sec)
• Overclocked 1553 (target 5 Mbit/sec)

4
Data Networks Interfaces Working Group

• Background (Cont)
• In 2003 USAF invited US industry to develop a
  high speed 1553 capability
• Edgewater Computer Systems won contract
• In late 2004 USAF publish pre-solicitation notice
  with target performance requirements of
• Data throughput greater than 200 Mbit/sec (no
  compression)
• Use existing aircraft wiring
• Concurrent operation with standard 1 Mbit/sec
  1553B
• Backwards compatibility to existing 1553 protocol
• Achieve standard 1553B bit error rate of 1 x
  10-12

5
Data Networks Interfaces Working Group

• Background (Cont)
• UK interest established
• Feb 2005 QinetiQ White Paper published
• August 2005 MOD award Phase 1 study to QinetiQ
• October 2005 MOD considering development options
• Throughout 2005 Fast 1553 now becoming growing
  subject of interest
• Various articles published
• DDC demonstrate 40 Mbit/sec combined and 100
  Mbit/sec on real 1553B bus network

6
Data Networks Interfaces Working Group

• Background (Cont)
• October 2005 USAF claim at IQPC conference that
  Mil-Std-1553C with companion guide will be
  published in January 2006
• October 2005 QinetiQ phase 1 study completed and
  reported to MOD
• Edgewater claim to be near to demonstrating 200
  Mbit/sec on real system but their actual
  progress shrouded in secrecy

7
Data Networks Interfaces Working Group

• Current situation (Feb 05)
• Still no announcement on release of Mil-Std-1553C
  or 1553B Notice 5
• DDC announce successful flight demonstration of
  their technology in F15 aircraft
• System known as HyPer-1553
• 40Mbit/sec combined operation demonstrated
• 80 and 120 Mbit/sec single operation demonstrated
• Digital imagery application communicating between
  front equipment bay of aircraft to modified store
  on wing pylon

8
Data Networks Interfaces Working Group

• QinetiQ Study
• Title - Enhanced 1553 data bus scoping and
  requirements identification
• Objectives
• To determine UK requirement for this technology
• To determine technology risk - particularly EMC
• Main findings
• UK Requirement
• Difficult to quantify for this technology,
  different from US situation
• Could help certain projects in short term
• Impact of NEC not widely understood
• MOD looking at avionics strategy

9
Data Networks Interfaces Working Group

• QinetiQ Study (Cont)
• EMC
• Intra System compatibility will be difficult to
  achieve against current test requirements and
  will require tight management
• Platform level EMC is considered the greatest
  risk if interference with on-board communications
  systems is to be avoided.
• Recommendations
• Continue to work with US to develop technology
• More detailed study of technology risks
  (hardware, software and EMC) needed
• More detailed assessment of UK legacy platform
  requirements needed

10
Data Networks Interfaces Working Group

• ASSC involvement
• Monitor introduction of fast 1553 technologies
• Partner with SAE in review of emerging 1553C or
  1553B Notice 5
• Consider this technology for inclusion within the
  Guide to Digital Interface Standards

11
Data Networks Interfaces Working Group

• Conclusions
• Fast 1553 solutions will become available either
  as bespoke designs or as a new standard
• Higher bandwidth data network capability is
  required to meet NEC platform requirements
• Choice for legacy platforms is new fit new or use
  exisiting wiring
• Benefits in UK not as clear as in the US
• ASSC should have active role