20 Customer interface Page 98 of 142
MCS301 meter - product Manual 1.25 MetCom Solutions GmbH
See below example telegram
/MCS5\@00000000001234
0-0:1.0.0(101209113020W)
0-0:96.1.1(4B384547303034303436333935353037)
1-0:1.8.1(123456.789*kWh)
1-0:1.8.2(123456.789*kWh)
1-0:2.8.1(123456.789*kWh)
1-0:2.8.2(123456.789*kWh)
1-0:1.7.0(01.193*kW)
1-0:2.7.0(00.000*kW)
1-0:32.7.0(220.1*V)
1-0:52.7.0(220.2*V)
1-0:72.7.0(220.3*V)
1-0:31.7.0(001*A)
1-0:51.7.0(002*A)
1-0:71.7.0(003*A)
1-0:21.7.0(01.111*kW)
1-0:41.7.0(02.222*kW)
1-0:61.7.0(03.333*kW)
1-0:22.7.0(04.444*kW)
1-0:42.7.0(05.555*kW)
1-0:62.7.0(06.666*kW)
0-1:24.1.0(003)
20.3 Data interface according IDIS package 2 specification
The data from the meter pushed to the CII (consumer information interface) are secured
(encryption and/or authentication) by the meter.
• If it is secured, then security suite 0 is applied.
• The security material used for this Meter-CII- ConsumerEquipment communication is
independent of the security material used for the remote Meter-HES communication.
The CIP security context is defined in a dedicated security setup object. The keys (CIP keys)
used for the data pushed to the CII are managed by the HES. To change a CIP key:
1. the HES wraps the new CIP key with the meter’s master key,
2. the HES sends the wrapped key to the meter using the method global_key_transfer of
the object “Security setup-Consumer Information” (logical_name: 0-0:43.0.1.255) via
the Management Client association.
Figure 163: Key handling of the customer interface
To Next Page
Loading...
Need help?
General