The current SQLtag CSV import/export alert data format is difficult to use, with multiple alert data items jammed into one column. It should be easy to migrate alert parameters from a competitor’s HMI, with one column per data item. A side benefit would be a more human readable/editable/verifiable format.
The name of the game in successful system integration is speed and precision. Beefing up Ignition’s abilities to import competitor’s HMI configurations will go a long way in helping upgrade systems. Just say’in…
As long as each “State Name” is unique for each tag’s alerts, a new spreadsheet row for each alert should be workable.
I must also emphasize the importance of an easy, human-readable format. The SCADA systems I work typically require client independent QA verification and documentation of tag configuration and alert configuration. Importing/Exporting with CSV files has always been the tool for this job, but if it takes a Rosetta Stone to encode it/decode it, it’s for all practical purposes unusable.
Please take this as a suggestion, not a criticism. I know you guys are peddling as fast as you can!
I think XML format is forward-looking, and I could get used to using it, no problem. With more and more industry usage and better editing/viewing tools coming available, I think it would be a fine choice, not only for verification but also bulk imports and exports. Just please stay away from the urge to compact the data format with encoding so it is very readable.
-Thanks
Could you do both? One of the (big) reasons for the XML format is that when importing/exporting to/from other tools/programs, the data can be manipulated easily into different formats. The easiest format to work with (manually) is excel.
Maybe you can created a number of "plugins" to create files in different formats for different size=50[/size] programs
