Template:SysCAD Tag Changes 135 to 136
Changes affecting various types of tags and tag management new to SysCAD 9.3 Build 136.
Model Tags |
Stricter rules for naming of Model Tags. You can no longer use '{', '}', ' | ' and ':' when creating or changing model tags. The maximum length of Model Tags has been reduced from 62 to 50. If either of these issues are encountered at project upgrade they are listed as problem tags. You are not forced to change these immediately, they continue to be allowed. It is recommended that the tags are changed. In some cases if these tags are referenced or used in controllers they can cause errors. It can be better to fix the tags in the original model before upgrading to avoid any of these issues. | ||||
Species | Require QM, MF and M in some full species tags |
| |||
Main Species tags Case Sensitive | The species part of tags used in a Stream, Image or Content are now case sensitive. You can now reference P_001.Qo.QM.Co(l) and P_001.Qo.QM.CO(l) separately. | ||||
Stricter Species Tag Names | Species tag naming is stricter. Key changes include (see Species Tags for full details):
If there are any problem species tags in your project, these need to be corrected
It is recommended that these changes are made in Build 135, prior to upgrading of the project. | ||||
Species tag conversion |
Species tag conversion (%) may require a more specific conversion unit. You may get a warning such as: (%) no longer allowed change to (%Sol). For example the unit (%) is no longer an option for some species properties and should be replaced with more specific units of measurement such as (%Sol) or (%Liq) or (%Vap). An example of a full tag is component mass fraction in the liquid phase "My_Pipe.Qo.CMF:LPh.H2O (%)" is now "My_Pipe.Qo.CMF.LPh.H2O (%Liq)". | ||||
Full Tag Changes | Changed Tags | Many tags have been renamed either to achieve consistency across different models or to provide a better description of the tag. Both short and long tags have been improved. The use of _ has been reduced. Begun applying consistent use of abbreviations (e.g. "Reqd" rather than "Rqd" for "Required"). Where "Reqd" is used, generally use this at end of full tag.
| |||
Discontinued Tags | A few tags that were rarely used or are from very old versions have been removed. In this case a new tag does not exist and these are reported as unknown tags. The user will need to delete these tags or find an alternative tag. | ||||
Pipe 'Fxd_dP' pressure boost/drop tag |
In Build 135 the tag 'Fxd_dP' used for pressure drop and boost depending on the pressure change method selected. In Build 136 there are now separate tags 'PDropReqd' and 'PBoostReqd'. So any use of 'Fxd_dP' needs to be manually changed to the correct tag. A warning message is given by the pipe model whenever the old tag is used to set a value, however the source is unknown. This could be by controllers, Excel, etc. | ||||
PlantModel Activate/Deactivate Flowsheet Tags | Activate/Deactivate Flowsheet Tags have changed in SysCAD 9.3. These tags on Plant Model - Flowsheets tab are numbered differently and sorted alphabetically by name. If these tags are used to activate or deactivate flowsheets via external packages (such as MS Excel) their use needs to be reviewed and updated before use. | ||||
UnitType rather than ClassId | On the Info tab page for all models, the tag "ClassId" has been changed to "UnitType". And "ClassGroup" has been changed to "UnitGroup". Where these are used in TagSelect statements in Excel these will need updating. | ||||
$SDB Tag Changes |
$SDB tags with parameters no longer work. Due to changes on Species Properties page, the tags have changed and can no longer include a temperature and pressure specification. For example "$SDB.H2O(l).msSf(550.00,200.00) (kJ/kg.C)" will give "tag not found" error. In PGMs use the Species Database Class instead. | ||||
Audit and Links pages Tag Changes |
Almost all models have a Links and Audit tab page. Some tags have been updated but importantly the grouping of tags into sections has changed resulting in many 9.2 full tags for these pages no longer being recognised or auto-upgraded. If these tags are used in your project or reports they will not be recognised as valid tags and will need to be corrected. | ||||
Managing Tag Changes |
|