Tisoft Xref

Just a Quick question i hope somebody can help me with. We are using ti505 series plc's and wonderware on our hmi's. Recently in order to keep from losing the value of a tagname in WW I assigned it to a V# in the PLC so that when the hmi is rebooted it doesn't lose its value. My question is: Is there an easier way to do this without using a retentive value tag and if not what would be the easiest way to make the v#'s show up an a crossrefernce so that we know that they are being used. Thanxs in advance for any reply.

Where are you getting the value from..PLC or Operator input?
Is this a changing value or constant? I'm currently working on replacing all the tcp screens at our facility with ww. We are also interfacing with TI's. I haven't had much time lately to work on it, but may be able to help with more info.

FasTrak SoftWorks, Inc. makes 505 WorkShop, which is the Windows replacement for TISOFT. It allows you to have Synonyms, like TISOFT (called Descriptions in 505 WorkShop), and also allows you to assign Tag names to each address. Besides this, 505 WorkShop, allows you to do a cross reference of all addresses and parameters used, and displays the appropriate documentation for those. You will also find that the cross reference is Resident, right on the display, and doesn't have to be printed like the TISOFT makes you do. There are also numerous advantages to 505 WorkShop over TISOFT, such as it is a 32 Bit Windows application and it's communications are all OPC. It is also much easier to work with, especially if you are using any kind of ethernet with your PLCs. Please feel free to contact me for any further information.
[email protected]

Sorry Rodney, but just because a V-memory location has a value in it doesn't make it show up in the Tisoft Xref listing. What a cross-reference does is to display the memory addresses that are used by code, listed in order of memory address. The intention of cross-reference lists is to allow you to see if the same address (X, Y, C, V ... whatever) has been used more than once, and if so, at what locations in the code.

If you want to use V-locations to hold values unrelated to the rest of the program you can give them a synonym like "DONT USE THIS ONE!!" and put something in your program title documentation to tell people that any address with this synonym is to be avoided. Or you could stick a series of simple instructions like LDC's or MOVW's which do use these V-locations in to an uncalled subroutine. This means they will show up in the xref listing, but will not get executed.

Regards

Ken.

I put all the addresses in an uncalled SFPGM to serve as a place holder.

Something like:
* THESE ADDRESSES ARE USED FOR XREF PURPOSES ONLY
MATH T8 := V100+V102+V103+V104+V105+V106

ti505

The Integers that i'm using are constantly changing with production on the line. The results are stored in an SQL server through a quickfunction that is called at the end of each shift. Thanks to everyone for their replies, you've all been a great help. thanx again. Rodney