Replacing a VFD... DeviceNet Steps to match new/old controls (SLC 5/0...

1 of 5

http://www.plctalk.net/qanda/showthread.php?t=82692

You are not registered yet. Please click here to register!

This board is for PLC Related Q&A ONLY. Please DON'T use it for advertising, etc.
Try our online PLC Simulator- FREE. Click here now to try it.
---------->>>>>Get FREE PLC Programming Tips

New Here? Please read this important info!!!

PLCS.net - Interactive Q & A > PLCS.net - Interactive Q & A > LIVE PLC Questions And
Answers

Replacing a VFD... DeviceNet Steps to match new/old controls

(SLC 5/05)
Register

FAQ

Calendar

Downloads

PLC Reviews

User Name

Remember Me?

Password

PLCS.net Store

Today's Posts

Thread Tools

Search

Display Modes

October 10th, 2013, 03:32 PM

#1

AutomationTechBrian

Replacing a VFD... DeviceNet Steps to match new/old controls (SLC 5/05)

Member

My DeviceNet skills are rusty and weak... so of course, an old, obsolete Reliance
400 HP VFD goes down and we're looking at replacing it with a Yaskawa A1000.
...AND, of course we're under the gun and I'm the sole controls tech for this
plant.

Join Date: Jul 2013

Location: St. Cloud, MN
Posts: 37

I'm hoping to get an idea of the steps to take in changing the drives and
re-establishing the same DeviceNet connections with the SLC 5/05 ladder logic.
I'll be reviewing the DeviceNet manual tonight, but I remember being foggy
about how to even start this process. The good thing is that once I learn how to
do it, I'll be able to replace 8 more small drives on the machine.
Here are some details...
Old drive, GV3000/SE
New drive, Yaskawa A1000
PLC: AB SLC 5/05
I do own: RSNetworx for DeviceNet
1770 KFD
My understanding of DeviceNet with the SLC is that RSNetworx writes addresses
in the SLC's memory, and then we can access those bits/words for the different
communication functions between the PLC and drive... like run enable and amp

2014-03-07 10:43 PM

Replacing a VFD... DeviceNet Steps to match new/old controls (SLC 5/0...

2 of 5

http://www.plctalk.net/qanda/showthread.php?t=82692

You are not registered yet. Please click here to register!

So many details I'm unsure about... do I remove all the old addresses for that
node? do I give the new drive a new node address and change the ladder logic to
the new addresses?
I've set up connection like this in the classroom... once, about 3 years ago. I
didn't have to *replace* a device with a totally different device, though.
I appreciate any help/advice you can offer. Even just an outline of the steps to
take, in order, would help. Thank you so much!
Brian

October 10th, 2013, 04:24 PM

widelto
Member

Join Date: Jul 2005

Location: barranquilla
Posts: 1,644

#2

Brian:
First of all you have to be sure how big is your new (EDS) devicenet driver (
yaskawa) compared to the old one (reliance), if the new one is bigger then you have
to remap the whole things and you have to be aware of this.
What I mean is like this: if you have other devices on the same network you have to
modify your program due to remapping.
Be careful or otherwise you're going to be in a mess.
Or you can try to use unused addresses in order to avoid remap and leave reliance
space free on the scanner list.
__________________
My two cents.

October 10th, 2013, 04:50 PM

#3

AutomationTechBrian
Member

Yes! That's what I thought! I'm thinking of giving it a new node address and just
moving the pertinent instructions to the new addresses. So...
Step one: Compare the new EDS size to the old EDS size... consider giving the
new EDS a new, unused location in the memory.

Join Date: Jul 2013

Location: St. Cloud, MN
Posts: 37

Step two: Is there a way to easily see the open locations... in RSNetworx, I'm
guessing?

Sidenote: I was surprised how many devices were linked to this one SLC through
DeviceNet. This company bought just a portion of this huge plastic extruder, and
the portions of the machine they didn't purchase are still configured into the
DeviceNet card and SLC ladders. I've been hesitant to remove the missing
devices because I don't want to make a decision like that without knowing the
full consequences. This gives me a #78, config error on the scanner. The
machine still runs with that error, so I've been fine with that until now. Now, I'm
wondering if there is enough open memory to add the new drive... Hmmm.

October 10th, 2013, 05:28 PM

504bloke
Lifetime Supporting
Member + Moderator

#4

Error 78 is a node error from memory - f what you say is correct and lots of nodes
are missing then thats why your getting a 78 error
Again from memory it normally cycles from the error (78) and the node address
Its sounds a bit of a devicenet mess to be honest.....
__________________

2014-03-07 10:43 PM

Replacing a VFD... DeviceNet Steps to match new/old controls (SLC 5/0...

3 of 5

http://www.plctalk.net/qanda/showthread.php?t=82692

You are not registered yet. Please click here to register!

Dave

Join Date: Jan 2005

Location: West Ssx
Posts: 2,632

"When you are courting a nice girl an hour seems like a second. When you sit on a
red-hot cinder a second seems like an hour. That's relativity."
Albert Einstein (1879-1955)

October 10th, 2013, 05:32 PM

504bloke
Lifetime Supporting
Member + Moderator

#5

Manual Here for Device Net Scanner

http://literature.rockwellautomation...n058_-en-p.pdf
__________________
Regards
Dave

Join Date: Jan 2005

Location: West Ssx
Posts: 2,632

"When you are courting a nice girl an hour seems like a second. When you sit on a
red-hot cinder a second seems like an hour. That's relativity."
Albert Einstein (1879-1955)

October 10th, 2013, 05:38 PM

Ken Roach
Lifetime Supporting
Member + Moderator

#6

The first two things you need are the RSNetworx for DeviceNet project file (*.DNT)
and of course the RSLogix 500 project file for the SLC-5/05 controller.
The crucial thing that needs to be in the RSNetworx for DeviceNet project file is the
1747-SDN Scanlist. That's what tells the 1747-SDN how much data to exchange with
each slave device, and where to put that data in the 1747-SDN memory so that the
SLC controller can use it.
EDS files do tell you a lot about the I/O connections and how they are formatted, but
the Scanlist is the most important thing.

Join Date: Apr 2002

Location: Seattle, WA
Posts: 9,900

If you also have a backup copy of the RSNetworx project file, it might have the
GV3000 configuration in it as well. That's going to help you tune up the sort of things
that you would have to do on any drive; set the acceleration and deceleration rates,
figure out the speed reference scaling, etc.
Imagine that the GV3000's output assembly was something like this:
Word 0: Run / Stop / Reset / Jog / Forward / Reverse / Speed Select
Word 1: Speed Reference, 0-32767 = Min Hz to Max Hz
And maybe the Yaskawa output assembly is something like this:
Word 0: Run Forward / Run Reverse / Jog / Speed Select / Reset
Word 1: Speed Reference, 0-12000 = 0 to 120.0 Hz.
You would have to convert your logic both for starting and stopping the drive, and for
sending it a speed reference.
Get whatever files you can and post them, or send them to me by PM.

2014-03-07 10:43 PM

Replacing a VFD... DeviceNet Steps to match new/old controls (SLC 5/0...

4 of 5

http://www.plctalk.net/qanda/showthread.php?t=82692

You are not registered yet. Please click here to register!

Ken Roach
Lifetime Supporting
Member + Moderator

The info given here is correct about status code 78; it indicates the scanner is not
communicating with a DeviceNet slave node. The status codes alternate with the
slave address.
Status code 72 appears when a device was communicating and stops. Once the
scanner has attempted to re-establish communication (or if it has never been able to
start), you'll see Status Code 78.
You can de-Activate a particular slave device's scanlist entry without removing it
from the scanlist or from the memory map, if you're being conservative. It's nice
sometimes to not have to stand there and try to keep up with a flashing list of status
codes, most of which you need to ignore.

Join Date: Apr 2002

Location: Seattle, WA
Posts: 9,900

October 10th, 2013, 08:06 PM

AutomationTechBrian
Member

#8

Yes!!! Thanks! DeviceNet is the last area of this extruder that I'm fuzzy on. The
new VFD is expected on Monday, and I'll be getting familiar with what I need to
know between now and then.
Ken... I'm always amazed and grateful when you post! Thanks once again!

Join Date: Jul 2013

Location: St. Cloud, MN
Posts: 37

Jump to Live PLC Question and Answer Forum

Bookmarks
Twitter

Reddit

Digg

del.icio.us

StumbleUpon

Google

Previous Thread | Next Thread

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Posting Rules
You
You
You
You

may
may
may
may

not
not
not
not

post new threads

post replies
post attachments
edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Topics
Thread

Thread Starter

Forum

Replies

Last Post

AB SLC 5/05 Ethernet MSG Errors

mrdegold

LIVE PLC Questions And Answers

January 20th, 2009

12:10 PM

SLC 5/05 to Powerflex 700 vfd

mdwyer39

LIVE PLC Questions And Answers

13

October 13th, 2006

06:29 PM

2014-03-07 10:43 PM

Replacing a VFD... DeviceNet Steps to match new/old controls (SLC 5/0...

5 of 5

http://www.plctalk.net/qanda/showthread.php?t=82692

You are not registered yet. Please click here to register!

Similar Topics

how SLC 5/05 control motor AC Drive thru

DeviceNet

yuez2000

LIVE PLC Questions And Answers

13

watlow sd6c devicenet on slc 5/05

LTBarnette

LIVE PLC Questions And Answers

January 24th, 2006

07:21 PM

SLC 5/05 Ethernet hardware fault (A2h)

Znatok

LIVE PLC Questions And Answers

October 11th, 2005

11:26 AM

May 8th, 2006 07:50

AM

All times are GMT -5. The time now is 01:17 PM.
Contact Us - PLCS.net - Text - Top
.

2014-03-07 10:43 PM