Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Got it thanks.

A multi-state meta data point would probably be your easiest option.

Add the 4 binary data points as context points. The script would look something like this -

var a = contextA.value << 0; var b = contextB.value << 1; var c = contextC.value << 2; var d = contextD.value << 3; return a | b | c | d;

If you set it too high you'll be more likely to crash a browser.

Hi Phil,

The two errors were from two different attempts. The first was placing the new zip file in the Mango directory and the second was tail -f for the log when ruining a stop/start.
As you mentioned, I look into the ports and it seems like this may be the issue since mysqld.exe is listening on port 8080 and mango is also on 8080. I will change the ports as recommended. Thank you.

Solved -
Accept point attribute updates must be enabled on the receiving data source.

@wingnut2-0 said in Use Watchlist to query for multiple datapoint History:

are you referring to :8080/ui/watch-list/

Yes.

Glad you figured it out! You could have done print(pointsList[k].runtime) to see the functions or what sort of thing it was, too.

@sbaik said in Button graphic layover:

@jared-wiltshire said in Button graphic layover:

@sbaik It doesn't have to be used in conjunction with a <ma-button> you can use it on any element/component. Try it out.

I must have tried to use it on other components before it was added as a directive. It works perfectly now. Thanks

No problems.

@pikey4 said in Menu & Pages:

Also have found that if I accidentally select Root - Top Level as a parent item on anything, it wipes the entire menu back to defaults. Which I have found out the hard way.

I was not able to reproduce that easily. So, if you have further observations on how to make that happen they may be useful.

Thank you, Phillip - Working now.

@jared-wiltshire said in Dashboard Designer Choose page to edit unresponsive:

@sbaik I've released dashboard designer v3.4.2, can you try that version for me please.

Both switching between pages to edit and going from markup back to page does not create any error and functions fine.

Thanks Jared!

@mattfox Thank you for sharing that code.
As of this project, I don't think it would be cost effective for me to learn and redo all the pages just for the drag to zoom function on a chart.

That enables one to handle multiple event types with the same event handler, not only point event detector event types. There is not a way through the UI to configure that sort of situation yet, but you can import it already and it'll work. It would be many-events-to-single-handler instead of single-handler-to-many-points.

Looping over points and using the set() function is the only way to set multiple values from a set point handler. You can still construct the context (which should work automatically with the snippet I shared) through JSON via the "additionalContext" property of the set point handler.

You guys are awesome :)
Thank you

It worked perfectly! The module is working now. Thank you.

@jared-wiltshire Thank you very much, now I am clear on what I will do thanks to your help.

Hi BG,

That looks like a fine boot (ignoring the connection timeout to the store). I would wonder if perhaps he has a browser extension like an adblocker that maybe blocked a script? You could try the /login.htm page (although that may only get you one step farther, as you'd probably have to navigate to an old UI page like /data_point_details.shtm or you'll be loading the new UI again, that spinning circle on grey).

To find the cause, you probably need to have them open their browser developer tools and examine if there is an error while they are loading the grey spinning circle and report back.

Hi psysak,

I think having the importer check to see if the value exists is a possible and not incorrect direction. You should be able to import whatever classes you like and use them however you like. This may be the right time to use a com.serotonin.m2m2.rt.dataImage.PointValueFacade: https://github.com/infiniteautomation/ma-core-public/blob/main/Core/src/com/serotonin/m2m2/rt/dataImage/PointValueFacade.java

There would be a hacky way of getting that information more available to the CSV importer somewhat simply by adding a point to the data file data source in question, and then updating that point's "Identifier in import document" through a meta point triggered by the new data imported.

var timePoint = JSON.parse(JsonEmport.dataPointQuery("eq(xid,DP_time_informer)"))["dataPoints"][0] timePoint.pointLocator.fromIdentifier = String( targetPoint.time ); JsonEmport.doImport( JSON.stringify( { "dataPoints": [timePoint] } ));

Then changing the importer with something like...

private long lastImportTime; @Override public boolean takesPointIdentifiers() { return true; } @Override public void setIdentifiers(String[] identifiers) { //super.setIdentifier(identifiers) if you want this.identifiers = identifiers for(String s : identifiers) if( !"".equals(s) ) { //Presuming all other identifier fields are empty lastImportTime = Long.valueOf(s); break; } }

It could also be that the best solution is to modify the data file importer to import a digested data set into an alphanumeric point. Say, pick some format to encode the last ten days into an alphanumeric point, and then use a script to digest it farther and check if the value for that day / time already existed.

var valuesList = alphanum.value.split("~"); //5@15~10@20 //iterate valuesList, split the time from the value and set to the end point for(var k = 0; k < valuesList.length; k+=1) { var valuePair = valuesList[k].split("@"); output.set( Number(valuePair[0]), Number(valuePair[1]) ); }

I didn't test any of that, but it should work....

Edit: Also, if using NoSQL this shouldn't be an issue. The date should always resolve to the same millisecond and it should overwrite the previous value at that millisecond.