ControlLogix and Devicenet

I am preping for an upgrade of our IFM ASi bus gatways
that sit on a Devicenet string. I have 1 set up on a test rig
in my office. Everything is configured, EDS is registered.
I can see it when I browse with RSnetworx. I am also seeing
data change in the PLC from the I/O I have installed.
The only issue I see at present is when I try to up/down-load
the parameters I get an EDS:2011 error.
I have tried this with the DNB in run and idle modes
and with the IFM AC1029 in protected and config modes.
Any input would be much appreciated

"9/27/2013 11:59:45","EDS :2011","Address 06: Communication Error(0xC) 'Error response received: [0x0416, 0x0000]. Object does not exist.', SCIA(0xE, 0x64, 0x1, 0x64), Param1"

Post the EDS file or a link to the EDS file.

I suspect that RSNetworx is telling you the truth: it's trying to read a Parameter object out of the device, and the device responding with a message saying the object doesn't exist.

Class 0x64 is a Vendor-specific class, so the IFM manual or EDS is going to have to describe it.

Here is about 3/4 of the EDS file

$ DeviceNet Manager Generated Electronic Data Sheet
[File]
DescText = "";
CreateDate = 03-17-98;
CreateTime = 13:10:39;
ModDate = 03-17-98;
ModTime = 13:10:39;
Revision = 1.0;
[Device]
VendCode = 322; $ Vendor Code
ProdType = 12; $ Product Type
ProdCode = 1008; $ Product Code
MajRev = 3; $ Major Rev
MinRev = 1; $ Minor Rev
VendName = "ifm efector inc.";
ProdTypeStr = "Communication Adapter";
ProdName = "ASI-DeviceNet-Controller";
Catalog = "AC1008";
[IO_Info]
Default = 0X000F;
PollInfo = 0X000F, 1, 1;
StrobeInfo = 0X000F, 2, 2;
CosInfo = 0X000F, 3, 3;
Input1 = 2;
Input2 = 2;
Input3 = 2;
Output1 = 2;
Output2 = 2;
Output3 = 2;

[ParamClass]
MaxInst=10;
Descriptor=0;
CfgAssembly=0;

[Params]
$ ****************************************************************************
$ * Parameter Instance #1: IO Length ASI Master 1
$ ****************************************************************************
Param1=
0, $ parameter value slot
6, "20 64 24 01 30 64", $ link size and path
0x0020, $ descriptor (Mon)
8, 1, $ USINT, 1 bytes
"IO Length ASI Master 1",$ parameter name
"Bytes", $ units string
"Length of ASI Master 1 Data Block within IO Messages",
0, 16, 1, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision

$ ****************************************************************************
$ * Parameter Instance #2: IO Length SPS
$ ****************************************************************************
Param2=
0, $ parameter value slot
6, "20 64 24 01 30 6A", $ link size and path
0x0020, $ descriptor (Mon)
8, 1, $ USINT, 1 bytes
"IO Length pre-processed data", $ parameter name
"Bytes", $ units string
"Length of pre-processed Data Block within IO Messages",
0, 32, 1, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision

$ ****************************************************************************
$ * Parameter Instance #3: Poll/COS Rx Length
$ ****************************************************************************
Param3=
0, $ parameter value slot
6, "20 64 24 01 30 6D", $ link size and path
0x0030, $ descriptor (Mon,RO)
8, 1, $ USINT, 1 bytes
"Poll/COS Rx Length", $ parameter name
"Bytes", $ units string
"Poll / Change of State/Cyclic Receive Message Length",
0, 16, 3, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision

$ ****************************************************************************
$ * Parameter Instance #4: Poll Tx Length
$ ****************************************************************************
Param4=
0, $ parameter value slot
6, "20 64 24 01 30 6E", $ link size and path
0x0030, $ descriptor (Mon,RO)
8, 1, $ USINT, 1 bytes
"Poll Tx Length", $ parameter name
"Bytes", $ units string
"Poll Transmitt Message Length",
0, 16, 3, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision

$ ****************************************************************************
$ * Parameter Instance #5: COS/Cyclic Tx Length
$ ****************************************************************************
Param5=
0, $ parameter value slot
6, "20 64 24 01 30 6F", $ link size and path
0x0030, $ descriptor (Mon,RO)
8, 1, $ USINT, 1 bytes
"COS/Cyclic Tx Length", $ parameter name
"Bytes", $ units string
"Change of State/Cyclic Transmitt Message Length",
0, 16, 3, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision
$ ****************************************************************************
$ * Parameter Instance #6: COS/Cyclic Ack. Length
$ ****************************************************************************
Param6=
0, $ parameter value slot
6, "20 64 24 01 30 70", $ link size and path
0x0030, $ descriptor (Mon,RO)
8, 1, $ USINT, 1 bytes
"COS/Cyclic Ack. Length", $ parameter name
"Bytes", $ units string
"Change of State/Cyclic Acknowledge Message Length",
0, 16, 3, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision
$ ****************************************************************************
$ * Parameter Instance #7: Bit Strobe Tx Length
$ ****************************************************************************
Param7=
0, $ parameter value slot
6, "20 64 24 01 30 71", $ link size and path
0x0030, $ descriptor (Mon,RO)
8, 1, $ USINT, 1 bytes
"Bit Strobe Tx Length", $ parameter name
"Bytes", $ units string
"Bit Strobe Transmitt Message Lenght",
0, 8, 1, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision

$ ****************************************************************************
$ * Parameter Instance #8: IO Error Action
$ ****************************************************************************
Param8=
0, $ parameter value slot
6, "20 64 24 01 30 73", $ link size and path
0x0022, $ descriptor (MON,ENUM)
4, 1, $ BOOL, 1 bytes
"IO Error Action", $ parameter name
"", $ units string
"Behaviour of the ASI-Output-Data and pre-processed input data if the IO data is not valid",
0, 1, 1, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision


$ ****************************************************************************
$ * Parameter Instance #9: MAC ID
$ ****************************************************************************
Param9=
0, $ parameter value slot
6, "20 03 24 01 30 01", $ link size and path
0x0020, $ descriptor (Mon)
8, 1, $ USINT, 1 bytes
"Controller Address", $ parameter name
"MAC ID", $ units string
"",
0, 63, 63, $ min, max, default
1, 1, 1, 0, $ mult, div, base, offset scaling
0, 0, 0, 0, 0 ; $ scaling links and precision

It got displayed a little different by the editor but all the info is there.

Christoph said:

The only issue I see at present is when I try to up/down-load the parameters I get an EDS:2011 error.

Click to expand...

There's a known anomaly with RSNetworx for DeviceNet v11.0 not uploading/downloading to devices if you have installed RSLogix 5000 v20.01, or Add-On Profiles (AOP) Core 8.03.

AB KnowledgeBase said:

Articles: 509671; 509535; 502282

509671 - RSNetWorx for DeviceNet error EDS:2011

Problem:

After installing RSLogix5000 version 20, RSNetWorx for DeviceNet shows:

Unable to go online, upload or download to some safety devices

An error similar to this will be shown in RSNetWorx for DeviceNet:

EDS:2011 Address xx: Communication Error (0xC) 'Error response received: [0x416]. Object does not exist, SCIA (0x10,0x4,0x3003,0x0) Assem864

Click to expand...

Are you using RSNetWorx for DeviceNet v11.0?
Have you recently installed RSLogix 5000 v20.01?
Have you added any AOPs lately?

If you think this applies to you, look at KB Article 502282.

Download the the zipped "RSEds.dll" file and extract it into your "RSCommon" folder at:

32-bit OS
C:\Program Files\Rockwell Software\RSCommon

OR

64-bit OS
C:\Program Files x86\Rockwell Software\RSCommon

Make sure you overwrite the existing "RSEds.dll" file.

Then reboot.

G.

Wow, good catch, Geospark !

The RA document suggests it's a problem specific to some Safety devices, but it's entirely possible it applies to this device too.

You can probably troubleshoot the basic connectivity by using the SCIA Editor tool (right-click on the device in the RSNetworx browse view) to attempt to read Class 0x04, Instance 0x01, Attribute 0x64.

Yes Ken,

I noticed the reference to safety devices as well.

Also, even if the minor software versions that Christoph is using are slightly off from the KB ones, I'd still replace that file. It cannot hurt as I know they recommend any RSNetWorx v11 users to do so.

The fact the only issue is up/downloading and no other connectivity issues appear to be present suggests this is highly likely to be the cause.

Hopefully!

G.

Thanks for the info. I will get back with you all on Monday.

Hi

I had this issue but it was with some I/o hanging off a smart guard 600.
It was after I installed ver 20. I also found that kb file and installed the zip file and it messed up my networks even more. I had to reinstall logix ver 20 as it would not open any more. I programmer I work with also had some trouble but only with his networks after he installed the zip file.



Donnchadh

That doesn't sound good Donnchadh.

It'd be wiser so to copy that file out before over-writing it in case you need to put it back. I'm not sure if it is that simple to revert though?

Another fix for this problem is to upgrade RSL5K v20.01. This supposedly does the same thing.

G.

Another twist. I can upload or download to the same type devices in a working system out in the plant. same EDS
But these are IFM AC1008 and I have the AC1029 on the test stand. (Drop in replacement for the AC1008)

I downloaded the patch now I'm really hosed. Networx won't browse any more.
Will have to do a delete and a reload. Down loaded version 11 and it wants to
register with Factorytalk. We are not ready for that step yet. So back to V10.

Christoph,

I appreciate you're trying to get it sorted quickly, but we're trying to help. You're sort of jumping ahead without us.

Are you saying you were running RSNetWorx v10?
And swapped in the RSEds.dll patched file?

You never answered my questions?

Geospark said:

Are you using RSNetWorx for DeviceNet v11.0?
Have you recently installed RSLogix 5000 v20.01?
Have you added any AOPs lately?

Click to expand...

Did you need to apply the RSEds.dll v4.2.0.1 patched file?

Did you save the original RSEds.dll file?

If so, did you try to copy back in the original file?

If you didn't save it, I have a copy of the original RSEds.dll v4.1.0.104 if you would like to revert back and see can you get RSNetWorx browsing again. It's 5MB, so if you want it, I can e-mail it to you if you private message me.

You may not need to re-install RSNetWorx at all, I hope. Unless you've already un-installed it?

G.

P.S. Donnchadh was this in anyway related to your problem?

KB Article: 506554

Sorry. I am on V10.01. The highest version of RS5k is V19. I did install the patch 502282. (Not good) Now I have reloaded V10.01 Networx for Devicenet. Basically the same issue as before. But now it shows a red - sign on the device and says:"10/1/2013 8:58:57","DNET:0013","The device at address 06 has experienced an identity communications error (80080005). Properties failed." and this:Communication Error(0xC) 'Error response received: [0x0416, 0x0000]. Object does not exist.', SCIA(0xE, 0x64, 0x1, 0x64), Param1"

Christoph,

Sorry for the late reply.

You may have corrupted your Harmony files while trying that patch and re-installing RSNetWorx, etc.

If you haven't gotten rid of the "DNET:0013..." error yet, I'd flush the driver configuration and let it refresh.

To do this follow the instructions here: 48241

If that works you'll at least be back to where you were.

G.