One big problem with devicenet is that if the signal is not clean, clean clean and/or if the power is not tightly regulated and/or if shield grounding is not absolutely perfect, Ken Roach View Public Profile Visit Ken Roach's homepage! The reason these values appear a little different than the ranges shown on the scope trace, is that the signals are switching, which slightly affects the DC value being read by Anyway, a Bus-Off condition can be cleared by cycling power on the slave. his comment is here
The time now is 09:26 PM. Register a new account Sign in Already have an account? When another device powers up on the network, it will send its own Duplicate MAC ID Check message, which the 1769-SDN will hear and acknowledge. I have to go home and dig up my handy DeviceNet quick ref manual to confirm. http://www.plctalk.net/qanda/showthread.php?t=12879
The problem is that you can't get anywhere near the Flex I/O adapters until the equipment is stopped and by that time everything is cool except the processor and the DNB Is this a new or existing machine? The CAN-H swings between 2.5 VDC (Recessive State) and 4.0 VDC (Dominant State) while the CAN-L swings between 1.5 VDC (Dominant State) and 2.5 VDC (Recessive State)Without a network master connected My best guess is that there is something unusual about your device's powerup behavior.
The total trunk line from scanner is only about 3 meters in length. Set address to something other than scanner.check you have 24Vdc on both scanner and node in the correct places.I found this somewhere years ago and it is good to know.##################It needs Sometimes those require a certain amount of network traffic. Devicenet Error Code 91 Being that the comms are over slip rings I think that when the equipment returns home due to gravity after the fault the comms are re-established (maybe?) and all is normal,
Share this post Link to post Share on other sites Ken Roach 85 Propeller Head MrPLC Member 85 2487 posts Posted 17 Aug 2006 Cycling the run mode of the Devicenet Scanner Error Codes Termination resistors are installed at both ends, measured 60.3 ohms across the Can_H and Can_L at the scanner. This can show up if there are no scanlist entries, or if there is a damaged receiver section of the CAN interface on the 1747-SDN. Thread Tools Display Modes February 9th, 2005, 10:22 AM #1 pickerel Member Join Date: Dec 2003 Location: London, Ont, Canada Posts: 26 AB DeviceNet Scanner Issue (1769-SDN) I'm having
Be happy. Bus Off Detected Devicenet If you're not already a member, consider joining. I currently do not have any network analysis software and hardware that I can use to get on the devicenet network to monitor communications. What is the device?
This board is for PLC Related Q&A ONLY. In this case there are no other devices powered up and the 1769-SDN just keeps sending its DUP MAC ID Check packets for a few seconds until it declares an Error Allen Bradley Devicenet Error Codes I'm using RSNetWorx version 5.00.00 (build 81) and scanner's firmware version is 2.2. Devicenet Error Code 78 If Can-H to V- and Can_L to V- are too low; less than 2.5 V dc and 2.0 V dc respectively the issue is probably a bad transceiver or bad wiring.
Share this post Link to post Share on other sites rwraley 0 Sparky MrPLC Member 0 94 posts So. this content Usually, another node on the network acknowleges the DUP MAC ID check packet right away, and the 1769-SDN can commence to opening connections to its I/O slaves. Any changes been made recently? Are the codes the same for Control logix devicenet modules? Devicenet Error Code 77
For some reason the scanner and slave device fail to establish communications with each other and I don't know why. Edited 16 Aug 2006 by pseudoquas Share this post Link to post Share on other sites Ken Roach 85 Propeller Head MrPLC Member 85 2487 posts Posted 16 Aug 2006 The trunkline cable's shield and drain are only connected to earth at one end, the scanner end. weblink Share this post Link to post Share on other sites rwraley 0 Sparky MrPLC Member 0 94 posts So.
California Posted 16 Aug 2006 Does anyone know off hand what the error code "F78" on the devicenet module indicates?. 1756 Dnb Error Code 78 Check for disconnected cables. When I request only one slave to be on and apply mains power to the device, the scanner reports the following error codes: first 79 (mentioned above), then 76 for node
I did some research in the Knowledgebase and the only thing I found was that the code indicates "Slave device in scan list table does not exist" but this is in Basically they maintain and develop the devicenet firmware for the devices. Error 78 means that the scanner has tried and failed to establish a connection to the corresponding slave device. 1756-dnb Error Codes This page served by Yesod4 in the beautiful Blackstone Valley of Massachusetts, the home of the American Industrial Revolution.Follow @c_com FortuneQ: What happens when four WASPs find themselves in the same
Sign in here. Share this post Link to post Share on other sites pseudoquas 1 Sparky MrPLC Member 1 37 posts US United States Posted 16 Aug 2006 (edited) I recall that the I'm surprised, though that you are not getting alternating error and node info on the scanner LED. 7X type errors I recall always refer to scan list node problems. check over here Usually Error 72 occurs first, indicating that an I/O connection has failed, followed several seconds later by Error # 78 when the scanner cannot re-establish communications.
A: A dinner party. To search the site, enter your search terms in the box labeled "search the site" and hit Enter.Some tips for better search results...Precede each search term with a "+", as follows:+Modbus Please read those terms and conditions carefully. Share this post Link to post Share on other sites TWControls 41 Industrial Sorcerer MrPLC Admin 41 4430 posts Gender: Male Roanoke, Virginia United States Posted 17 Aug 2006 Need
Try ouronline PLC Simulator- FREE. pickerel View Public Profile Find More Posts by pickerel Jump to Live PLC Question and Answer Forum Bookmarks Twitter Reddit Digg del.icio.us StumbleUpon Google « Previous Thread | Next Thread » On the 1756-DNB they are accompanied by "N#" for node number and "E#" for error number. California Posted 17 Aug 2006 (edited) The reason we have to cycle the processor is because the system monitors the devicenet status tags and when the error is detedted it shuts
When the 1769-SDN powers up, it will send "Duplicate MAC ID Check" messages onto the network. Do you have a network analysis software package of any kind ? The fun part is finding the offending node, especially if your plant electrical schematics do not indicate node numbers. This sounds about right since all the slave devices (10 in total) are powered down.
If you're not already a member, consider joining. Perhaps somebody has locked-out a DN remote rack somewhere, or locked-out a Drive. The processor is actually being faulted and that is why we need to cycle run mode. The only devices on the bad network are 2 flex I/O adapters(nodes 1 and 2).
Make sure that your module is connected to a valid network. You're going to have to get a good look at the 1756-DNB display when this happens. All rights reserved.Users of this site are benefiting from open source technologies, including Linux, PHP, MySQL and Apache. Find More Posts by Ken Roach February 10th, 2005, 01:21 PM #3 Ken Roach Lifetime Supporting Member + Moderator Join Date: Apr 2002 Location: Seattle, WA Posts: 12,733
You will have to match baud rate with each one. California Posted 17 Aug 2006 It jsut dawned on me why the panel view is fine there are two 1756-DNB,s in the rack and they are handling different parts of the