When you have a question about process automation that needs a short answer, let us know with #WishIknew and @Visaya! We’ll reply with a #WishIknew post. It’ll give a quick explanation, then some related articles, videos, or reviews if you want to know more.
I wish I knew how to deal with DeviceNet error codes!
You can deal with DeviceNet error codes in two ways, and you can use either for corrective or preventive maintenance.
Way Number 1: You can find specific tools for the DeviceNet network from various vendors, such as NetAlert for DeviceNet, DeviceNet Detective 2 and others. This is probably the easiest way for most users.
Way Number 2: You can use a simple multimeter to verify your network. This way will require a bit more knowledge, but you can still do it.
Now, let’s talk about the data you’ll collect. If you start getting DeviceNet error codes but have a tool to verify your network, then you can get the following:
- Errors – The tool can measure errors and show relevant data for easy analysis, such as minimum or maximum rate and total errors. You can also identify and find the errors by nodes.
- Traffic – Studying the traffic messages (bandwidth by errors, bus frames per second, etc.) can tell you if you have too many devices on the same network. Then you can plan to move them to other networks to reduce the data volume.
- Voltage – You should check this in the field where you have your device installed. Measuring the peak-to-peak value or minimum and maximum may point the way to the problem.
You can get other types of data with DeviceNet analyzer tools or multimeters, such as shield voltage, a voltage differential between recessive and dominant, and so on. Somewhere in all this data, you should find your answer.
On the right, you can find some DeviceNet analyzers and multimeters. If you need to get one or just want to upgrade, then check them out and see which looks best for your needs.