Iec 60728 7 3 2009

IEC 60728-7-3Edition 2.0 2009-10 INTERNATIONAL STANDARD Cable networks for television signals, sound signals and interactive services – Part 7-3: Hybrid fibre coax outside plant statu

Terms and definitions

For the purposes of this document, the following definitions apply

DLL layer 2 in the Open System Interconnection (OSI) architecture; the layer that provides services to transfer data over the physical transmission link between open systems

An NE is a crucial component in the outside plant (OSP) that can receive commands from a head-end element (HE) and, when needed, relay status information and alarms back to the HE.

The OSI framework, established by the International Organization for Standardization (ISO), standardizes communication between multi-vendor systems by organizing the communication process into seven distinct layers These layers are arranged in a sequence that reflects their relationship to the user.

Each layer in the network architecture relies on the layer beneath it while offering services to the layer above Layers 7 to 4 focus on facilitating end-to-end communication between the source and destination of messages, whereas layers 3 to 1 are responsible for essential network functions.

The Physical (PHY) layer 1 in the Open System Interconnection (OSI) architecture is responsible for transmitting bits or groups of bits over a transmission link between open systems This layer encompasses essential electrical, mechanical, and handshaking procedures to ensure effective communication.

The transponder device connects to outside plant (OSP) network elements (NEs) and communicates status and alarm information to the headend (HE) It is capable of interfacing with an active NE through a combination of parallel analog, parallel digital, and serial ports.

LICENSED TO MECON LIMITED - RANCHI/BANGALORE, FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.

Abbreviations

CATV Community Antenna Television (network)

HMS Hybrid Management Sub-Layer

ISO International Organization for Standardization

MATV Master Antenna Television (network)

PSTIB Power Supply to Transponder Interface Bus

SNMP Simple Network Management Protocol

Tx En Transmit Enable xpndr Transponder

4 Reference architecture forward and return channel specifications

The reference architecture for the series of specifications is illustrated in Figure 1

* The diplexer filter may be included as part of the network element to which the transponder interfaces, or it may be added separately by the network operator

In Figure 1, all measurements for forward channel transmission and reverse channel reception are taken at point A, while measurements for forward channel reception and reverse channel transmission are recorded at point B for two-port devices and at point C for single-port devices.

5 Power supply to transponder interface bus specification overview

General

The PSTIB specification introduces a new status monitoring topology designed to replace outdated analog interfaces for monitoring power supplies and related equipment in HFC networks This innovative approach simplifies the transponder by relocating all measurements and sensors to the monitored equipment, such as power supplies The transponder connects to the monitored equipment using a single multi-conductor cable, which also supplies power to the transponder The monitored equipment is responsible for measuring battery parameters, voltages, and other relevant data Communication of status and commands occurs through a serial data interface bus between the transponder and the monitored equipment.

The data protocol and command set are designed for easy implementation in basic microcontrollers This open and expandable communication protocol allows for the seamless addition of new requirements in future revisions of the specification.

Interface compliance

Transponder and power supply vendors are considered interface compliant when they meet the mechanical and electrical interface requirements at the PHY layer, as well as the packet and protocol message formats at the DLL layer specified in this document.

The Get_Configuration command allows the transponder to verify compliance with specific revisions of the power supply standards This capability is essential as the PSTIB specification evolves, ensuring that power supply equipment of varying revisions can operate together within the same network.

Implementation compliance

Not all vendors will support the complete data set defined throughout this standard The

Get_Configuration response (see 8.4.3) provides the transponder or EMS with the specific status data that is and is not supported for each installation

Revision control

The command and response data in this standard are synchronized with associated HMS

SNMP MIBs are utilized in management systems to represent data, as outlined in Table A.1 To ensure synchronization, a revision control mechanism is essential When the standard is revised to include new data items, these items must be added to the end of existing command or response definitions Additionally, new command and response sequences can be created as necessary, but revisions must not alter the location, definition, or function of any previously defined datum.

6 Power supply to transponder interface bus – Physical layer specification

Interface requirements

Connector type

The physical connector for serial communications over the PSTIB between compliant transponders and managed OSP power supply hardware must feature an RJ-45 connector with eight-wire conductors, adhering to IEC 60603-7 standards It should have suitable metallic plating for outdoor use and operate effectively within a temperature range of –40 °C to +70 °C Additionally, the monitored equipment must include dual connectors wired in parallel to facilitate daisy-chaining multiple monitored devices from a single compliant transponder.

Communications interface

The communications interface shall support the EIA RS-485 [1].

Connector signals

Connector pins shall support signalling as described in Table 2

Table 2 – RJ-45 Connector pin assignment

Transponder power

Transponders powered by PSTIB interface compliant power supplies must adhere to specific requirements: they should exclusively draw power from the power supply without direct connection to system batteries; the power supply must ensure proper isolation and system grounding to maintain functionality of the communication interface and transponder power under defined operating conditions; and the transponder must be bonded to the chassis ground either directly or via the system coaxial cable sheath.

This document is licensed to Mecon Limited for internal use at the Ranchi/Bangalore location, supplied by Book Supply Bureau It specifies that the transponder power may optionally be bonded to the chassis ground at the power supply interface, as determined by the power supply vendor Additionally, the power supply must include over-current and short-circuit protection for the transponder power to ensure the functionality of both the communication interface and transponder power under specified operating conditions Furthermore, it allows for the connection of up to eight power supplies in parallel using the RS-485 interface.

Line balance

To implement line balance for monitored equipment, connect RS-485 (+) to a DC voltage of +5 V via a removable resistor, and RS-485 (–) to ground through another removable resistor Additionally, RS-485 (+) should be linked to RS-485 (–) through a removable resistor The monitored equipment must also feature jumpers that allow for the selection or bypassing of resistors to achieve an open state.

Jumper or switch-selectable terminating resistors enable on-site configuration of individual installations Transponders shall include line balance resistors only Refer to Figure 2

Line balance for transponders shall be implemented as follows:

– RS-485 (+) tied to RS-485 (–) through a required resistor

NOTE Values for each resistor and the decision to include or exclude specific bias resistors as a default should be determined by individual vendors.

Cable length

A maximum cable length of 1 219,2 m (4 000 ft) (for 100 kbit/s) properly terminated wire segment.

Data encoding

The transmission format consists of non-return to zero (NRZ) encoding, with asynchronous communication featuring 1 start bit, 8 data bits (in the order of bits 1 to 8), and 1 stop bit All integers are sent with the most significant byte transmitted first, and any deviations from this standard will be explicitly mentioned as needed.

Bit rate

The bit rate supported shall be 9 600 Bd.

Duplex

This interface shall support half duplex operation Multi-drop characteristics of RS-485 enable up to 32 drops per segment without signal repeaters.

Method of communications

All communication is transponder-initiated One monitored device response per query.

Indicators

A LED or other visual device installed at the monitored equipment shall indicate communication has been established with a transponder over the PSTIB interface

Interface diagram

The diagram in Figure 2 illustrates a sample RS-485 interface implementation to support

The PSTIB communications diagram serves solely to illustrate line bias and the placement of termination resistors, rather than as a design requirement For detailed information on the signals referenced in the diagram, please refer to Table 3.

Figure 2 – Sample PSTIB RS-485 interface Table 3 – Sample PSTIB RS-485 interface – Reference signals

+Vxpndr Voltage supplied from the monitored equipment to the transponder as defined per this specification +5xpndr Transponder operating voltage derived at the transponder from +Vxpndr

*Option Indicates resistors that can be included or removed from circuit via user configurable jumper or switch

Required Indicates resistor is required per this specification

J1, J2 The RJ-45 connectors according to IEC 60603-7 used to interface transponders to monitored equipment Pin numbers show currently defined interface signals per this specification

Rx, Tx, Tx En Transmit, Receive and Transmit Enable Illustrates possible connections to an RS-485 interface IC

The transponder must be chassis grounded, and the monitored equipment can be connected to this ground either directly at the equipment's status interface or via the interface ground (J1 pins 1,8) The choice of grounding method should be determined by the monitored equipment vendor, ensuring that both the monitored equipment and the status interface operate correctly regardless of the selected grounding approach.

7 Alternative power supply to transponder interface bus – Physical layer specification

Introduction to alternative

Certain applications may require power levels that exceed the limits specified in Clause 6 Consequently, this physical layer specification introduces an alternative power supply for the transponder interface bus, serving as a supplement to the existing specifications in Clause 6 and designed to coexist with them.

Interface requirements

Connector type

The physical connector for serial communications over the PSTIB between compliant transponders and managed OSP power supply hardware must feature an RJ-45 connector with eight-wire conductors, adhering to IEC 60603-7 standards It should have suitable metallic plating for outdoor applications and operate effectively within a temperature range of –40 °C to +70 °C Additionally, the monitored equipment must include dual connectors wired in parallel to facilitate daisy-chaining multiple monitored devices from a single compliant transponder.

Communications interface

The communications interface shall support the EIA RS-485 [1].

Connector signals

Connector pins shall support signalling as described in Table 4

Table 4 – RJ-45 Connector pin assignment

Transponder power

Transponder power requirements include the necessity for a power supply to ensure proper isolation and system grounding, maintaining functionality of the communication interface under specified operating conditions The transponder must be directly bonded to chassis ground or through the coaxial cable sheath, with optional bonding at the power supply interface as determined by the vendor Additionally, the power supply must provide over-current and short-circuit protection to keep the transponder power operational Furthermore, up to eight power supplies can be connected in parallel via the RS-485 interface.

This document is licensed to Mecon Limited for internal use at the Ranchi and Bangalore locations, and it has been supplied by the Book Supply Bureau The power supply must meet the specified operating requirements outlined in this document.

The transponder is designed to operate with a continuous power draw of 4.8 W from the PSTIB It must limit inrush current to a maximum of 250 mA during start-up while ensuring that power consumption does not exceed 4.8 W Additionally, the power supply is required to reach the minimum voltage requirement promptly during the start-up phase.

Line balance

To implement line balance for monitored equipment, connect RS-485 (+) to a DC voltage of +5 V via a removable resistor, and RS-485 (–) to ground through a removable resistor Additionally, RS-485 (+) should be tied to RS-485 (–) through another removable resistor The monitored equipment must also feature jumpers that allow for the selection or bypassing of resistors to achieve an open state.

Jumper or switch-selectable terminating resistors enable on-site configuration of individual installations Transponders shall include line balance resistors only Refer to Figure 3

Line balance for transponders shall be implemented as follows:

– RS-485 (+) tied to RS-485 (–) through a required resistor

NOTE Values for each resistor and the decision to include or exclude specific bias resistors as a default should be determined by individual vendors.

Cable length

Maximum cable length of 1 219,2 m (4 000 ft) (for 100 kbit/s) for a properly terminated wire segment.

Data encoding

The transmission format follows a non-return to zero (NRZ) scheme, utilizing asynchronous communication with 1 start bit, 8 data bits (in the order of bits 1 to 8), and 1 stop bit All integers are sent with the most significant byte transmitted first, and any deviations from this standard will be explicitly mentioned as needed.

Bit rate

The bit rate supported shall be 9 600 Bd.

Duplex

This interface shall support a half duplex operation Multi-drop characteristics of RS-485 enable up to 32 drops per segment without signal repeaters.

Method of communication

All communication is transponder-initiated, one monitored device response per query

Indicators

A LED or other visual device installed at the monitored equipment shall indicate communication has been established with a transponder over the PSTIB interface.

Interface diagram

The diagram in Figure 3 illustrates a sample RS-485 interface implementation to support

The PSTIB communications diagram serves solely to illustrate line bias and termination resistor placement, rather than as a design requirement For detailed information on the various signals referenced in the diagram, please refer to Table 5.

* Op tion Req uir ed

Figure 3 – Sample PSTIB RS-485 interface Table 5 – Sample PSTIB RS-485 interface – Reference signals

+Vxpndr Voltage supplied from the monitored equipment to the transponder as defined per this specification +5xpndr Transponder operating voltage derived at the transponder from +Vxpndr

*Option Indicates resistors that can be included or removed from circuit via user configurable jumper or switch

Required Indicates resistor is required per this specification

J1, J2 The RJ-45 connectors according to IEC 60603-7 used to interface transponders to monitored equipment Pin numbers show currently defined interface signals per this specification

Rx, Tx, Tx En Transmit, Receive and Transmit Enable Illustrates possible connections to an RS-485 interface IC

The transponder must be chassis grounded, and the monitored equipment can be connected to this ground either directly at the status interface or via the interface ground (J1 pins 1,8) The choice of grounding method should be determined by the monitored equipment vendor, ensuring that both the monitored equipment and status interface operate correctly regardless of the selected grounding approach.

8 Power supply to transponder interface bus – Data link layer specification

DLL packet structure

General

DLL packets are composed of several key components: a start field, destination address field, source address field, identification field, a variable-length datagram field, an end field, and a two-byte checksum field The structure of a DLL packet is visually represented in Figure 4.

All DLL packets shall have the general format as described in Table 6

Table 6 – Generic DLL packet structure

Field name Length bits Subclause

Start

The Start field consists of two octets (bytes) This is the start sequence of all communication packets This field shall consist of DLE (0x10) followed by STX (0x02).

Destination Address

The Destination Address field is a single octet that uniquely identifies the device receiving the packet, with values ranging from 0x00 to 0xFF (0-255 in decimal) For a comprehensive overview, refer to Table 7, which outlines the currently defined address ranges as part of this standard.

Table 7 – Reserved destination address ranges

1 to 8 0x01 to 0x08 Power supplies and Generators

9 to 15 0x09 to 0x0F Reserved for HMS use a

16 to 127 0x10 to 0x7F Reserved for vendor-specific use b

128 to 255 0x80 to 0xFF Reserved for HMS use

To ensure interoperability among different applications using the PSTIB, it is crucial to utilize company or product datagram identifiers, as vendor-specific implementations are not governed by the standard It is advised to avoid using 0x10 as a device address to prevent additional DLE sequences The destination address range from 16 to 127 (0x10 to 0x7F) is designated for non-standard vendor use of the PSTIB However, any vendor-specific applications must comply with all physical, DLL packet structure, timing, message synchronization, and interaction requirements outlined in the specification, ensuring that they do not disrupt standard communications between devices on the PSTIB.

Source Address

The Source Address field is a single octet that uniquely identifies the device sending the packet, and it shares the same format as the Destination Address field.

Identification

The Identification field is a single octet that aids in identifying packets and matching send-receive sequences This field's contents are determined by the initiating device, which is always the transponder The receiving device will echo the identification in the corresponding field of its response packet.

Datagram

The Datagram field is composed of at least four octets, encompassing commands, command responses, and data exchanged with higher layer protocols The specific types of datagrams and their structures are detailed in section 8.4.

End

The End field consists of two octets This is the end sequence of all communication packets

This field shall consist of DLE (0x10) followed by ETX (0x03).

Checksum

The Checksum field is composed of two octets, representing a 16-bit (modulo 0x10000) sum of all bytes in the packet, excluding the Start, End, and Checksum fields, as well as any stuffed DLEs.

DLE sequence

Data Link Escape (DLE) sequence stuffing assures that both START (DLE, STX) and END

In packet transmission, the sequences DLE (0x10 or decimal 16) and ETX are unique and will not be duplicated within a packet This method aids in marking the beginning and end of variable-length packets When a DLE octet is detected in the data stream, a second DLE is inserted to ensure accurate transmission.

NOTE The above example illustrates only the DLE stuffing technique Specific command and response information is not intended to represent actual data

In the original packet example, the 6th and 7th octets may be misinterpreted as the end-of-packet sequence However, the DLE-stuffed packet contains an additional DLE, which the receiving device will recognize It will then discard the inserted DLE and overlook the DLE ETX code that is embedded within the packet.

DLE stuffing rules dictate that it applies to the entire packet, including the checksum, resulting in an additional DLE character for each checksum byte sent as 0x10 (DLE) Notably, the start packet sequence (DLE, STX) and end packet sequence (DLE, ETX) are exempt from DLE stuffing Furthermore, the "Size of Data" field in any DLL datagram does not account for stuffed DLE characters, and these stuffed characters are excluded from packet checksum calculations.

Interface timing

Message synchronization and interaction

Transponders must initiate all communications, while monitored equipment, such as power supplies, should only respond to specifically addressed packets Additionally, transponders are powered directly through the RJ-45 physical connector, in accordance with IEC 60603-7 standards.

PSTIB-compliant power supplies must wait at least 15 seconds after power-up and initialization before discovering connected power supplies They should be fully initialized and able to respond to data messages within this timeframe If interrogated prematurely, they will not respond or may provide incorrect data Each data message from transponders must have a unique identifier, which will be included in the response packet to ensure command/response synchronization Transponders should have a mechanism to re-request communications if a corrupt or no response is received, retrying at least three times before reporting a communication loss to the EMS In case of a communication loss, transponders will attempt to re-establish contact at regular intervals Additionally, transponders will periodically discover new devices on the PSTIB, conducting auto-discovery attempts for all HMS device addresses every 5 minutes or less to query for new or changed configurations.

Transmission timing requirements

Figure 5 illustrates the data and timing diagram for transmissions over the PSTIB Table 8 de- scribes all relevant timing parameters and allowed minimum and maximum values

Figure 5 – PSTIB data and timing diagram Table 8 – PSTIB timing specifications

The packet duration for PRIMARY or SECONDARY devices ranges from a minimum of 30 ms to a maximum of 30 ms The delay from the completion of a PRIMARY or SECONDARY device message to the start of the power supply response is between 1 ms and 30 ms The power supply packet duration for chatter detection is set at 300 ms The time from the start of the PRIMARY device packet to the start of the SECONDARY device packet varies from 390 ms to 510 ms Additionally, the polling cycle period for the PRIMARY device is between 900 ms and 3 s.

Figure 5 and Table 8 illustrate the communication initiation over the PSTIB, distinguishing between two types of devices A device with the address 0x00, known as a PRIMARY device, is a transponder that initiates communications In contrast, devices with non-zero addresses, such as laptop PCs or other transponders, are classified as SECONDARY devices.

8.3.2.2 Requirements for PRIMARY and SECONDARY devices

It may be desirable for on-site technicians to access power supply and generator system status using a laptop PC This subclause defines the timing requirements for a laptop-based

The PC application program facilitates the sending and receiving of status updates to and from monitored equipment through the RS-485 interface, ensuring uninterrupted communication with the transponder This operation adheres to specific rules: firstly, transponders and monitored equipment must be prepared for the presence of a secondary device, such as a laptop PC, connected to the RS-485 bus; secondly, the primary device, known as the transponder, should be configured to address zero.

SECONDARY device shall be set to any unused address; c) in order to establish timing synchronization with the SECONDARY device, the transponder

The device at address 0x00 will consistently send packets according to the timing requirements set for the PRIMARY transponder Additionally, the SECONDARY device will check for the presence of a zero-addressed PRIMARY device on the bus by monitoring for signals from a zero-addressed transponder.

Licensed to Mecon Limited for internal use in Ranchi and Bangalore, supplied by Book Supply Bureau The secondary device monitors the bus for a duration equal to the maximum value of a specified parameter.

The PRIMARY device has a poll cycle period of 3 seconds If it does not detect a zero-addressed transponder, it will function as the PRIMARY transponder Additionally, if a SECONDARY device is operating as PRIMARY and has not listened for a zero-addressed transponder for 60 seconds or more, it will continue its operation accordingly.

A SECONDARY device must verify the presence of a zero-addressed transponder on the bus before transmitting Additionally, a PRIMARY transponder is designed to withstand continuous bus collisions for up to 60 seconds without failure, while still adhering to all other specified requirements.

A PRIMARY transponder must continuously transmit at defined intervals, regardless of whether it receives responses If a SECONDARY device with a non-zero address detects a zero-addressed transponder on the bus, it must stop functioning as a PRIMARY and switch to a SECONDARY role When a PRIMARY transponder is active, a SECONDARY device must initiate its transmission no less than "t4 minimum" and no more than "t4 maximum" after observing the PRIMARY's transmission Permanently installed transponders should be configured with address 0x00 to operate as PRIMARY transponders Both PRIMARY and SECONDARY devices must verify that the destination address matches their own and only process packets addressed to them, ensuring they do not assume all bus traffic is relevant to them Additionally, monitored equipment must handle requests from multiple devices without interleaving messages, guaranteeing that while responding to one device, it will not receive requests from another.

DLL datagrams

Structure

The Datagram field is a crucial component of the DLL packet structure, encompassing commands, command responses, and related data The structure of DLL datagrams is visually represented in Figure 6.

Size of data Variable binding

All DLL datagrams shall have the general format as described in Table 9

Table 9 – Generic DLL datagram structure

Field name Length (bits) Subclause

The Command/Response field, consisting of two octets, specifies the action to be performed and is always present in the data structure This field is transmitted with the most significant byte first, and valid commands and responses are detailed in section 8.4.3.

The Size of Data field consists of two octets This value defines the size (in bytes) of the

The Variable Binding field is a crucial component that is always included, with its Size of Data field indicating a value of 0x0000 when no data is linked to the command This two-octet field is transmitted with the most significant byte first.

The variable field holds specific data related to a particular command or response, but it may not always be present When there is no data available, the Size of Data field is set to 0x0000.

Resolution versus accuracy

The Variable Binding field in a DLL datagram features digital representations of analogue values, with their resolution detailed in the tables for each DLL datagram type It's important to note that resolution does not equate to accuracy; therefore, vendors must provide accurate status data for equipment in accordance with this specification Additionally, any scaled analogue representation obtained from a Get_Power_Supply_Data response should be considered.

8.4.3.4) that reaches the minimum or maximum range defined for that value, i.e 0 or 255, shall report the maximum (or minimum) value and not wrap around.

DLL datagram types

Valid datagram types defined in this standard are listed in Table 10

Datagram name Encoding a Size of data (bytes) Subclause

Get_Configuration (Response) 0x3130 Device type dependent 8.4.3.3

Get_Power_Supply_Data (Command) 0x3031 0 8.4.3.4

Get_Power_Supply_Data (Response) 0x3131 33 8.4.3.5

Reserved for vendor specific use b 0xC000 to

Non-standard, vendor-specific use of the PSTIB shall not interfere with or interrupt standard communications between devices on the PSTIB

To prevent interoperability issues among different vendor applications using the same encoding value, it is highly recommended to utilize company or product-specific datagram identifiers, such as Get_Configuration (Response) “ID.” Additionally, all DLL Datagram encoding values not explicitly defined in Table 11 are reserved for future use.

The range from 0xC000 to 0xFFFF in HMS is designated for nonstandard, vendor-specific use of the PSTIB, while still adhering to all specified requirements for physical structure, DLL packet structure, timing, message synchronization, and interaction Additionally, "nn" refers to the second byte of both the unrecognized command and the command currently being processed.

Table 11 provides a description for this datagram

Table 11 – Command: Get_Configuration datagram

Description Encoding Size of data

This command from the transponder to the monitored equipment requests the configuration status of the monitored device

Table 12 provides a description for this datagram

Table 12 – Response: Get_Configuration datagram

Description Encoding Size of data

Response from the monitored device to the transponder to a

The configuration data includes important details outlined in Tables 13, 14, and 15 Notably, fields in a Get_Configuration response must not take the value "255," as this is reserved as an extension flag for potential future use, ensuring backward compatibility Additionally, fields that contain ASCII text data are NULL terminated, meaning any unused locations following the text message must be filled with NULL characters (0x00) to signify the end of the message, which should not be displayed as printed characters on the EMS display terminal.

Table 13 – Response: Get_Configuration datagram a variable binding (general)

The SCTE HMS protocol version implemented in the monitored equipment ranges from 1 to 254 This field indicates the HMS PSTIB interface version in the responding device, represented as a decimal value multiplied by 10 For instance, a power supply that supports all commands and responses defined in HMS PSTIB Rev 1.1 would return a value of "11" in this field.

2 Device type 1 to 254 A code identifying the general class of equipment being monitored

The intent of this field is to provide a one-to-one correspondence between a monitored device and an MIB file used by the EMS Devices are defined as

– power supply – corresponds to SCTE HMS PS MIB document, – generator – corresponds to SCTE HMS GEN MIB document, – fibre node – corresponds to SCTE HMS FIBERNODE MIB document

The software version field, consisting of 8 octets, is vendor-specific and aims to represent the software version of the power supply or generator system This field can include any printable ASCII characters.

NULL (0x00) characters are non-printable and are used to fill any unused locations in the 8-octet field following the text data

The 4 ID 32 octets field contains vendor-specific information, designed to convey manufacturer or product-specific ASCII text directly to the management console This field includes defined special characters that are relevant to its content.

“\” - used to cause a new line on the console display Example:

“ALPHA\XM2 9015” would appear at the monitoring station as:

NOTE IEC 60728-7-3 (2003) [6], refers to HMS PSTIB specification, v1.0, and IEC 60728-7-3 (2009), refers to

The HMS PSTIB specification, version 1.1, outlines that field entries 1 through 4 are standardized across all monitored devices, while the remaining entries in the Response: Get_Configuration datagram are specific to the device type, with power supplies responding differently than field power generators Each field is defined as one octet (8 bits) in length unless specified otherwise Notably, the "Protocol Version" field definition has been updated in version 1.1; previously, in version 1.0, devices were required to return the value 1 to confirm compliance with that version.

1.1 of HMS PSTIB specification some vendors return the value 10 in this field as an indication that the device is compliant with version 1.0 of HMS PSTIB specification So transponders need to recognize that a response of either 1 or 10 means compliance with version 1.0 of HMS PSTIB specification.

Table 14 defines the balance of field entries expected from power supplies in the variable binding for the Response: Get_Configuration datagram

Table 14 – Response: Get_Configuration datagram a , b variable binding (power supply)

5 Batteries 0 to 8 Number of batteries per string Example: A 36V system will return

A system may indicate "0" (0x00) to signify that no batteries are connected This field allows the transponder and/or EMS to ascertain the number of "V(batt)" battery voltage measurements to be utilized, as detailed in the Get_Power_Supply_Data response.

NOTE 1 The number of batteries reported must not exceed 8 for a single string and 4 for a dual string Systems reporting more than 4 batteries are limited to 1 battery string

NOTE 2 The transponder and/or EMS will interpret a “0” (0x00) re- turned from either Get_Configuration – “Batteries” or “Battery Strings” as no batteries connected

0 to 2 Number of battery strings This field enables the transponder and/or

The EMS determines the number of battery strings connected to a power supply and manages the "V(batt)" data from a Get_Power_Supply_Data request A battery strings value of "0" signifies that all V(batt) data should be disregarded, indicating no batteries are connected A value of "1" denotes a single system battery string containing up to 8 batteries, as defined by the Get_Configuration – Batteries Meanwhile, a value of "2" indicates the presence of two system battery strings, each accommodating up to 4 batteries.

NOTE 3 The transponder and/or EMS will interpret a “0” (0x00) re- turned from either Get_Configuration – “battery strings” or “batteries” as no batteries connected

7 Temperature sensors 0 to 2 Number of battery temperature sensors

NOTE 4 The location of each temperature sensor is application- specific

The number of power supply outputs ranges from 1 to 5, allowing the transponder and/or EMS to identify how many of the "I(out) 1-5" values in fields 2 through 6 of the Get_Power_Supply_Data response datagram should be utilized If only one output is active, I(out) will reflect that.

1 to 4 Defines if battery current is measured in this installation Values are enumerated as follows

1 = no battery current measurements Discard associated values in fields 16, 17, 18 and 19 of the Get_Power_Supply_Data response datagram

The current of battery string "A" is measured exclusively in this configuration, which is also applicable for a single current sensor setup that captures the total current of both battery strings "A" and "B" This indicates that the values in fields 16 and 18 of the Get_Power_Supply_Data response datagram are valid, while fields 17 and 19 should be disregarded.

The measurement of battery string "B" current is indicated by the value 3, which confirms the validity of the values in fields 17 and 19 of the Get_Power_Supply_Data response datagram, while fields 16 and 18 should be disregarded.

4 = battery strings “A” and “B” are measured with separate sensors

Indicates that the values in fields 16, 17, 18 and 19 of the Get_Power_Supply_Data response datagram are all valid

10 Float current 1 to 4 Same format as “battery current” Values are enumerated as follows

1 = No float current measurements Discard associated values in fields 26 and 27 of the Get_Power_Supply_Data response datagram

The float current for battery string "A" is exclusively measured, which is applicable in a single current sensor configuration that captures the total current of both battery strings "A" and "B." This indicates that the value in field 26 of the Get_Power_Supply_Data response datagram is valid.

The measurement of battery string "B" float current indicates the validity of the value in field 27 of the Get_Power_Supply_Data response data-gram, while field 26 should be disregarded.

4 = Battery strings “A” and “B” are measured with separate sensors

Indicates that the values in fields 26 and 27 of the Get_Power_Supply_Data response datagram are valid

1, 2 Defines if power supply supports monitoring of output voltage

1 = No support Discard associated value in field 1 of the Get_Power_Supply_Data response datagram

2 = Field is supported in this installation Indicates that the value in field 1 of the Get_Power_Supply_Data response datagram is valid

12 Input voltage 1, 2, 3 Defines if power supply supports monitoring of input or line voltage

1 = No support Discard associated data in field 7 of the Get_Power_Supply_Data response datagram

2 = Field is supported – binary representation Indicates that field 7 of the Get_Power_Supply_Data response datagram contains valid data

3 = Field is supported – analogue representation Indicates that field

7 of the Get_Power_Supply_Data response datagram contains valid data

1, 2 Defines if power supply supports the remote test feature

14 Major alarm 1, 2 Defines if the power supply supports the major alarm indicator:

1 = no support Discard associated value in field 23 of the Get_Power_Supply_Data response datagram

2 = field is supported in this installation Indicates that field 23 of the Get_Power_Supply_Data response datagram contains valid data

15 Minor alarm 1, 2 Defines if the power supply supports the minor alarm indicator:

16 Tamper 1, 2 Defines if the enclosure door switch is installed in this location

1, 2, 3 Defines support level for battery voltage monitoring

1 = no battery voltage is monitored Discard associated values in fields 8, 9, 10, 11, 12, 13, 14, 15 and 28 of the

Get_Power_Supply_Data response datagram

Tiêu đề	Cable Networks for Television Signals, Sound Signals and Interactive Services – Part 7-3: Hybrid Fibre Coax Outside Plant Status Monitoring – Power Supply to Transponder Interface Bus (PSTIB)
Thể loại	Standard
Năm xuất bản	2009
Thành phố	Geneva

Định dạng
Số trang	42
Dung lượng	1,02 MB