JohnnyQuanex
Lifetime Supporting Member
Hi folks,
First of all, Merry Christmas and Happy New Year to everyone!
I'm the lucky heir (as process engineer) to a dated process that include 13 very old lines that use SLC 5/3, 4, 5 processors, and DNet for the device network. I am slowly, but surely making control system upgrades, but I will need to deal with this equipment for quite some time.
I have worked with dnet quite a bit since taking this position several years ago and am at a 85% confidence level in using it and modifying it. I've upgraded some drives and successfully mapped I/O, parameters, etc into SLC 500 data tables. So, I'm not asking as an amateur, but rather I do have some experience working with this stuff...
I'm dealing with a headache today (actually for a few days, but haven't focused much on it) involving a faulted AB 1336 Plus II drive and devicenet. At first I thought it was simply a bad drive because my dnet seemed to be functioning fine. However, a replacement drive did not solve the problem. If I unplug the network adapter card from the 1336 Plus II drive, and cycle power, the fault light goes off. Then, if I plug the card in, the fault returns.
I'm not really familiar with the 1336 drives and I don't really even know how to find out what the fault code is. I tried looking at the parameters via RSNetworks for Dnet, but I'm not sure what parameter, if any, provides that data for me. I also don't and can't find any literature for the drive.
Having said that, I not convinced I need to chase that rabbit because now I'm getting an error code on my 1747 SDN scanner module. The code references the node I'm having this trouble with, which is 15, and the error code is 77. According to my sdn manual, this means "Data size expected by the device does not match scanlist entry." When I switching drives out, I allowed dnet software to correct key mismatches and such in an attempt to clear some device mismatch error codes I was getting. I had tried an entirely different drive with more I/O to map, just to make sure my drive wasn't the issue (tried two different drives, because our spare drives are "supposedly good" used drives. Wanted to rule out a bad spare drive.)
Anyway, I can upload my entire machine's dnet network and generate a report; I can compare that with a report for last year, when all was good. the mapping is the same and so I'm just throwing out a call for help. Maybe somebody can help steer me and give me something to try at the very least.
Thanks,
John
The line is not scheduled to run right now so I am able to take my time on this problem.
First of all, Merry Christmas and Happy New Year to everyone!
I'm the lucky heir (as process engineer) to a dated process that include 13 very old lines that use SLC 5/3, 4, 5 processors, and DNet for the device network. I am slowly, but surely making control system upgrades, but I will need to deal with this equipment for quite some time.
I have worked with dnet quite a bit since taking this position several years ago and am at a 85% confidence level in using it and modifying it. I've upgraded some drives and successfully mapped I/O, parameters, etc into SLC 500 data tables. So, I'm not asking as an amateur, but rather I do have some experience working with this stuff...
I'm dealing with a headache today (actually for a few days, but haven't focused much on it) involving a faulted AB 1336 Plus II drive and devicenet. At first I thought it was simply a bad drive because my dnet seemed to be functioning fine. However, a replacement drive did not solve the problem. If I unplug the network adapter card from the 1336 Plus II drive, and cycle power, the fault light goes off. Then, if I plug the card in, the fault returns.
I'm not really familiar with the 1336 drives and I don't really even know how to find out what the fault code is. I tried looking at the parameters via RSNetworks for Dnet, but I'm not sure what parameter, if any, provides that data for me. I also don't and can't find any literature for the drive.
Having said that, I not convinced I need to chase that rabbit because now I'm getting an error code on my 1747 SDN scanner module. The code references the node I'm having this trouble with, which is 15, and the error code is 77. According to my sdn manual, this means "Data size expected by the device does not match scanlist entry." When I switching drives out, I allowed dnet software to correct key mismatches and such in an attempt to clear some device mismatch error codes I was getting. I had tried an entirely different drive with more I/O to map, just to make sure my drive wasn't the issue (tried two different drives, because our spare drives are "supposedly good" used drives. Wanted to rule out a bad spare drive.)
Anyway, I can upload my entire machine's dnet network and generate a report; I can compare that with a report for last year, when all was good. the mapping is the same and so I'm just throwing out a call for help. Maybe somebody can help steer me and give me something to try at the very least.
Thanks,
John
The line is not scheduled to run right now so I am able to take my time on this problem.