OT: Descriptive Tag Names

From a customer of ours in the states, just why?

6eer91.jpg

Whats wrong with that??

fgdfsg = Forget Gosh Darn Fast Sensor Good

FKSDFJGHKSD = Fast Knot Sensor Detector Fumbling Just Good High Known Sensor Dead

gfbhgfhgfh = Good Fast Bubble High Good Fast High Good Fast High (this is a aray)

H = hell (short for "oh hell")
 
Whats wrong with that??

fgdfsg = Forget Gosh Darn Fast Sensor Good

FKSDFJGHKSD = Fast Knot Sensor Detector Fumbling Just Good High Known Sensor Dead

gfbhgfhgfh = Good Fast Bubble High Good Fast High Good Fast High (this is a aray)

H = hell (short for "oh hell")


I have a different take on some of the "f"s :whistle:
 
Ok, so I can understand a converted RSLogix500 program retaining the old names, but I have had the fortune to work on a program written from scratch in RSLogix5000 where the programmer chose to name all the tags just like in 500 instead of using descriptive names.
 
YES! Four years in and I'm still cleaning up converted programs left by my predecessor. I can't fathom why he didn't spend a little time creating proper tag names. Then again, his code on two identical machines was often completely different, so...
OK, I'll admit to putting all of the original code into a single array on a PLC-2 to ControlLogix conversion two years ago. The tag was mapped for PLC-2 messages because the CLX had to support the existing computer until the last stage of the project. Every used word and bit had the description filled in with the original description, the PLC-2 octal address and the I/O wire number.


Ok, so I can understand a converted RSLogix500 program retaining the old names, but I have had the fortune to work on a program written from scratch in RSLogix5000 where the programmer chose to name all the tags just like in 500 instead of using descriptive names.
Once again communications drove the tag naming, in this case a Delta V DCS using a Mynah Ethernet card with the A-B driver loaded. On the first project the driver only supported PLC/SLC messaging, so I named the array tags to match the mapped file numbers. On the next project I had already done the same before the Delta V programmer confirmed that the new driver would support Logix tags.
 
OK, I'll admit to putting all of the original code into a single array on a PLC-2 to ControlLogix conversion two years ago. The tag was mapped for PLC-2 messages because the CLX had to support the existing computer until the last stage of the project. Every used word and bit had the description filled in with the original description, the PLC-2 octal address and the I/O wire number.

Backwards compatibility is a different story. We still have a couple of small CompactLogix machines that are full of arrays mapped to N and B files because the external devices can't be modified to pull tags from a Logix. It's the standalone stuff that was run through the converter and then left as-is that I don't understand. ;)
 
Yeah, that's just a nightmare.


A client of mine ordered two CIP systems from a company. They were built brand new with a compact logix but the entire tag database is just arrays of N7[255] and B3[255]. And no comments. They provided an excel spreadsheet to cross reference the tags.


They also used a 4" black and white non-touch HMI, and were nothing short of amazed at my ability to make their PLC talk to the line central control PLC. I can't help but wonder if nobody has told them it's not 1995 any more.
 
Rockwell was actually going to do this for us for a program in a modernization project. Went through explaining how the program would be converted and tested by their engineers and how great it would be.
Me: “Are you going to rename the tags to descriptive names?”
Rockwell: “No...”
Me: “So what service are you offering again? I thought we were modernizing?”

I'm glad my company isn't the only one they pulled that trick on. I wish I would've had that reply though! :D
Yeah, one of my part-time projects is rewriting those tags into something that makes sense.
 

Similar Topics

I need help in trying to retreive the descriptive part of a ladder logic to help me troubleshoot the machine...somebody wrote it and I am having a...
Replies
9
Views
3,060
I have a German programed ME program. I want to know what tag in the PLC a latched button turns on. However when I open up the tag properties I...
Replies
14
Views
196
Hi, I'm having an issue in crimson 3.0 when I create a programme using a case statement referencing a fault word that each bit needs to change the...
Replies
4
Views
177
Has anyone ever seen where you have a tag reading from the plc in scada. In this instance it's just a PEC, I set it up on one scada terminal and...
Replies
0
Views
87
I want to set user security level based on the value of a tag in my PLC called "ActiveUser". That tag will contain the A-P code which we use for...
Replies
6
Views
207
Back
Top Bottom