Hi guys;
I'm using Wavenet Explorer to read (and configure) some Elster-Kent (Coronis) 'WaveFlow' water-meter MIUs in a sub-metering installation. These are used "stand-alone" with a WaveLook LCD display unit and a WavePort USB RF modem (ie not with AMR). I have some questions about using the the "Profile" feature of the WaveFlow module, specifically on a 4-channel MIU. According to the spec sheet on the WaveFlow, the MIU is able to store the last 12 total readings at the selected profiling interval. Referring to the attached screengrabs :

1) Can somebody explain the difference between the use of the "Profile" and "Extended Profile" tabs ?
To me it looks like under the "Profile" tab, I can retrieve the last 12 profile readings (raw and scaled data); but only for the meters connected to MIU channels A and B.
By comparison, under the "Extended Profile" tab, I can see profiled readings for all 4 meters, but only the last 5 readings. Why is that ?
This might well be a limitation/quirk in the MIU itself, ie nothing to do with Wavenet itself.
2) What does it mean when Wavenet returns a "-1" code for a profile slot ? Referring to the attached screengrab from the "Extended Profile" tab (the one showing 5 records for all 4 meter channels); you can see that the second slot (ie the second most recent profile snapshot) shows -1's for the raw data of all 4 connected meters (I have 3 meters connected to this 4-channel MIU, profiling at 1-day intervals at midnight). This always seems to happen in the second slot, ie as days go by, it is always the second slot that shows -1's, irrespective of the date.
Is this something with Wavenet Explorer, or do I have a faulty MIU ?
Thanks
Sparks

Profile is the last 12 values on the first 2 channels.
Extended profile is the last 4 values on 4 channels.
Most waveflows these days have only 1 or 2 pulse counters/channels.
So, if you are using all 4 channels on the waveflow, you have to use extended profile to get the 3rd and 4th channel's profile.
Otherwise, you can use the profile.

So yes, the limitation for profile I think is actually in the size of the packet

regarding extended profile
I dont really know what that means
I also get -1 (or 4294967295, or 0xFFFFFFFF) when reading using Coronis's own program, as can be seen in
IndexA0="1"
IndexA1="4294967295"
IndexA2="1"
IndexA3="0"
IndexA4="0"
IndexA5="0"
IndexB0="0"
IndexB1="4294967295"
IndexB2="0"
IndexB3="0"
IndexB4="0"
IndexB5="0"
IndexC0="3"
IndexC1="4294967295"
IndexC2="3"
IndexC3="3"
IndexC4="3"
IndexC5="3"
IndexD0="2"
IndexD1="4294967295"
IndexD2="2"
IndexD3="2"
IndexD4="2"
IndexD5="2"

and
from the actual bytes returned by the device:
00000001 ; A0
00000000 ; B0
00000003 ; C0
00000002 ; D0
FFFFFFFF ; A1
FFFFFFFF ; B1
FFFFFFFF ; C1
FFFFFFFF ; D1
00000001 ; A2
00000000 ; B2
00000000 ; C2
00000000 ; D2
00000000 ; A3
00000000 ; B3
00000000 ; C3
00000000 ; D3
00000003 ; A4
00000003 ; B4
00000003 ; C4
00000003 ; D4
00000002 ; A5
00000002 ; B5
00000002 ; C5
00000002 ; D5
0E0909 ; date
01 ; day of week
0800 ; time
13 ; measure period

Hi Matiaan
Great, thanks for the clarification on the Profile and Extended Profile.
Regarding the -1's ... OK, that's pretty weird, looks like a bug in the MIU itself, possibly only in the 4-channel version. I haven't tried reading the Extended Profile on a 2-channel MIU (not that there would be much point, other than to confirm the MIU bug).
So I guess the lesson/workaround here is to put one's "most important" meters on MIU channels 1 and 2 if you have a 4-channel MIU. That way you get full profile history (ie all 12 snapshots) for channels A and B, with no -1 problem.
Bit of a bummer to lose 25% of the available capacity on the Extended Profile, though :-|
Thanks again
Sparks

Something else I just noticed .. referring to the same two screengrabs ... the data for Profile and Extended Profile is different for the same meter, on the same channel, at the same time .. !?
For example, Meter A at 00:00 (midnight) on 19/11/2012 :
Profile : 330171 / 165.0855kl
Extended Profile : 332659 / 166.3299kl
Looking further, I can see that the index readings for the Extended Profile are displaced by two days relative to the Profile, ie the index readings for 00:00 on 21/11 in the Profile (eg 332659 on Meter A) appear identically in the Extended Profile, but two days earlier, ie at 00:00 on 19/11.
Maybe a data offset problem between Profile and Extended Profile ? Could be (another) problem in the 4-channel MIU itself.
Sparks