Automatic Addressing Protocol for Shared Bus Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for connecting multiple hardware components using a shared bus require manual address assignment, which is cumbersome and inefficient, especially when dealing with a large number of slave devices, as they need unique identifiers for individual control, often involving complex wiring or manual configuration using switches or jumpers.

Innovation Solution

An automatic addressing protocol that utilizes an independent electrical connection between neighboring devices to assign unique IDs, where each device receives and computes its ID from its upstream neighbor, allowing for a chain of devices to be connected and addressed without manual intervention, using a shared bus for communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual address assignment using switches or jumpers is used, then unique device identifiers can be assigned, but the process becomes cumbersome and inefficient especially with large numbers of slave devices

Engineering Contradiction:
Improveaddress assignment processVSAvoidtime for address configuration
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system enables automatic address assignment where the master device autonomously assigns addresses to slave devices without human intervention. The master device transmits address information to each slave device through the shared bus, and each slave device automatically configures its address identifier, eliminating the need for manual switch or jumper configuration.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The address assignment is performed automatically during system initialization or device connection, before the system begins normal operation. The master device pre-configures all slave device addresses in sequence, so that when the system starts operating, all devices are already properly addressed and ready for communication.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If a shared data bus is used to connect multiple components, then wiring complexity is reduced, but each slave needs a unique identifier which requires manual configuration

Engineering Contradiction:
Improvewiring complexityVSAvoiddevice configuration
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

Each slave device automatically receives and configures its unique address identifier through the shared bus communication protocol. The master device transmits address information to each slave, and the slave device autonomously configures its identifier, eliminating the need for manual switch or jumper configuration while maintaining the simplified shared bus wiring structure.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If devices are connected in a chain by a shared bus, then physical management becomes easier, but manual address assignment becomes even more cumbersome with large numbers of devices

Engineering Contradiction:
Improvephysical connection managementVSAvoidaddress configuration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements automatic address assignment where the master device sequentially assigns addresses to slave devices connected in the chain through the shared bus. Each slave device automatically receives and configures its address without human intervention, maintaining the ease of physical chain connection while eliminating the complexity of manual address configuration even with large numbers of devices.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8478917B2Automatic addressing protocol for a shared bus
Publication Date: 2013.07.02 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8478917B2 patent drawing
  • US8478917B2 patent drawing
  • US8478917B2 patent drawing

AI summary

An automatic addressing protocol for a shared bus is described. In an embodiment, devices connected in a chain by a shared bus are also connected by an independent electrical connection between each pair of neighboring devices. A protocol is used over the independent electrical connections which is independent of that used on the shared bus. Devices in the chain receive at least one device ID from an upstream neighbor via the independent electrical connection and either use this received ID as their ID or use the received ID to compute their ID. Where the device has a downstream neighbor, a device then transmits at least one device ID to the downstream neighbor via the independent electrical connection and this transmitted ID may be their ID or an ID generated based on their ID, for example, by incrementing the ID by one. The process is repeated by devices along the chain.