GT6Steve

Mission accomplished! Apparently I wasn't going deep enough at the AB Firmware download page. I clicked the red Download at the bottom of the page and nothing happened but when my friend did the same thing it worked for hi and brought up a download menu box. Guess I'll have to sharpen my mouse....! Thanx to all for trying to respond to a somewhat vague question, Regards, Steve

Yeah, I still have that sticker. Version 16.023 is the earliest it'll work with so I should be good there. I recall loading EDS's for a drive long ago, I'll have to dig around on Google for a while. Thanx for the clue, I'll do some more study.... Just as an informational input.. I recently purchased two L23E's.. There was a nice bright orange sticker that stated a minimum requirement for being able to program it. Not sure if you are in the same situation. I would right click on the device in RSLinx and select "Upload EDS from device", or go to the EDS file section from AB.com and select.

Thanx for the report, It's a keeper. I personally LOVE the Yaskawa's and have had great successes with them over the years. Sadly I have none in my current plant.

Because if you're not adequately committed the contactor may not make full contact across all three phases which will single phase the motor, draw high currents and generate a lot of heat. Throughout this I've been picturing the NEMA contactors I've grown up with which are very robust and can tolerate this kind of abuse. Nowadays we're all faced with these toy IEC crap which will not forgive a mistake. Your newage electrician needs to be VERY aware of the protections the IEC assumes will be built into an application using their standard. Mixing old school NEMA and IEC creates a very dangerous condition when it's not fully understood. Hmmm, rereading your post I want to expand a bit. When there's an arc of any kind it ionizes the air making it conducive to conduction. If perhaps, one leg of the contactor lags it will draw an arc and cause ionization. Now this ionized air supports if not encourages conduction making it easier to arc across barriers to another phase. IEC equipment is much smaller than NEMA so the barriers are much smaller reducing the safety factor for this arcover. Often, IEC contactors are replaced into panels because they're available, they fit or just because. That panel has not been designed to IEC specs and now that toy contactor is a bomb. It is nowhere near as forgiving as the old NEMA giant was. Just saying, take care and pay attention to how things are changing....

Absolutely agree. This is a very common and relatively dangerous practice. I've done it since 1973 but have been getting more wary as I become aware of my mortality. Like what if the motor is shorted and the fuses were oversized by the previous shift? I stll do it but I'm sure to ram it home hard with a long screwdriver and wear PPE. Not a recommended practice as I've seen too much that goes wrong over the years....

We did this with a high speed wrapping machine that needed to keep tension on the web thru each phase of the bag assembly and cutoff. Three Drives were cascaded with a small trim pot on each to control the relative speed. Signal from the previous drive plus a trim. We used Yaskawa drives but I'm certain a Siemens would have as much flexibility. We made the main speed pot knob large and stiff while the two tension trim pots were small.

I need to start collecting data from my facilities Cutler Hammer DP-4130 power monitors. I'll need a lot of expensive PONI cards, probably the EPONIF fiber version. I'll want to bring these into my Rockwell Contrologix and into SCADA. Anybody worked with these and able to point me to protocal details? Internet search doesn't turn up a lot of detail beyond "use our Powernet software".... How do I deal with the serial data from the EPONI's once I get it into the PLC's via the Ethernet. (That'll be a trick unto itself) Thanx in advance, Steve

Forgive me for pushing this to the top but enquiring minds wanna know..... How was this resolved? Steve

I'll take a peek tomorrow when I'm back to work....

Several years ago I worked on a nice RSView application that used Enum's to display extensive motor data lists for selected motors. Over 500 motors in the facility could be brought up to dispaly about 20 different parameters for each. I worked it at the time and was able to make changes. I can't say I fully understood it but I had a glimmer. Now I've forgotten. Can't someone point me to a treatise or discussion on the use of enumerated arrays? If that's the correct question..... BTW, this data came from Cutler Hammer Advantage contactors via Devicenet over their WDNPONI comms module.

Thanx for the pointers Shawn, I will explore as you've indicated. As I'm stewing on it I recall inserting a number which related to the list. I could draw up any tag that was defined in the list by referencing the number. I recall colors were called up similarly. I'm entirely self taught and learning all of the time. Sometimes well, sometimes it's a struggle Thanx for the input, I'll pursue it. Steve

Hmmm, Thanx Ken. I'm talking about RSView 32 but enum may be a carry over from the days of Labview. I certainly can't find a reference on the Internet beyond C++. I'll ponder what you've said above because you remind me that each motor had all of the "sub" tags in the dropdown window. a UDT for motors. I guess I'll do some study from there. Thanx for the insight... Steve

So these are standard shaft encoders, optical disc and photoeye? It is the encoder motors specifically that failed. Not the drive motors. Right The drive motors are the originals, merely having the shafts modified for the encoders. Same style of encoder as the original one? Are the encoders electrically isolated from the motor or bonded. Transient currents Is where that's going. I'm purposely ignoring the obvious connection faults and such as you've certainly got the expertise on hand to find the obvious. All that's essentially changed is the drive package.....

Did the other work in the area involve welders??

Presumably the ignition gas flow is a fixed orifice and you invoke the PID with a flame proving sensor. How often does it jump to a high flame instead of an orderly transition? My first suspect would be the gas valve sticking requiring the relatively fast gain to ramp up and compensate. Mr. Ross's questions are valid. The kiln must warm slowly at first and I assume you're doing some kind of ramped startup to control that. I get Kilns and temperature control but don't yet see your issue. Check the actuator carefully with an injected control signal. Maybe adjust the gain to move the valve either faster or slower so as to ride thru the binding point. Keep us informed...I like temperature control

Wow! I thought I kinda understood arrays, I could work them but it was still a little fuzzy. Thanx immensely for the excellent clarification.

You'll probably export the entire galaxy and import it to your new machine.You may need to have Archestra IDE loaded as well as Intouch. And then the licensing....

I access my RS Logix 5000 PLC's over the network from a host computer. I've found it good practice to go online with the target PLC as soon as the file opens so I don't foolishly make a change and then have a mismatch. Can I setup RS Logix to automatically Go Online when the file opens so forgetting isn't as annoying anymore? Or am I doing something wrong that I need to change? What's the standard practice? Thanx in advance, Steve

Well, it took a while but I found the Logicmaster 90-30 V9.05 AND the Infolink CD. Do you still need it? Steve

Ahahh! I just stumbled onto your reference. I've never used that before but I'll make a point of remembering it in the future. Maybe I won't have to keep my IP file open all the time now Thanx, Steve

I'm pretty sure I have that software at home. I used to do a lot of 90-30 work. I'll try to remember to have a look tonight... Steve

LOL, I didn't even notice the date, I just saw four posts. Certainly no offense meant...Steve

I was just being a paranoid about downloading an unknown file from a relatively new user. No offense meant to Elcan, just cautious. Steve

Has anybody downloaded this file yet??

I started just as Mr Ross outlines above. I hired into a plant as a maintenance electrician and evolved into instrumentation slowly shedding the floor level maintenance duties as PLC's and Scada's consumed more of my time. From your mini resume here it sounds like you'd be useful to an integrator more so than a plant electrician. That's just a guess of course. Good Luck with your search, we had a tough time finding good people at that plant.