See these examples available in Appendix B: Note: The output point itself is populated with a copy of the data SourceTag whether the output operation was successful. Otherwise, the output tag will receive a digital state of Bad Output. Mapping of Value and Status Data Output – For output of data in the direction from PI to RDB, no fixed table structure is required. Corresponding placeholders are used for the intended data output. Although mapping of the placeholders (VL, SS_I, SS_C, etc.) to RDB data types works similarly as for the data input (see section ), some variations do exist. Following paragraphs list the differences. DIGITAL Tags Digital output tag values are mapped only to RDB string types. This means that the corresponding field data type in the table must be string, otherwise explicit conversion is required The following table shows the assignment of CAST(value_exp AS data_type). value placeholders (VL, SS_I, SS_C) for a Digital tag: Digital Output Tags Can only be Output to RDB Strings PI Value VL SS_I SS_C Field Type String Field Type Integer Field Type String or Float Digital state is NOT in <Digital State 0 "O.K." the error range <String> defined by /SUCC1 /SUCC2 start-up parameters Digital state IS in the <Digital State String> 1 "Bad Value" error range defined by /BAD1 /BAD2 start-up parameters See this example available in Appendix B: Examples Float, Integer and String Output Tags Value and Status Mapping – PI Value VL SS_I SS_C Field Type Numeric Field Type Numeric Field Type String or String Value NOT in error <Value> 0 "O.K." Digital State < Previous Value> <Digital State> <Digital State String>
See these examples available in Appendix B: Note: The output point itself is populated with a copy of the SourceTag data whether the output operation was successful. Otherwise, the output tag will receive a digital state of Bad Output. Mapping of Value and Status – Data Output For output of data in the direction from PI to RDB, no fixed table structure is required. Corresponding placeholders are used for the intended data output. Although mapping of the placeholders (VL, SS_I, SS_C, etc.) to RDB data types works similarly as for the data input (see section ), some variations do exist. Following paragraphs list the differences. DIGITAL Tags Digital output tag values are mapped only to RDB string types. This means that the corresponding field data type in the table must be string, otherwise explicit conversion is required CAST(value_exp AS data_type). The following table shows the assignment of value placeholders (VL, SS_I, SS_C) for a Digital tag: Digital Output Tags Can only be Output to RDB Strings PI Value VL Field Type String SS_I Field Type Integer or Float SS_C Field Type String Digital state is NOT in the error range defined by /SUCC1 /SUCC2 start-up parameters <Digital State <String> 0 "O.K." Digital state IS in the error range defined by /BAD1 /BAD2 start-up parameters <Digital State String> 1 "Bad Value" See this example available in Appendix B: Examples Float, Integer and String Output Tags – Value and Status Mapping PI Value VL Field Type Numeric or String SS_I Field Type Numeric SS_C Field Type String Value NOT in error <Value> 0 "O.K." Digital State < Previous Value> <Digital State> <Digital State String>
PI_RDBMSPI_3.21.4.30.docx