KRC1 Device Net configuration

The content of the devnet.ini is more or less the same.

The big difference is the driver

- dndrv.o for Kuka System Software running under Win95

- dn2drv.o for Kuka System Software running under WinXPe (like KSS V5.6.9)

normally base system driver for Win95 systems most of the time are not compatible with base system driver for WinXPe systems (even if they have the same name)

If the complete CD is missing you could give KUKA the serial number of your robot and ask for a copy of the cd or at least for the dndrv.o for your system.

I have this error during config devicenet.

What could be wrong ?

you may want to change GUI language to English before taking screenshot... and resize the columns so message number is visible or show them individually.

Hi panic mode.

Im using Allan Bradley module with i/o's.

Ive got this errors in devnet.log

devnet.log 1

devnet.log 2

devnet.ini

iosys.ini

well, part that was not mentioned before is that you are using AB Point IO.

I have used PointIO with EIP, not the DeviceNet but as i remember they are not straight forward as most of the other products because they always needed to be configured. In case of 1734-AENT this was possible through web browser...

... and in case of DeviceNet version (1734-ADN) there is no Ethernet port, so you need to have RSNetWorx for DeviceNet to configure it or ... you will be stuck.

https://literature.rockwellautomation.com/idc/groups/lit…um002_-en-p.pdf

panic mode precious information for me as always

I don't even know how to do it

I will swap Io device for other vendor which is straight to connect, in meantime I will make huge step to be familiar with AB point IO.

Yes, I just went through this with that exact same AB module.

Bottom line: the I/O "slices" are all factory-configured for the same address on the 1734's backplane. That entire module (1734 plus the I/O slices) must be set up using RSLogix before it can be connected to a robot.

It also turns out that the default I/O modes are tricky -- you have to deliberately set them all to Polled. Strobe, Change Of State, and Cyclic are other options, but Polled is the only one I'm sure will work with a KRC's DN driver.

Also, I don't try reading code or errors off of photos. My eyes just aren't up to it anymore. Transcribe or copy&paste actual messages and log contents.

Skye thanks for reply.

Main errors in log are for interrupt and no ability to run instance. I've checked configuration devicenet on vss 5.4.7 hf4 and kss 5.4.11 same errors. I was wondering it could be problem with kss which originally doesn't work with mfc 3.02 but i run vss which works smoothly with mfc 3.02.

Now as You said I'm stuck with AB point IO.

Looking for Wago , Wago needs some special configuration or is straight ?

It's been a few years since I used Wago, but I recall it being fairly straightforward -- all polled, and as you add slices, the bus coupler increases the "size" of bytes in/out, which you can see using the 'dnwho' commands via Telnet. Wagos only got a bit odd if you started mixing analog and digital -- the ordering of the bytes on the bus was based on the I/O type, rather than the physical order of the slices.

SkyeFire nice to hear You.

The main problem is when I'm using command in run Telnetk 192.0.1.1 using dnWho command was not recognized

Functions in telnet must be used with exec for example: exec "dnWho"

The telnet commands changed a few times over different versions of KSS. Since this is a KRC1, it probably used the older type of the command, that did not use the "exec" prefix.

SkyeFire thanks for answer.

I was using docs where was

Pin 1 - 0V

.

Pin 5 -24V

I've swapped power supply and can_hi and can_low and it works.

this agrees with my experience. in most cases (by far) problem is the faulty wiring, not configuration...