wfc -
You are correct, the TestStand expression language as well as the "Measurement Must Be" controls for the Numeric Limit step type only support decimal, binary(0b101) and hex(0xabc) notation. The C language defines a preceeding zero as octal notation, but we cannot use that because it would break backwards compatibility for users that have entered numbers in our expression language that happened to have preceeding zeros. For a future version we are considering defining "0c" as a prefix to define an octal number and this would apply to the Numeric Limit step type, but unfortuneately this will not address your issue for TestStand 3.1 or our next planned release.
The only workaround you could do would be to implement a change in the code for the Edit Numeric Limit step type dialog box to handle the octal conversion case as you see fit. The step type is written in MSVC.
Scott Richardson