pete.long
My feedback
-
4 votespete.long
shared this idea
·
-
3 votes
An error occurred while saving the comment pete.long
shared this idea
·
-
315 votes
Reopening this suggestion to collect additional feedback.
pete.long
supported this idea
·
-
172 votesEVALUATING · 22 comments · PI Server » Analytics & Calculations · Flag idea as inappropriate… · Admin →pete.long
supported this idea
·
-
9 votespete.long
supported this idea
·
-
16 votespete.long
supported this idea
·
-
3 votespete.long
supported this idea
·
-
1 vote
An error occurred while saving the comment pete.long
commented
Yes, ran into this a few times - helpful when you need to have the extra digit when your 'equal-to' direction is different than the default for the multistate, e.g., you need to set to 5.49 and alarm at 5.5. I know it takes the 5.49, but anyone looking can't tell because it rounds up in display to 5.5.
-
1 vote
An error occurred while saving the comment pete.long
commented
This happened twice again today
pete.long
shared this idea
·
-
88 votespete.long
supported this idea
·
An error occurred while saving the comment pete.long
commented
echoing sentiments, a simple drag and drop works for the initial build, but subsequent updating is tedious.
-
134 votespete.long
supported this idea
·
-
147 votespete.long
supported this idea
·
-
159 votesEVALUATING · 1 comment · PI Server » Analytics & Calculations · Flag idea as inappropriate… · Admin →pete.long
supported this idea
·
-
190 votespete.long
supported this idea
·
-
7 votes
For this particular use case, you should be able to use the TagTot() function which executes at 6:00am with an output timestamp override for 5:30am. It’s not clear why you’re using output as input. Can you provide an example?
pete.long
supported this idea
·
An error occurred while saving the comment pete.long
commented
One example of crazy time stamp shifting would be lab samples. Samples from the day before are tested some time, any time, later in the day or sometimes a few days later with the time stamp forced back to match the sampled time (i.e., using PutVal or DataLogger). The analyses need to wait for the samples to be entered, but then refer to them at the sampled time then apply it's override for final synching of the output.
-
2 votespete.long
supported this idea
·
An error occurred while saving the comment pete.long
commented
I concur : )
-
3 votes
An error occurred while saving the comment pete.long
commented
We're guessing the red squiggly underline isn't there because there are no characters to underline. Yes, a more obvious identification of the expression in error would be appreciated!
pete.long
supported this idea
·
-
54 votes
An error occurred while saving the comment pete.long
commented
Yes, being able to compare a collection of attributes in a single trend vs. several individual trends would be very useful!
pete.long
supported this idea
·
-
15 votes
An error occurred while saving the comment pete.long
commented
The original request sounds 'manual'. Another option, i think James alludes to, would be a single trend 'collection'.
For my immediate thought, color wouldn't be an issue, but the trace identification would. If you're comparing the "temp" of 30 assets, 30 traces labeled "temp" is of no value - need some way to get identification of element.pete.long
supported this idea
·
-
83 votespete.long
supported this idea
·
(Not sure why it won't take the underscores and randomly italicizes the two tuning parameters, but you know what I mean)