Component: Injector (API Digital Output) (Test Injectors): Difference between revisions
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
==Detailed description== | ==Detailed description== | ||
| Line 26: | Line 28: | ||
==Examples== | ==Examples== | ||
| Line 109: | Line 113: | ||
|- | |- | ||
|- | |- | ||
| 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'' | ||
|} | |} | ||
Revision as of 15:38, 17 December 2021
| 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.
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. | |
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
|
Simulation I/O Pin |
| Pin monitored by the simulation | |
|
|
SCADA Slave Pin |
| Pin used by the connected SCADA Slave hardware | |
|
Connections |
|
|
Simulations |