I’ve just arrived from our client’s factory. Although the system has been left working, I found a few bugs (or are they features? ) on the process:
I created a tag on KepServer with a name that started with a number (like 05TT456). When associating it with a group on FSQL, the name is prepended with an underscore (like _05TT456). Is this normal behavior? This changes the Oracle column names, and we needed the tags to have the same names everywhere.
I created a tag on KepServer that is a Byte (Siemens S7 Ethernet driver). FSQL tells me on the OPC pane that it is a Short(2). Is this (2) the number of bytes of the tag? When associating it with a group on FSQL, it maps the tag’s type to a String in FSQL and a VARCHAR2(255) on Oracle. It should be an Integer, right? I know I can choose for it to be an Integer on the Groups pane (I did it and it worked fine), but I’m trying to automate the tag import process as much as possible. Having the person configurating FSQL changing the type of 4000 tags is not an option… maybe this can be addressed with the mapping on the Oracle.xml file?
Whenever I try to create a new group with a table name that has been created automatically by FSQL and then dropped from the database, FSQL does a mess of the creation. It fails creating the table, but the table is created (and apparetly well) on Oracle. And when I try to start the group anyway, I get errors on trying to write NULL to the index column…
Any ideas so I can attack these issues?