Difference between revisions of "Component: Injector (API Digital Output) (Test Injectors)"

From Flowcode Help
Jump to navigationJump to search
 
(2 intermediate revisions by the same user not shown)
Line 14: Line 14:
 
==Injector (API Digital Output) component==
 
==Injector (API Digital Output) component==
 
Data injector to allow a physical digital output pin to be attached to a simulated component.  The component will forward any output state changes through to a SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly interface with a physical I/O pin.
 
Data injector to allow a physical digital output pin to be attached to a simulated component.  The component will forward any output state changes through to a SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly interface with a physical I/O pin.
 +
 +
==Component Pack==
 +
 +
FREE
  
 
==Detailed description==
 
==Detailed description==
 +
 +
 +
 +
 +
 +
  
  
Line 26: Line 36:
  
 
==Examples==
 
==Examples==
 +
 +
 +
 +
 +
 +
  
  
Line 109: Line 125:
 
|-
 
|-
 
|-
 
|-
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:]] -  
+
| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-h32-icon.png]] - HANDLE
 
| width="90%" style="border-top: 2px solid #000;" | ''Return''
 
| width="90%" style="border-top: 2px solid #000;" | ''Return''
 
|}
 
|}
Line 134: Line 150:
 
| colspan="2" | Specifies the number of pins the component can monitor and control. 
 
| colspan="2" | Specifies the number of pins the component can monitor and control. 
 
|-
 
|-
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
+
| width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]]
| width="90%" | Simulation I/O Pin
+
| width="90%" style="background-color:#EAE1EA; color:#4B008D;" | Pin 0
|-
 
| colspan="2" | Pin monitored by the simulation 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
 
| width="90%" | SCADA Slave Pin
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
 
| width="90%" | Simulation I/O Pin
 
|-
 
| colspan="2" | Pin monitored by the simulation 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
 
| width="90%" | SCADA Slave Pin
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
 
| width="90%" | Simulation I/O Pin
 
|-
 
| colspan="2" | Pin monitored by the simulation 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
 
| width="90%" | SCADA Slave Pin
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
 
| width="90%" | Simulation I/O Pin
 
|-
 
| colspan="2" | Pin monitored by the simulation 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
 
| width="90%" | SCADA Slave Pin
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
 
| width="90%" | Simulation I/O Pin
 
|-
 
| colspan="2" | Pin monitored by the simulation 
 
 
|-
 
|-
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
 
| width="90%" | SCADA Slave Pin
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
 
|-
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
Line 193: Line 163:
 
|-
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
|-
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
 
| width="90%" | Simulation I/O Pin
 
|-
 
| colspan="2" | Pin monitored by the simulation 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
 
| width="90%" | SCADA Slave Pin
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-5-icon.png]]
 
| width="90%" | Simulation I/O Pin
 
|-
 
| colspan="2" | Pin monitored by the simulation 
 
|-
 
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
 
| width="90%" | SCADA Slave Pin
 
|-
 
| colspan="2" | Pin used by the connected SCADA Slave hardware 
 
|-
 
| width="10%" align="center" style="background-color:#D8C9D8;" | [[File:Fc9-conn-icon.png]]
 
| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''Connections'''
 
|-
 
|-
 
| width="10%" align="center" style="background-color:#D8C9D8;" | [[File:Fc9-conn-icon.png]]
 
| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''Simulations'''
 
|-
 
 
|}
 
|}

Latest revision as of 17:21, 9 November 2022

Author Matrix Ltd
Version 1.2
Category Test Injectors


Injector (API Digital Output) component

Data injector to allow a physical digital output pin to be attached to a simulated component. The component will forward any output state changes through to a SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly interface with a physical I/O pin.

Component Pack

FREE

Detailed description

No detailed description exists yet for this component

Examples

No additional examples


Downloadable macro reference

Fc9-comp-macro.png InitialiseInjector
Sets up the injector ready to receive commands or send data 
Fc9-string-icon.png - STRING InjectorName
Name of the console that will be created 
Fc9-u8-icon.png - BYTE Return


Fc9-comp-macro.png RxByteCount
Returns the number of bytes currently sat in the receive buffer. 
Fc9-u16-icon.png - UINT Return


Fc9-comp-macro.png TxByte
Puts a byte onto the comms channel. 
Fc9-u8-icon.png - BYTE DataByte
 
Fc9-void-icon.png - VOID Return


Fc9-comp-macro.png RxByte
Attempt to receive a byte back from the injector 0 - 255 = Valid data 256 = RX timeout no data available 
Fc9-u16-icon.png - UINT Return


Fc9-comp-macro.png GetConsoleHandle
Gets the handle to the console allowing data displaying on the panel etc. 
Fc9-h32-icon.png - HANDLE Return



Property reference

Fc9-prop-icon.png Properties
Fc9-type-17-icon.png API Slave
SCADA Slave component to use to pipe data to a physical SPI bus 
Fc9-type-16-icon.png Number of Pins
Specifies the number of pins the component can monitor and control. 
Fc9-conn-icon.png Pin 0
Fc9-type-5-icon.png Simulation I/O Pin
Pin monitored by the simulation 
Fc9-type-21-icon.png SCADA Slave Pin
Pin used by the connected SCADA Slave hardware