Configuring LPDN Scanner

[Ed_Gein67]

Hi guys, I've been trying to configure a LPDN scanner and I noticed that the KUKA manual does not explain very well what all the instructions of the ini files do. Does anyone have any kind of documentation, os does anyone know what every parameter does?

Thank You For Your Attention.

[Jim Tyrer]

I would go further and say that Kuka English documentation sucks.
Hope this helps.
JimT

[Jack_Kuka]

If you have any questions, you just ask me.
I can maybe you respond.
I managed to configure my card LPDN.
I can maybe help you.

Jack

[SkyeFire]

This would be an LPDN DeviceNet scanner card, correct?

One of the best places to look is actually the notes in the ini files, particularly the IOSYS.INI file and the DNSCxCO.INI and DNSCxSL.INI files.

A KRC1/2 controller can have up to 3 LPDN dual-channel DeviceNet cards, for a total of six channels.  Each channel has two setup files, and a seperate driver activation line in IOSYS.INI. 

The DNSCxCO file controls how the channel is set up: if it is a master or slave, what baud rate it uses, whether the error logging is on or off.  In this file, setting the MAC ID to 0 makes the LPDN card act as a network master on that channel.  Any other setting makes the channel a slave.  Any LPDN card channel can be set to master or slave in any combination: two masters, two slaves, one each, whatever.

The DNSCxSL.INI file is the slave scanlist.  If the channel is configured as a slave, you still have to have one entry in this file, for the channel itself, with the LPDN's vendor ID, Device type, etc, and the number of I/O bytes produced/consumed on the poll line.  The MAC ID for this single entry should match the MAC ID set in the DNSCxCO file.
On the other hand, if the channel is acting as a network master to another device(s), then the DNSCxSL file should contain an entry for each slave node that the LPDN will be a master of.  Each slave block entry begins with a number in brackets, like this:  [1]
This number is how each slave entry in the file is separated from the other entries.  These must be numbered in order, but the good news is that the order of the MAC IDs is not important. 
Inside each entry, there needs to be a MAC ID, Vendor ID, Product Type, Product Code, and a number of bytes for Polled Input and Output data.  All these values should be in the EDS files provided for each slave device by the device's manufacturer. 

After getting the DNSC files set up, you just need to map the I/O inside IOSYS.INI like you would for any other IO system, and make sure to uncomment the DNSC1=12,dnsc1Init,dnsc1drv.o line (or DNSC2,3,4, etc) that should already be present in your IOSYS.INI file.  These days, KUKA installs all the driver activation lines in IOSYS.INI, and has them commented out.  Just remove the semicolon from the beginning of the line to activate the channel: DNSC1 activates channel 1, DNSC2 channel 2, etc.  If you have multiple LPDN cards, figuring out which channels are on which cards can be a pain -- I recommend activating each channel one at a time and troubleshooting them separately.  It saves headaches.