User Tools

Site Tools


ddsf:public:guidebook:03_user:11_instrument

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ddsf:public:guidebook:03_user:11_instrument [2021/07/14 10:58]
murphy ↷ Links adapted because of a move operation
ddsf:public:guidebook:03_user:11_instrument [2021/07/14 16:20] (current)
murphy
Line 1: Line 1:
-====== User Scenario 2: Data Acquisition and Instrumentation ​Scenario ​====== +====== User Scenario 2: Data Acquisition and Instrumentation====== 
-[[ddsf:private:​guidebook:​03_user| Return to User Experiences]] +[[ddsf:public:​guidebook:​03_user:start| Return to User Experiences]]
- +
-  * **<color #​FF0000><​todo @char>​Please Review</​todo></​color>​** +
-  * **<color #​FF0000><​todo @DDSFmember>​Please Review</​todo></​color>​** +
  
 ===== Overview ===== ===== Overview =====
  
-Instrumentation and data acquisition is focused on the collection of large volumes of [[ddsf:private:​guidebook:​06_append:​glossary:​s:​sensor]] data in a short amount of time. One example, is an aircraft engine test bed ( for example, ​ [[https://​www.mtu.de/​e-papers/​MTU_ePaper/​Marketing/​Engine_test_beds/​epaper/​ausgabe.pdf | MTU Aero Engines]] where various sensors for things like temperature,​ pressure and vibration are place all around the inside and outside of an engine to collect data as the engine is running. ​+Instrumentation and data acquisition is focused on the collection of large volumes of [[ddsf:public:​guidebook:​06_append:​glossary:​s:​sensor]] data in a short amount of time. One example, is an aircraft engine test bed ( for example, ​ [[https://​www.mtu.de/​e-papers/​MTU_ePaper/​Marketing/​Engine_test_beds/​epaper/​ausgabe.pdf | MTU Aero Engines]]where various sensors for things like temperature,​ pressure and vibration are place all around the inside and outside of an engine to collect data as the engine is running. ​
  
 Data acquisition is not limited to jet engines, but found in a number of industries. On a small scale, there might be eight to sixteen sensors collecting information maybe at the 10 hertz rate. On a large scale , such as testing a jet engine, there might be hundreds to thousands of sensors collecting data anywhere from 1 hertz to 20 kilohertz. ​ Data acquisition is not limited to jet engines, but found in a number of industries. On a small scale, there might be eight to sixteen sensors collecting information maybe at the 10 hertz rate. On a large scale , such as testing a jet engine, there might be hundreds to thousands of sensors collecting data anywhere from 1 hertz to 20 kilohertz. ​
Line 18: Line 14:
 [[ddsf:​private:​guidebook:​02_body:​01_intro:​start| Return to top]] [[ddsf:​private:​guidebook:​02_body:​01_intro:​start| Return to top]]
  
-A major benefit is to standardize an architecture around [[ddsf:private:​guidebook:​06_append:​glossary:​d:​data_distribution_service_dds]]. These larger systems contain multiple data acquisition systems from multiple vendors developed at different times and locations. So, standardization on one [[ddsf:private:​guidebook:​06_append:​glossary:​m:​midware]] and technology standard and interface allows for easy reconfiguration between different engine tests. ​+A major benefit is to standardize an architecture around [[ddsf:public:​guidebook:​06_append:​glossary:​d:​data_distribution_service_dds]]. These larger systems contain multiple data acquisition systems from multiple vendors developed at different times and locations. So, standardization on one [[ddsf:public:​guidebook:​06_append:​glossary:​m:​midware]] and technology standard and interface allows for easy reconfiguration between different engine tests. ​
  
-DDS is one of the few technologies to handle the amount of data and strict processing schedules for these distributed systems while providing multiple DDS vendor product [[ddsf:private:​guidebook:​06_append:​glossary:​i:​interoperability|interoperability]].  ​+DDS is one of the few technologies to handle the amount of data and strict processing schedules for these distributed systems while providing multiple DDS vendor product [[ddsf:public:​guidebook:​06_append:​glossary:​i:​interoperability|interoperability]].  ​
  
-  * Low Overhead / High [[ddsf:private:​guidebook:​06_append:​glossary:​t:​thruput|Throughput]] Data Delivery with low [[ddsf:private:​guidebook:​06_append:​glossary:​l:​latency]]. +  * Low Overhead / High [[ddsf:public:​guidebook:​06_append:​glossary:​t:​thruput|Throughput]] Data Delivery with low [[ddsf:public:​guidebook:​06_append:​glossary:​l:​latency]]. 
-  * [[ddsf:private:​guidebook:​06_append:​glossary:​s:​scalable]] to 1000’s of devices making it a great solution for all data acquisition systems. +  * [[ddsf:public:​guidebook:​06_append:​glossary:​s:​scalable]] to 1000’s of devices making it a great solution for all data acquisition systems. 
-  * On-the-wire [[ddsf:private:​guidebook:​06_append:​glossary:​i:​interoperability]] between DDS products allows for the fast binary transmission of data and ease of accessing the data on each end of the "​wire"​.+  * On-the-wire [[ddsf:public:​guidebook:​06_append:​glossary:​i:​interoperability]] between DDS products allows for the fast binary transmission of data and ease of accessing the data on each end of the "​wire"​.
  
 <figure figtag> <figure figtag>
ddsf/public/guidebook/03_user/11_instrument.1626274700.txt.gz · Last modified: 2021/07/14 10:58 by murphy