Introduction - KNX

More documents

Recommendations

Info

Contents 00 – closed 01 – opened 02 – released (ready to open) 00 – closed 01 – opened 02 – released (ready to open) 03 – moving 04 - ready The Dutch approach is to refer to the valve as remotely controlled device; the MUC approach is to refer to the valve as Digital Output. Note that in the German approach I personally would have selected “Digital Input” (VIFE=1BH) for valve status (MUC_080128_inkl_Anlagen.pdf SRR section 5.3.4). Meter fault / alarm handling (MUC_080128_inkl_Anlagen.pdf section 5.2.4) The extended error flag (German definition DIF=n4H, VIF=FDH, VIFE=17H) is not used in the Dutch version. The error flag in the Data Header is used in the Dutch version. This limits the number of errors in the Dutch definition to eight bits, five of which are predefined. Time Synchronisation The Dutch smart meter specifications include time synchronisation. Whether or not Daylight Savings Time is used is up to the grid company managing the meter. The MUC documents include Summer/Wintertime (DST) updates (MUC_080128_inkl_Anlagen.pdf SRR section 5.2.5). Indexes Log (MUC_080128_inkl_Anlagen.pdf SRR section 5.2.8). In the Dutch smart meter specifications, the M-Bus devices (meters) do not maintain logging. The MUC maintains all historic logs, meters transfer current measured data. The indexes log functions are therefore not used in the Dutch version. Gas Volume, transfer and calculation OMS chooses to Define a new gas metering device to enable transfer of corrected volumes (OMS-Spec_Vol2_Primary_v102.pdf section 4.3.1). In our opinion, the device is still a regular gas meter; however the data item is different. We choose to define a new DIF/VIF combination to signify corrected gas volumes. This would, in theory and in future systems, also allow the transfer of both corrected and uncorrected volumes by one single M-Bus device (MUC_080128_inkl_Anlagen.pdf SRR section 5.3.2). Other Data Transfers The Dutch Smart meter specifications do not define large storage indexes for metered data, however the meter reading of the previous full hour is stored as storage index #1. The is never more than one measured value stored in the Dutch meters. In the MUC documents, measurement and reading logs are defined (MUC_080128_inkl_Anlagen.pdf SRR section 5.4). Review M-bus.doc 4 04/12/2008
Other issues Frame Format The MUC_080128_inkl_Anlagen.pdf SRR section 5, ANNEX A: WIRELESS M- BUS MESSAGES, refers to the FT1.2 message format. For all wireless transmissions the FT3 message format should be used. This is corrected in the OMS-Spec- Vol1_General_v100.pdf and OMS-Spec_Vol2_Primary_v102.pdf. Wireless modes I strongly suggest to choose between S2 and T2 modes for wireless transmissions. Leaving the choice open will probably not help much in designing interoperable systems. (MUC_080128_inkl_Anlagen.pdf SRR section 3.1). Differences between OMS/MUC and Dutch approach 1 Topic RWE spec Dutch spec Identification Serial Number R/W R - Header Meter Type R R - Header Manufacturer text R - Manufactured date R - Volume / Tariff Volume Index Corrected W - Volume Index with Active Tariff R - New Tariff – Effective date/time W - Valve Valve State R/W R/W Valve Number of Closes R - Battery Remaining Battery Days R - 2 System State Date and Time R/W R/W Time Synchronisation Offset W - Extended Error Flag R/W - Daylight Saving R/W - Information Transfer Meter Information Request R - Transparent Information R/W - Configuration Time between RF polls R/W - 3 1 Note that the Dutch specification explicitly specifies that all DIF/VIF codes in the EN13757-3 can be exchanged. It is likely that some data objects do not contain useful information, but technically they can be exchanged. In this table we only refer to data objects that will contain “defined and useful data”. 2 Calculated in MUC Review M-bus.doc 5 04/12/2008
Page 1 and 2: Review M-Bus documentation as inclu
Page 3: • Does this mean that a “rogue

Introduction - KNX

Create successful ePaper yourself

Delete template?

Save as template?