1747-SDN DNET with SM-Devicenet issue

jj4parker

Member
Join Date
Oct 2006
Location
Thailand
Posts
15
I met the issue on the configuration of SM-Devicenet to 1747-SDN (c. I have only 1 drive (Unidrive SP with devicenet) that is connected to the network.

The problem is that the 1747-SDN always shows error code 79 and flashing red on Module status (net channel indicator is "Off"

When I tried to unplug the terminal at SM-Devicenet side, the 1747-SDN show code 01 --> 75 --> 63 --> 78 and Flashing red @ Module and Flashing green @ Net channel.

I've checked the configuration both side and the results are below;

1747 - SDN (on RSNetworx)
- Address : 01
- Speed: 500k

SM-Devicenet
- Address : 63
- Speed : 500k ( as parameteer 17.04 = 2)

On RSNetworx, the device from SM-Devicenet never exists. Only 1747 scanner appears.

One more thing, I cannot change speed of the SM-Devicenet because whenever I 've changed the drive will trip "SL3.ER" and the Fieldbus diagnostics would show "Configuration error" (parameter 17.06 = -3). This occured even I disconnect the DNET cable at 1747-SDN or changed the speed of 1747-SDN to 125k.

I also tried to restore the default values both side and still the same problem.

I've checked the cable many times and confirmed that it looks OK. Power supply is 23.9 V. CAN H to V- is 4.4 and CAN L to V- is 3.1. and 121 ohms resistors at both ends

Would you please help suggest what I miss or should try more.

Thanks a lot.

PS: On RSlinx I've got the driver diags as attached picture
 
The error code is telling you that node 1 is error 75 (no network traffic) and node 63 is in error 78 (device in scanlist does not exist). We need to know what error codes you get when everything is hooked up.

DNET_TECHBIBLE_3_14_2007.PPT is a good document for DeviceNet in general written by Dr. DNet. I tried attaching it, but was too large. Maybe you can search the web for it.
 
Sounds like you need to get the EDS file for the Unidrive SP device, build a network in RSNetworx, configure the scan list and download it to the SDN card.
 
jstolaruk said:
Sounds like you need to get the EDS file for the Unidrive SP device, build a network in RSNetworx, configure the scan list and download it to the SDN card.

Actually, it sounds like once upon a time, the device was in the scanlist. Hence, the error 63/78. That means that the scanner card has a device with node 63 configured in it, but it is unable to locate it on the network. So, it sounds to me like either a physical media problem, or a device problem.

To the OP, you said that device 63 doesn't show up. Do you mean in the online scan or offline configuration? I would expect it not to show up in the online scan because of the error you are receiving. The scanner module can't find it either. Go in the offline configuration mode and see if you have a device 63 and whether it has been dropped into the scan list. If it has, then the issue is with your device or the devicenet link itself.

One other thing to check too. I'm not familiar with this particular drive, but I've seen some get the addressing scheme wrong. Devicenet is a decimal addressing scheme, so make sure that the address you are setting in the SP is not 63 octal, but 63 decimal.
 
Last edited:
Firstly, thank you all a lot.

gmferg: I've downloaded it and it's good to read. Thanks.

The error code always shows 79 when the PLC and Drive got the power.

jstolaruk: I have got the EDS of Unidrive SP and ever installed it into network sucessfully in another project.

robertme: Once upon a time, it'd ever worked since after I turned off the power for 3 months. I think that the Scanner is working well but SM-Devicenet (Unidrive SP) may be a problem but I don't know.

The device 63 doesn't show when I scan in the online mode. In the scan list, there is 63 device in the scanner.

Thanks again to all.

I'm trying to contact specialist of this kind of drive to help.

However, any suggestions are still welcome.
 
My RSNetworx version is 8.00.01

Thanks.


Today I appoint one guy to help on phone, I will update you all after.


Appreciate your help.
 
jj4parker said:
My RSNetworx version is 8.00.01

Thanks.


Today I appoint one guy to help on phone, I will update you all after.


Appreciate your help.

Examining your DNT file, the scanlist for the SDN does not have the drive added to it; the scanlist is empty. The SDN card is just sitting there idle waiting for something to do.
 
jstolaruk said:
Examining your DNT file, the scanlist for the SDN does not have the drive added to it; the scanlist is empty. The SDN card is just sitting there idle waiting for something to do.

Yeah, shows up empty for me too.
 
jj4parker said:
Sorry I posted a wrong one, because I've tried so many ways.

Below is the right one.

thanks. I would probably enable ADR but I don't think that is the problem.

I noticed that the Unidrive has the capacbility of 4 in and 4 out of polled I/O words, yet the scanner is configured for 56 in and 56 out so it doesn't match. Where does the extended I/O space come from?

One last thing, can you move the card from slot 19 to something closer to the CPU? Like in the same physical rack? I may not be accurate on this but I thought I recall reading a note on this from A-B that communication modules are best placed close to the CPU. At least in the systems I design, interface modules always get priority on the first couple of slots.
 
jstolaruk said:
thanks. I would probably enable ADR but I don't think that is the problem.

I noticed that the Unidrive has the capacbility of 4 in and 4 out of polled I/O words, yet the scanner is configured for 56 in and 56 out so it doesn't match. Where does the extended I/O space come from?

One last thing, can you move the card from slot 19 to something closer to the CPU? Like in the same physical rack? I may not be accurate on this but I thought I recall reading a note on this from A-B that communication modules are best placed close to the CPU. At least in the systems I design, interface modules always get priority on the first couple of slots.

According to the SP Unidrive DeviceNet manual (sec 6.2), 28 Words In and Out are the max allowable to configure for a total of 56, so I assume that's where they come from. The 4/4 is the default from the EDS but can be reconfigured as done in the DNT file.

Here's the manual: http://www.leroy-somer.com/documentation_pdf/notices_pdf/3935a_GuideSMDeviceNet_en.pdf

I would assume that you've gone through the above manual step-by-step for the DN quick setup? It might be worth defaulting everything and restart again. Perhaps something got corrupted somewhere.

Also, when you get the SL3.Er, what error code are you getting in Pr MM.50?
 
Last edited:
Hi, just back update that the network is Ok now.

I've ordered the new card (Drive devicenet) and then reconfigured it. The problem is due to the broken card.

Thanks everyone.
 
SL3.er

Dear Sir
We changed the bearing servo motor.After re-fixing the motor we connected to the drive(Unidrive SP,resolver type) it shows SL3.er error.Please guide me further steps.

By
Thiru.S
 

Similar Topics

Hello everyone. Working on a small project. We are trying to use (/ get rid of) old hardware we have lying around. I am trying to get an old 2.04...
Replies
0
Views
1,458
We are in the process of upgrading a controls system. The existing system is a SLC500 with some IO cards and a 1747-SDN module communicating to a...
Replies
5
Views
564
One of our running machine's DeviceNet Module (1747-SDN) had malfunctioned. So, we replaced it with a new one from spares. We maintained the...
Replies
4
Views
3,092
I have a 1398-DDM-009X-DN that was talking to a 1747-SDN in a rack with a SLC 5/05. Recently, after a download of new parameters to the servo...
Replies
8
Views
3,133
Good Morning , After all these years , I still can't wrap my head around DeviceNet :( . I have RS Networx / DeviceNet. I would like to...
Replies
18
Views
5,185
Back
Top Bottom