64-bit float or Int in trends and display pages

There's a Cicode function in the Plant SCADA Toolbox that works for 64 bit unsigned integers:

softwareforums.aveva.com/.../display-unsigned-int64-values

Hi Eric Black ,

Thank you.

This solves the display issue. but what about using this value in trends, is that possible?

Probably not, since the function returns the 64 bit value in a STRING. However, there's a possibility that the trend server will convert it to a 64bit floating point value (which could mean some loss of precision)--you'd have to try it.

I forgot about this code for 64-bit REALs:

softwareforums.aveva.com/.../reading-64-bit-double-4-register-tag

Eric Black 

I tried configure a string as a trend but with bigger numbers (larger than 32000 approximately) the trend value is N/A.

I found in Cicode the real is 64-bit. Can I use the Cicode real as a trend?

Yes, you can trend a 64-bit REAL returned from a Cicode function. In this screenshot, I set up a trend tag, GetReal2, to record the value returned from the GetReal Cicode function I wrote. 

I set the default display Format using the short notation: 1.15, which means 1 whole digit, plus 15 decimal places. Process Analyst will not show that many decimal places, though. 

I set the Scale to the minimum and maximum values I wanted to record. If you don't do that, it defaults to 0-32000 since you're not recording a scaled variable tag. If you need a larger number than you can type in, I believe you can use scientific notation.

I used the TrendReader utility (available from the Toolbox: softwareforums.aveva.com/.../trend-reader) to view the raw data in the trend file to verify it was recording 15 decimal places, or 15 total digits, as expected for a 64 bit REAL.

Actually, it looks like the short-form format notation 1.15 didn't work...it just gave 2 decimal places (in Process Analyst) instead of 15. So, you could set the format to #.######### for the most decimal places or ########### for the most whole digits. That does not affect the precision of that data that's recorded...just how it's displayed by default.

Thank you. It worked as intended.