Difference between revisions of "Component: IButton (DS1990) (Storage)"
From Flowcode Help
Jump to navigationJump to search| Line 16: | Line 16: | ||
==Detailed description== | ==Detailed description== | ||
| + | |||
| + | |||
| Line 24: | Line 26: | ||
==Examples== | ==Examples== | ||
| + | |||
| + | |||
Revision as of 13:31, 17 November 2021
| Author | MatrixTSL |
| Version | 1.0 |
| Category | Storage |
Contents
IButton (DS1990) component
A rugged 48-bit unique identifier allowing for unique codes for logistical tracking or device identifiers etc. Compatible with the DS1990A and DS1990R iButton devices. Requires a One Wire component to perform the bus operations.
Detailed description
No detailed description exists yet for this component
Examples
No additional examples
Downloadable macro reference
|
GetSerialString |
| Gets the Serial String for the current addressed device. | |
 - STRING
|
Return |
|
|
AddressNextDevice |
| Scans for the next connected device with a matching family code. Goes through the device list generated by the ScanBus macro. | |
 - VOID
|
Return |
|
|
Initialise |
| Configures each matching sensor on the bus with the specified conversion bits. | |
| - VOID
|
Return |
Property reference
|
Properties |
|
One Wire Component |
| Link to the one wire component to host the bus. | |
|
|
Number Devices |
| Sens the number of sensors we can communicate with during simulation | |
|
Serial 0 |
| Serial number for simulated one wire device | |
|
Connections |
|
|
Simulations |
|
Simulate Comms |
| No - We use the panel GUI to perform the simulation. Yes - We use OneWire comms via an API to communicate with real hardware. | |
