Converting 1769-SM2 from DeviceNet to Ethernet

[Big Brunsy]

So I have a system that is running on DeviceNet. We have been having nothing but problems with it for the last 3 years. I am trying to switch one node of Remote I/O from communicating with a 1769-ADN to a 1769-AENTR. I have never had to configure an SM2 before, and I thought I did everything correctly by reading the manuals.

There are 3 local 1769-SM2s and then 2 more in this remote rack. When I readdressed everything i copied the logic from the Local ones and just addressed to the remote ones. When I installed the new AENTR and downloaded the program all of the drives just either give a comm loss fault, or sit there and do nothing.

I have included both versions of the ACD file and the DNT file if someone wants to take a look and see what I did wrong, I would greatly appreciate it.

Files too big to attach. Can be found here..
https://drive.google.com/drive/folders/1E3Pjfx_Hhq3_e011iFle9TSxwYpTWgYX?usp=sharing

 

[Ken Roach]

It's one of the rare things that the DeviceNet software does better than Studio 5000... the configuration module profile for the 1769-SM2.

In your DNet configuration, it shows the three channels on each module configured for different numbers of slave drives:

Slot 1 Port 1: Drives 0-4
Slot 1 Port 2: Drives 0-4
Slot 1 Port 3: Drives 0-3

Slot 6 Port 1: Drives 0-3
Slot 6 Port 2: Drive 0
Slot 6 Port 3: Drive 0


In Studio 5000, there is no module profile that shows you the meaning of each Configuration word. So we have to go back to the user manuals and the example code, or copy the configuration values from similar modules as you did.

My reading is the Configuration element that describes the number of drives per port (DSI I/O Config) are elements [3], [17] and [31].

Let's compare them for all the 1769-SM2 modules in your system:

Local:4:C.Data[3] = 0x0004
Local:4:C.Data[17] =0x0004
Local:4:C.Data[31] =0x0000

Local:5:C.Data[3] = 0x0003
Local:5:C.Data[17] =0x0004
Local:5:C.Data[31] =0x0000

Local:6:C.Data[3] = 0x0003
Local:6:C.Data[17] =0x0003
Local:6:C.Data[31] =0x0004

Corrugation_RIO:1:C.Data[3] = 0x0004
Corrugation_RIO:1:C.Data[17] = 0x0004
Corrugation_RIO:1:C.Data[31] = 0x0000

Corrugation_RIO:1:C.Data[3] = 0x0003
Corrugation_RIO:1:C.Data[17] = 0x0000
Corrugation_RIO:1:C.Data[31] = 0x0000


The RA Knowledgebase has Answer ID # 502674 (Access Level: Everyone) that shows the values for these configuration words. From that document:

DSI I/O Config
Sets the number of this channel's drives that are used in Multi-Drive mode. Identifies the connections that would be attempted on a reset or power cycle.
Default: 0 = Drive 0
Values: 0 = Drive 0
1 = Drives 0…1
2 = Drives 0…2
3 = Drives 0…3
4 = Drives 0…4
5 = RTU Master
Type: Read/Write
Reset Required: Yes

The only one that looks wrong is Port 3 on the Slot 1 module, which should be 0x0003 instead of 0x0000.

Be sure to do a reset of the 1769-SM2 or its Adapter to get the Configuration data to be written to the module. It doesn't get sent every I/O scan like the Output data does.

 

[Big Brunsy]

Thank you very much Ken!! You're a life saver!
I bet I looked at that about 20 times and could never see that. I'll get it changed and try changing it over again Saturday!