WH - Water Heater
The values in parentheses are the default values provided by RCT.
All WH-series tests begin by searching for the DUT address. This requires two settings to be correct.
- Identifying DGN. Pick a status DGN that the device transmits frequently automatically. The value is in hexadecimal (e.g. WATER_HEATER_STATUS -> 1FFF7).
- Identifying Instance. Used in combination with the Identifying DGN to find the DUT. If the DGN does not have an Instance field, enter FF.
All tests require the following settings be defined.
- WATERHEATER_STS Instance.
Circulation pump tests use
- CIRCULATION_PUMP_STS Instance.
WH-10 WATERHEATER_STATUS
This is a DGN Status Test - it covers the ordinary use of the DGN and its fields. For convenience, the DGN and all of the fields are tested in one pass. Thus, testing WH-10 also covers WH-11 through WH-30.
Like all Status Tests, WH-10 begins by monitoring the DGN for 20 seconds to determine whether it is being broadcast as specified. Next, a series of Request_for_DGN messages are sent to test whether the DUT responds promptly. While these tests are running, do not perform any operations which would force a change in the DUT's state.
In the next stage, every attempt must be made to force the DUT to produce every possible output. As much as is safely possible, the DUT should be forced into every possible state and range of values, including error states.
To aid in this, RCT provides a Data Sniffer, which parses ALL messages coming from the DUT, and a WH-specific "control panel".
A full test should exercise every means by which a device changes state:
- RV-C commands. The control panel provides an easy interface for this. Each button sends a command to change a specific field.
- Integrated controls. e.g. the park brake switch in the dash, or the position of the ignition key.
- Changes in the environment. e.g. the location of the keyfob in a remote-ignition system.
- Internal changes. e.g. the shifting of the gears in an automatic transmission.
Make every attempt to "break" the DUT!!! This includes generating faults. Any fault that prevents the device from reporting a field accurately should generate an "Error" value in that field.
After exhausting all possibilities, press the Done button on the panel to end the test. RCT will then ask four questions:
- Did the Data Sniffer update promptly for all changes in device state?
- Did all Reported values match the Actual status?
- Were all Out-of-Range values reported correctly?
- Were all Error values reported correctly?
RCT can't see the real water heater so these answers must rely on human perception. The promptness and accuracy must be consistent with user expectations and the requirements of other devices that might rely on the data. In general, it should seem "instantaneous".
If you could not generate any Out-of-Range or Error values, select "Yes" for those questions.
RCT will log the results for WH-10 and all its associated field tests, including WH-20 and WH-30. If the DUT didn't provide data for any particular field, the corresponding test will be marked as Skipped , with reason: "No support detected".
WH-40 Water Heater Timer
This test requires the following setting.
- WH Timer Test OpMode
The test proceeds by setting the water heater to the indicated OpMode, then monitoring the timer. The only user intervention is to press
WH-50 Water Heater Change Set Point
This test requires the following setting.
- WH Set Point Test OpModes. Select all modes supported by the DUT.
The test proceeds automatically, looping through the selected OpModes and setting the Set Point to various temperatures while in those modes.
WH-60 Water Heater Change Electric Element Level
This test requires the following setting.
- WH Element Level Test OpModes. Select all electric modes supported by the DUT.
The test proceeds automatically, looping through the selected OpModes and setting the Element Level to various levels while in those modes. The test does not monitor the Max Element Level, and may register an error if there is a limit in place.
WH-70 Water Heater Change Hot Water Priority
This test requires the following setting. * WH Set Point Test OpModes. Select all modes supported by the DUT.
The test proceeds automatically, looping through the selected OpModes and setting the Priority to "Hot Water" or "Heating" while in those modes.
WH-80 Water Heater Hot Water Priority Timer
This test requires the DUT be started in any mode that allows the Priority to be set. For convenience, a control panel is provided to allow the status to be observed during the test.
Once
WH-90 Water Heater Set Engine Preheat
This test requires the following setting. * WH Set Point Test OpModes. Select all modes supported by the DUT.
This test proceeds automatically, looping through the selected OpModes and setting the Engine Preheat to "Off" and "On".
WH-110 Status DGN - CIRCULATION_PUMP_STATUS
This test proceeds automatically, toggling the Pump Output between "Off" and "On". This one test covers the following Status tests:
- WH-110 - CIRCULATION_PUMP_STATUS
- WH-111 - cpPumpOverCurrnt
- WH-112 - cpPumpUnderCurrnt
- WH-113 - cpPumpTemperature
- WH-120 - cpPumpOutput
For convenience, a control panel is provided to allow the status to be observed during the test and to send PumpOutput commands directly from RCT.
Like all Status Tests, WH-160 begins by monitoring the DGN for 20 seconds to determine whether it is being broadcast as specified. Next, a series of Request_for_DGN messages are sent to test whether the DUT responds promptly. While these tests are running, do not perform any operations which would force a change in the DUT's state.
Like most Status tests, RCT must ask whether the output of the DUT matches reality and values are updated promptly. All the considerations noted for WH-10 apply here as well. You must attempt to expose all the possible behaviors of the DUT, as much as practically possible.
WH-130 Circulation Pump Timer
This test requires the DUT be started in any mode that allows the pump to be forced on. For convenience, a control panel is provided to allow the status to be observed during the test.
Once
WH-140 Water Heater Timer Configuration
This test covers the following tests:
- WH-140 whSysTimerStartVal
- WH-150 whWaterTimerStartVal
It requires the following settings.
- WH Set Point Test OpModes. Select all modes supported by the DUT.
- WH Default System Timer Start Value.
- WH Default Water Timer Start Value
These allow RCT to return the unit to its default values at the conclusion of the test.
The test proceeds automatically, looping through the various modes and testing whether the configuration changes are applied correctly.
WH-160 Status DGN - WATERHEATER_STATUS_2
This is a DGN Status Test - it covers the ordinary use of the DGN and its fields. For convenience, the DGN and all of the fields are tested in one pass. Thus, testing WH-160 also covers WH-170 through WH-320. It also reports on several other data items contained in WATERHEATER_STATUS_2 that are not officially included in the RV-C testing specification.
Like all Status Tests, WH-160 begins by monitoring the DGN for 20 seconds to determine whether it is being broadcast as specified. Next, a series of Request_for_DGN messages are sent to test whether the DUT responds promptly. While these tests are running, do not perform any operations which would force a change in the DUT's state.
In the next stage, every attempt must be made to force the DUT to produce every possible output. As much as is safely possible, the DUT should be forced into every possible state and range of values, including error states.
To aid in this, RCT provides a Data Sniffer, which parses ALL messages coming from the DUT. A control panel is also provided to allow sending various commands directly from RCT.
Like most Status tests, RCT must ask whether the output of the DUT matches reality and values are updated promptly. All the considerations noted for WH-10 apply here as well. You must attempt to expose all the possible behaviors of the DUT, as much as practically possible.