Hilscher CIFxx-DNM
The CIF30-DNM is a DeviceNet ISA master card.
The CIF50-DNM is a DeviceNet PCI master card.
The CIF60-DNM is a DeviceNet PCMCIA master card.
The C104-DNM is a DeviceNet PC104 master card.
The DPRAM of the CIFx0-CNM is 8 Kbytes. There are no interrupts used.
The following description relates to the CIF30-DNM. The other cards vary from the point of view of TwinCAT in form only.
Context menu
Append Box... <Insert>
Adds DeviceNet boxes.
Currently supports the following boxes (further details on the boxes given later):
Supported boxes | Description |
|---|---|
Bus Coupler | |
Economy Bus Couplers | |
Low-Cost Bus Couplers | |
General DeviceNet device |
Delete Device... <Del>
Removes the CIF30-DNM fieldbus card and all subsidiary elements from the I/O configuration.
Online Reset
Initiates an online reset on the DeviceNet.
"CIF-30 DNM" tab
Address: Enter the DPRAM card address here (CIF30-DNM and C104-DNM). This address is jumped/configured on the card and can assume the following values: from 0xC8000 to 0xEE000 in steps of 0x2000
PCI Slot/Ring: (CIF50-DNM) Indicates the logical PCI slot into which the card is inserted.
Search: Searches the computer for available CIFxx-CAN cards
MAC ID: Enter the master node (scanner) card address here. These must not be duplicated within the network.
Heartbeat: Set the rate with which the DeviceNet card sends heartbeat messages (not supported at the present time).
Baudrate: Used to set the baudrate used for DeviceNet operation.
Watchdog: Watchdog, used by the DeviceNet card to monitor TwinCAT.
VendorID: Gives the vendor ID with which the scanner card is identified in the network (e.g. in the Duplicate MAC ID Detection protocol)
AutoClear: If you select this box, a node failure will halt the whole network. Otherwise, the system attempts to re-incorporate the node and continues operating.
Synchronous Mode: The highest priority task linked with the corresponding device controls the fieldbus cycle and is thereby synchronized with the fieldbus. All other tasks are served asynchronously via corresponding buffers.
Firmware Update... Update the CIFxx-DNM firmware version here. The currently loaded firmware version is shown in the window - in red if the TwinCAT recognises and is awaiting a more recent version.
Diagnostic
Error Code | Description | Troubleshooting |
|---|---|---|
0x00 | No error |
|
0x01 | Ctrl: Parameter error | Check Master Parameter |
0x02 | AClr: Device stops the transmission to all nodes | Check cabling, Reconfigure Master |
0x04 | NExc: at least one node has not reached the data exchange state | Check ErrorRemAddr and ErrorEvent. inspect the field device indicated by ErrorRemAddr. |
0x08 | Fatal error because of heavy buserror | Check cabling, inspect the field devices, may one node makes trouble on the bus, Check DeviceNet Voltage |
0x10 | Event: transmission errors were detected | Check cabling, inspect the field devices, may one node makes trouble on the bus, Check Baudrate and MAC Id |
0x20 | NRdy: HOST is not ready | Check TwinCAT System for general errors |
0x40 | Duplicate MacId detected | Check Masters MacId |
0x80 | Duplicate MacId Test active | Check Baudrate and cabling, Master is may not able to set up his Duplicate Mac Id messages |
Error Code | Description | Troubleshooting |
|---|---|---|
Station Number | Number of faulted slave device | Inspect the field device with the indicated MAC id, Check ErrorEvent Diagnoses |
255 | Error inside Device | Check Master Parameter, Check ErrorEvent Diagnoses |
Error Code | Description | Troubleshooting |
|---|---|---|
57 | Duplicate MAC Id detected | Check the addresses of the field devices, change Masters MAC Id |
58 | Master Config Error, download error of Master parameter | Contact technical support |
212 | Failure in reading masters data base | Contact technical support |
Error Code | Description | Troubleshooting |
|---|---|---|
30 | device access timeout, device stopped communicating | Inspect the field device, verify connections, check cabling |
32 | Device rejects access with unknown error code | Check IO features of the device, check explicite access to device, check object class, instance, and attribute id |
35 | Device responses in allocation process with connection error | Check IO features of the device, check explicite access to device, check object class, instance, and attribute id |
36 | Produced connection length is different to the configured one | Check number of Bytes to be produced by the device, check devices IO configuration |
37 | Consumed connection length is different to the configured one | Check number of Bytes to be consumed by the device, check devices IO configuration |
38 | Device service response telegram unknown | Contact technical support of the device manufacturer |
39 | Connection already in Request | Check cabling, inspect device, Master is not able to set up a connection to the device |
40 | Number of CAN-message data bytes in read produced or consumed size response not matches expected one | Contact technical support of the device manufacturer |
41 | Predefined Master- / Slave Connection Set already exists | Check number of Masters connected to the network, device my already in use by another master |
42 | Polling IO data length is different to the configured one | Check number of Bytes to be produced by the field device, check field devices IO configuration, contact technical support of the device manufacturer |
43 | Sequence Error in fragmented polling IO transmission | Inspect device, contact technical support of the device manufacturer |
44 | Fragment Error in fragmented pollingIO transmission | Inspect device, contact technical support of the device manufacturer |
45 | Sequence Error in fragmented polling IO transmission | Inspect device, contact technical support of the device manufacturer |
46 | Polling IO data length is different to the configured one | Check number of Bytes to be produced by the device, check devices IO configuration, contact technical support of the device manufacturer |
47 | Sequence Error in fragmented Change of State / Cyclic IO transmission | Inspect device, contact technical support of the device manufacturer |
48 | Sequence Error in fragmented Change of State / Cyclic IO transmission | Inspect device, contact technical support of the device manufacturer |
49 | Sequence Error in fragmented Change of State IO transmission | Inspect device, contact technical support of the device manufacturer |
50 | Change of State / Cyclic IO data length is different to the configured one | Check number of Bytes to be produced by the device, check devices IO configuration, contact technical support of the device manufacturer |