文件名称:
德国赫优讯(Hilscher)netTAP(DeviceNet从站转串口协议3964R)协议配置手册.pdf
开发工具:
文件大小: 188kb
下载次数: 0
上传时间: 2019-10-09
详细说明：德国赫优讯(Hilscher)netTAP(DeviceNet从站转串口协议3964R)协议配置手册pdf,德国赫优讯(Hilscher)netTAP(DeviceNet从站转串口协议3964R)协议配置手册NT 30-DNS (DeviceNet Slave /3964R)
Tab| e of contents·3
Table of contents
INTRODUCTION
5
About this manual
2 STARTUP GUIDELINE
2.1
General
■重面
3 COMMUNICATION MECHANISM
Data Management -Conversion Principle
3.1.1
The Handshake(Error-)Bytes
10
3.1.2
Principles of communication
13
3.2 Task States in the deviceNet Input data
4 SETTINGS- PARAMETERIZING- CONF GURATION
18
4.1 About the Configuration
42 Parameterizing of the master……
111■重■1
3 Parameterizing of the Gateway……
18
4.4
Editing the 3964R Table
.19
4.5 Editing the BUs DNS Table
20
4.6 Editing the BRIDGE Table
21
4.7 Editing the sERIAL_ STS Table.….….…..…..….…..….....2
4.8 Editing the bridge sts table
22
5D| AGNOSTIC∴
23
LEDS
2
5.2
Extendedtaskstatewwwww.23
5.2.1
Extended task state of the 3964r Protocol task
24
52.2
Extended task State of the bridge dNsnVR
6 ERROR MESSAGES
.27
General
27
6.2
Error Handling of the3964 R Protocol Task∴…28
6.2.1
Initialization errors
28
62.2
Errors when Sending and Receiving Data
29
62.3
Internal System Errors
6. 3 Error Messages of the Bridge DNSNVR
6.3.1
Initialization errors
31
6.3.2
Protocol-and Message Errors
31
6.3.3
Internal System Errors
.32
7 TECHNICAL DATA
.33
NT30-DNS With deviceNet slave on 3964R
33
Copyright Hilscher Gesellschaft fur Systemautomation mbH. Br: NTDNSNVR#2EN
Table of contents
NT 30-DNS (DeviceNet slave /3964R)
8 LISTS
35
8. 1 List of Figures
35
8.2
List of tables
36
Copyright Hilscher Gesellschaft fur Systemautomation mbH. Br: NTDNSNVR#2EN
NT 30-DNS (DeviceNet slave /3964R)
Introduction·5
1 Introduction
1.1 About this manual
In this manual the conversion of the 3964R protocol on the Device Net
Slave is described. The conversion takes place on the gateway netTAP 30
DNS. It realizes a transparent data communication between the deviceNet
Slave and a 3964R communication partner. The gateway works as Slave
on the device net
nettAP 30-DNS
Device with 3964R Protoco
+24V
DeviceNet
Interface
3964R
DeviceNet
Figure 1: Connection of the 3964R communication partner via the gateway on the device NE
Values with an attached letter h' are in hexadecimal way of writing values
without following letters are in decimal way of writing(for example: 1Eh
30)
Copyright Hilscher Gesellschaft fur Systemautomation mbH. Br: NTDNSNVR#2EN
NT 30-DNS (DeviceNet slave /3964R)
Startup Guideline·7
2 Startup Guideline
21 General
For the startup of the gateway as Slave the following sequence has to be
considered
A firmware has to be loaded on the gateway
A valid configuration data base has to be saved at the gateway
The bus address must be adjusted on the gateway at the rotary
switches
The 3964R communication partner needs to be connected. For
configuration of the physical interface and preparation of the cable
please consult the device manual
Configure the DeviceNet Master with the help of the enclosed EDS
file. Exactly the same data as in the master configuration must be
given in the table BUs DNS
Connect the DeviceNet cable and the power supply
The rdy and the run leds need to be on static and must not flash
Note: With a device defect it can also affect cyclic flashing of the RDY LEd
because of sequential responding of the Watchdog monitoring
Copyright Hilscher Gesellschaft fur Systemautomation mbH. Br: NTDNSNVR#2EN
8. Kommunikationsmechanismus
NT 30-DNS (Device Net slave /3964
3 Communication Mechanism
3.1 Data Management - Conversion Principle
The Device Net knows input and output data which are exchanged cyclically
between the Master and the Slaves. The Gateway works as Slave on the
DeviceNet and makes the following memory available
DeviceNet
Output data
Input data
from master
to Master
Hands hake
Handshake/ Error
Number of user data
Number of user data
User data(64 Byte)
ser data(64 Byte)
3946R
Queue
couplIng
pal
netTAP 30-DNS
Figure 2: Internal memory of the Gateway(Example with 64 Byte user data)
The meaning of inputs and outputs must always be seen from the viewpoint
of the devicenet master
Input data
are always data that are received from the device Net master
Output data
are always data that are output from the DeviceNet Master
Copyright Hilscher Gesellschaft fur Systemautomation mbH. Br: NTDNSNVR#2EN
NT 30-DNS (DeviceNet slave /3964R)
Communication Mechanism. 9
The output data from the Master are placed into the output memory whilst
the data is transported from the input memory to the Master. The size of
both memories is always preset to(2+64), but can be correspondingly
parameterized to the requirements of the user. Only the user data are
always exchanged with the 3964R communication partner. According to the
above example this is a maximum of 64 bytes
If the 3964R communication partner sends a telegram without the
DeviceNet Master having acknowledged the previous telegram, then the
Gateway can place it, and following telegrams, into a queue buffer. The
queue works on the FIFo principle, i.e. the sequence of the telegrams
remains intact. As long as there are telegrams in the queue, all the
incoming telegrams from the 3964R communication partner are routed
through the queue! Only when the queue is empty, the telegrams go the
direct way again (see diagram). The size of the queue can be
parameterized from 0.20, whereby 0 means that the queue is not active
An overrun of the queue is entered into the error bits(see below). These
telegrams get lost!
At the beginning of both memory ranges a first byte is always defined for
controlling the telegram input and output. Furthermore, in the input data
area, additionally occurring errors are reported to the deviceNet in the form
of error bits. For instance, it can send an error telegram to the 3964R
communication partner
The user data quantity is entered into the second Byte. The Device Net
master must enter the user data quantity in the output data. The Gateway
automatically takes up the user data quantity in the input data from the
3964R telegram received and enters it. the user must parameterize the
maximum user data quantity in both directions. The Gateway monitors it
and an overstepping of this limit is entered into the error bits
The actual user data then follow. These are passed between the deviceNet
and the 3964R communication partner without alteration. On the
DeviceNet, the quantity of Bytes parameterized for each direction is always
exchanged cyclically. The current quantity of the actual user data is given in
both transfer directions in the preceding Byte
Copyright Hilscher Gesellschaft fur Systemautomation mbH. Br: NTDNSNVR#2EN
10. Kommunikationsmechanismus
NT 30-DNS (Device Net slave /3964
3.1.1 The Handshake(Error-)Bytes
These two bytes are defined in the following manner
D7 D3 D2 D1 DO
nd request
Ceive receiption
reserved
reserved
reserved
reserved
reserved
reserved
Figure 3: Handshake byte in the output data from the Master to the Gate way
D7 D4
ID3 D1DO
Send receiption
Receive request
Internal software error
NACK: The 3946R communi cation partner has refused a telegram
Timeout The 3946R communi cation partner does not answer
Telegram from the 3964R communication partner was refused(e.g. full queue
The 3964R communication partner has exceeded the max telegram length
The profiBUs-DP Master has exceeded the max number of user data
Figure 4: Handshake/Error-Byte in the input data of the Master from the Gateway
The Gateway passes the contents of the output memory to the 3964R
communication partner only when the handshake bits"Send acknowledge
and "Send request become unequal. This means it reacts only to
alterations noticed by the DeviceNet master. For acknowledge of the
utput, the Handshake bit " Send acknowledge" in the input data are set by
the Master to the value of the Handshake bit Send request. The
DeviceNet Master can take any errors that occur from the error bits in the
input data. If both bits are equal again, then the DeviceNet Master can
release the next task
Copyright Hilscher Gesellschaft fur Systemautomation mbH. Br: NTDNSNVR#2EN
(系统自动生成,下载前可以参看下载内容)
下载文件列表
相关说明
- 本站资源为会员上传分享交流与学习,如有侵犯您的权益,请联系我们删除.
- 本站是交换下载平台，提供交流渠道，下载内容来自于网络，除下载问题外，其它问题请自行百度。
- 本站已设置防盗链，请勿用迅雷、QQ旋风等多线程下载软件下载资源，下载后用WinRAR最新版进行解压.
- 如果您发现内容无法下载，请稍后再次尝试；或者到消费记录里找到下载记录反馈给我们.
- 下载后发现下载的内容跟说明不相乎，请到消费记录里找到下载记录反馈给我们，经确认后退回积分.
- 如下载前有疑问，可以通过点击"提供者"的名字，查看对方的联系方式，联系对方咨询.
