赫优讯(Hilscher)netX技术PROFIBUS DP主站协议接口手册

综合资料

需积分: 10 102 浏览量更新于2024-07-16 收藏 1.14MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"德国赫优讯(Hilscher)基于netX技术的PROFIBUS DP主站协议接口手册提供了一本详细的指南，介绍了如何使用Hilscher公司的netX技术实现PROFIBUS DP主站的功能。该手册适用于系统集成商和开发人员，帮助他们理解和实施与PROFIBUS DP主站相关的通信协议。手册经过多次修订，包含了丰富的编程接口信息，以英文为主要语言。" 在工业自动化领域，PROFIBUS DP是一种广泛应用的现场总线标准，用于实现分布式I/O通信。此手册的核心内容可能包括以下几个方面： 1. **PROFIBUS DP主站功能**: PROFIBUS DP主站是网络中的控制中心，负责组织和管理通信，以及与从站设备的数据交换。手册将详细解释主站如何通过netX芯片执行这些功能。 2. **netX技术**: netX是由Hilscher公司开发的一种微处理器技术，专为工业通信设计，支持多种通信协议。手册会介绍如何利用netX的特性来实现高效、可靠的PROFIBUS DP通信。 3. **协议API接口**: 接口定义了主站软件与硬件之间的交互方式，包括数据传输、错误处理和状态管理等。手册中会详细列出各种命令和函数，如`PROFIBUS_FSPMM_CMD_APP_REG_REQ/CNF`，供开发者使用。 4. **编程接口**: 手册可能会涵盖如何编写驱动程序或应用软件，以控制基于netX的PROFIBUS DP主站。这可能包括API调用的示例，以及如何处理不同类型的从站响应。 5. **主站状态块和参数**: 主站状态块包含关于网络和设备状态的信息，而参数则定义了主站的配置。手册会解释如何访问和修改这些状态和参数，以适应不同的系统需求。 6. **错误处理**: 手册中的错误消息描述有助于开发者识别和解决通信问题。错误代码和处理方法的详细文档是调试和优化系统的关键。 7. **版本更新**: 版本历史显示手册经过了多次更新和改进，如添加新的章节、扩展API描述和修复错误，反映了Hilscher对技术支持的持续投入。 8. **兼容性**: 虽然手册主要关注PROFIBUS DP，但netX技术可能还支持其他协议，如PROFINET或EtherCAT。因此，手册可能还会提供与其他协议集成的指导。通过这份手册，工程师可以获得深入的理论知识和实践指南，从而有效地利用Hilscher的netX技术构建和维护PROFIBUS DP主站系统。对于那些致力于工业自动化系统开发的人来说，这是一份非常有价值的参考资料。

资源详情

资源推荐

PROFIBUS DP-Master Fundamentals • 16

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim

Edition 5 – API:PROFIBUS DP-Master#EN– 2007/12

2.3 Accessing the Protocol Stack via the Dual Port Memory

Interface

This chapter defines the application interface of the DP-Master Stack.

2.3.1 Communication via Mailboxes

The mailbox of each communication channel has two areas that are used for non-cyclic message

transfer to and from the netX.

 Send Mailbox

Packet transfer from host system to netX firmware

 Receive Mailbox

Packet transfer from netX firmware to host system

For more details about acyclic data transfer via mailboxes see section 3.2. The concept of using

messages called packets in this context, is described in detail in section 3.2.1 “General Structure of

Messages or Packets for Non-Cyclic Data Exchange” while the possible codes that may appear are

listed in section 3.2.2. “Status & Error Codes”.

However, this section concentrates on correct addressing the mailboxes.

PROFIBUS DP-Master Fundamentals • 19

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim

Edition 5 – API:PROFIBUS DP-Master#EN– 2007/12

Example

This example applies to command messages initiated by a process in the context of the host

application. If the process #22 sends a packet through the channel mailbox to the AP task, the packet

header has to be filled in as follows:

Object Variable

Name

Numeric

Value

Explanation

Destination

Queue

Handle

ulDest = 32

(0x00000020)

This value needs always to be set to 0x00000020 (the channel

token) when accessing the protocol stack via the local

communication channel mailbox.

Source

Queue

Handle

ulSrc = 444

Denotes the host application (#444).

Destination

Identifier

ulDestId = 0

In this example it is not necessary to use the destination identifier.

Source

Identifier

ulSrcId = 22

Denotes the process number of the process within the host

application and needs therefore to be supplied by the programmer

of the host application.

For packets through the channel mailbox, the application uses 32 (= 0x20, Channel Token) for the

destination queue handler ulDest. The source queue handler ulSrc and the source identifier ulSrcId

are used to identify the originator of a packet. The destination identifier ulDestId can be used to

address certain resources in the protocol stack. It is not used in this example. The source queue

handler ulSrc has to be filled in. Therefore its use is mandatory; the use of ulSrcId is optional.

The netX operating system passes the request packet to the protocol stack's AP task. The protocol

stack then builds a reply to the packet and returns it to the mailbox. The application has to make sure

that the packet finds its way back to the originator (process #22 in the example).

2.3.2.3 How to Route rcX Packets

To route an rcX packet the source identifier ulSrcId and the source queues handler ulSrc in the packet

header hold the identification of the originating process. The router saves the original handle from

ulSrcId and ulSrc. The router uses a handle of its own choices for ulSrcId and ulSrc before it sends the

packet to the receiving process. That way the router can identify the corresponding reply packet and

matches the handle from that packet with the one stored earlier. Now the router replaces its handles

with the original handles and returns the packet to the originating process.

PROFIBUS DP-Master Fundamentals • 20

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim

Edition 5 – API:PROFIBUS DP-Master#EN– 2007/12

2.3.3 Obtaining useful Information about the Communication Channel

A communication channel represents a part of the Dual Port Memory and usually consists of the

following elements:

• Output Data Image

is used to transfer cyclic process data to the network (normal or high-priority)

• Input Data Image

is used to transfer cyclic process data from the network (normal or high-priority)

• Send Mailbox

is used to transfer non-cyclic data to the netX

• Receive Mailbox

is used to transfer non-cyclic data from the netX

• Control Block

allows the host system to control certain channel functions

• Common Status Block

holds information common to all protocol stacks

• Extended Status Block

holds protocol specific network status information

This section describes a procedure how to obtain useful information for accessing the communication

channel(s) of your netX device and to check if it is ready for correct operation.

Proceed as follows:

1) Start with reading the channel information block within the system channel (usually starting at

address 0x0030).

2) Then you should check the hardware assembly options of your netX device. They are located

within the system information block following offset 0x0010 and stored as data type UINT16.

The following table explains the relationship between the offsets and the corresponding xC

Ports of the netX device:

0x0010

Hardware Assembly Options for xC Port[0]

0x0012

Hardware Assembly Options for xC Port[1]

0x0014

Hardware Assembly Options for xC Port[2]

0x0016

Hardware Assembly Options for xC Port[3]

Check each of the hardware assembly options whether its value has been set to

RCX_HW_ASSEMBLY_PROFIBUS = 0x0050. If true, this denotes that this xCPort is suitable

for running the Profibus protocol stack. Otherwise, this port is designed for another

communication protocol. In most cases, xC Port[2] will be used for field-bus systems, while xC

Port[0] and xC Port[1] are normally used for Ethernet communication.

剩余229页未读，继续阅读

weixin_38744435

粉丝: 373
资源: 2万+

赫优讯(Hilscher)netX技术PROFIBUS DP主站协议接口手册

德国赫优讯(Hilscher)基于netX技术的EtherCAT主站协议接口手册.pdf

德国赫优讯(Hilscher) 基于netX技术的CANopen主站协议接口手册.pdf

德国赫优讯(Hilscher)基于netX技术的PROFIBUS DP从站协议接口手册.pdf

德国赫优讯(Hilscher)DeviceNet主站计算机板卡协议接口手册.pdf

德国赫优讯(Hilscher)基于netX技术的Powerlink_Controller协议接口手册.pdf

德国赫优讯(Hilscher)基于netX技术的EtherCAT从站协议接口手册.pdf

德国赫优讯(Hilscher)基于netX技术的CANopen从站协议接口手册.pdf

德国赫优讯(Hilscher)CANopen主站计算机板卡协议接口手册.pdf

HILSCHER CIF PROFIBUS-DP主站板卡应用手册.pdf

德国赫优讯(Hilscher)基于netX技术的 EtherNetIP_Adapter协议接口手册.pdf

德国赫优讯(Hilscher)基于netX技术的DeviceNet从站协议接口手册.pdf

德国赫优讯(Hilscher)基于netX技术的CC-Link从站协议接口手册.pdf

德国赫优讯(Hilscher)netX技术Powerlink_Controller协议接口手册

numexpr-2.8.3-cp38-cp38-win_amd64.whl

最新资源