Component: IButton (DS1990) (EEPROM): Difference between revisions

Latest revision as of 14:37, 13 July 2026

Author	MatrixTSL
Version	1.0
Category	EEPROM

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.

Component Source Code

Please click here to download the component source project: FC_Comp_Source_IButton_DS1990.fcfx

Please click here to view the component source code (Beta): FC_Comp_Source_IButton_DS1990.fcfx

Detailed description

No detailed description exists yet for this component

Examples

No additional examples

Macro reference

AddressNextDevice

	AddressNextDevice
Scans for the next connected device with a matching family code. Goes through the device list generated by the ScanBus macro.
- VOID	Return

GetSerialString

	GetSerialString
Gets the Serial String for the current addressed device.
- STRING	Return

Initialise

	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.
	Simulation
	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.
	Panel Simulation
	Number Devices
Sens the number of sensors we can communicate with during simulation
	Serial 0
Serial number for simulated one wire device

@@ Line 17: / Line 17: @@
 ==Component Source Code==
-Please click here to download the component source project: [https://www.flowcode.co.uk/wiki/componentsource/FC_Comp_Source_temp/IButton_DS1990.fcfx FC_Comp_Source_temp/IButton_DS1990.fcfx]
+Please click here to download the component source project: [https://www.flowcode.co.uk/wiki/componentsource/FC_Comp_Source_IButton_DS1990.fcfx FC_Comp_Source_IButton_DS1990.fcfx]
-Please click here to view the component source code (Beta): [https://www.flowcode.co.uk/FlowchartView/?wfile=componentsource/FC_Comp_Source_temp/IButton_DS1990.fcfx FC_Comp_Source_temp/IButton_DS1990.fcfx]
+Please click here to view the component source code (Beta): [https://www.flowcode.co.uk/FlowchartView/?wfile=componentsource/FC_Comp_Source_IButton_DS1990.fcfx FC_Comp_Source_IButton_DS1990.fcfx]
 ==Detailed description==
@@ Line 73: / Line 73: @@
 ''<span style="color:red;">No additional examples</span>''
@@ Line 86: / Line 88: @@
 ===AddressNextDevice===
-{| class="wikitable" style="width:60%; background-color:#FFFFFF;"
+{| class="mtx-class-macrotable wikitable"
 |-
-| width="10%" align="center" style="background-color:#D8C9D8;" align="center" | [[File:Fc9-comp-macro.png]]
+| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
-| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''AddressNextDevice'''
+| width="90%" class="mtx-class-macrohead" | '''AddressNextDevice'''
 |-
 | colspan="2" | Scans for the next connected device with a matching family code. Goes through the device list generated by the ScanBus macro.&nbsp;
@@ Line 100: / Line 102: @@
 ===GetSerialString===
-{| class="wikitable" style="width:60%; background-color:#FFFFFF;"
+{| class="mtx-class-macrotable wikitable"
 |-
-| width="10%" align="center" style="background-color:#D8C9D8;" align="center" | [[File:Fc9-comp-macro.png]]
+| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
-| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''GetSerialString'''
+| width="90%" class="mtx-class-macrohead" | '''GetSerialString'''
 |-
 | colspan="2" | Gets the Serial String for the current addressed device.&nbsp;
@@ Line 114: / Line 116: @@
 ===Initialise===
-{| class="wikitable" style="width:60%; background-color:#FFFFFF;"
+{| class="mtx-class-macrotable wikitable"
 |-
-| width="10%" align="center" style="background-color:#D8C9D8;" align="center" | [[File:Fc9-comp-macro.png]]
+| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-comp-macro.png]]
-| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''Initialise'''
+| width="90%" class="mtx-class-macrohead" | '''Initialise'''
 |-
 | colspan="2" | Configures each matching sensor on the bus with the specified conversion bits.&nbsp;
@@ Line 129: / Line 131: @@
 ==Property reference==
-{| class="wikitable" style="width:60%; background-color:#FFFFFF;"
+{| class="mtx-class-macrotable wikitable"
 |-
-| width="10%" align="center" style="background-color:#D8C9D8;" | [[File:Fc9-prop-icon.png]]
+| width="10%" align="center" class="mtx-class-macrohead" | [[File:Fc9-prop-icon.png]]
-| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''Properties'''
+| width="90%" class="mtx-class-macrohead" | '''Properties'''
 |-
 |-
@@ Line 140: / Line 142: @@
 | colspan="2" | Link to the one wire component to host the bus.&nbsp;
 |-
-| width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]]
+| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
-| width="90%" style="background-color:#EAE1EA; color:#4B008D;" | Simulation
+| width="90%" class="mtx-class-propfolder" | Simulation
 |-
 |-
@@ Line 149: / Line 151: @@
 | colspan="2" | No - We use the panel GUI to perform the simulation. Yes - We use OneWire comms via an API to communicate with real hardware.&nbsp;
 |-
-| width="10%" align="center" style="background-color:#EAE1EA;" | [[File:Fc9-conn-icon.png]]
+| width="10%" align="center" class="mtx-class-propfolder" | [[File:Fc9-conn-icon.png]]
-| width="90%" style="background-color:#EAE1EA; color:#4B008D;" | Panel Simulation
+| width="90%" class="mtx-class-propfolder" | Panel Simulation
 |-
 |-

SteveT (talk | contribs)