goovView Trends Float variable too long

[KosmosDesign]

I took the EPIC class last year, August class, I asked how to truncate float variables in groovView trend graphs. Terry said he had a solution in your forums. I couldn’t find it.

Please give me directions to shorten the decimal places on float variables when using a trend in groovView. 15 decimal places is too much, not just for groovView trends, but also when I send an event as a text it makes it difficult to see on the phone screen.

I’m using EPIC PR1 with Firmware 3.5 and PAC Project 10.5b running the strategy on the EPIC PR1, with a temperature thermocouple on the PAC R1 controller with firmware R10.4d for my test input.

Thanks, Larry

[Beno]

One post per topic is enough, so I deleted your other.

The command you need in the computed tags is toFixed(2)

[KosmosDesign]

Ben, Thanks for responding quickly!

Can you give me an example using toFixed(2) in OptoScript?

Larry

[Beno]

What was the error you got when you tried?

I grabbed a tag that had 4 digits and used a computer tag to make it toFixed(1).

Here is the computed tag.

[KosmosDesign]

Ah, I am using OptoScript, not javascript. Are you suggesting I use NodeRed to modify my float variables? Then put it in a groovView trend graph? My goal is to look at a groovView trend graph, interactive, and not see 15 decimal places, just 1, 2, or 3 decimal places when I hover over the pen lines.

[Beno]

@KosmosDesign

I asked how to truncate float variables in groovView trend graphs.

You only need them truncated in the groov view trend, so use the computed tags as you need.

Nice and neat.
No OptoScript, no Node-RED, very quick and clean.

[KosmosDesign]

Okay, I just figured out that’s a feature I didn’t know groovBuild had to offer.

Groov View Computed Tag: Integer → String Status

Computed tags in groov View are perfect for quickly transforming some data to either a different unit (e.g. °C → °F) or to a different data type entirely, like integer 0/1 → Boolean true/false. In this post I’ve written up how to expand on this using the JavaScript case-switch statement to turn a range of values into a status. In this example I am using integers and strings respectively, but this could work for any data type on either end just by modifying the input and output. Here’s the resu…

I am learning all the time with Opto 22! Thanks for the support today, Larry

[KosmosDesign]

Well, not so quickly. I can’t select the new computed tag in a trend graph because it is a string, it’s grayed out. Am I missing something? Larry

[Beno]

Sorry, too much going on here.

[KosmosDesign]

Perfecto!

It’s working as expected now, thanks again.

[Beno]

Thanks very much for dropping back and letting us all know.
Sorry the very staccato replies… The stuff thats going on a typical Sunday… < bleh >