DeviceNet new user

Chris K

Member
Join Date
Feb 2016
Location
North East
Posts
15
Hello,
I would like to say HELLO for all the users here as I am new to this forum and also to PLC world. I am learning AB controllers currently, and I would like to learn about DeviceNet. Where I can find some info about it such as typical connection schematics, programming and in general how they are working etc. Any help would be appreciate!
 
Your best option will be the manuals from Rockwell.

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/dnet-um004_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/dnet-um072_-en-p.pdf



On a side note, in a lighthearted jest, I personally would hope your curiosity stems from wanting to support existing equipment and not from wanting to implement the networks on new installations. I've only dealt with a few DeviceNet and ControlNet installations, and when they work, they work. But when they don't work, they are a bit of a headache.
 
Thanks Tharon, thats what I am getting from all the guys with experience. DeviceNet when they work, they work... :) I will take a look on those publications. And yes, its existing installation. Any other words of wisdom?
 
Last edited:
That's about it from me. I have one DeviceNet installation that I take care of. And I leave it be for the most part. A few years back I had to change an obsolete valve pack to a new one, and it was not too bad. And (I shouldn't say this) but since we've left it alone, it has behaved (Have to go find some wood now).

We have had to have a Rockwell specialist come in and troubleshoot network media issues. Our last one turned out to be a T-branch which was damaged internally and shorting the B channel to ground on occasion. The Tech was able to diagnose the problem using an oscilloscope. So you may want to invest in one if they'll let you. Handy little devices, but not exactly cheap.
 
Chris K:
I've been working with devicenet for almost 15 years, I have written a small course in SPANISH for my technicians, if you or anybody wants to have it just send me a PM with your email adsress.
 
That's about it from me. I have one DeviceNet installation that I take care of. And I leave it be for the most part. A few years back I had to change an obsolete valve pack to a new one, and it was not too bad. And (I shouldn't say this) but since we've left it alone, it has behaved (Have to go find some wood now).

We have had to have a Rockwell specialist come in and troubleshoot network media issues. Our last one turned out to be a T-branch which was damaged internally and shorting the B channel to ground on occasion. The Tech was able to diagnose the problem using an oscilloscope. So you may want to invest in one if they'll let you. Handy little devices, but not exactly cheap.

Yeah, I know, they are not cheap.... Thanks for input:beerchug:
 
Any other words of wisdom?

If it's working, don't f*** about with it!

If it's not working, check that you are using exactly the right power supplies, cabling, connectors, terminating resistors, network architecture, etc; stand on your left foot and face toward the nearest Rockwell office and pray to the gods of automation, and then just keep trying until something works. Then, once it's working, stop f***ing about with it!

In all seriousness, I once viewed part of the help file for a Rockwell DeviceNet application, and I kid you not, it basically said "if none of this works, just try it again until it does, DeviceNet is like that and it will probably work eventually if you keep trying."
 
stand on your left foot and face toward the nearest Rockwell office and pray to the gods of automation

And I will hear your lamentations.


In addition to the dry-as-Melville wiring guidelines book, I encourage you to download the DeviceNet Book of Knowledge, a giant collection of notes developed and maintained by RA Commercial Engineering.

It's in the RA Knowledgebase: Answer ID # 44883 (Access Level: Everyone).
 
dnet

I deal with tons of dnet. One location I maintain has over 50 networks. Ive been working with it for close to 20yrs. So Ive seen alot of interesting issues. When it works it works.
 

Similar Topics

We've run into an old system that we are upgrading which is still running Steeplechase with Citect using Devicenet to Wago. I had some experience...
Replies
4
Views
138
Sigh, DeviceNet noob... I have a 1756-L55, with a DeviceNet module, and 10 PF700 all commanded with DeviceNet. One of the PF700's blew up...
Replies
3
Views
128
Good day Forum Members I got a older Lincoln welder and hoping to make it work at our shop. Welder in question is the Lincoln Power Wave 455M...
Replies
4
Views
191
Hello Friends We have 10 Powerfocus 4000 with DeviceNet, We need to backup the configuration, the Powerfocus is detected but as unrecognized...
Replies
0
Views
102
Hello, I have a device with 68 words input. But one block on the Devicenet Scanner is only 61 words. I am trying to map this device to 2...
Replies
3
Views
523
Back
Top Bottom