Devicenet Configurator Software
To Configure a device net network one defenately needs RSNetworx software for Devicenet Configuration along with RSLINX. To configure a devicenet network one can either use 1784-PCD communication card or 1770-KFD (a RS232 To Devicenet Converter) available from Allen Bradley. Once network is configured ie. Perameter setting for devices are done and I/O addresses are included in Scanlist of 1747-SDN, Network is ready to be controlled by SLC or PLC. Any further clearificatons needed, please feel free to contact. THanks for posting here. I am having trouble getting my 1770-kfd to work and scan right with the 1771-sdn scanner card that I have installed on a plc 5 at school with the skits package number 3 for Devicenet.
Everytime I scan my network thru RsLinx I get different modules detected. I have ohm'd all my connection points on the flat cable and my network connection blocks. I am not sure about having to use a 9V power supply with the 1770-kfd converter either since a power supply did not come with it.
I am a bit short on the starter manuals that came with the kit for trouble shooting this system and need to find more information especially working with Windows 2000 operating system.Thanks Jim MayP.S. I am also to install a device net kit to a Slc 500/04 also.
Below are the steps I utilized to get my project going. In so doing I found that to configure a DeviceNet device in LV2012SP1, I do not need to manually type in the EDS file data. There is a tool for loading EDS files. This addressed questions I had in previous Forum posts: concering loading EDS files in LabView and concerning configuration of a DeviceNet network.Environement: Windows 7, 64bit processor. IndComm 2.2 Driver.
Devicenet Master
Labview 2012 SP1Beginning with LabView Example Project: 'Devicenet PXIPCI Basic.lvproj'Add a DeviceNet Master to a LabView Project. Within the Project: Right click on My Computer.
Devicenet Configurator Software
Select New. Select Target(s) and Device(s). Select 'Discover Existing Devices' option. Select the discovered device. Click 'OK' ( Note: In this case my Master is a NI-8532 PCI card)Add a DeviceNet Slave Device to a LabView Project. Right click on the newly added Master Device in the Project Tree. Select New.
.gif "Configurator")
Select Target(s) and Device(s). Select 'Discover Existing Devices'. Select the discovered device. Click OK. ( Note: In this case my Slave is a Festo CPX-FB11 block.)Load an EDS file for the slave device. Right Click on the Slave Device. Select 'datasheet.'
. Click Add Files. Navigate to the location of the EDS file. Select the file.
Click OK. In the left pane, expand the newly added Datasheet until you reach the node displaying the version.
Select the version. Click OK.Verify the EDS file and Device. Right Click on the Slave Device. Select Utilities. Select Online Test Panel.
Select the 'Device State' option in Category field on the left. On the right Select the Slave Device you wish to verify. Click 'Verify the Device'. Read the errors/warnings or lack thereof.In my case I had errors in my EDS file. Basically the slave device was not set to the correct number of Input/Output Bytes in the EDS file, i.e. Improper configuration. To correct these I had to edit the EDS file.Edit EDS FileTo Edit the EDS file I utilized which is a freeware, devicenet specific EDS editor from ODVA.I made my corrections and saved my EDS file.
(After backing up my original, of course).Remove Installed EDS file from Labview. Navigated to the following Location: C:ProgramDataNational InstrumentsNI-IndComm for DeviceNetDatasheet. Delete the Datasheet ( Note: There are more than just the one manually added datasheet. The additional EDS files come with the IndComm driver. Find the EDS File for the specific device you wish to replace and delete it).I restarted LabView.I went through the above steps again and loaded my new EDS file.I saved the project and exited LabView.I rebooted the computer and the slave device.I restarted the project and launched a VI.I was able to communicate with the device. Which is something I had not been able to previously accomplish.
And, in so doing I discovered how the device is talking and why each module did not display. (I have a standard EDS file for my block of devices as it appears LabView is not capable of a Modular system which requires an EDS file for each module. I could be incorrect on that last part though as it might be a setting on my actual device. But it is unecssary in my project.
So I did not look into it further.) Because I was using a standard EDS file, only the one single slave device showed, and thus the data for each module is in the stream of bytes returned over the DeviceNet network. Addressing each module is a matter of parsing the bits and bytes appropriately.Thank you,Tennessee Paul. We still use mainly NI PCI DNET master cards for our test fixtures, but we have already also some of the NI PCI-8532. BTW, you cannot mix the cards in the same PC.We never use EDS files. I am not sure if this is possible in your case, but you always scan the network using explicit messaging and figure out:.
available MAC IDs. slave input/output byte sizes. also some other things like device type, vendor, serial #, etc., but this is not relevant to the I/O connection.MAC ID and input/output byte size is sufficient to establish I/O connection via EasyIO Config.vi and read process data. Since DeviceNet follows the ODVA specification, I think that all DeviceNet slaves support Class 0x5, Instance 2, Attribute 7 and Attribute 8 which provide this information via explicit message connection and the Get Attribute VI.I am not sure if the same approach works on RT target with the NI 9882, but it works for sure on a PC with NI DeviceNet master card.