The purpose of this library is to enhance the API parameters for Communicable State Machine (CSM). It allows for the inclusion of various data types in plain text format.
Two more templates which include "Data: Get Configuration", "Data: Set Configuration" and "Data: Get Internal Data" states, are provided in the library. These templates can serve as a starting point for building your CSM module with the ability to access data stored in the '>> internal data >>' shift register.
- String
- Path
- Boolean
- Integer(I8,I16,I32,I64,U8,U16,U32,U64)
- Float(DBL/SGL)
- Complex(DBL/SGL)
- Timestamp
- Enum
- Array
- Cluster
- Other(use CSM-Hexstr)
For String/Path datatype, CSM Key words '->|' '->' '-@' '-&' '>>' ',' ';' will be replaced with %[Hex] String before passing, which is as same as using CSM AdvanceAPI\CSM Make String Arguments Safe.vi.
Predefined TRUE/FALSE String Pairs:
TRUE/FALSE String Pairs:
- T/F
- True/False
- On/Off
- Enable/Disable
- Active/Inactive
- valid/Invalid
- 1/0
- Open/Close
- Non-null/null
Note
For Boolean, empty string will be converted to the input prototype value
Note
Use API String - Add Boolean Strings.vi or API String - Remove Boolean Strings.vi to set your own boolean string to be used.
Note
Tag-value pair(Tag:Value) could be parsed correctly. Tag is used for readability and will be ignored during conversion.
Supported format: Normal, Hex, Binary, Octal, Hex with suffix H, Octal with suffix O, Binary with suffix B, Decimal with suffix D. Example:
- 12345
- 0d12345
- 0x1234
- 0b10101010
- 0o777
- 1234H
- 10101010H
- 7777O
- 10k
- 1M
Note
For Integer, empty string will be converted to the input prototype value
Note
Tag-value pair(Tag:Value) could be parsed correctly. Tag is used for readability and will be ignored during conversion.
Supported format: Normal Float, Scientific Notation, Special Float. Example:
- 1.2345
- 1.23E+2
- 1.23E-2
- 1.23Y (1.23*10^24)
- 1.23Z (1.23*10^21)
- 1.23E (1.23*10^18)
- 1.23P (1.23*10^15)
- 1.23T (1.23*10^12)
- 1.23G (1.23*10^9)
- 1.23M (1.23*10^6)
- 1.23k (1.23*10^3)
- 1.23m (1.23*0.001)
- 1.23u (1.23*0.000001)
- 1.23n (1.23*10^-9)
- 1.23p (1.23*10^-12)
- 1.23f (1.23*10^-15)
- 1.23a (1.23*10^-18)
- 1.23z (1.23*10^-21)
- 1.23y (1.23*10^-24)
- Special Float: `e`,`-e`,`pi`,`-pi`,`inf`,`+inf`,`-inf`,`NaN`
Note
For float datatype, empty string will be converted to the input prototype value.
Note
Default precision is 6. You can change it by API String - Set Float Precision.vi
Note
Tag-value pair could be parsed correctly. Tag is used for readability and will be ignored during conversion.
Note
Float String with Unit is also supported.
special case:
- If there is a
spacebetween float string and unit string, all strings include notation behind float string is recognized as unit string.
1.23mA : Float: 1.23m; Unit: A 1.23 mA : Float: 1.23; Unit: mA
- For scientific notation mode, any string behind the float string is recognized as unit string.
1.23E+5mA: Float: 1.23E+5; Unit: mA 1.23E+5 mA: Float: 1.23E+5; Unit: mA
Note
Unit is not supported for e,-e,pi,-pi,inf,+inf,-inf,NaN
a+bi or a-bi stands of complex data type. a and b is supporting all Float format.
Note
For Complex, empty string will be converted to the input prototype value
Note
Tag-value pair could be parsed correctly. Tag is used for readability and will be ignored during conversion.
Timestamp's string format is TimeStamp_String(Format_String). Format_String will be used to parse the TimeStamp_String.
"2023-10-11 22:54:33(%<%Y-%m-%d %H:%M:%S>T)" equal to UTC timestamp string "2023-10-11T14:54:33.000Z".
special case:
If no time string format included in string, ISO8601 UTC standard is used.
"2023-10-31T14:49:39.597Z" is valid.
"2023-10-31T22:49:39.597+08:00" is valid.
TimeStamp String(FormatString)is supported. FormatString in "" will be used to parse TimeStamp String.
Note
For Timestamp, empty string will be converted to current time.
Indexed Enum is defined as Enum Strings composed with [number] [separator] [enum String]. The following are supported expressions:
hex Number, -- as separator
- 0x01 -- boolean
- 0x02 -- string
- 0x04 -- dbl
- 0x08 -- number
binary Number, -- as separator
- 0b0001 __ boolean
- 0b0010 __ string
- 0b0100 __ dbl
- 0b1000 __ number
Decided Number, == as separator
- 1 == boolean
- 2 == string
- 4 == dbl
- 8 == number
Note
Index Number supports all integer expression.
Rule1: When Index is not Specified, the string will be converted to Enum by matching the string.
Enum = {AAA,BBBB,CCCC}
- String "AAA" will be converted to Enum(AAA), IntegerValue = 0
- String "CCC" will be converted to Enum(CCC), IntegerValue = 2
Rule2: When Index is Specified, the string will be converted to Enum by matching the string or Index.
Enum = {1- AAA,5 - BBBB, 9 - CCCC}
- String "AAA" will be converted to Enum(1- AAA), IntegerValue = 0
- String "5" will be converted to Enum(5 - BBBB), IntegerValue = 1
- String "9 - CCCC" will be converted to Enum(9 - CCCC), IntegerValue = 2
',' is used for element separator, ';' is usd for row separator. '[' & ']' are used for boundary symbol. If it's not a complex mixed data type, '[' & ']' can be omitted.
Example:
a,b,c,d,e and [a,b,c,d,e] stands for 5 elements array
a b c d e
a;b;c;d;e and [a;b;c;d;e] stands for 5 elements array
a
b
c
d
e
a1, b1, c1, d1, e1; a2, b2, c2, d2, e2 and [a1, b1, c1, d1, e1; a2, b2, c2, d2, e2] stands for 2*5 2D array
a1 b1 c1 d1 e1
a2 b2 c2 d2 e2
Note
Empty String will be ignored and the prototype input will be used as output.
Tag:Value Mode
In this mode, the input string is a list of tag:value pairs. The tag is the name of the element in the cluster, and the value is the value to be set. The tag and value are separated by a colon(':'). The tag:value pairs are separated by a semicolon(';'). '{' and '}' are used for boundary symbols. If it's not a complex mixed data type, '{' and '}' can be omitted. Other rules are as follows:
- The tag is the name of the element in the cluster, and the value is the value to be set.
- Only the changing elements need to be described, and the data consistent with the data prototype can be omitted.
- The order is not important.
- For nested clusters, the tag of the sub-cluster is the tag of the cluster plus the tag of the elements in the sub-cluster, separated by '.'.
- For nested clusters, if the tag name of the sub-cluster is unique, the tag of the parent cluster can be omitted.
- If no name is given, the string input will be converted to the first element of the cluster. This is useful to make the first element primary.
Example:
Suppose a cluster as below:
typedef cluster{
Boolean b;
String str;
U32 integer
Cluster subCluster
{
Boolean b2;
}
}
b:Onand{b:On}stands for change the input cluster's boolean b to TRUE. Other elements will keep as before.
b:On;str:abcdefand{b:On;str:abcdef}stands for change the input cluster's boolean b to TRUE and String str to "abcdef". Other elements will keep as before.
{subCluster.b2:On}stands for change the input cluster's subCluster's boolean b2 to TRUE. Other elements will keep as before. Since b2 is unique, the parent cluster's tag can be omitted.b2:Onalso stands for the same conversion.
Not Tag Mode
For Cluster, only input data string is supported. These value strings are separated by semicolons(;).
- The order of the elements is important. The first element will be set as the first element of the cluster, the second element will be set as the second element of the cluster, and so on.
- If the input string has fewer elements than the cluster, the remaining elements will remain unchanged.
- If the input string has more elements than the cluster, the extra elements will be ignored.
on;abcdef;13和{on;abcdef;13}stands for change the input cluster's boolean b to TRUE, string str to "abcdef", and U32 integer to 13. If the cluster has more elements, they will remain unchanged.
on;abcdefand{on;abcdef}stands for change the input cluster's boolean b to TRUE and string str to "abcdef". Other elements will keep as before.
Note
Empty String will be converted to the input prototype value.
Other Datatype will be treated as variant and use CSM-HexStr for data transformation.