倍加福R2000 Ethernet通信协议详解

需积分: 46 149 浏览量更新于2024-07-14 收藏 4.23MB PDF 举报

"该文档是关于倍加福(PEPPERL+FUCHS)R2000系列传感器的以太网通信协议，标题为'倍加福通信协议.pdf'，描述中提到的'OMD30M-R2000-B23-V1V1D-1L'可能是该系列传感器的一个具体型号。标签强调了倍加福R2000通信协议以及OMD30M-R2000-B23。文档内容涵盖了协议的基础知识、传感器参数化方法等关键信息。" 详细说明: 1. **协议基础** - **基本设计**: 文档介绍了R2000系列传感器的以太网通信协议的基本设计，可能包括协议的结构、数据包格式和通信流程。 - **HTTP命令协议**: 传感器与主机间的通信基于HTTP命令，这表明可以通过HTTP请求来操控和获取传感器数据。 - **发送命令**: 描述了如何向传感器发送HTTP命令以执行特定操作或获取信息。 - **查询参数编码**: 解释了如何对命令中的参数进行编码以便于传输和解码。 - **命令响应**: 详述了传感器如何回复接收到的命令，包括成功响应、错误信息等。 - **HTTP状态代码**: 列出了可能返回的各种HTTP状态代码，如200（成功）、404（未找到）等，这些代码用于指示命令执行的状态。 - **传感器错误代码**: 提供了传感器可能出现的错误代码，帮助诊断通信问题。 - **协议信息(get_protocol_info)**: 这是一个命令，可以用来获取关于当前使用的通信协议的详细信息。 2. **传感器参数化使用HTTP** - **参数类型** - **枚举值(enum)**: 允许用户在预定义的选项中选择一个参数值。 - **布尔值(bool)**: 用于设置或读取二进制开关状态。 - **位字段(bitfield)**: 可能表示多个独立的设置，每个设置对应位的1或0。 - **整数值(int, uint)**: 用于表示整数类型的参数。 - **双精度浮点值(double)**: 用于处理高精度的数值参数。 - **字符串值(string)**: 用于存储文本数据。 - **IPv4地址和网络掩码值(IPv4)**: 用于配置传感器的网络设置。 - **NTP时间戳值(ntp64)**: 可能涉及与网络时间协议相关的设置。 - **二进制数据(binary)**: 用于传输非结构化的二进制数据。 - **参数化命令** - **list_parameters**: 列出传感器的所有可用参数及其当前值。 - **get_parameter**: 读取指定参数的当前值。 - **set_parameter**: 修改参数的值。 - **reset_parameter**: 将参数重置为其默认值。这些内容对于理解如何通过以太网与倍加福R2000系列传感器进行通信至关重要，包括如何配置传感器参数、获取传感器状态以及诊断和解决问题。

R2000 Ethernet communication protocol

Sensor parametrization using HTTP

Protocol version 1.02 Document release 2016-03

2 Sensor parametrization using HTTP

2.1 Parameter types

The sensor provides access to different types of parameters. The following table gives a quick overview of the relevant types, a

more detailed description follows in separate sub-sections:

type description

enum enumeration type with a set of named values (strings)

bool boolean values (on / off)

bitfield a set of boolean ﬂags

int signed integer values

uint unsigned integer values

double ﬂoating point values with double precision

string strings composed of UTF-8 characters

ipv4 Internet Protocol version 4 addresses or network masks

ntp64 NTP timestamp values

binary Binary data

Independently of their type, each parameter belongs to one of the following access groups:

access description

sRO static Read-Only access (value never changes)

RO Read-Only access (value might change during operation)

RW Read-Write access (non-volatile storage)

vRW volatile Read-Write access (lost on reset)

Most sensor parameters are stored into non-volatile memory. Thus their value persists even if the device encounters a power-

cycle. Please note though, that non-volatile storage has a limited number of write cycles only (typical > 10.000 cycles). There-

fore all non-volatile parameters should be written only if necessary.

2.1.1 Enumeration values (enum)

Notes on parameters using enumeration values (enum):

• An enumeration type parameter accepts a single value out of a list of predeﬁned values.

• Each enumeration values is deﬁned by a string (’named’ value).

• Each enumeration value is typically (but not necessarily) unique to the speciﬁc parameter.

• Each enum parameter can hold only a single value at a time.

• URI: Named enumeration values use non-reserved ASCII characters only and need no percent encoding [7] when

speciﬁed as argument to a command on the URI.

2.1.2 Boolean values (bool)

Notes on parameters using boolean values (bool):

• Boolean parameters are a special case of enumeration parameters.

• Only the named values on and off are accepted.

• Each bool parameter can hold only a single value at a time.

R2000 Ethernet communication protocol

Sensor parametrization using HTTP

Protocol version 1.02 Document release 2016-03

2.1.3 Bit ﬁelds (bitfield)

Notes on parameters using bit ﬁelds (bitfield):

• Bit ﬁelds combine multiple boolean ﬂags into an unsigned integer value.

• Each ﬂag occupies a single bit of the integer.

• Not every bit of the integer needs to be assigned to a ﬂag.

• Bits might be marked as reserved. These should always be zero.

• Bit ﬁeld parameters are read and written using the integer representation.

2.1.4 Integer values (int, uint)

Notes on parameters using signed integer values (int) and unsigned integer value (uint):

• Unless denoted differently, the value range of integer values is limited to 32 bit.

• Leading zeros are accepted when writing a value (they will be ignored).

• Neither a hexadecimal nor an octal representation of integer values is supported.

2.1.5 Double values (double)

Notes on parameters using double precision ﬂoating point values (double):

• A dot ’.’ is used as decimal mark (separating the decimal part from the fractional part of a double number).

• The ﬂoating point decimal format (xxx.yyy) should be used when accessing double parameters. The ﬂoating point

exponential format (xxx.yyy Ezzz) is not supported.

• The number of signiﬁcant digits of the fractional part of a double value might be limited for some parameters. Excess

digits are rounded or discarded.

2.1.6 String values (string)

Notes on parameters using string values (string):

• Strings represent a set characters.

• All characters of the string need to be encoded in UTF-8 format [6].

• The maximum size of a string is usually limited. Please refer to the description of the speciﬁc parameter for its actual

size limitation.

• URI: For write access to a string parameter, its new value is implicitly delimited by the surrounding ’=’ and ’&’ within the

URI (see RFC 3986 [7]). Any additionally added delimiter (e.g. ’"’) will be interpreted as part of the string.

• URI: Some characters are reserved within an URI and need to be percent encoded [7] (see section 1.2.2 for details).

When parsing a string-typed parameter within an UTF-8 encoded command URI the sensor performs the following steps:

1. Dissect the URI into it individual parts

2. Resolve percent encoded characters

3. Check string for a valid UTF-8 encoding

4. Process the string (UTF-8 bytes), e.g. store it into non-volatile memory

When the sensor outputs a string-typed parameter in JSON format, it applies escaping for the following reserved UTF-8 char-

acters (as required by RFC 7159 [9] section 2.5):

R2000 Ethernet communication protocol

Sensor parametrization using HTTP

Protocol version 1.02 Document release 2016-03

character code replacement

backspace U+0008 ’\b’

tabulator U+0009 ’\t’

new line U+000A ’\n’

form feed U+000C ’\f’

carriage return U+000D ’\r’

double quote U+0022 ’\"’

solidus U+002F currently not replaced

backslash U+005C ’\\’

other control characters U+0000 . . . U+001F ’\uXXXX’

2.1.7 IPv4 address and network mask values (IPv4)

Notes on parameters using IPv4 network addresses and subnet masks (IPv4):

• Addresses and network masks need to follow the rules of the Internet Protocol speciﬁcation (RFC-791 [1])

• Addresses are denoted as string values in human-readable dotted decimal notation (i.e. 10.0.10.9)

• Subnet masks are denoted as string values in human-readable dotted decimal notation (i.e. 255.255.0.0)

2.1.8 NTP timestamp values (ntp64)

Notes on parameters using NTP timestamps (ntp64):

• NTP timestamps are part of the Network Time Protocol (NTP) as deﬁned by RFC 1305 [2].

• NTP timestamps are represented as a 64 bit unsigned ﬁxed-point integer number (uint64) in seconds in reference to a

speciﬁc point in time. The most signiﬁcant 32 bit represent the integer part (seconds), the lower 32 bit the fractional part.

• Absolute timestamps (synchronized time) refer to the time elapsed since 1 January 1900.

• Relative timestamps (raw system time) refer to the time elapsed since power-on of the sensor.

Please refer to section 3.1.5 for more details on timestamps.

2.1.9 Binary data (binary)

Notes on parameters using binary data (binary):

• Parameters of type binary store binary data without further data-speciﬁc knowledge. Parameter values are simply

treated as a collection of bytes. The interpretation of binary data is speciﬁc to the individual parameter. See the

description of the speciﬁc parameter for details.

• For binary parameters usually only size checking is performed. The maximum size of data depends on the speciﬁc

parameter.

• Read access to a binary parameter returns its value as base64 encoded string within the JSON reply (see section 1.2.3).

The base64 encoding transforms an 8 bit data stream to a string with a particular set of 64 ASCII characters (6 bit) that

are printable and common to most character encodings (see RFC 4648 [8] for details). This encoding requires 33 %

more storage space.

• Write access to a binary parameter requires the binary data to be encoded as base64url [8] string on the URI. The

base64url encoding is very similar to the base64 encoding but uses a slightly different character set, that avoids using

reserved URI characters.

剩余58页未读，继续阅读

hulei_accp

粉丝: 17
资源: 47

倍加福R2000 Ethernet通信协议详解

R2000模组用户通信协议手册

R2000通讯协议用户手册_V3.1.doc

r2000API使用说明

倍加福设置手册.pdf

基于西门子PLC自由通信协议实现倍加福工业识别系统的通信.pdf

倍加福 倾角传感器F99.pdf

tdoct1794f_eng倍加福转换器说明书.pdf

倍加福AS-Interface选型手册.pdf

倍加福WHA无线网关英文样本.pdf

倍加福通信协议详解与应用指南

最新资源

倍加福倾角传感器F99.pdf