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.

@kirill-kostin Thank you for letting us know, I've fixed the issue on our end.

@lgorence https://docs-v4.radixiot.com/clean-mango-properties-file

@BigKING please create a new thread and reference this one. This one was solved over twelve years ago! Fox

@hayden_AUS thanks for your help! Fox

@ms_brunette you're welcome! Always happy to help. Also, my apologies, angular.element(htmlelrnent), I misunderstood the jqlite reference. So HTML string or DOMElement should be the value in the element method. It will return a jQuery object. https://docs.angularjs.org/api/ng/function/angular.element Feel free to post another forum question if you are unable to find a solution via the search box. Fox

@BG meta are virtual datapoints that can return a value. Scripting datasource scripts are functions that run an alert or can send/set data to a variety of destinations. The benefit of a scripting datasource though is it doesn't cost you your datapoint count. But do note that because it's a datasource, it doesn't retain a value Also, fantastic news on your progress. I'm always about and happy to assist if you need me. Email is fine too! Fox

@sean does the user have read permission for the datasource? Fox

@BG sorry instantiated sqlClassInstance twice... Have edited the code above. Please try again Fox

@lgorence Hello Liv, and anyone else who comes across this thread. I discovered that the AlmaLinux 9 was not allowing the Mango 3 install to complete due to permissions. Even after making the mango user the owner of the /opt/mango folder the install still failed at the last module and kept trying to restart itself over and over again. I recursively set the execute permission on the mango folder for the mango user and the install completed and we were able to get to the log in screen and pick up the correct license file. That seems to have been the crux of the whole install problem. Cheers Brian

@ryanlo assuming you're using tcp/ip, check that you can actually ping the unit from your mango box. Second, confirm of the unit has a zero or one offset for the registers. Mango is zero by default, you may need to increment your register addresses by one. Fox

@ryanlo In addition to what @MattFox is saying you should also see an Event / Alarm in the UI to correspond to the event being detected. The handler should be linked to that event and as Matt said, if you setup logging correctly you will also see it in the logs.

@mkart-vrn there are help docs available. This can be exposed by showing them via the edit menu page and saving the changes. Alternatively, on the scripting datasource page. There are question marks you can click on that will render a sidebar to the right with a detailed explanation and or help docs. I also encourage you to look through the forum and see what has been accomplished by other mango power users. As for delays, there is a delay option so you can delay the firing of a script upon a trigger as well as using a cron style scheduler. There's also an advanced scheduler which you can attach event actions to for triggering scripts, running a local application, even setting point values. Feel free to raise more forum posts in user help to fill in any blank areas. I'm on here throughout the week usually. I'm currently remote however so expect up to week delays... Fox

That really helps. Setting up the new data source isn't a problem. The B part: JSON import/export - that looks like the easiest way to go. In each data point, I'd just have to change dataSourceXid and the settings under pointLocator to reflect JSON fields instead of RegEx fields. Sounds not too hard, but I find documentation is a bit lacking on the NoSQL tools. It would be useful is mango provided an easy point history import/export feature. I know in the watch-list I can export CSV, but it would be nice to have an "export all" for a datapoint somewhere that could be easily imported back in. Like an additional tab to import/export data points. Sounds more complicated than the route I'd like to go down. Keeping the XID the same wouldn't break things elsewhere. I don't know how often it happens, but maybe a future tool to move a data point to a new data source would be useful?

@MattFox Thank you very much. That puts my mind at ease a bit more now. Cheers Brian

@Mark you can, just wrap in <span> tags, there are other ways, but depends how technical you want to be Fox

@terrypacker Thanks, I will set them up using meta points as you suggest.

@MattFox When I execute your command, a container is created, but without Mango being installed. Since my knowledge is too limited, I'm going to install mango in a windows environment. Still, thank you for your efforts!

@sean You cannot query values per se, that's not the intended purpose of a time series DB. One suggestion I have is generating values and filtering the output based upon the provided timeframe, the input field, and displaying those timestamps for those records entered. The other is having a dedicated virtual datasource of virtual points whose Xids align with the accessCardID numbers and updating the corresponding datapoint everytime that accessCardID is entered into the system... Fox