RS Networx For Device Net

[trobertd]

I am trying to get new eds files using RS Networx for Device Net, but it keeps telling me that RSLinx is not configured right. I have went over and over my Linx configuration and can't find any obvious issues. But in short I can't go online with it to see all the connected nodes on my 1756 device net scanner module. I have about 30 1799 imbedded I/O cards controlling zones for conveyors. I just need any pointers, help, and a clue to try and get this thing going.

 

[jde777]

Where did you get the new EDS files? Did you register them via start>>progams>>rockwell software>>rslinx>>tools>>eds hardward installation tool?

Once registered then reboot pc.

What version of rslinx are you using and version of networx?

I also would go to windows explorer then to c:\program files\rockwell software\rslinx and locate the file Install.log/ open this up in notepad and look for any failed or unsuccessfull entries. If there are then most likely uninstall re-install rslinx.

Is you path to devicenet pc>>ethernet>>backplane>dnb>devicenet?
If so when you browse down to the dnb does it have a "plus" sign next to it?

 

[trobertd]

I am running Linx ver 2.51, and RSNetworx ver 8.00.01. I got these EDS files from our installer. I work at a big .com, and we have a really nice warehouse, but my weakness is really RSNetworx, I am comfortable with 5000 no problem, but I just can't get Networx to cooperate with me. I got the EDS files from the installer they left us a high end laptop, with RS Logix, and everything installed.

But when I am in RS linx, through eterhnet, then down to device net scanner, then drop down device net, it just shows the device net card at address 00, but doesn't show all the 30+ nodes that are in it's scan list.

I will keep looking for that tool, it is not in my start menu items, I will look around in program files through all the Rockwell stuff. Thanks again jde777.

 

[controlsdude]

the obvious thing that you point out this statement

"But when I am in RS linx, through eterhnet, then down to device net scanner, then drop down device net, it just shows the device net card at address 00, but doesn't show all the 30+ nodes that are in it's scan list."

I believe the issue is that the the PLC is in RUN mode and the devicenet network is busy, so what happens is that it will not let you browse the network due to the bandwidth restrictions.

I remember on the SLC500 there was a setting on the M1 M2 settings that when you increased these file sizes that it would let you browse the network when the processor was in Run Mode. Otherwise all that you saw was the devicenet card and not the the rest of the nodes.

My suggestion is during downtime, put the plc in program mode and then you should be able to browse the network. I am not aware presently that there is a setting that needs to change on the Devicenet card for RSLogix5000 as there was with SLC500.

Also, have you verified that your firmware, software, eds files are at the right level as stated above?

This is shown on the AB website, "Get Support Now" then go to the Download, and then Flash Firmware Updates. Look here to make sure that the firmware matches the correct release level with the software.
RSLogix5000 Firmware Updates

Also, get online with the knowledgebase on AB website and ask the same question.

 

[controlsdude]

This is what I was talking about from the SLC500, pass thru feature. This came from the Devicenet Bible which you can download from AB website.

Pass Thru
RSNetWorx running on a PC talks to a communication port on the Processor. The commands/data are then passed through the processor to the SDN scanner who then passes them onto the DeviceNet network. This allows the DeviceNet network to be completely configured, monitored, etc. without the RSNetWorx PC being physically connected to the DeviceNet network.
RSlinx must contain the appropriate driver for the 1747-SDN and 1771-SDN for the feature to work. Also the SDN scanners must have a firmware revision that supports Pass Through. RSNetWorx, revision V2.22.18 (service 1) and RSLinx V2.1.176 (Service Pack 1) are the minimum revisions of software that work reliably.
1756-DNB supports ControlLogix Bridging, which is a feature comparable to Pass Through where RSNetWorx can be connected to the processor or other communication module and the DeviceNet network can be accessed.

 

[jde777]

I disagree controlsdude. Not a bandwidth issue here perhaps if it were the passthru. Passthru needs to have the processor toggled from prog to run and back to initiate the driver.

What does the dnb show on its display? if 91 or 78s then there is your problem.

Try the following.

Shut down rslinx and go to task manager and end the process rsobserv.exe.

Then go to windows explorer and c:\prog files\rockwell software\rs common and delete harmony.rsh and harmony.hrc

Reboot pc and try browsing again.

Were you able to locate the Install.log for Rslinx?? If so what were the results?

 

[trobertd]

Yeah I don't know about the passthrough being the issue. The DNB doens't show 91, or 78 on the display. Just Run, and ADR 00. I tried ending the RSLinx service, and shutting down rsobserv.exe, and then I deleted the harmony files, and then rebooted, still couldn't get it to work. I guess I am going to try and re-install Linx, I checked the install log and didn't see any errors. Still trying, the re-install is what the guys at AB suggested to me, so I guess I might see how that goes. Thanks for the feedback guys.

 

[trobertd]

I also have been onsite with our installer, and in Linx they were able to view those nodes in the list under device net. They have the same version of Linx and the same version of networx for device net that I do. Just thought I would add that.

 

[jde777]

When you highlight the A, Devicenet under the DNB what does it say at the top of RSLinx? Browsing Network or Browsing Node, with node #'s scrolling, if this one do they scrool fast or slow?

 

[controlsdude]

If the devicenet network was having issues such as a node problem or a network issue, the poster I believe probably could not browse the network. But there are no errors and the devicenet module shows everything ok. Then it is either a bandwidth issue during run or a Rslinx reinstall.

I have never took that route where support tells you to reinstall, that is the most lame thing to do that support always tells you. I would never reinstall based on their input about my rslinx.

I might delete a few files for harmony but never a reinstall.

I would double check the passthru feature that was mentioned above. Its worth looking into then reinstalling rslinx which never gets you anywhere except to waste time.

Also talk with your local distributor, they would be more familar with these issues then engineers like me who only installs and configures network, but usually never maintains the system.

 

[trobertd]

That is the issue when I have device net highlighted it doesn't say anything about browsing. And autobrowse is enabled. I tried deleting the harmony files, and then rebooting, but didn't seem to make a difference. I wish I knew more about configuring and installing, but I am more of the maintainer than anything. But I guess that is why I am here getting advice from the pros. Thanks again guys, I didn't figure that a re-install would do much good, but at this point I didn't know what else to try. I am not going to waste my time though. Thanks again.

 

[jde777]

The install.log did not indicate any failed ocx or dll's? Normally that would be the case in the situation you are seeing. The uninstall/reinstall of linx may be the next step.

One other thing are you using the ethernet devices driver or ethip?

Use the eth-1 (ethernet devices) and if configured already the delete it and recreate. What firmware rev is the DNB?

 

[trobertd]

The revision on the DNB is 7.1. I am using an ethernet driver, not ethip. And the log didn't indicate any failures what so ever. I thought that it would. I looked over it like 3 times, and didn't see anything that failed. I might try the re-install, but I just don't think it will help.

 

[trobertd]

You know what. I mis-spoke on that driver. I do believe that it is ethip. Sorry about that.

 

[controlsdude]

RSLinx 2.51 and 1756-DBN should support passthru where you can browse by RSLinx. I would use the ehternet driver. I have found the ethernetip driver to be very inconsistant and sometimes it works and other times it does not.

Did you talk with your local distributor about this issue?

What does the oem say about this issue?

Have you tried putting the processor in program and try to browse the network by rslinx?

There might be some setting on the DBN that has created a bandwidth issue. I am probably unaware of it I am sure.

Look at these two settings on the 1756-DNB module under RSNetworx

Interscan Delay = ? msec
Foreground to Background Poll Ratio = ?
Expected Packet Rate = ?

If these are set to a low setting this might be the reason you can not browse the network, not enough time or bandwidth to view it. I would get on the phone with the local distributor and see what they say. They can call Rockwell for you and get you an answer if you do not have the support contract with Rockwell. Do not change these settings unless the Rockwell guy has told you to do so, otherwise you might crash your network.

 

[jde777]

Trobertd


Try shutting down any antivirus/firewall especially if mcafee. And then reboot with these shut down and not restarting on reboot. If it does not say "browsing node" or "browsing network" still then uninstall 2.51 and reinstall 2.52.

Controlsdude why on earth would he want to connect passthru when he has an enbt in the rack to go enet>>backplane>>dnet????

The passthru driver was specifically created for the SLC line of processors because you cannot browse across the backplane. It is a slow drive that is not rec0mmended for configuring networks and just offers a way to get on dnet if you have no other interface.

 

[controlsdude]

jde

I do not know what your problem with me, but let me explain it to you.

Passthru as defined by the 1756-dnb is done in the firmware and supported by the later releases of RSLinx 2.2 and later.

I brought up the slc as a history of passthru for the devicenet scanner.

 

[trobertd]

Hey jde, I tried the firewall thing, still nothing. The lowest level it is letting you scan is the backplane itself for the control panel. Once you get to the level of the DNB it will not browse anything. I have a local controls friend of mine coming to try a few things, I will let everyone know how that goes. For some reason his seems to work on this network, and mine doesn't. He was part of the team that built the system. Once he sheds some light on it, I will post my findings if I am able to resolve it.

 

[jde777]

Trobertd

One last thing. You see the backplane then the dnb in the chasis right. Does the dnb infact have a plus sign next to it?if not the re-register the eds file for the 7.x dnb reboot and re-try.

Controls, no problem with you maybe we are mis-interpreting what passthru in terms of devicenet is. What it is is a driver specifically designed in the firmware of and SLC and SDN to allow people to be able to get online to dnet when no other means are available.
This however does not apply in any way to the control logix line because the backplane browse is built in to firmware AND hardware, com lines across the backplane.

So when you are talking about using passthru with a CLX processor it make no sense. Sorry if I offended you did not mean to.