DeviceNet problem

We have just upgraded our KRC2 to version 5.2.12 HF5. Everything is working, apart from the DeviceNet. It is giving an error "6503 Configuration Error I/O DN2DRV"

Our IOSYS.INI file includes :-

[DRIVERS]
DEVNET=2,dnInit,dn2drv.o

[DEVNET]
;------- Inputs ---------
INB0=10,0,x2
;------- Outputs --------
OUTB0=10,0,x2

and DEVNET.INI is
[krc]
debug=0
baudrate=500

[1]
macid=10

The MACID of the DeviceNet module (Beckhoff BK5200) is definitely set to 10 on the DIP switches, and the baud rate is set to 500.

The only difference between this KRC2 and our other KRC2 is that the DeviceNet connector is in a different place on the PC. It appears that this one is on an ISA card - would that cause the problem?

Any ideas ?

Problem is, I bought a robot from someone who didnt give me all the information

The MFC card is in the PC and has DeviceNet connector X801 and RJ-45 X804. X801 was pre-wired to a board A30 X943.1 where there are three DeviceNet connectors, .1 .2 and .3

I have wired X943.2 to my Beckhoff BK5200 using a Beckhoff ZS1052-3000 connector (which has a switchable Termination Resistor, set to ON.)

The top LED on the Beckhoff unit shows RUN always (means Status is OK). The Connect LED flashes first (means Ready and waiting for Communication) and then stays always on (means Assigned and OK). I have a new spare BK5200 unit, and I tried this but it made no difference.

Someone else told me to run dnShow in Telnet, and this is what it gave :-

DN2DRV Version 1.22.5.0
Scanner Enable running
Scanner State OK
CAN Errors 0
CAN Overflow 0
SystemTime -86674677
BaudRate 500 KBaud
[00]KRC State 00 Master none
I:
O:

[10] Warn 0 State 30:30 running online
I: 00 00 00
O: 00 00

Value = 1 = 0x1

Does that help at all ?

There is 24V at the MultiPowerTap A30, and also at the Beckhoff connector.

ZS1052-3000 is http://www.beckhoff.com/german/busterm/zs10xx.htm It has incoming and outgoing connections, and the cable is definitely wired to the incoming side.

When installing 5.2.12, it is always a good idea to select MFC2 driver instead of MFC1 driver. This REALLY helps when trying to work with DeviceNet

The way I found the problem in the end was to look at number of Network Connections available in Win XPe. Even though I have RJ-45 option on the MFC card, it did not have a Network Connection for me to use (other than VxWorks) so I was not able to connect to our network. This set me thinking about which driver I had chosen when installing . . .

I have just done a complete reinstall of XPe and 5.2.12, selected MFC2 ( ) driver and it worked first time

Very very

Many thanks for your help LindePaul