Analysis of Industry Standards Protocol: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Introduction=
=Introduction=
The best starting point for open source product development is to study what has been done already: history, prior art (patents), and industry standards.


Industry Standards refers to products that are being produced by the mainstream economy. Open Source Ecology takes industry standards as the starting point converting these norms to ones that are based on [[Open Source Ecology]]. Once these industry standards are understood, they can be modified to fit the needs of open source, appropriate technology.
Industry Standards refers to what is in common use for a given technology. Industry standards can refer to off-the-shelf products that are being produced in the current economy. This may include proprietary and open source products.


The best starting point for building any device or machine is to study what has been done already: history, prior art (patents), and industry standards.
A study of industry standards is an indispensible part of an [[Open Source Product Development]] process.
 
The study of industry standards should this include those products which alraedy exist in the mainstream economy, and those open source products and processes that are merely emerging - especially as [[Distributive Enterprise]] via [[OSPD]].
 
Open Source Ecology takes industry standards as the starting point converting these norms to ones that are based on [[Open Source Ecology]]. Once these industry standards are understood, they can be modified to fit the needs of open source, appropriate technology ([[OSAT]]).


It is an assumption of OSE that here are no inventions, but only small incremental developments on a large, existing pool of knowledge. These are known as innovations.
It is an assumption of OSE that here are no inventions, but only small incremental developments on a large, existing pool of knowledge. These are known as innovations.
Line 20: Line 26:
The analysis of history and industry standards is a good starting point for a Modules Breakdown Diagram, and for extracting working mechanisms for a Tech Tree of Choices.
The analysis of history and industry standards is a good starting point for a Modules Breakdown Diagram, and for extracting working mechanisms for a Tech Tree of Choices.


=Protocol=
=Formal OSE Protocol=
{{Hint|*Start by linking to representative products, patents, 'how it works' descriptions, commenting on notable features, or why the features are important and noteworthy. The end goal is finding patterns or common ways and costs in which services/functions are provided.
*Delve into details of the products - to explore working mechanisms of the different products
*Start identifying patterns of features - such as, "everyone seems to use x as opposed by y because..."
*Filter the technology through OSE Specifications - such as, "how does the instance of the technology endorse OSE values and design methods, and how does it contribute to the OSE product ecology?"


#Use [[Study of Industry Standards Template]] - make a copy of it for your use.
==Crowd Protocol==
#Research the machine or module on the internet.
#Use [[Coggle]] as a collaborative mindmap to work on this collaboratively. Paste in pictures and key performance and cost data. See example of embedding with including an edit link below the embed:
#Publish on the wiki and link in your [[Work Log]].
<html><iframe width='400' height='300' src='https://embed.coggle.it/diagram/UjyEStgsvqlxAE6U/a45f88079c65c5df50eb798159b1d4d8b9ab12685caec974a66d79157fa8676f' frameborder='0' allowfullscreen></iframe></html>


=IOT Protocols=
[https://embed.coggle.it/diagram/UjyEStgsvqlxAE6U/a45f88079c65c5df50eb798159b1d4d8b9ab12685caec974a66d79157fa8676f edit]


The protocols for use with the IOT will probably follow industry standards, since currently available protocols are sufficient for our needs and are readily available at very low cost.
#Use [[Study of Industry Standards Template]] for an idea of the key performance data points.
 
#Research the machine or module on the internet.
==Wireless Protocol==
#Publish on the wiki and link in your [[Work Log]].}}
 
===802.11===
Communication between the IOT will probably use IEEE 802.11:
[https://en.wikipedia.org/wiki/IEEE_802.11]
 
This is already used with the IOT, but the current implementation is not very robust, due to the limited WIFI ability of the HUZZAH ESP8266.
 
==Controller Protocol==
 
===TTL===
Transistor to Transistor Logic (TTL) is based on digital voltage levels:
[https://en.wikipedia.org/wiki/Transistor%E2%80%93transistor_logic Wikipedia TTL]
 
The proposed controller uses direct connections with digital voltage levels to control the relays. This is a limited protocol, since it requires one pin for each line controlled. For example: A 4 relay board requires 4 digital pins from the arduino. The state of each pin (high / low) determines the state of the relay (on / off). Several TTL lines can be multiplexed to expand the number of control lines into addresses - this requires additional hardware.
 
===PWM===
Pulse Width Modulation (PWM) uses digital pulses of varying widths to transmit information:
[https://en.wikipedia.org/wiki/Pulse-width_modulation Wikipedia PWM]
 
PWM used by the digital input lines of the arduino and is currently used in the IOT to communicate with the DHT22 temperature & humidity sensors and the remote power switch transmitter. PWM is commonly used by arduino compatible devices.
 
==Sensor Protocols==
The sensors use two protocols:
 
===I2C===
I2C is a two wire bus protocol detailed as follows:
[https://en.wikipedia.org/wiki/I%C2%B2C Wikipedia I2C]
 
This is already useful for the IOT, since three of the sensors use I2C and it is commonly used in arduino compatible devices. Also, it only requires 2 pins to support hundreds of devices. Often, I2C device addresses are configurable. When they cannot, workarounds are possible, but require additional hardware.
 
===PWM===
Pulse Width Modulation (PWM) uses digital pulses of varying widths to transmit information and is documented above.
 
===TTL===
Transistor to Transistor Logic (TTL) is based on digital voltage levels in electronics and is documented above.


===SPI===
The Serial Peripheral Interface Bus (SPI) is a 4 wire bus protocol:
[https://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus Wikipedia SPI]


While SPI is supported by the arduino, it is not very common in arduino devices or in available arduino software. It can be useful for this application, as it can be used for the SD Memory card interface.
=Evaluation=
*Someone who has learned the background research on a given technology may qualify to be a wiki page [[Maintainer]] for a given technology or its subset.

Latest revision as of 14:03, 1 March 2021

Introduction

The best starting point for open source product development is to study what has been done already: history, prior art (patents), and industry standards.

Industry Standards refers to what is in common use for a given technology. Industry standards can refer to off-the-shelf products that are being produced in the current economy. This may include proprietary and open source products.

A study of industry standards is an indispensible part of an Open Source Product Development process.

The study of industry standards should this include those products which alraedy exist in the mainstream economy, and those open source products and processes that are merely emerging - especially as Distributive Enterprise via OSPD.

Open Source Ecology takes industry standards as the starting point converting these norms to ones that are based on Open Source Ecology. Once these industry standards are understood, they can be modified to fit the needs of open source, appropriate technology (OSAT).

It is an assumption of OSE that here are no inventions, but only small incremental developments on a large, existing pool of knowledge. These are known as innovations.

In order to create an innovative design, it is critical to have a deep understanding of the designs and mechanisms that are in common use - such as in products that are available on the open market. The critical enabler of open innovation is access to documentation of what has already been done.

A study of Industry Standards includes:

  1. History - what has been done already? What is the first ever working example of the artifact? How has this evolved in time and geography?
  2. Prior Art - patents may be used as an official record of innovations' descriptions
  3. Study of Industry Standards - What kind of features and performances are common in commercially-available, mainstream products? These may not necessarily be desirable, but it is important to understand why they exist.
  1. Comprehensive listing of mechanisms or designs that are in common use today, as well as listing of lesser known designs
  2. Explanation of the key features of each design
  3. Analysis of performance to cost ratio for each machine or component. This should be expressed as cost per unit of performance, such as: cost per kW of power generated, cost per throughput of production, etc.

The analysis of history and industry standards is a good starting point for a Modules Breakdown Diagram, and for extracting working mechanisms for a Tech Tree of Choices.

Formal OSE Protocol

HintLightbulb.png Hint: *Start by linking to representative products, patents, 'how it works' descriptions, commenting on notable features, or why the features are important and noteworthy. The end goal is finding patterns or common ways and costs in which services/functions are provided.

  • Delve into details of the products - to explore working mechanisms of the different products
  • Start identifying patterns of features - such as, "everyone seems to use x as opposed by y because..."
  • Filter the technology through OSE Specifications - such as, "how does the instance of the technology endorse OSE values and design methods, and how does it contribute to the OSE product ecology?"

Crowd Protocol

  1. Use Coggle as a collaborative mindmap to work on this collaboratively. Paste in pictures and key performance and cost data. See example of embedding with including an edit link below the embed:

edit

  1. Use Study of Industry Standards Template for an idea of the key performance data points.
  2. Research the machine or module on the internet.
  3. Publish on the wiki and link in your Work Log.


Evaluation

  • Someone who has learned the background research on a given technology may qualify to be a wiki page Maintainer for a given technology or its subset.
Retrieved from "https://wiki.opensourceecology.org/index.php?title=Analysis_of_Industry_Standards_Protocol&oldid=246558"