ezeio2:userinterface:configuration:devices:driverlist:discretein

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
ezeio2:userinterface:configuration:devices:driverlist:discretein [2022-06-22 00:04] johparezeio2:userinterface:configuration:devices:driverlist:discretein [2023-10-13 18:03] (current) – [Status & Registers (right panel)] johpar
Line 1: Line 1:
 ==== Discrete Input driver ==== ==== Discrete Input driver ====
 +
 +==== Configuration settings (center panel) ====
  
 === Description === === Description ===
Line 31: Line 33:
 **REGISTER 1 & 2 modes** - Each discrete input is duplicated, providing the opportunity apply two modes of initial processing and two methods of scaling. The ezeio controller's microprocessor reads the onboard inputs at a rate of 1000 times per second and exports the results every 1/10 of a second (//connected I/O Expander inputs are sampled slower as they are transmitted via CANbus//). Additional processing is applied to logged registers (see [[ezeio2:userinterface:configuration:fields|"Fields"]]) **REGISTER 1 & 2 modes** - Each discrete input is duplicated, providing the opportunity apply two modes of initial processing and two methods of scaling. The ezeio controller's microprocessor reads the onboard inputs at a rate of 1000 times per second and exports the results every 1/10 of a second (//connected I/O Expander inputs are sampled slower as they are transmitted via CANbus//). Additional processing is applied to logged registers (see [[ezeio2:userinterface:configuration:fields|"Fields"]])
  
-**Register 1 & 2 modes** - Choose one of the setting below for registers 1 & 2.+**Register 1 & 2 modes** - These modes control how the analog to digital converter calculates the live values. //Separate settings on the individual "Field" settings control how each channel is logged//.  Choose one of the setting below for registers 1 & 2.
  
 | **Mode** | **Description** | **Effect** |  | **Mode** | **Description** | **Effect** | 
Line 44: Line 46:
    
  
-**SCALING OF REGISTER 1** - Register 1 can be scaled to a unit value such as PSI or LPM. The relationship between the Min/Max raw & scaled settings creates a 2 point linear conversion. The result of this conversion is shown in register 3. In addition, a Low/High error range (in the scaled unit) can be entered, representing a normal or safe operating range for the application.  +**SCALING OF REGISTER 1** - Register 1 can be scaled to a unit value such as PSI or LPM with a 2 point linear conversion method. A rough conversion can be obtained by entering corresponding values from a table supplied by the sensor manufacture. For a calibrated conversion, use a trusted gauge or probe to provide readings at two points within the sensors range. Enter the value for one point and use the driver's copy function to capture the corresponding live raw reading. The result of this conversion is shown in register 3. In addition, a Low/High error range (in the scaled unit) can be entered, representing a normal or safe operating range for the application.  
  
-**Min raw - Max raw** - By default, the range shown here is set based on the "Input hardware type" selected, such as 0-10V (0.0 - 10.0) or 0-30mA (4.0 - 20.0). This would correlate to the full scale of a typical sensor. These  fields can be changed if required to match the output of your sensor or the scale range you wish to use in the next step.  +{{:ezeio2:userinterface:configuration:devices:driverlist:copy_button.png?600|}}
  
-**Min scale Max scale** - Enter values here that correlate to the Min/Max raw values. For example: 4.0mA = 0 psi and 20.0mA = 250 psi      +**Raw value point A & B** By default, the range shown here is set based on the "Input hardware type" selected, such as 0-10V (0.0 - 10.0) or 0-30mA (4.0 - 20.0). This would correlate to the full scale of a typical sensor. These  fields can be changed if required to match the output of your sensor or the scale range you wish to use in the next step.   
 + 
 +**Scaled value at point A & B** - Enter values here that correlate to the Min/Max raw values. For example: 4.0mA = 0 psi and 20.0mA = 250 psi      
  
 **Low error - High error** - Enter values here that represent the normal range for the application. This could also represent the operating range of the sensor, so a negative value could indicate an open circuit. When the value is out of this range, the "Driver status" will indicate an "App error". This error can be see on the Driver status, incorporated in expressions by use of ds(DVCSTAT_APPSTAT) and included in messages with the "Message Template Tag" [DVCSTAT#APPSTAT].  **Low error - High error** - Enter values here that represent the normal range for the application. This could also represent the operating range of the sensor, so a negative value could indicate an open circuit. When the value is out of this range, the "Driver status" will indicate an "App error". This error can be see on the Driver status, incorporated in expressions by use of ds(DVCSTAT_APPSTAT) and included in messages with the "Message Template Tag" [DVCSTAT#APPSTAT]. 
Line 66: Line 70:
 **Logic** - Set the true (or ON) state to be above or below the threshold value, with a value of 1 or 100. Choosing 100, make it easy to use the value to drive a digital output via "Fields"   **Logic** - Set the true (or ON) state to be above or below the threshold value, with a value of 1 or 100. Choosing 100, make it easy to use the value to drive a digital output via "Fields"  
  
- ==== Thermistor options ====+ ==== Thermistor options (use Thermistor driver for more options and features) ====
  
 <WRAP center round tip 60%> <WRAP center round tip 60%>
Line 81: Line 85:
 | TX1001 Pro | ThermoWorks | TX-1001X-OP |  | | TX1001 Pro | ThermoWorks | TX-1001X-OP |  |
 | ET7273 |  | ET7273 |  |  | ET7273 |  | ET7273 |  | 
 +
 +----
 +
 +==== Status & Registers (right panel) ====
 +
 +----
 +
 +=== Device Status ===
 +
 +**Driver info** - Typically this is the name from the program file
 +
 +**Driver updated/version** - Date loaded or updated and the version of the driver
 +
 +**Battery & Signal** - Signal indicates the progress through the script. If driver fails to operate, signal number indicates progress 
 +
 +**Driver status** - Color and text of status bubbles give a quick visual reference of Communication, Operation, and Application
 +
 +**Communication** - Com count indicates number of successful and unsuccessful data packets received
 +
 +----
 +
 +=== Available registers ===
 +
 +| 1 | Raw electrical value | Unit type is set by "Input hardware type", V, mA, Ohm |
 +| 2 | Raw electrical value | Unit type is set by "Input hardware type", V, mA, Ohm |
 +| 3 | Scaled value, Register 1 | Scaled by 2 point calibration | 
 +| 4 | Scaled value, Register 2 | Scaled by offset and factor |
 +| 5 | Logical state | Analog value converted to digital (on/off) based on threshold setting |
 +| 6 | Logical cycles | Number of times "Logical state" changes from off to on |
 +| 7 | Logical active time | Number of seconds logical state is "on" (runtime) | 
 + 
  • ezeio2/userinterface/configuration/devices/driverlist/discretein.1655856245.txt.gz
  • Last modified: 2022-06-22 00:04
  • by johpar