decoding information from current value request

Asked by kreutpet

Hi ,

many thanks for the great program.
I have been using it for a while now and started last year to implement a binding for openhab home automation based on your project.
You can find more details here
http://knx-user-forum.de/openhab/41186-neues-stiebel-eltron-waermepumpen-binding.html
and
https://github.com/openhab/openhab/pull/2101

The complete decoding of the different request are described in and xml file - > https://github.com/kreutpet/openhab/blob/master/bundles/binding/org.openhab.binding.stiebelheatpump/src/main/resources/2.06.xml

When decoding the current value request with a serial sniffer a saw also other values which are currently missing in the decoding definition. I was wondering if somebody already find any details on decoding the following infos from the original stiebel software. Here the info i see on the screen of the original stiebel software. Here a screenshot of the dialog showing the info->https://drive.google.com/file/d/0B76ZUH63aPGQRl9RTzhMZHNtc2c/view?usp=sharing
Status messages
1. compressor defrost
2. Power enabled
3. HP limiter
4. LP limiter
5. Anode
6. Stove/fireplace operation

Outputs
1. Heat stage 1
2. Heat stage 2
3. Heat stage 3
4. Compressor A
5. Heat pipe valve
6. Mixer open
7. Mixer close
8. Diverter valve
9. Heating circuit pum
10 DHW circulation pump

How can I decode above information from below reponse of the heat pump?

This is the response of my lwz 303i version 2.06:
01 00 48 fb 01 aa 00 72 01 3a 00 a2 02 dc 01 ce
00 00 00 00 00 59 01 73 11 18 27 27 f4 ca 0c 22
1d 00 00 57 00 00 00 00 00 00 00 01 00 10 03

based in this response "Compressor A" and "Heating circuit pump" are the only active (true) info i see. All other are deactiveated

The the following decoding rules i can successfully decode the current values.
    <request name="CurrentValues" description="Reads measurements" requestByte="FB">
        <recordDefinition name="CollectorTemperatur" position="4" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="OutsideTemperature" position="6" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="FlowTemperature" position="8" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="ReturnTemperature" position="10" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="HotGasTemperature" position="12" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="CylinderTemperature" position="14" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="EvaporatorTemperature" position="20" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="CondenserTemperature" position="22" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
        <recordDefinition name="ExtractFanSpeed" position="30" length="1" scale="1.0" dataType="Sensor" unit="°C"/>
        <recordDefinition name="SupplyFanSpeed" position="31" length="1" scale="1.0" dataType="Sensor" unit="°C"/>
        <recordDefinition name="ExhaustFanSpeed" position="32" length="1" scale="1.0" dataType="Sensor" unit="°C"/>
        <recordDefinition name="FilteredOutsideTemperature" position="34" length="2" scale="0.1" dataType="Sensor" unit="°C"/>
    </request>

Many thanks
Peter

Question information

Language:
English Edit question
Status:
Expired
For:
heatpumpMonitor Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.