OK. Well, does anyone know how I am trying to import the tags from my SLC 5/03 project. I exported them to a CSV file, but when I try toi import them, the software appears to not actually do anything. There is no tag list. Does anyone know how to help? Thanks.
http://www.plctalk.net/qanda/showthread.php?t=70427&highlight=crimson+3.0+tag+import+RSLogix500
Also, I don't know if it's covered in the linked thread(s) above, but if you try to massage the csv file with MS Office ware, it will foul up the file, inserting extra commas for every missing field to pad them out.
When the imoprt mechanism in Crimson 3.0 encounters all these strings of commas, it bails, with only a glimpse of an error on the bottom status bar.
I fixed this manually with notepad++ with show all characters turned on. I had the raw and the edited side by side with compare highlighting, then a few select/copy/find and replace plaste clicks later, my csv saved from an xls sheet was repaired.
If you don't get the 'success' dialog box and see the import tags being listed as imported, then it bombed out.
Get Notepad++.
By copying and pasting the correct section with line returns and commas format from an unadulterated csv file into the one that MacroShaftExcel decided to flub up for me. I could identify, select, copy the wrong, find, paste, replace, copy the correct, paste, replace all and it's fixed.
Notepad++, I have barely tapped its power, but it rocks out of the box. It's like the wireshark of text editors.
I think with OpenOffice it is easier to import/save without these hassles, but my final workaround was to use a dummy copy of the rss file with all non-HMI stuff purged out before exporting.
This allowed me to define the data stream in all directions up front, and I like limits and generic structure when it comes to HMI comms. Many would say this defeats the purpose of importing. It is a question of style, not right or wrong.
Only importing what you need from a stripped down RSLogix file may not hold any real performance advantage except for the storage space of the tags not being accessed on your PC. But it is nice not to have a list of addresses to wade through during development. Describe them as you go, marking them used, leave space between groups, (use array tags on the Crimson side).
If you like a clean and planned structure with generic tag names like I do, then this method works. Just leave lots of room for expansion so you will never have to change it.