Direct models - Revision history

KKoPV: /* Switcher */

2014-09-10T06:28:00Z

‎Switcher

KKoPV: /* Switcher */

2014-09-10T06:27:36Z

‎Switcher

KKoPV at 21:57, 22 March 2014

2014-03-22T21:57:46Z

KKoPV at 21:57, 22 March 2014

2014-03-22T21:57:30Z

KKoPV at 21:49, 1 March 2014

2014-03-01T21:49:13Z

KKoPV: /* Direct models */

2014-03-01T21:48:36Z

‎Direct models

KKoPV: Created page with "== Direct models == === Counter === A counter stores impulses from sensors, for example S0 impulses from watt meters. The real data will be calculated during readout by the..."

2014-03-01T21:25:14Z

Created page with "== Direct models == === Counter === A counter stores impulses from sensors, for example S0 impulses from watt meters. The real data will be calculated during readout by the..."

New page

== Direct models ==

=== Counter ===

A counter stores impulses from sensors, for example S0 impulses from watt meters.

The real data will be calculated during readout by the time difference between the readings and the defined resolution.

It can handle both types of stored data:
* Store realtime data (every tick) as value <tt>1</tt>
* Store accumulated tick counts, e.g. accumulated for a minute

=== Meter ===

A meter channel stores always increasing measuring data, so every reading must be greater or equal as the last reading.

Meter channels can have an auto adjust flag set.

This is used for sensor equipments, which resets their internal counter for example at power loss.

If a meter channel is flagged as auto adjust, the following will happen
* If the actual reading is lower than last reading, the offset value will set to the last reading
* The actual reading will be stored as <tt>offset + value</tt> as for any other channel with offset.

=== Sensor ===

A sensor is the most generic model for universal use, it stores any value as is.

=== Switcher ===

A switcher model will store actual reading '''only''', if the actual value is '''different''' from the last stored reading.

Switching sensors are for example an inverter state or valve state.

The predefined weather condition channels (storing "sunny", "cloudy" etc.) are also based on this model.

@@ Line 30: / Line 30: @@
 === Switcher ===
-A switcher model will store actual reading '''only''', if the actual value is '''different''' from the last stored reading. It works for numeric and non-numeric readings.
+A switcher model will store actual reading '''only''', if the actual value is '''different''' from the last stored reading.<br />It works for numeric and non-numeric readings.
 Switching sensors are for example an inverter state or valve state.

← Older revision		Revision as of 21:57, 22 March 2014
Line 1:		Line 1:
	{{TOCright}}		{{TOCright}}
−	~~== Direct models ==~~
−
	Direct models implement the '''direct''' data access. They don't accept child channels and handles data storing or readout by themselves.		Direct models implement the '''direct''' data access. They don't accept child channels and handles data storing or readout by themselves.

← Older revision		Revision as of 21:57, 22 March 2014
Line 1:		Line 1:
		+	{{TOCright}}
	== Direct models ==		== Direct models ==

← Older revision		Revision as of 21:49, 1 March 2014
Line 36:		Line 36:

	The predefined weather condition channels (storing "sunny", "cloudy" etc.) are also based on this model.		The predefined weather condition channels (storing "sunny", "cloudy" etc.) are also based on this model.
		+
		+	[[Category:Model]]

← Older revision		Revision as of 21:48, 1 March 2014
Line 1:		Line 1:
	== Direct models ==		== Direct models ==
		+
		+	Direct models implement the '''direct''' data access. They don't accept child channels and handles data storing or readout by themselves.

	=== Counter ===		=== Counter ===