This is going to be a chore to explain the complexity of what can happen
Issue #1: Scripts spread out between different folders for the same device
1) You place scripts in device workspace, compile and save to station.
2) If it's the first scripts created, a new folder appears in Station File area
showing the new controller name along with files placed in source and compilation.
UserHome source and compilation will have files added as well in respective folders
3) Rename device
4) No name changes occur for any files in Station Files or User Home,
5) Create more scripts in workspace, compile and save to station.
6) A new folder appears in Station File area showing the new controller name
7) Files added to this new folder are the new compiled and source scripts
😎 User Home area will have new scripts added to the same lists
9) Rename device again
10) Create more scripts in workspace, compile and save to station
11) A new folder appears in Station File area showing new controller name
12) Files added to this new folder are the new compiled and source scripts
13) User Home area will have new scripts added to the same lists
14) All script object paths will still point to the unique folders that were current
at the time it originally was created.
End result is a Station File area with 3 folders with 2 obsolete controller
names and 1 current controller name. Current and viable scripts are
spread out between all three. The UserHome section folders of
Compiled and Source show all the scripts lined up.
Issue #2: Obsolete folders
1) You decide you want to clean this up, so you open each script manually in the
whole workspace, then compile, then save to station.
2) The Station Files folder with the most current controller name will now have all
the current saved files for the entire controller in both the compiled and source
sections. The properties paths of the script objects will now point to the most
current controller name.
You now have two obsolete folder file locations in Station Files with names
you might not even remember where they came from, and still containing
the original scripts from the time the controller used to be that name, but
at least the scripts are now obsolete.
Issue #3: Sharing scripts with others. Finding everything you need.
1) Copying the bog file for the particular objects
2) Copying the Station System Files relating to the particular
script in both the Compiled and Source folders
3) If the script paths got spread around by Issue #1, then may not
be very easy to locate quickly.
Is there a nice easy way to package the various files you need without needing
to give them the entire station?
Issue #4: Copying and pasting within same wiresheet
1) Copying and pasting a script in the same wiresheet will create a new object with
the proper instance number but all property references point to the original script.
2) If you open, compile, and save back to station...then everything will line up with
the new script.
In trying to reduce mouse clicks, this part could add alot of additional
overhead and can be easily be missed or forgotten about.
Issue #5: Copying and pasting to a different controller's wiresheet
1) Suffers the same problem as Issue #4, and everything still points back to the original
wiresheet's files. No new UserHome files are created for source and compile at this time.
2) If you open and compile each script, then new source and compile files will be created
in the new controller's Station Files and UserHome sections for source and compile.
It seems like there's going to be a lot of overhead in keeping track of all the script
files in trying to copy, paste, export, import, and so forth. Add in the factor of
obsolete controller names still having folders with possibly current scripts inside
them seems like it could lead to alot of potential issues with accidental erasures
or the folder structure gets completely out of hand and beyond figuring out what is
Is there an easy way to do what i described for the 5 issues other than
manipulating each block directly and having a good memory of previous
controller names or cross referencing instance numbers?
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!