DeviceNet Master Protocol API
DeviceNet Master Protocol API
DeviceNet Master Protocol API
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>DeviceNet</strong>-<strong>Master</strong> Dual-Port Memory • 51<br />
The following error numbers are valid for bErr_Event, if bErr_device_adr is not equal to 255:<br />
bErr_Event signification error source Remarks/help<br />
0 No error<br />
1 Missing node Device Device guarding failed,<br />
after device was<br />
operational. Check if<br />
device is still running<br />
2 Device has been stopped Device Try to restart the device<br />
30 Device access timeout Device The slave device does<br />
not respond, check the<br />
baudrate and its MAC-ID<br />
32 Device rejects access<br />
with unknown error code<br />
35 Device response in<br />
allocation phase with<br />
connection error<br />
36 Produced connection (<br />
process data input length<br />
in the view of the Hilscher<br />
master device) is different<br />
to the configured one<br />
37 Consumed connection (<br />
process data output<br />
length in the view of the<br />
Hilscher master) size is<br />
different to the configured<br />
one<br />
38 Device service response<br />
telegram unknown and<br />
not handled<br />
39 Connection already in<br />
request<br />
40 Number of CAN-message<br />
data bytes in read<br />
produced or consumed<br />
connection size response<br />
unequal 4<br />
41 Predefined master slave<br />
connection already exists<br />
42 Length in polling device<br />
response unequal<br />
produced connection size<br />
43 Sequence error in device<br />
polling response<br />
Device<br />
Device<br />
Device / configuration<br />
Device / configuration<br />
Device / Hilscher master<br />
device<br />
Device<br />
Device<br />
Device / Hilscher master<br />
device<br />
Device<br />
Device<br />
Use single device<br />
diagnostic to get reject<br />
code<br />
Use single device<br />
diagnostic to get<br />
additional reject code<br />
Use single device<br />
diagnostic to get real<br />
produced connection size<br />
Use single device<br />
diagnostic to get real<br />
consumed connection<br />
size.<br />
Use single device<br />
diagnostic to get real<br />
consumed connection<br />
size<br />
The connection will be<br />
released automatically.<br />
Device does not have<br />
operability with Hilscher<br />
master device or it<br />
conflicts with the<br />
<strong>DeviceNet</strong> specification.<br />
The connection will be<br />
released automatically<br />
First two segments in<br />
multiplexed transfer were<br />
received<br />
44 Fragment error in device Device Fragmentation counter<br />
while multiplexed transfer<br />
Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim<br />
Edition 3 – <strong>API</strong>:<strong>DeviceNet</strong>-<strong>Master</strong>#EN– 2009/01
Change language