hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.3 Error Codes Configuration (optional) | ET22 allows the user to define which alarms may be configured as scrolling errors that will be displayed as the last item in the display list or locking errors that will lock the normal display regardless of position in display list and will display the errors in two screens with an error code for each screen (one for ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.4 Simulated Wheel Rotation Configuration (optional) | ET01 allows the user to configure the rate of rotation for optional simulated mechanical wheel on the display. The simulated wheel is an optional visual indicator for the relative rate of energy consumption measured by the OSGP device. ETSI ETSI TS 104 001 V2.1.1 (2016-12) 43 |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.5 Disconnect Configuration (optional] | ET05 allows the user to configure text that will be displayed explaining why the load disconnect contactor was opened. The 4 digit ID code that will be displayed while the disconnect open text is shown is also configurable via ET05. The behaviour of the Disconnect Open icon is also configurable via ET05. The disconnect... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.6 CT and VT Ratios (optional) | BT15 allows the user to configure how the devices CT and VT ratios will be displayed. These ratios can be displayed as an industry standard method where a ratio X : Y is displayed representing the primary transformer rated current : the secondary transformer rated current, or as the multiplier value that the ratio corr... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.7 Firmware Version on Power-Up (optional) | ET07 allows the use to configure the OSGP device to display the firmware version currently running in the OSGP device on power-up. The OSGP device can be configured to display its firmware version for 1 seconds to 15 seconds on power-up, if desired. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.8 PLC signal quality Icons (optional) | The device may have indicators on its display to show PLC traffic detection and received-message quality. The signal strength thresholds that trigger these icons are specified via ET55.14 for non-ATM traffic. For ATM discovery queries, the initiator can specify the signal strength threshold via the query message. If th... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.9.9 Scheduled Display Messages (optional) | ET55 may be used to configure preset messages to be shown on the device's display. The "Scheduled Display Message Text" field defines this message, which can include up to 4 characters that will be shown on the display. The date/time can be configured which the preset message will be displayed, and the date/time at whi... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10 Load Disconnect Contactor (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.0 Foreword | The device may contain up to two internal control outputs that can be used to control two independent devices. The primary control output shall be the load disconnect contactor used to control a circuit disconnect that controls the load to the customer. It can be programmed for use via several different automatic and m... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.1 Maximum Power and Current Level Thresholds | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.1.0 Foreword | The device contains a series of settings that establish a maximum power level threshold. When the OSGP device detects this level of power on the line, it indicates that excessive power is in use and the OSGP device will automatically shut off (trip) the load disconnect contactor. After an excessive power condition trip... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.1.1 Changing the Device's Maximum Power Level Threshold | In order to set the maximum power level threshold for the OSGP device, configure the following settings: • Maximum Power Level Thresholds: The OSGP device may contain both a Primary Power Level Threshold and a Secondary Power Level Threshold value. The OSGP device can be programmed to use either value to determine when... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.1.2 Changing the Device's Maximum Current Level Threshold | The settings below need to be configured for the OSGP device to use current measurements, instead of power measurements, to determine when excessive power is in use and the OSGP device should shut off the load disconnect contactor: • Maximum Current Level Thresholds: The OSGP device contains both a Primary Current Leve... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.1.3 Choosing Power or Current (optional) | By default, the OSGP device will use power measurements to determine when the load disconnect contactor has reached its trip point and should be shut off. EP42 "Control Output Settings" is used to switch from power measurements to current measurements, and vice versa. NOTE: The "Disconnect Control Type" field in ET46 "... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.2 Prepaid Metering (optional) | The device will automatically turn off the load disconnect contactor once the credit level in energy has gone to zero in a prepaid metering installation. The OSGP device reduces the amount of remaining credit based on energy usage and tariff level as time goes by. ETSI ETSI TS 104 001 V2.1.1 (2016-12) 46 Once the prepa... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.3 Local Manual Control (optional) | Manual opening of the load disconnect contactor can be enabled or disabled. When configured to be disabled, the OSGP device will not respond if the consumer attempts to open or close the load disconnect contactor manually. Manual operation of the load disconnect contactor can be enabled or disabled by writing the "Disa... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.10.4 Load Contactor Remote Control (optional) | EP23 can be used to close the load disconnect contactor remotely. Upon execution of this procedure, the load disconnect contactor will close immediately. There are several OSGP device fields that can be configured to prevent execution of EP23: • The "Enable Remote Disconnect Closed" field in ET05 can be set to prevent ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.11 Control Relay (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.11.0 Foreword | One optional control relay can operate an external low current device, such as a contactor coil, which in turn can control a larger amperage device. The open or closed state of the control relay is determined by the present tariff level that is in effect. The tariff period that activates the relay is configurable. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.11.1 Control Relay Randomization | The OSGP device includes a randomization option for control relay open and close operations. As part of this feature, the maximum number of seconds of randomization time to open or close the control relay for each control relay operation that is sent to a group of OSGP devices can be specified. The time the command is ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.11.2 Time-Based Control Relay Calendar | Each device can contain a calendar that specifies when the control relay should be opened or closed. The calendar supports the following types of schedules: • Daily: The control relay calendar includes a separate schedule for each day of the week. • Weekday/Weekend: The control relay has two schedules: one for weekdays... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.11.3 Remote Control | EP02 is used to control both the control relay and the load disconnect contactor. If EP02 is used to force either output open, the automatic controls (such as the time-based relay control calendar) for that output are disabled. Automatic control is re-enabled when EP02 is invoked to close the output. ETSI ETSI TS 104 0... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12 History Log (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12.0 Foreword | The event log holds a chronological time-stamped record of alarms and events that occur in the OSGP device. Event log data can be found in BT74 "History Log Data". Dimension information is in BT70 "Dimension Log" and BT71 "Actual Log". Proper interpretation of the offsets in BT74 relies on reading BT71 first to determi... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12.1 Critical Events (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12.1.0 Foreword | Any of the status and alarm events can be defined as critical events. Once an event has been designated as a critical event, the last 10 instances of that event will be retained in the event log at all times. Critical events will be maintained in the event log along with all of the other events that have not been desig... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12.1.1 Critical Event Categories | If multiple events have been classified as critical events, then they could consume a large portion of the event log. Therefore, up to 9 critical event categories can be specified in order to add flexibility to the critical events. A critical event category is a user-selected group of events which, taken as a whole, wi... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12.1.2 Critical Event Bitmasks | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12.1.2.0 Foreword | Many events return arguments that indicate what caused the event to occur. If it is desirable to designate a critical event based on the specific arguments returned, a bitmask and a value for each critical alarm that is designated as a critical alarm can be specified. The bitmask will identify which bits of the argumen... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.12.1.2.1 Example Critical Event Bitmask | This clause provides an example of defining a critical event bitmask. The following example describes how to create a critical event bitmask for the Load Disconnect State Changed event. As described in the last clause, the instances of this event that should be considered critical can be specified based on three criter... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.13 One-Time Reads (optional) | A One-time-read can be requested by calling EP24. One-time-reads do not occur multiple times in a scheduled pattern as Self-reads do. Each One-time-read is programmed to occur at a specific date and time, and occurs only once. Up to 3 separate One-time-reads in the OSGP device at once can be scheduled. If the OSGP devi... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.14 Group Broadcasts (optional) | The OSGP device may be capable of sending group broadcast messages to multiple devices, in which group IDs are used to target broadcast messages to a subset of meters on the network. ETSI ETSI TS 104 001 V2.1.1 (2016-12) 51 ET33 holds a list of group IDs that pertain to different feature groups in the OSGP device. When... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15 Demand Metering (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.0 Foreword | The OSGP device may offer various types of demand calculations that can be performed to measure the peak active and reactive power being delivered to the system over a designated time period. Demand measurements are useful in that they provide information on peak usage as opposed to accumulation over time. In addition,... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1 Demand Values (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.0 Foreword | Clauses 8.15.1.1 to 8.15.1.6 summarize the various demand values the OSGP device can calculate. ETSI ETSI TS 104 001 V2.1.1 (2016-12) 52 |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.1 Present Demand | Present demand values are stored in BT28. Present demand is the demand value of the interval currently in progress. It is updated every second. There are two ways to calculate present demand, depending on the time value that is used to normalize the energy used in the interval. The first measures the accumulated energy... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.2 Previous Demand | Previous demand values are stored in ET39. These are the demand values for the last complete or partial interval. The previous demand is updated every sub interval and the following formula describes how previous demand is calculated. Previous demand is measured by dividing the accumulated energy for the main interval ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.3 Maximum (Peak) Demand | Maximum demand (in BT23) is the largest demand value since the last demand reset. At every sub-interval for rolling demand or main interval for block demand, the previous (present demand for the last interval) demand is compared with the maximum demand and if the previous demand is bigger than the maximum demand, the m... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.4 Coincident Sources | The OSGP device can store up to two coincident values, chosen from the available measured and calculated values, along with each maximum demand value. When the maximum demand values are updated, the coincident values are also updated at the same time. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.5 Cumulative Demand | Cumulative demand is the summation of all previous maximum demand values that were present at the time of their respective demand resets. At each demand reset, the cumulative demand is incremented with the value of the new maximum demand. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.6 Continuous Cumulative Demand | Continuous cumulative demand is the summation of cumulative demand and the maximum demand value since the last demand reset. Continuous cumulative demand should be correctly calculated if cumulative demand is disabled and continuous cumulative demand is enabled. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.7 Demand Reset | A demand reset marks the end of a demand billing cycle. The following tasks are performed for each demand reset: • Update all calculations evaluated at demand reset. • Save the current demand values to previous (latest) demand reset table and historical demand reset table. The OSGP device can hold one or more copies of... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.8 Historical Demand Reset Log | The historical demand reset log is stored in ET41. This is an adjustable table that can be set to any number of entries up to the capacity of the optional feature memory space (48K with no adjustable logs configured). The number of current entries of ET41 is set via EP32, and is recorded in ET36. If the count is config... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.9 Initializing Demand Metering | Demand metering is an optional feature. Therefore, initialization of demand consists of two steps: activation and configuration. 1) Activation is achieved by executing EP31 with the appropriate authentication parameters. Before demand is activated, BT21 reflects having no demand data or features enabled and the billing... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.15.1.10 Reconfiguration | Some demand parameters can be reconfigured without affecting table dimensions, but they do change the content of what is being recorded. This is done via EP33 "Billing Reconfiguration". No logs are reset when EP33 is executed. A demand reset is logged and a self-read can occur if requested. If any demand source is spec... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.16 Test Mode | Test mode is used to test the OSGP device accuracy without disturbing billing registers. Upon entering test mode, the OSGP device suspends standard energy accumulations, standard demand calculations, power quality analysis, tariff register calculations and storage in billing tables, automated control of the disconnect ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17 MEP Device Overview | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.0 Foreword | An OSGP device may contain two communication ports on the OSGP device's terminal block: • An M-Bus port which allows connection of up to 4 M-Bus devices to the OSGP device. • A bidirectional multipurpose expansion port (MEP), which may be implemented at the discretion of the OSGP manufacturer, e.g. as an isolated UART ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.1 Downlink Data Transfer | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.1.0 Foreword | Communication from the OSGP device to the MEP device is implemented via two different mechanisms, depending on the urgency and need for acknowledgment of the data transfer. The mechanisms for urgent and non-urgent downlink data transfers are described in clauses 8.17.1.1 and 8.17.1.2. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.1.1 Reading Non-Urgent Data | Non-urgent data to be transferred to the MEP device resides in a section of ET13 called "MEP Non-Urgent Data". The MEP device should read this area for new data every time it communicates with the OSGP device, or at some manageable periodic interval. This space is not managed or cleared by the OSGP device. Non-urgent d... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.1.2 Reading and Processing On-Demand Requests | An urgent, or on-demand, data transfer is one that is to occur as soon as possible, usually with the expectation of an acknowledgment of the success or indication of failure of the transfer. Urgent downlink data transfers, or on-demand write requests, to the MEP device are limited to 24 bytes (25 bytes, including the l... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.2 Uplink Data Transfer | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.2.0 Foreword | Data flow from the MEP device to the OSGP device is also facilitated by one of several different mechanisms, depending on the source and type of the data transfer. All of the mechanisms for uplink data transfers are described in clauses 8.17.2.1 to 8.17.2.5. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.2.1 Responding to a Scheduled Read Request (With and Without Alarms) | ET13, "MEP Device Configuration" can be provisioned to facilitate scheduled reads of MEP device data. The schedule can be set for hourly, daily, weekly, or monthly reads at specified times. Once a schedule is established, the following steps occur: 1) The scheduled read period elapses, and the OSGP device sets the "Sch... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.2.2 Responding to an On-Demand Read Request (With and Without Alarms) | Urgent uplink data may be posted to the OSGP device independently by the MEP device, or in response to an on- demand read request from NES. Alarms are considered as a special type of urgent uplink data. Both data and alarms are posted to the OSGP device in the same way, similar to the mechanism for posting non-urgent u... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.2.3 Posting Unsolicited Non-urgent Data (With and Without Alarms) | The MEP device can post non-urgent data on its own (i.e. not in response to a scheduled read or on-demand request) to the OSGP device for transfer upstream. This is done as follows: 1) The MEP device posts the requested data to the OSGP device through procedure EP39 with the parameter "Non-urgent data only" or "Non-urg... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.2.4 Posting Unsolicited Urgent Data | Posting urgent data independently, i.e. not in response to an on-demand request, consists of the following steps. Note that data posted through this mechanism does not consume the scheduled and non-urgent data buffer: 1) Post the data through procedure EP39 with the parameter "Unsolicited Urgent Data Only". NOTE: If a ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.17.2.5 Posting Alarms Only | Posting alarms generated by the MEP device to the OSGP device consists of the following steps: 1) The MEP device should execute EP39 with the parameter "Alarms Only" and the single byte of alarms to be posted to the OSGP device. Figure 26 2) The OSGP device copies the alarms data to a table that is read by the Data Con... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18 M-Bus Device support (optional) | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.0 Foreword | The optional M-Bus capabilities in the OSGP device can discover and query up to four M-Bus devices, such as gas, water, or heat meters. The OSGP device stores the consumption data collected from the M-Bus devices along with any alarm or status messages. The data and messages are sent to the utility central service cent... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.1 Billing Data Collection | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.1.0 Foreword | Billing data can be collected during a scheduled polling of the M-Bus devices, or by an on-demand read request. These methods are described in clauses 8.18.1.1 to 8.18.1.4. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.1.1 On-Demand Reads for M-Bus Devices | An on-demand read can be performed at any time, and need not be scheduled in advance. The date and time of each reading is included with the collected data. Up to 525 bytes (mostly data, but including some overhead) can be stored for an M-Bus device on-demand read, and the OSGP device can store data for one on-demand r... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.1.2 Scheduled Reads for M-Bus Devices | The OSGP device can be programmed to perform regularly scheduled reads of the M-Bus device. The time of day that a scheduled read occurs is configurable. Scheduled reads can be set to repeat daily, weekly, monthly, or yearly. The scheduled read schedule for each M-Bus devices is stored in the "Scheduled Billing Read Ti... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.1.3 One-Time-Reads for M-Bus Devices | The OSGP device can be programmed to perform a scheduled One-time-read of an M-Bus device. One-time-reads may be useful if it is desirable schedule a billing read on a specific date and time, e.g. when a customer moves out of a residence. Up to 4 One-time-reads can be scheduled in the OSGP device at once. This can be 1... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.1.4 Power Outage Data-Read Interruptions | If a scheduled or on-demand record is interrupted or missed entirely by a power outage, the read will be performed when the power is restored. Timestamps of the read will represent when the read was completed. ETSI ETSI TS 104 001 V2.1.1 (2016-12) 68 |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.2 Auto-discovery | Auto-discovery is the process by which the OSGP device polls the M-Bus network for new and previously commissioned devices. Newly discovered devices are added to the commissioned device list for regular polling, up to a maximum of four devices. The auto-discovery mode status can be determined by reading the "Mode" fiel... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.3 Device Removal | An M-Bus device can be logically removed from the OSGP device with EP17 "Remove M-Bus/MEP Device". |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.18.4 M-Bus Status and Alarms | M-Bus status information and alarms can be read at a configurable interval, on-demand, or at the same time that billing information is collected. The date and time of each reading is included. The OSGP device can recognize the standard M-Bus alarms and status messages for items such as the type of counter, power level,... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 8.19 Compatibility Settings (mandatory) | The OSGP device has a compatibility setting that is used to control behaviour when working with PLC clients such as Data Concentrators. The compatibility setting is readable via read-only tables ET42 and ET54. The compatibility setting bit mask has these bits that determine: • ICS - ICA NAK bit - whether a OSGP device ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9 Basic OSGP services | 9.0 Foreword All fields in the following messages, except <data> fields, are in MSB format. A sequence number and digest is added by the OSGP security mechanism in all messages, see clause 7. For pending tables, all <count> and <length> fields include the Pending Event Descriptor (<PED>), when present. Furthermore, the... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.1 Matching of requests and responses | The OSGP protocol is master-slave to avoid collisions because the nodes may not be able to hear each other. Therefore, overlapping transactions cannot be supported. Procedures shall be executed strictly one at a time, waiting for a first procedure result before calling the next. Each OSGP transaction request is carried... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.2 Buffer sizing restrictions | The following restrictions apply to buffer sizing: a) The maximum length of explicit message (including OSGP commands) is 114 bytes. b) The maximum number of table bytes requested on partial reads is 84 bytes. c) The maximum number of table bytes sent on partial writes is 75 bytes. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.3 Full Table Read service | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.3.1 Request | The OSGP Full Read Request command provides the capability to read the entire specified data table in the device. <length> 2 (MSB - Most Significant Byte first) The number of bytes in the remainder of the message, not including the <length> field. To me it seems this item is part of the Lon transport layer (it is not i... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.3.2 Full Read Response | The Full read service response will contain the table data as specified in the read service request. Full read response: <response> <count> <data> When the read request targets a pending table, a six octet pending event description is added before the table data. The Full Read service response uses the following parame... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.4 Full Table write service | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.4.1 Request | The Full Write Request command writes bytes to the entire specified data table in the device. If fewer bytes are provided than will fill the table, only those bytes provided are written and the remainder is left as is and no error is returned. If more bytes are provided than will fit in the table, the extra bytes are i... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.4.2 Response | Full write response: <response> The Full Write service response uses the following parameters: Table 9 Message field Data type Value Comments <response> UINT8 <nok>|<ok> See response code for details |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.5 Partial table read | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.5.1 Request | The Partial Read Request command reads the specified bytes in the specified data table in the device. If the number of bytes requested exceeds the number available in the table, the extra bytes are returned as zeroes and no error is returned. Partial read request: <command> < table ID> <offset> <count> The Partial Read... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.5.2 Response | Response is of the same format as the full read response. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.6 Partial table write | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.6.1 Request | The Partial Write Request command writes the specified bytes into the specified data table in the device. If more bytes are provided than will fit in the table, the extra bytes are ignored and no error is returned. Partial write request: <command> <table ID> <offset> <count> <data> ETSI ETSI TS 104 001 V2.1.1 (2016-12)... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.6.2 Response | Response is of the same format as the full write response. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.7 Request/Response sequencing | The BS EN 14908-1 [1] sequence number is handled by the OSGP device as follows: a) If incoming sequence number is N as expected, OSGP device fulfills request and responds appropriately. b) If incoming sequence number is N-1 OSGP device does not re-perform the action requested, but sends the response that was sent for t... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.8 Request/Response OSGP APDU example | Partial read request: • > 00:3F:0034:000000:0006:F52F5481:599DF7BCF192C236 OSGP APDU description: 00: BS EN 14908-1:2014 [1] application code. 3F: OSGP service request code (partial table read). 0034: OSGP table ID (BT52). 000000: Table offset (0). ETSI ETSI TS 104 001 V2.1.1 (2016-12) 73 0006: Count (6). F52F5481: OSG... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.9 Response error codes | The two types of response codes the OSGP device may return are <ok> and <nok>. • <nok> indicates one of the following response codes: - <nok> = <sns> | <onp> | <iar> | <bsy> | <dig> | <seq> | <inc> | <ica> Table 12 Response code Response value Definition Reason <ok> 0x00 Acknowledge - No problems, request accepted. Com... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.10 Transactions | The OSGP protocol supports a very limited message size. It is not possible to atomically read/write tables larger than a few dozen bytes. It is also not possible in OSGP to deliver multiple write commands and be sure that all will take effect. The transaction table provides an ability to safely execute complex interact... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.11 Secure Broadcasts | The sequence number of 0 shall be used during broadcasts to indicate that no sequence check is to be performed. Such broadcasts are not immune to replay attack. Consequently normal sequencing shall not use the sequence number 0 and therefore, secure broadcasts shall be sent using the secure broadcast sequence number as... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.12 Downloading | Downloading shall use a broadcast sequence number allocated from the above range that shall be fixed for the duration of the download. |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.13 Procedure invocation | |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.13.0 Foreword | Actions performed by the OSGP device are achieved through procedures. Procedures are initiated by writing into BT07 in the OSGP device and the response is read in BT08 "Procedure response Table", if configured. Writing to BT07 "Procedure Initiate Table" with the procedure number requested and any input parameters, the ... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.13.1 Procedure Timing | In general, procedures shall be executed synchronously. This means that the OSGP device shall receive the BP07 write, execute the procedure, and send the response to the BP07 write. As a result, by the time BP08 is read for the result, the procedure will have executed. However, in some cases the procedure may set the r... |
b3377a9ce5a4f1019b8cde05cb5e8004 | 104 001 | 9.13.2 Slow and Non-Responsive Procedures | Another concern with synchronous execution is the duration of the procedure execution. For most procedures, the time to execute the function is very short and thus the execution time will not affect the timing of the BP07 write response. However, in some cases the delay in responding to the BP07 write may be significan... |
91e3c38fe3abe88e8cedf4746c134c72 | 103 983 | 1 Scope | The present document specifies the general aspects and principles of the A1 interface. |
91e3c38fe3abe88e8cedf4746c134c72 | 103 983 | 2 References | |
91e3c38fe3abe88e8cedf4746c134c72 | 103 983 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.