Jump to content

Component: Injector (API Analog Input) (Test Injectors): Difference between revisions

From Flowcode Help
No edit summary
No edit summary
Line 15: Line 15:
Data injector to allow a physical analog input pin to be attached to a simulated component.  The component will poll for any input state changes via SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly interface with a physical I/O pin.
Data injector to allow a physical analog input pin to be attached to a simulated component.  The component will poll for any input state changes via SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly interface with a physical I/O pin.


==Component Pack==
==Component Source Code==


FREE
Please click here for the component source code: [https://www.flowcode.co.uk/wikicopy/componentsource/FC_Comp_Source_InjectorSCADAAnalogInput.fcfx FC_Comp_Source_InjectorSCADAAnalogInput.fcfx]


==Detailed description==
==Detailed description==




Line 34: Line 36:


==Examples==
==Examples==




Line 151: Line 155:
| colspan="2" |  
| colspan="2" |  
|-
|-
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
| width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]]
| width="90%" | Simulation ADC 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 ADC Pin
|-
| colspan="2" | Pin used by the connected SCADA Slave hardware 
|-
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
| width="90%" | Simulation ADC Pin
|-
| colspan="2" | Pin monitored by the simulation 
|-
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
| width="90%" | SCADA Slave ADC Pin
|-
| colspan="2" | Pin used by the connected SCADA Slave hardware 
|-
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
| width="90%" | Simulation ADC Pin
|-
| colspan="2" | Pin monitored by the simulation 
|-
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
| width="90%" | SCADA Slave ADC Pin
|-
| colspan="2" | Pin used by the connected SCADA Slave hardware 
|-
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
| width="90%" | Simulation ADC Pin
|-
| colspan="2" | Pin monitored by the simulation 
|-
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
| width="90%" | SCADA Slave ADC Pin
|-
| colspan="2" | Pin used by the connected SCADA Slave hardware 
|-
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
| width="90%" | Simulation ADC Pin
|-
| colspan="2" | Pin monitored by the simulation 
|-
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
| width="90%" | SCADA Slave ADC Pin
|-
| colspan="2" | Pin used by the connected SCADA Slave hardware 
|-
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
| width="90%" | Simulation ADC Pin
|-
| colspan="2" | Pin monitored by the simulation 
|-
|-
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
| width="90%" | SCADA Slave ADC Pin
|-
| colspan="2" | Pin used by the connected SCADA Slave hardware 
|-
|-
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
| width="10%" align="center" | [[File:Fc9-type-6-icon.png]]
Line 220: Line 168:
|-
|-
| 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-6-icon.png]]
| width="90%" | Simulation ADC Pin
|-
| colspan="2" | Pin monitored by the simulation 
|-
| width="10%" align="center" | [[File:Fc9-type-21-icon.png]]
| width="90%" | SCADA Slave ADC 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'''
|-
|}
|}

Revision as of 17:47, 9 November 2022

Author Matrix Ltd
Version 1.2
Category Test Injectors


Injector (API Analog Input) component

Data injector to allow a physical analog input pin to be attached to a simulated component. The component will poll for any input state changes via SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly interface with a physical I/O pin.

Component Source Code

Please click here for the component source code: FC_Comp_Source_InjectorSCADAAnalogInput.fcfx

Detailed description

No detailed description exists yet for this component

Examples

No additional examples


Downloadable macro reference

InitialiseInjector
Sets up the injector ready to receive commands or send data 
- STRING InjectorName
Name of the console that will be created 
- BYTE Return


RxByteCount
Returns the number of bytes currently sat in the receive buffer. 
- UINT Return


TxByte
Puts a byte onto the comms channel. 
- BYTE DataByte
 
- VOID Return


RxByte
Attempt to receive a byte back from the injector 0 - 255 = Valid data 256 = RX timeout no data available 
- UINT Return


GetConsoleHandle
Gets the handle to the console allowing data displaying on the panel etc. 
- HANDLE Return



Property reference

Properties
API Slave
SCADA Slave component to use to pipe data to a physical SPI bus 
Number of Pins
Specifies the number of pins the component can monitor and control. 
Poll Rate
 
Pin 0
Simulation ADC Pin
Pin monitored by the simulation 
SCADA Slave ADC Pin
Pin used by the connected SCADA Slave hardware