Revisions Rev No. Date Description Rev 1 6/26/2008 Updated for hardware and firmware updates to SmartPoint Module. This document contains proprietary information. It is to be used only for the purpose for which it is intended. Information in this document is subject to change without notice and does not represent a commitment on the part of Sensus Metering SystemsNorth America, Inc.
Table of Contents i Table of Contents 1 Introduction ........................................................................................................................ 1-1 1.1 Purpose ..................................................................................................................................... 1-1 1.2 Safety ........................................................................................................................................ 1-1 2 SmartPoint Module Overview.
Table of Contents ii 4.4.3Meter Serial Number ......................................................................................................................... 4-3 4.4.4Latitude / Longitude........................................................................................................................... 4-3 4.4.5Programmer ID.................................................................................................................................. 4-4 4.4.5.1 Setup Flags ............
Table of Contents iii 4.11.5Current Meter Reading.................................................................................................................. 4-17 4.11.6Extended Time Since Event.......................................................................................................... 4-17 4.11.7Device Temperature...................................................................................................................... 4-17 4.11.8µP Status ..................................
Table of Contents iv 5.2.5Transmit Frequency Channels .......................................................................................................... 5-3 5.2.6Receive Frequency Channel............................................................................................................. 5-4 5.2.7C&I Mode Channel............................................................................................................................ 5-4 5.2.8Priority Mode Channel.........................
Table of Contents v (Narrow-Band PCS) 2 Systems Operating Under RSS-134 in Canada (Narrow-Band PCS) 2 A.3 SmartPoint Radio Transmit Modes ..........................................................................................A-2 Normal Mode 3 A.3.1.1 Staggered Transmissions .....................................................................................................A-3 A.3.1.2 Poll-response Message Traffic ........................................................................................
Introduction 1 1-1 Introduction 1.1Purpose This manual provides technical information for the FlexNet SmartPoint module installed in the Elster A3 meter. This document is intended for technically qualified personnel of energy supply companies and their contractors who are responsible for the system planning, installation, commissioning, operation, maintenance, decommissioning, and/or disposal of meters. 1.
SmartPoint Module Overview 2 2-1 SmartPoint Module Overview 2.1 FlexNet SmartPoint Assembly The SmartPoint assembly consists of a SmartPoint printed circuit board and a separate antenna printed circuit board. A 20-pin connector joins the SmartPoint module to the sensor board. The SmartPoint module is installed on three plastic standoffs inserted in the sensor board. The antenna is fitted into a slot on the side of the base. A 20-pin connector joins the SmartPoint module to the sensor board.
SmartPoint Module Overview 2-2 Figure 2-1: FlexNet Fixed Base AMI Network Overview 2.3.2 FlexNet AMI Local RF Network The Local RF network consists of FlexNet SmartPoint modules (transceivers) located at each meter, and a network of FlexNet Tower Gateway Base Stations (TGBs). 2.3.2.1 Meter Endpoints The integrated SmartPoint module communicates with the Elster A3 bus to provide internal AMR capability to the Elster meter for use on commercial services.
SmartPoint Module Overview 2-3 Figure 2-2: Elster Meter with SmartPoint Module Installed The SmartPoint modules transmit the meter consumption and status information at regular intervals. Critical meter status and power outage alarms are also monitored on a real-time basis. The SmartPoint module transmits the meter data to the fixed network using long-range, licensed, narrowband radio.
SmartPoint Module Overview 2-4 2.4 SmartPoint Terminology On-Air Messages (see Chapters 3 and 4). This term is used to describe messages sent by FlexNet endpoint devices. The exception to this is the command message, which carries On Air Commands from the RNI through the TGB to the endpoint (see Section 4.6). Serial Commands (see Chapter 5). These messages are used to control a FlexNet endpoint device over a serial interface.
On Air Message Format 3 3-1 On Air Message Format All fields are sent least-significant byte first.
On Air Message Format 3.1.5 3-2 Control Provides status data to the receiver. Bits 3.1.5.1 Control 0-3 RF Sequence Number 4 AC Power Failed 5 Power Restored 6 Low Battery Detected 7 Payload Encrypted RF Sequence Number A 4 bit modulo 16 counter, increments each RF transmission. 3.1.5.2 AC Power Fail Set if AC Power is not present. In AC only powered end point devices, set in Last Gasp messages. 3.1.5.
On Air Message Format 3.1.7 3-3 Repeat Level / Status Bits 0 History Overflow 1 In Time Sync 2 Tamper 3 Brown Out 4 Meter Read Failure 5 RF Sequence Number MSB 6-7 3.1.8 Repeat Level / Status Repeat Level Application Sequence An 8 bit modulo 256 counter that increments every time new application data is transmitted by the end point device. 3.1.9 Application Code An 8 bit code used to determine the format of the data in the Application Data field. 3.1.
On Air Message Format 3-4 3.3 Addressing Endpoint addresses are also called Meter ID, FlexNet ID, or Tx ID. In a FlexNet protocol packet, the endpoint address is carried in the Meter ID field defined above. 3.3.1 Command Addressing The Receiver will accept commands that are addressed to it via the Device ID of the on air message. The three accepted addresses are one that matches its own Device ID, one using the Broadcast Address, or, lastly, one using the Group Address. 3.3.
On Air Message Types 4 4-1 On Air Message Types All fields are sent least-significant byte first unless otherwise specified. The format of the data in the Application Data field dependent on the value of the Application Code field as follows and is always 28 bytes in length. 4.
On Air Message Types 4-2 rolls over (every 16 messages). The Application Data below show an example of the Testing Message with a sequence number of 0x64: 0x0064000102030405060708090a0b0c0d0e0f10111213141516171819 4.
On Air Message Types 4-3 Byte (Bits) Field 27 (0:3) Outage Time Threshold 27 (4:7) Restored Time Threshold Specific definitions for these fields are shown in Chapter 5, with the exception of the first two fields, Firmware Version and Device Type. Firmware version contains the version of the firmware of the device. If the most significant bit of Firmware version is set, the firmware is a beta test set. The Device Type is currently defined as Device Type 5. 4.
On Air Message Types 4.4.5 4-4 Programmer ID The 16 bit ID of the handheld programmer used to setup the device. 4.4.5.1 Setup Flags An 8 bit field indicating which setup messages have been received by the device. The individual bits in the byte are defined below: Setup Message Received Bit 0 Set ID 1 Static Setup 2 Set Crystal Offset 3 Set Lat / Long 4 Set Meter Reading 5 Set Voltage Quality Levels 6 Set Encryption Key 7 (reserved) 4.5 GPS Mapping Message 4.5.
On Air Message Types 4-5 4.5.1.1 Latitude These fields contain a representation, in degrees of the end point device’s installation latitude as presented by the attached GPS module. The actual latitude can be calculated using the following formula: Latitude (degrees) = (3 Byte App Data Latitude) * 90.0/8388608 Negative values are in the southern hemisphere; positive values are in the northern hemisphere.
On Air Message Types 4-6 4.7 Buddy Message—App Code 8 4.7.1 Message Format This is a message sent by a relaying two way transmitter sent after repeating a message in order to build routing information in the central database. Meter reading data from the repeating device has been added to the previously unused portion of the Buddy Message for extra system redundancy.
On Air Message Types 4.7.3 4-7 Buddy Fields These fields represent the values received in the message from the device that has been buddy relayed. 4.7.4 Queue Time The time in seconds that the buddy device stored the message before forwarding it. 4.7.5 Meter Reading Fields These fields, Relative Time Stamp, Current Reading and History Samples have the same format as that defined in the Type 12 Meter Read Message.
On Air Message Types 4-8 4.8 C&I Meter Read With History—App Code 13 4.8.1 Message Format This is the standard meter reading message and has the following format: App Data Byte Data 4.8.2 0-1 2-4 5-8 9-11 12-27 Relative Time Stamp Delta Data Type / Current Reading Peak Demand Reading Phase A, Phase B, Phase C Voltage History Samples Relative Time Stamp 16 bits of byte 0-1, elapsed time since last meter reading. Time is always represented in two-second resolution. 4.8.
On Air Message Types 4.8.6 4-9 Peak Demand Reading 32 bits, all of bytes 5-8. The peak demand reading is represented as a four byte floating point number in W. 4.8.7 Phase A, B and C Meter Voltages Three 8 bit fields containing meter line voltage readings of the voltage for all available phases at the time of the meter reading. The values in the fields can be converted to voltage using the following formula which provides voltages from 50 to 560 volts: Voltage = Value*2 + 50 4.8.
On Air Message Types 4.8.9 4-10 Fixed Bin Width History Samples All bits of bytes 12-27. As many History Sample bins as possible are packed into the remaining space in the on air message. Each history sample is stored as the difference from the last reading. Note: A residential meter at maximum load can generate 346 counts per hour. The size and number of History Sample bins in the message are determined by the Delta Data Type field are shown in the following table (6-7 are reserved).
On Air Message Types 4-11 App Data Bytes 4.9.2 Data 21 # Demand Resets 22 Summation Source Index 23 Demand Source Index 24 Coincident Source Index 25 Quantity of Tier Information Tier Information 8 bits of byte 0 (bit 7 is reserved). Used to identify the tier and sub tier of the data in this message. A separate message is sent for each Tier and SubTier configured in the meter as defined in the following tables: Bits 0-2 Tier 3-6 Sub Tier 7 4.9.2.
On Air Message Types 4.9.3 4-12 Meter Type Lower 6 bits of byte 1. The type of data and unit of measure reported in the tier data message is dependant on the meter type as defined below: 4.9.4 Value Meter Type 0 (reserved) 1 Elster A3R 2 Elster A3K 3 Elster A3D 4 Elster A3T 5 Elster A3Q 6-255 Reserved Selected Data Table Upper 2 bits of byte 1. This selects data from table ST-23, ST-24, or ST-25: 4.9.
On Air Message Types 4-13 2 (4-7) Peak Demand Month 0-11 = Jan-Dec 3 (0-4) Peak Demand Day 1-31 = 1st to the 31st 3 (5-7), 4 (0-1) 4 (2-7) 4.9.6 Peak Demand Hour 0-23 = Midnight to 11:00pm Peak Demand Minute 0-59 Summation Reading (103 resolution) Bytes 5-8. The Summation for this Tier and Sub Tier in represented as a floating point number in kilo resolution. 4.9.7 Demand Reading (100 resolution) Bytes 9-12.
On Air Message Types 4.9.12 4-14 Quantity of Tier Information 8 bits of byte 23 (bit 7 is reserved). Used to report the total number of tiers and sub tiers in all of the tier data in this messages as defined in the following tables: Bits Description 0-2 Number of Tiers 3-6 Number of Sub Tiers 7 Reserved 4.9.12.1 Number of Tiers Bits 0-2 of the Quantity of Tier Information byte which represent the number of reported tiers not including the Totalization tier.
On Air Message Types 4-15 4.10 C&I Tunneling Read—App Code 15 Message Format: This message is used to transmit raw C12.19 table data in response to a C12.19 Table Read Command. The Application Sequence number of this message matches that of the Table Read Command. The C12.19 table and offset of the raw data also match the command. If the number of returned bytes is 0, then an error has occurred reading the table.
On Air Message Types 4-16 4.11 C&I Alarm Message – App Code 16 4.11.1 Application Data This message contains alarm data from the meter and is also used to report power failures. App Data Bytes 0 Voltage Phase A 1 Voltage Phase B 2 Voltage Phase C 3 Click Count 4 Time Since Event 5-6 Extended Time Since Event 7-9 Current Reading 10 Device Temperature 11 µP Errors 12 Lock Errors 13-14 15 4.11.
On Air Message Types 4.11.5 4-17 Current Meter Reading 20 bits, of the meter setting. All 6 decimal meter digits represented in binary. 4.11.6 Extended Time Since Event A 16 bit fields containing the MS two bytes of Time Since Event in 1536 second resolution since a power failure or power restoration actually occurred. This yields over 3 years of possible measurement.
On Air Message Types 4-18 4.11.10 Alarm Data All bits, bytes 13-14. The Alarm provides 16 bit fields, each of which can represent a different failure mode as shown in the table below.
On Air Message Types 4-19 4.11.13 Flags An eight-bit field containing two status flags, one indicating an EEROM is available on the board, and another indicating that the temperature exceeds the programmed threshold. Bits Description 7:2 Reserved 1 Hot Socket Alarm 0 Interval EEPROM Available 4.12 Demand History Message—App Code 25 4.12.1 Message Format This message is sent in response to Demand Reset commands and Demand History pings. All values are read from C12.
On Air Message Types 4-20 Byte (Bits) 17(5:7),18(0:1) 18(2:7) 4.12.2 Field 2nd Peak Demand Hour (0-23) 2nd Peak Demand Second (0-59) 19-22 2nd Peak Demand (floating point Watts) 23-26 2nd Consumption Reading (floating point Wh) Number of Demand Resets Number of times this meter reports that it has had it’s Peak Demand reset. 4.12.3 Last Demand Reset Date and Time The time and date that this meter last had its’ demand reset via on air command. 4.12.
On Air Message Types 4-21 4.13 Load Profile Metadata Message—App Code 28 Message Format: This message is sent in response to a Load Profile Metadata ping. All values are read from C12.19 tables in the meter. Elster document “DD228-01.05/01.02 A3 Tables for 3rd Party Developers” can be used as additional reference. The references ST-xx and MT-xx represent C12.19 Standard Table xx and Manufacturer’s Table xx respectively.
On Air Message Types 4-22 The format of the message is as follows: Byte (Bits) Field 0 (0:3) Message Sequence Number 0 (4:6) Number of Messages 0 (7) LP Read Failed 1-n LP Samples, from ANSI C12.19 table ST-64 n+1 - n+4 (Last Message Only) The ANSI C12.
On Air Message Types 4-23 4.15 Firmware Image Check Response—App Code 30 Message Format: The device responds back to the download host with a Firmware Image Check Response packet containing the number of bad blocks in the response, followed by a sequence of block numbers ( wordsized, 2 bytes each, little endian ) which have not been received by the device since the last Load Start message was received.
On Air Message Types 4.17.1 4-24 Demand Enable Status/Interval Configuration Ping Response to Data Byte (Bits) 0 (0) 0 (1:7) Message Sequence Number Number of Messages 1 LP Read Failed 2 LP Samples, from ANSI C12.19 table ST-64 3 (Last Message Only) The ANSI C12.19 Sequence Number of the Block Requested 4 - 26 4.17.
On Air Message Types 4-25 Ping Response to Data Byte (Bits) Field 18 (B) Tier 3: Last 15-Min Interval (1-96) 19 (B) Tier 4: First 15-Min Interval (1-96) 20 (B) Tier 4: Last 15-Min Interval (1-96) 21 (0:3) Weekend Tier 21 (4:7) Holiday Tier 22-26 SmartPoint Module for the Elster A3 Meter (reserved) ECMTM40000
On Air Message Types 4.17.
On Air Message Types 4-27 Ping Response to Data Byte (Bits) 22-23(0) 23(1:7)-26 SmartPoint Module for the Elster A3 Meter Field Holiday 12: Julian Day (0-366) Reserved ECMTM40000
On Air Message Types 4.17.5 4-28 Click History Ping Response to Data Byte (Bits) 4.17.6 Field 0-3 Epoch Time of Click 1 4-7 Epoch Time of Click 2 8-11 Epoch Time of Click 3 12-15 Epoch Time of Click 4 16-19 Epoch Time of Click 5 17-20 Epoch Time of Click 6 21-24 Epoch Time of Click 7 25-26 Reserved Load Limit Status/Threshold Ping Response to Data Byte (Bits) 0 (0:6) 0 (7) 1 3-26 4.17.
On Air Message Types 4.17.
On Air Message Types 4-30 4.18 C&I High Res Read with History Data—App Code 55 4.18.1 Application Data This message contains the C&I High Res Read with History Data as defined in the table below, sent in response to a Meter Read Ping message when the meter is in high res mode. Ping Response to Data Byte (Bits) 0-1 Relative Time Stamp 2 Delta Data Type (0:2) Click Count (3:7) 3-6 Current Consumption (ST23 SUMMATIONS[0]) 7-10 Peak Demand Reading (ST23 DEMANDS[0].
On Air Message Types 4-31 History Samp Interval (min) Delta Data Type 4.18.4 5 1440 (24 Hours) 6 240 (4 Hours) Click Count Byte 2 bits 3-7: The 5 LSBs of the modulo-256 click counter, a count of short duration power outages. 4.18.5 Current Consumption (wH resolution) Bytes 3-6. The Current Consumption in represented as a 32 bit integer number in wH resolution. 4.18.6 Peak Demand Reading 32 bits, all of bytes 7-10.
Setup and Configuration 5 5-1 Setup and Configuration 5.1 Electrical Configuration Interface 5.1.1 Magnetic Loop When the CPU detects the presence of a modulated magnetic field, it prepares to receive a setup message. Immediately after successful programming, the transmitter sends 4 Meter Setup / Configuration (Type 0) messages in 60 seconds. The message is sent using mode commanded by the setup command and is then repeated in the mPass mode.
Setup and Configuration 5.2.2 5-2 Meter Sample Rate The 3-bit field indicating how often the meter is read using the Elster interface. The meter is sampled without dither and is synchronized to the top of the hour by a real-time clock. The field is defined as shown in the table below (6-7 are reserved): Meter Sample Rate Field Value 5.2.
Setup and Configuration 5-3 12 4.5 hours 54 min 216 – 324 min 13 5 hours 60 min 240 – 360 min 14 5.5 hours 66 min 264 – 396 min 15 6 hours 72 min 288 – 432 min 16 7 hours 84 min 336 – 504 min 17 8 hours 96 min 384 – 576 min 18 9 hours 108 min 432 – 648 min 19 10 hours 120 min 480 – 720 min 20 12 hours 144 min 576 – 864 min 21 18 hours 216 min 864 – 1296 min 22 24 hours (1 day) 288 min 1152 – 1728 min 23 36 hours (1.
Setup and Configuration 5-4 Transmit Frequency (MHz) = Base Frequency (MHz) + (Transmit Frequency Channel * .00625) 5.2.6 Receive Frequency Channel A 16-bit field (13 used) representing the receive channel from 0-8000 spanning 50 MHz of bandwidth in 6.25 kHz slots. The Receive Frequency is determined using the following equation: Receive Frequency (MHz) = Base Frequency (MHz) + (Receive Frequency Channel * .00625) 5.2.
Setup and Configuration 5.2.10 5-5 Transmit Operational Mode A 4-bit field containing the transmission mode of the Transmitter as shown in the table below. Note that if the device is configured to Message Pass, it will always transmit on the Receive Frequency (all mPass transmissions are on the Rx Channel). Setting 5.2.
Setup and Configuration 5.2.12 5.2.13 5-6 Enable Encryption Setting AE-256 Encryption 0 Off 1 On Programmer ID A 16-bit field code containing the Id number of the handheld programming device that set up this device. 5.3 Setup Messages 5.3.
Setup and Configuration 5.3.2 5-7 Basic Command Message Format All setup command messages (setup tool to device) with have the following basic format: Byte 0 1 2 3 4->n n+1, n+2 Description Sync Address Command Type Length Data CRC Value 0x1b 0xff 0x9n # Bytes in Data Field CRC is a 16-bit CRC of all of the previous fields, the algorithm used is CCITT-16 (0x1021 or 0x8408 reversed).The remainder is initialized to all 1's (0xFFFF) and the CRC is inverted before being sent, MSB first.
Setup and Configuration 5-8 WORD crc16_lsb(BYTE *pData, WORD length) { BYTE i; WORD data, crc; crc = 0xFFFF; if (length == 0) return 0; do { data = (WORD)0x00FF & *pData++; crc = crc ^ data; for (i = 8; i > 0; i--) { if (crc & 0x0001) crc = (crc >> 1) ^ 0x8408; else crc >>= 1; } } while (--length); crc = ~crc; return (crc); } For example, a Status Request command: 1b ff 91 00 Would generate the following CRC: 1c 39 The complete message would be as follows: 1b ff 91 00 1c 39 SmartPoint Module for the Elst
Setup and Configuration 5.3.3 5-9 Basic Reply Message Format Reply Messages are only sent in response to a command, and are only sent if a direct serial connection is present (serial Reply Messages are NOT sent if the magnetic programming loop interface is used, responses can be gathered via the on-air Meter Setup / Configuration Message).
Setup and Configuration 5-10 Byte (Bits) Field 17-18 Transmit Channel C 19-20 Transmit Channel D 21-22 Receiver Channel 23-24 Boost Mode Channel 25 (0:3) 25 (4) Boost Mode Sub-Channel Boost Mode Hopping 25 (5:7) Transmit Channel Mask 26 (0:3) Transmitter Operational Mode 26 (4:6) Receiver Operational Mode 26 (7) Enable Encryption 27-28 Programmer Id 28 (7) Disable Compression 29-30 TXCO Correction 31-34 Latitude 35-38 Longitude 39-41 Meter Reading 42 Minimum Click Duration
Setup and Configuration 5-11 The data field in the reply message has the 1 byte data status byte only in the following format: Byte (Bits) 4(0) 4(1:6) 4(7) Field Status EEROM Write Failed(1) (Reserved) Status ACK(0) / NACK(1) 5.6 Device Static Setup Set all of the operational parameters of the device.
Setup and Configuration 5-12 The data field in the reply message has the 1 byte data status only. 5.7 Set TCXO Correction (0x94) Set TCXO Correction frequency offset. The command has the following format: Msg Type Length Bytes 0-1 0x94 2 TCXO Correction CRC The data field in the reply message has the 1 byte data status only. 5.8 Set Latitude/Longitude (0x95) Set the installation latitude and longitude.
Setup and Configuration 5-13 5.10 Set Voltage Quality Thresholds (0x97) Set the thresholds that control voltage quality based Alarm Messages.
Setup and Configuration 5-14 The data field in the reply message has the 1 byte data status only. 5.13 Send Data (0x9A) Send a message using the device’s ID and frequency settings. The command has the following format: Msg Type Length Byte 0 Byte 1 Byte 2 Byte 3-30 0x9A 31 Repeat Level/Status App Seq App Code App Data CRC The data field in the serial reply message has the 1 byte data status only. 5.14 Ping (0x9C) Ping the device, which responds with on-air commands.
Setup and Configuration 5-15 Ping Type Device Response 7 – Handheld mPass Demand Read Ping – Buddy Disabled mPass On Air Demand Read Message – Repeat Level set to 1 to block buddy 8 – Meter Read Message On Air Meter Reading Message (no alarms) 9 – Full Tier Data Meter Read Send Meter Reading Message followed by available Tier Messages 10- Test Meter Read On Air Meter Reading Message (no alarms) preceded by a meter reading 11 – Single Tier Data Meter Read Single Tier Data Message – The byte afte
Setup and Configuration 5-16 5.16 Set Customer ID (0x9E) Set the 4 bit Customer Meter ID number used for routing and customer differentiation in a local market. The command has the following format: Msg Type Length Byte 0 0x9E 1 Customer ID CRC The data field in the serial reply message has the 1 byte data status only. 5.
Setup and Configuration 5-17 Byte (Bits) Field 2-3 Transmit Channel 4-7 Device Id 8 Repeat Level / Status 9 App Seq 10 App Code 10-38 App Data The data field in the reply message has the 1 byte data status only.
Receiver Section 6 6-1 Receiver Section The device receiver section may be de-populated to reduce cost for a transmit only version using the same printed circuit layout. 6.1 Receiver Requirements 6.1.1 Operation Modes Receivers always listen for messages on a line powered end-point. Battery operated receivers listen for message only after transmitting a message.
Receiver Section 6.2.2 6-2 7 Demand Read Yes Yes 8 Ping No Yes 9 Set Transmitter Id No No 10 Set Customer Id No Yes 11 Set Encryption Key Yes Yes 12 Set Preferred Buddy No No 13 Set Customer Meter Number No No 17 Demand Reset No Yes 19 Set Group Address No No 20 Delay Supervisory Transmissions Yes No Command Acknowledge A message to acknowledge a previously transmitted message by the device.
Receiver Section 6-3 12 Setup Flags (Reply from Tower Only) 13-31 (reserved) The definition of the Auxiliary Status and (reserved) fields can be defined differently for different Command Types. They are set to 0 unless otherwise specified per command Type. 6.2.3 Set Static Setup A command to force the device update its static setup: Byte (Bits) 6.2.
Receiver Section 6.2.5 6-4 Set Latitude and Longitude A command to force the device update its position: Byte (Bits) 6.2.
Receiver Section 6-5 6.2.
Receiver Section 6.2.9 6-6 Ping A command that with no setup information that only causes the device to respond with ack message or set of messages.
Receiver Section 6-7 10- Test Meter Read On Air Meter Reading Message (no alarms) preceded by a meter reading 11 – Single Tier Data Meter Read Single Tier Data Message – The byte after the ping type contains the Tier Information byte for the desired tier. Note: Does not re-read meter.
Receiver Section 6.2.11 6-8 Set Customer Id A command to set the 4 bit customer id. Byte (Bits) 0 Repeat Level / Status 1 App Sequence 2 App Code: 7 – Command Message 3 Command Type: 10 – Set Customer Id 4-7 8 (0:3) 9-31 6.2.12 Field Buddy Routing Address Customer Id (reserved) Set Encryption Key A command to set the 16 byte encryption key.
Receiver Section 6.2.13 6-9 Set Preferred Buddy Id A command to set the 4 byte preferred buddy address for this meter. Byte (Bits) 0 Repeat Level / Status 1 App Sequence 2 App Code: 7 – Command Message 3 Command Type: 12 – Set Preferred Buddy Id 4-7 Buddy Routing Address 8-11 Preferred Buddy Address 12-31 6.2.14 Field (reserved) Set Company Meter Number A command to set the 13 byte customer number.
Receiver Section 6.2.15 6-10 C&I Read C12.19 Data A command to read raw C&I Table data. Byte (Bits) 0 Repeat Level / Status 1 App Sequence 2 App Code: 7 – Command Message 3 Command Type: 15 – Read C&I Meter Data 4-7 Buddy Routing Address 8-9 C12.19 Table Number 10-12 13 14-31 6.2.16 Field Table Offset # Bytes to Read (0-27) (reserved) C&I Write C12.19 Data A command to write raw C&I Table data.
Receiver Section 6.2.17 6-11 C&I Demand Reset A command reset the Demands in the C&I Tables. Byte (Bits) Field 0 Repeat Level / Status 1 App Sequence 2 App Code: 7 – Command Message 3 Command Type: 17 – Demand Reset 4-7 Buddy Routing Address 8-31 (reserved) 6.3 Command Addressing The Receiver will accept commtches its own Device Id and one using the Broadcast Address, which is all 1’s or 0xFFFFFF. Broadcast messages are not acknowledged. 6.4 Receiver Miscellaneous 6.4.
FlexNet SmartPoint Radio Overview Appendix A A-1 FlexNet SmartPoint Radio Overview The Sensus FlexNet SmartPoint module provides wireless communication capability to electric utility meters. The SmartPoint module interrogates the meter registers on a programmable interval from five minutes to daily readings. The SmartPoint module then transmits the meter consumption and status information at regular intervals.
FlexNet SmartPoint Radio Overview A-2 It is important to specify the actual operating frequency range of the TGB when it is ordered so the correct RF card frequency range is delivered to the installation. A.2.1 Systems Operating Under Part 24 of FCC Rules (Narrow-Band PCS) US NBPCS Frequency: • Inbound:901.125 MHz ±25 KHz • Outbound:940.125 MHz ±25 KHz A.2.2 Systems Operating Under RSS-134 in Canada (Narrow-Band PCS) Canadian NBPCS Frequency: • Inbound:901.625 MHz ±25 KHz • Outbound:940.
FlexNet SmartPoint Radio Overview A.3.1 A-3 Normal Mode Normal mode, as its name implies, is the preferred mode of transmitter operation for the SmartPoint when the SmartPoint is operating in a 25 KHz channel (13.6 KHz if operating under FCC Part 90 Rules). Normal mode is utilized by the SmartPoint for the RF path from the SmartPoint to the TGB.
FlexNet SmartPoint Radio Overview A-4 In these locations, the mPass mode communications method is used. The mPass mode also is the modulation type used by the TGB when it communicates with any SmartPoint device. These communications constitute (but are not limited to): • Timekeeping chores (allowing the EMD to set its internal clock, correcting for EMD crystal aging by re-tuning the EMD RF frequency within 50 Hz, etc.), • Polling tasks (gathering data from an individual EMD such as rate tables etc.
FlexNet SmartPoint Radio Overview A-5 A.3.3.1Buddy Mode Using mPass Transmissions Figure A-1: Remote SmartPoint to Tower mPass Buddy Mode Schematic Figure A-1shows how a remote SmartPoint device out-of-range of any tower, an ORD, can send messages in mPass mode to other Buddy transceivers, which then relay the ORD messages on to the tower. 1. The out-of-range transceiver (or transmit only device) sends an mPass modulated message which is received by multiple Buddy transceivers.
FlexNet SmartPoint Radio Overview A-6 Figure A-2: Remote Tower to SmartPoint mPass Buddy Mode Schematic 1. The tower sends an mPass-modulated message with the address of the outof-range transceiver as the primary address, and the address of the desired relaying Buddy as the Buddy Routing Address. The Buddy receives the message and identifies it as one the Buddy is commanded to relay. 2. The Buddy transmits the repeated message in the mPass channel to the outof-range transceiver. A.
FlexNet SmartPoint Radio Overview A.4.3 A-7 RNI Data Security The meter data stream is terminated at the RNI, where it is received via a secure, encrypted tunnel from the TGB. The actual meter readings are decrypted at this point using the WEP keys, and inserted into the utility customer-controlled meter-read database. A.4.4 Separation of Customer Data Another unique feature of the FlexNet system is the separation of customer data from network telemetry.
Specifications Appendix B B-1 Specifications B.1 External AC Line Power • DC Supply A: 13 VDC +/- 1V, 150mA max • Maximum Message Duration: Supported by supply capacitor, 200 ms B.2 Current Consumption The end point device shall have three modes of operation and a different current requirement for each. • Quiescent Mode: Normal quiescent state. Entered during periods of no input or reading activity to charge capacitor, microprocessor and local high speed crystal always running.
Specifications B-2 B.4 Internal Power Supplies B.4.1 Micro Power Regulator Always on, supplies power to CPU, VCO, Buffer Amplifier, Synthesizer, TCXO, and Receiver (if implemented). • Drop Out: 60mV @ 50 mA load • Minimum Voltage Input: 3.4V • Maximum Voltage Input: 3.8V • Voltage Output: 3.3V B.4.2 DC to DC Converter Enabled during transmit operation.
Index Index A AC power fail 2 alarm data 18 alarm messages 16 alarms click count 16 current meter reading 17 data 18 device temperature 17 extended time since event 17 lock errors 17 microprocessor status 17 power failure 1 time of last power failure 18 time since event 16 total number of outages 18 voltage phase 16 App code 1 2, 9 App code 5 3 App code 7 5 App code 8 6 application code 3 application codes alarm data 18 alarm messages 16 buddy message 6 click count 16 coincident reading 13 command message
Index set real time clock 13 set TCXO correction 12 set voltage quality threshold 12 command types, receiver 1 company meter number 9 component descriptions 1 compression enabled 8 compression enabled history 9 configurable parameters 1 base frequency channel 3 boost mode channel 4 enable encryption 6 endpoint id 1 meter sample rate 2 programmer id 6 receive frequency channel 4 receiver operational mode 5 supervisory transmit rate 2 transmit channel mask 4 transmit frequency channels 3 transmit operational
Index Q mPass mode 3 N narrow-band PCS 2 normal mode 3 notification, power restoral 1 number of demand resets 20 O on air time requirements 3 on air control fields AC power fail 2 battery low 2 payload encrypted 2 power restore 2 RF sequence number 2 on air fields application code 3 application data 3 application sequence 3 control 2 CRC 3 ID number 1 length 2 message leader 1 repeat level/status 3 sync 1 on air message format 1 on demand read 5 operating frequencies 1 operation modes 1 optical direct s
Index service quality 14 set A/D calibration 12 set company meter number 9 set customer id 15 set customer meter number 14 set device id 10 set encryption key 12 set encryption key, receiver 8 set installed latitude/longitude 12 set latitude and longitude 4 set preffered buddy id, receiver 9 set real time clock 13 set static setup 3 set TCXO correction 12 set TCXO correction, receiver 3 set time 5 set transmitter id 7 set voltage quality settings 4 set voltage quality threshold 12 setup messages 6 basic com