MIL-1553 Software Engineering and Software Development Workshop

MIL-1553 Software Engineering and Software Development Workshop

MIL-1553 Software Engineering Workshop is a 2-day technical workshop address MIL-1553 software and firmware development principles.

Designed for military and contractors professionals who have a role in MIL-1553 technical perspective, the workshops aim to introduce attendees to the skills of MIlL-1553 software development needed to work with traditional non-embedded software development.

MIL-STD-1553 Software Development Kits (SDKs) are a set of development tools that allow for the creation of different applications for 1553.

MIL-STD-1553 SDKs provide the framework for developing embedded and “real-time” drivers and applications for MIL-STD-1553 components and cards, to reduce development time.

Participants will learn about Libraries of Application Programming Interface (API) functions, driver and information files for driver information, flash utilities, samples, utilities and etc.

Learning Objectives:

Upon completing this workshop, participants will:

• Gain a profound understanding of MIL-STD-1553 protocols and their integration within avionics systems.
• Master software engineering principles tailored to MIL-1553 development, ensuring robust and reliable software.
• Learn how to design and implement MIL-1553 software solutions that meet the highest industry standards.
• Develop the skills to troubleshoot, debug, and optimize software in the context of MIL-1553 avionics systems.
• Acquire knowledge of best practices for security and data integrity within MIL-STD-1553 software.
• Enhance their ability to work effectively as part of a team and communicate technical concepts to stakeholders.

Audience:

If programming, software development, project management are part of your daily tasks or you lead technical teams, this workshop is for you. This workshop is ideally suited for:

• Software Engineers and Developers seeking to specialize in MIL-STD-1553 avionics systems.
• Systems Engineers involved in the design and integration of MIL-1553 software.
• Project Managers responsible for overseeing software development projects in avionics.
• Quality Assurance professionals ensuring compliance with MIL-STD-1553 standards.
• Avionics Technicians and Maintenance Personnel interested in deepening their understanding of software systems.
• Military and Aerospace professionals involved in avionics software projects.

Format
We offer on-site or live-online (16-teaching hours , 4 hours a day, 4 days) designed for 20 participants or less. These are delivered by a team of 2 training specialists.

Course Content

MIL-1553 Software Development Principles

• Overview of MIL-1553
• Mil-1553 Databus Structure
• MIL-1553 Architecture
• MIL-1553 Hardware, Software and Firmware

MIL-1553 Software Model

• Layering Approach
• API Modules
• The Layer 0 API
• Layer 1 API Module
• Layer 2 API Modules
• Device Identifier
• Error Code Constants
• Low Level Functions
• Interrupt Handlers
• Memory Management
• Mapping and Unmapping Memory
• Read/Write Memory

MIL-1553 Software Architecture and Design

• Host Software
• Round-robin
• Scalability
• Manual partitioning
• Manual scheduling
• Multiple cycles
• 8ms/16ms/32ms/64ms/128ms/512ms
• Host Software Architecture
• Asynchronous Interfaces
• Fail Safe
• Types of Software Interfaces provided
• House Keeping Data Transfer Schemes
• Major System Requirements Considered
• Bus Profiling
• Architecture Design:
• Minor Frame (8ms), Major Frame (64ms), Super Frame (512ms)
• Allocation of Bandwidth / Slots for Each Subsystem
• Identify Slots – Critical / Delay / Periodic / Post Delay
• Scheduling – Periodic / Handshake Driven / Asynchronous
• Bulk Message Slots Provisions
• Syncing of Hardware Events with Mil 1553 Cycle
• Margins in Each Minor Frame
• Execution Latency
• Minimum / Maximum Delays

MIL-1553 Programming

• 1553 Device & Protocol Initialization & Closing
• Advance 1553 Initialization Options
• Manual Device & Protocol Setup (1553A and Other Non 1553B Variants)
• MIL-1760 Startup
• Closing the Device

Overview of MIL-STD-1553 Functions

• Error Injection/Detection for Data Words of BC or RT Messages
• Setting Message Interrupts, Triggers

1553 Bus Monitor Operation

• Basic Programming Flow
• BM Filters
• BM Buffer Allocation
• BM Control Functions
• BM Message Read Functions

1553 Remote Terminal Operation

• Basic RT Programming Flow
• RT Initialization
• Single RT and Multiple RT Configurations
• BROADCAST Messages – Single RT and Multiple R
• RT Command Legalization
• RT Status and Last Command Words
• RT Status Response Time
• Error Injection on the RT Status Word
• RT Control Functions

1553 Bus Controller (BC) Operation

• Basic BC Programming Flow
• Data Structure
• BC Initialization
• Allocating Buffers
• Reading and Writing BC Data (and reviewing message results)
• Defining BC Messages (1553 Message Types)
• BC-RT
• RT-BC
• RT-RT
• Mode Codes without Data
• Mode Codes with Data
• Broadcast BC-RT
• Broadcast RT-RT
• Broadcast Mode Codes without Data
• Broadcast Mode Codes with Data
• Other BC Message Types: NOPs, Delays & Branches
• Inter-Message Gap Time & Frame Message Scheduling
• Starting and Stopping the BC & Synchronizing Stop

1553 Device Interrupts

• 1553 Devices and Interrupts
• 1553 Hardware Interrupts
• 1553 Software Polled Interrupts
• The Interrupt Queue
• General Device Interrupt Functions
• 1553 Device Interrupt Functions
• RT Interrupt Info Word
• BC Interrupts

Typical Scheduler Design

• BC and RT Considerations
• Bus Monitor Considerations
• Message Table for Each Message
• Grouping of Messages of Each RT
• Message Profiles
• Time Critical
• Periodic
• Asynchronous Messages
• Event Driven Messages
• Bulk Messages
• Fixed Scheduling
• Bulk messages dynamically

Transactions Allowed

• Six types of transactions are allowed between the BC and a specific RT or between the Bus Controller and a pair of RTs
• Controller to RT Transfer. The Bus Controller sends one 16-bit receive command word, immediately followed by 1 to 32 16-bit data words. The selected Remote Terminal then sends a single 16-bit Status word.
• RT to Controller Transfer. The Bus Controller sends one receive command word to a Remote Terminal. The Remote Terminal then sends a single Status word, immediately followed by 1 to 32 words.
• RT to RT Transfers. The Bus Controller sends out one receive command word immediately followed by one transmit command. The transmitting Remote Terminal sends a Status word immediately followed by 1 to 32 data words. The receiving Terminal then sends its Status word.
• Mode Command Without Data Word. The Bus Controller sends one command word with a Subaddress of 0 or 31 signifying a Mode Code type command. The Remote Terminal responds with a Status word.
• Mode Command With Data Word (Transmit). The Bus Controller sends one command word with a Subaddress of 0 or 31 signifying a Mode Code type command immediately followed by a single data word. The Remote Terminal responds with a Status word.
• Mode Command With Data Word (Receive). The Bus Controller sends one command word with a Subaddress of 0 or 31 signifying a Mode Code type command. The Remote Terminal responds with a Status word immediately followed by a single Data word.

MIL-1553 Protocol and Software Verification and Validation

• Required Bus Controller Operation
• Identification of Correct Address Field in Response
• Correct Address Field with Controller-Remote Terminal Message Transfers
• Correct Address Field with Remote Terminal-
• Remote Terminal Message Transfers
• Minimum No-Response Time-Out
  Minimum No-Response BC-RT Transfer
• Minimum No-Response Time-Out: RT-RT Transfers
• No-Response Time-Out
• No-Response Time-Out: BC-RT Transfers
• No-Response Time-Out: RT-RT Transfers

Error Injection: BC to RT Transfers

• Parity
• Status Word Validation for Transmit
• Commands
• Status Word Validation for Receive Commands
• Data Word Validation
• Word Length
• Status Word Validation for Transmit Commands
• Status Word Validation for Receive Commands

Error Injection: RT to RT Transfers

• Parity
• Status Word Validation for Responses to RT to RT Transmit Commands
• Status Word Validation for Responses to RT to RT Receive Commands
• RT to RT Data Word Validation
• Word Length
• Status Word Validation for Responses to RT to RT Transmit Commands
• Status Word Validation for Responses to RT to RT Receive Commands
• Data Word Validation
• Bi-Phase Encoding
• Status Word Validation for Responses to RT to RT Transmit Commands
• Status Word Validation for Responses to RT to RT Receive Commands
• Data Word Validation
• Sync Encoding
• Status Word Sync Validation for Response to
• RT to RT Transmit Commands
• Status Word Sync Validation for Response to
• RT to RT Receive Commands
• Data Word Sync Validation
• Response Message Length
• Message Length Validation for RT to RT
• Transmit Commands
• Message Length Validation for RT to RT
• Receive Commands
• Discontiguous Data

MIL-1553 Validation Test Plan – Multiplex Data Bus

• Power Up Sequence
• RT Power-Up
• BC Power-Up

Error Monitoring

• Error Handling Procedures
• RT-RT Transfers
• Suppressed Response
• Power Cycle Test
• Backup Bus Controller Operation
• Bus Retries
• Subsystem Reset
• Bus Switching

 Illegal Commands

• Multiple Bus Architectures
• Data Validity
• Latency
• Deadlock

Bus Profiling

• Data Ready and Data Request Messages
• Time Critical – Hence Sampling / handling is periodic
• Data Transfer Messages
• Dictated by Consumption of Message
• Gyro usage before Controller
• Actuator after Controller
• Loop bandwidth requirements
• Periodic Data messages
• Dictated by periodicity
• Source of data / Source Modules

System Integration Tests

• Normal Operation
• Monitor for Proper Sequencing
• Operational Modes
• Exercise of Options
• Dynamic Bus Control
• Acceptance
• Rejection
• Backup BC
• Service Request
• Busy
• Mode Commands
• Emergency Power Operation