Difference between revisions of "Component: Data Transfer (API UART) ()"
From Flowcode Help
Jump to navigationJump to search| Line 14: | Line 14: | ||
==Data Transfer (API UART) component== | ==Data Transfer (API UART) component== | ||
Comms data injector to allow a Serial UART peripheral to be attached to a comms component. The component will forward any byte transactions through to a SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly drive a physical UART. | Comms data injector to allow a Serial UART peripheral to be attached to a comms component. The component will forward any byte transactions through to a SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly drive a physical UART. | ||
| + | |||
| + | ==Component Pack== | ||
| + | |||
| + | FREE | ||
==Detailed description== | ==Detailed description== | ||
| + | |||
| + | |||
| Line 28: | Line 34: | ||
==Examples== | ==Examples== | ||
| + | |||
| + | |||
Revision as of 16:20, 7 January 2022
| Author | Matrix Ltd |
| Version | 1.2 |
| Category |
Contents
Data Transfer (API UART) component
Comms data injector to allow a Serial UART peripheral to be attached to a comms component. The component will forward any byte transactions through to a SCADA Slave enabled hardware. Enabling the Flowcode simulation runtime to directly drive a physical UART.
Component Pack
FREE
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 | |
| InjectorName | |
| Name of the console that will be created | |
| Return | |
| TxByte | |
| Puts a byte onto the comms channel. | |
| DataByte | |
| Return | |
| RxByte | |
| Attempt to receive a byte back from the injector 0 - 255 = Valid data 256 = RX timeout no data available | |
| Return | |
| GetConsoleHandle | |
| Gets the handle to the console allowing data displaying on the panel etc. | |
| Return | |