PointValue with question mark(?) register
-
Hi,
I wrote a script to get a linux file size as the following json. It works fine with the script verification and realtime value showed in the DP Details screen. However no value is recorded in the history, only a question mark(?) is shown along with the timestamp. The weird thing is that the cached values showed in the datapoints details are displayed correctly as you can see in the screenshot above, but when I update the screen, the values became do a question mak again.What I am missing?
Thanks in advance
{ "dataPoints":[ { "xid":"DP_09a1df37-0dc1-4bd0-a4e7-91f2ca4efbd0", "name":"Tamanho arquivo H2", "enabled":true, "loggingType":"ON_CHANGE", "intervalLoggingPeriodType":"MINUTES", "intervalLoggingType":"AVERAGE", "purgeType":"YEARS", "pointLocator":{ "dataType":"NUMERIC", "updateEvent":"MINUTES", "contextUpdateEvent":"CONTEXT_UPDATE", "context":[ { "varName":"p6678", "dataPointXid":"DP_ca4d75a0-4ccf-48b3-b7ce-94181afd4292", "updateContext":false } ], "logLevel":"NONE", "variableName":"my", "executionDelaySeconds":0, "logCount":5, "logSize":1.0, "script":"\/\/print(` du -s \/opt\/mango\/databases\/mah2.h2.db |awk '{print $1}'`);\nvar response = com.serotonin.m2m2.rt.maint.work.ProcessWorkItem.executeProcessCommand(\"\/home\/aaguiar\/script\/tamanhoH2.sh\",5);\n\/\/print( response );\nvar valor = response.key;\nreturn valor*1", "scriptPermissions":{ "customPermissions":"", "dataPointReadPermissions":"superadmin", "dataPointSetPermissions":"superadmin", "dataSourcePermissions":"superadmin" }, "settable":true, "updateCronPattern":"" }, "eventDetectors":[ { "type":"HIGH_LIMIT", "sourceType":"DATA_POINT", "xid":"ED_f4738cec-edc8-4aa3-8aa7-bd72ffd7f18d", "name":"Limite de 1GB alcançado no arquivo H2", "alarmLevel":"LIFE_SAFETY", "durationType":"SECONDS", "duration":0, "limit":1000000.0, "notHigher":false } ], "plotType":"SPLINE", "rollup":"NONE", "unit":"", "templateXid":"Numeric_Default", "simplifyType":"NONE", "chartColour":"", "chartRenderer":{ "type":"IMAGE", "timePeriodType":"DAYS", "numberOfPeriods":1 }, "dataSourceXid":"DS_355e23e3-f46d-4e4a-bb3f-106bd7e42f22", "defaultCacheSize":1, "deviceName":"!!Teste de controle de registros", "discardExtremeValues":false, "discardHighLimit":1.7976931348623157E308, "discardLowLimit":-1.7976931348623157E308, "intervalLoggingPeriod":1, "intervalLoggingSampleWindowSize":0, "overrideIntervalLoggingSamples":false, "preventSetExtremeValues":false, "purgeOverride":false, "purgePeriod":1, "readPermission":"", "setExtremeHighLimit":1.7976931348623157E308, "setExtremeLowLimit":-1.7976931348623157E308, "setPermission":"", "tags":{ }, "textRenderer":{ "type":"ANALOG", "useUnitAsSuffix":true, "unit":"", "renderedUnit":"", "format":"0.00" }, "tolerance":0.0 } ] }
-
Hi Ava2018,
Is this a fairly new point? It looks like it's set to log on change, but all the record in the table seem like the same value? So, is there one record at the top of the point value time history? That would be because only the changed value was logged, but the polling updates would be pushed out to the open pages and update the most recent PointValueTime for the point's cache.
-
I think something on the very beggining of the scripting tests was recorded in the history and was tricking the new values. I copied the DP to a new fresh one, and it worked.
Thanks!