DeviceNet: Uploading vs. downloading. Issues with Yaskawa Drive

The high and low byte don't split at the decimal point. They are the high and low bytes (8 bit) of a 16-bit Integer.

Usually 16-bit Integer values like "443.8 Amperes" are expressed as an integer value of 4438, where the units are 0.1 A and the decimal place is implied.

In the RSNetworx Parameters configuration screen, exactly which values did you set ?

Extended Speed Control Status = Assembly 71 = 4 bytes
or
Speed Status Dynamic Assembly = Assembly 134 = 8 bytes

Extended Speed Control Command = Assembly 21 = 4 bytes

I don't see any 12 byte assemblies.
 
Also: it's super-common to be confused about which is "input" and which is "output".... data Produced by the AC drive is Input data once it's Consumed by the PLC. Stick with the terms "Produced" and "Consumed" as much as you can.
 
Sorry for the delay....

I realized on the 90 min. drive home that I was confused with the 2-byte (16 bit) addresses. I was looking at the Yaskawa manual's layout, in bytes, and didn't remember that the M1.1.0 address is 2 bytes of information. It came when I thought about the terms "high byte" and "low byte". Doh! I probably needed to get away from it for a little bit anyway.

Well, a lot has happened today. I thought I had everything working... No errors on the scanner and everything playing nicely. But... I'm not so lucky.

I was having trouble setting the I/O sizes to anything other than the default, so I stopped fighting it and went back to the default just to see if the values would make it to the PLC.

I mapped the 4 bytes of both drive input and output the the first M addresses respectively.

-M1.1.0 thru M1.1.1
-M0.1.0 thru M0.1.1

I used the default for the values the drive produces (71), but switched from the extended values to the basic values for the values the drive consumes (20). I know I've got the ins and outs right because they match the other drives' values in RSLogix 500 (SLC 5/05).

In the ladder logic, I used COPY to move M1.1.0 to N11:22 (bottom value = 2), the COPY for N10:1 to M0.1.0 (again, 2). This program doesn't use DeviceNet values for the drive controls. Instead, the basic start/stop/speed ref/fault reset are all hooked up to and programmed on the drive terminals. It's the drive feedback values that come from the DeviceNet connection... ready/running/faulted/motor AMPs/RPM. There are parts of the ladder logic that require these inputs for timers and some other functions....

....and nothing is making it to N11:22. I pull up the N11 values, and nothing registers. All zeros... even the "ready" bit. Even when I start the drive and the motor is turning. Nothing.

It would be nice to be able to see the live "M" values... but I don't think that's possible. Anything to tell me that the drive is actually sending the values and the scanner is receiving them. They certainly aren't making it to the PLC.

I have to go to a different jobsite tomorrow (Wednesday). I'm going to use some manual pushbuttons in Wonderware to simulate "ready" and "run" so they can use the extruder tomorrow. I'll be back on Thursday to see if there are any more paths to try.


BTW... Yaskawa... I actually work for a company that specializes in VFD service (although I enjoy the PLC projects). We love Yaskawa! From a service tech's viewpoint, they are excellent drives. Very serviceable and great technical support. It's been a little harder to match available times with the specialist "applications" guy than the regular tech line. Fortunately, this forum is a phenomenal resource as well!!
 
Ken Roach said:
...it's super-common to be confused about which is "input" and which is "output"....

It sure is, seems even the Yaskawa Applications people can get confused as well?

Brian,

I've had another look at this for you and I think I've noticed something that may be causing your problem?

AutomationTechBrian said:
...the file I attached is a revision I had emailed to me directly from a Yaskawa Applications person...

In the 2010 EDS file you posted: AU4A0515_SI-N3_v1.8_(1).txt

Param2= $ Current PPA
0,
6,"20 64 24 03 30 C4",
0x0002,
0xC7,
2,
"PPA",
"",
"Polled Producing Assembly (Master to Drive)",
20,126,21,
,,,,
,,,,
;

Param3= $ Current PCA
0,
6,"20 64 24 03 30 C3",
0x0002,
0xC7,
2,
"PCA",
"",
"Polled Consuming Assembly (Drive to Master)",
70,199,71,
,,,,
,,,,
;

A couple of things.

Firstly...

The 'Master to Drive' and 'Drive to Master' are mixed up here.
Master being the Scanner, or PLC in effect.
A PPA is Produced in the Drive and Consumed in the PLC (Input Assembly). i.e. PPA = Drive to Master.

A PCA is Produced in the PLC (Output Assembly) and Consumed in the Drive. i.e. PCA = Master to Drive.

But that's just text in an EDS file that most won't ever see to mislead them.

Secondly, and more importantly...

In the 2013 EDS file I posted: AU4A0515_SI-N3_v1.008.txt

Param2= $ Current PCA
0,
6,"20 C7 24 03 30 C3",
0x0000,
0xC7,
2,
"PCA - Polled Consuming Assembly",
"",
"Polled Consuming Assembly (Master to Drive)",
20,126,21,
,,,,
,,,,
;
Param3= $ Current PPA
0,
6,"20 C7 24 03 30 C4",
0x0000,
0xC7,
2,
"PPA - Polled producing Assembly",
"",
"Polled Producing Assembly (Drive to Master)",
70,199,71,
,,,,
,,,,
;

Here the Master and Drive descriptions are correct, but notice how Param 2 and 3 have reversed rolls from the 2010 version?

Param 2 is now PCA and Param 3 is now PPA.

If you look at all the other EDS files from Yaskawa, you'll see that Param 2 = PCA and Param 3 = PPA.

Somehow, your currently registered EDS file has them reversed?

With them reversed, look at the parameters in your attached screenshot: PPA_PCA_Values.jpg

Param 2 = PPA
Param 3 = PCA

I'm pretty sure this is the wrong way around in the EDS you've registered, and the 2013 version is correct as above.

Thirdly...

Your parameters are selected as:

Polled Producing Assembly = Basic Speed Control

Basic Speed Control has two Assemblies available,
one for PCA and one for PPA:

1. Basic Speed Control Status - (PPA) Input Assembly 70 (0x46) 4 Bytes (Drive to Master)

OR

2. Basic Speed Control Command - (PCA) Output Assembly 20 (0x14) 4 Bytes

I'm not sure which you have selected, but for the PPA parameter, Basic Speed Control Status - Input Assembly 70(0x46) 4 Bytes should be used.

Polled Consuming Assembly = Speed & Current Status

Current & Speed Status has only one Assembly available and that is 132, as you attached here.
Assembly 132 (0x84) 6 Bytes is a PPA only Assembly.
You should not be selecting this for PCA.
Again, this could be because you're mixing PCA and PPA up.

Error 77 - Device's data sizes do not match scan list

You got this error when you had 12 Bytes for Polled Input size, and 8 Bytes for Polled Output size, instead of 4 Bytes each.

I don't know what errors you were getting with the first EDS files you tried, but my suspicion is that initially you were using the correct EDS file from the website, but setting the Polled Byte sizes incorrectly, and or, using PPA Assembly 132 for the PCA parameter value.

You then got an EDS from Yaskawa that threw up the errors listed in your first post. The Param 389 Instance 0x00 typo, an unrelated Modbus parameter,
which Ken solved,
and the Param 2 and 3 errors, possibly caused by them being reversed in the EDS file?

Whatever the mix-up is here...

I would try unregistering the 2010 EDS file using Tools/EDS Wizard and then register the 2013 EDS file.

Once the 2010 EDS file is unregistered, make sure you close RSNetWorx and shutdown RSLinx.
Then re-start RSLinx and then RSNetWorx.
Then use the EDS Wizard to register the 2013 EDS file.

Check the devices parameters again, and now they should be set to the defaults:

Param2 = PCA Extended Speed Control Output Assembly 21 (0x15)
Param3 = PPA Extended Speed Control Input Assembly 71 (0x47)

Polled Input = 4 Bytes
Polled Output = 4 Bytes

Change PCA and PPA parameters to the Assemblies you need...

AutomationTechBrian said:
...It's the drive feedback values that come from the DeviceNet connection... ready/running/faulted/motor AMPs/RPM. There are parts of the ladder logic that require these inputs for timers and some other functions...

PPA = Current & Speed Status - Assembly 132 (0x84) 6 Bytes

This will give you the data you require from the drive to the PLC. Make sure the Polled Input size = 6 Bytes.

You haven't specified anything you'd like to send from the PLC to the drive (PCA), so set...

PCA = Basic Speed Control - Assembly 20 (0x14) 4 Bytes

Even though you don't need these over the DeviceNet network, this gives, from the PLC to the drive, Fault Reset and Run Fwd bit control, and Speed Reference.

Then, if not already, add the device to the Scanners scan list and map the I/O to the M1 and M0 addresses again.

Hopefully this will get your data moving into the PLC.

G.
 
Last edited:
Wow! That was an amazing reply, Geospark!

After some time away, I'm back at the jobsite this week. The extruder is running today, so I can't work directly on the network. I'll start looking through what you wrote and figure out what I can do to prepare for the shut-down time.

Before I even begin, I want to express my appreciation to both you and Ken for the time you've spent on helping me.

If I have any questions, I'll post them.

Thanks, again!

Brian
 
Yaskawa has confirmed the mixed-up EDS file. They sent me a "clean" EDS sheet and I'll install it when they shut the machine down. Until then, I'm working on a Control Logix issue. I have a separate post for that.

I'll come back here once I install the new EDS.

Thanks again!

Brian
 

Similar Topics

Hi I'm new to Allen Bradly. I've managed to uploaded the PLC code, but need to diagnose the devicenet card. How do I upload the configuration so I...
Replies
6
Views
1,852
I have a client with 7 lines of conveyors which each have up to 30 Powerflex 40 drives on DeviceNet. I have vpn access to the site and am trying...
Replies
1
Views
3,083
Hi, I am looking to migrate some of our Electronic Overloads off of a Troublesome Devicenet Segment. Is there any documentation confirming the...
Replies
5
Views
115
We've run into an old system that we are upgrading which is still running Steeplechase with Citect using Devicenet to Wago. I had some experience...
Replies
4
Views
157
Sigh, DeviceNet noob... I have a 1756-L55, with a DeviceNet module, and 10 PF700 all commanded with DeviceNet. One of the PF700's blew up...
Replies
3
Views
139
Back
Top Bottom