Local Versioning Questions

[[Ch...]]

I have a couple questions about Local Versioning:

1.  Is there a report header parameter that outputs what version the program was ran on?   I want to know what revision of the program my data is from.  

2. If I swap the CAD model on a new revision, do prior revisions still use the old CAD model?   Looking at the file structure, it does looks like the old revisions do keep the old CAD model, but I want someone to confirm.  

 

I tried searching the forum but didn't seem to find an answer to my questions in the threads below.  But sometimes I'm blind. 

 

[[Th...]]

Recent iterations of the standard report include a header line for the plan version. It's this red bit of text at the top.

 

[[Ky...]]

1. The revision is in there, I just can't find any PCM code to get it.... As Thomas mentioned, it is in PiWeb pretty easily which, if that's where you want it that's great, I just can't tell from your post. I also can't find it in hdr_txt table file.

 

2. Based on my testing, Calypso stores the CAD with the version, so going back restores the CAD that the version in question was made with.

[[Ja...]]

Whenever I rev a program, I move the old program to directory I made called "Obsolete". I never save over existing programs, or delete the old one. That way I can use the old program anytime I want and know the entire program is 100% intact. Takes up more HDD space that way, but HDDs are cheap.

[[Ch...]]

Please sign in to view this quote.

Please sign in to view this username.

This is what I currently do.  And honestly, it works just fine.  With a few exceptions

I'm exploring Local Versioning because I like how it forces my programmer to make notes about what changed.  It's nice to have everything logged right there within the same program. 

But the revision not being in the _hdr file really doesn't sit well with me.  I didn't see it either when I looked.  That's going to be a pain when I export from my database. 

[[Ma...]]

Please sign in to view this quote.

I also do the same but I have a running text element at the beginning of the program with the revision number, the date, and what the changes are. I mask this out in the program but I can always refer to it.

[[Ma...]]

I would say both methods have pros and cons.
We are using versioning, because i am only programmer, so whenever i do changes i do it with a reason - minor changes or repairs i am not saving as a revision.
But bigger change in different alignment or minor change on CAD model i do a revision.

I see only plus that it's the only place of that program.
Con is you can not use different versions on autorun, when you recall older revision you are losing working copy ( aka not saved changes in revisions )

Using separate folders is quite space demanding ( based on program size ), but you can use many of similar programs on autorun.
Also you keep track of stored measured points for each version.

[[Ch...]]

We have the revision name listed directly in the test plan name: Example

SAP#-01_rv01 SAP#-01_rv0xxx

-01_ is an example of which setup / short or long

The old version will be archived

Maybe the name have the same revison as the drawing.