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.

@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.

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.

@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

@ryanlo To answer your initial question, the default login is still admin : admin. The easiest way to do a reset would be to stop Mango, move the database (move it to root ~/) from the /opt/mango/databases/ directory (from directory use, mv mah2.200.* ~/ command), then restart Mango. Similar direction could be found on our document site, you will not need to do the restore since this is a new unit. Thank you!

@MaP Understandable, that's why I went with the reverse proxy route, using ip tables is too low level in the OSI for the CORS related issues in the application layer.
You may be able to set the env.properties to set the ip address of the interface you're trying to access to force it to only listen on that host ip address. See if that bears any fruit...

Fox

@emeinig

I got it resolved with a workaround. I'm going to post what I did for posterity and to hopefully help anyone who might come across the same issue in the future.

What I ended up doing is creating a scripting data source. The datasource uses Rhino as its scripting engine so you can use some Java in it. With the Java, you can read/write to files and leverage the "Everything is a file" philosophy in *nix systems.

The code:

// import the file reader var FileReader = java.io.FileReader; var BufferedReader = java.io.BufferedReader; // import the writer. We must use OutputStreamWriter to write to device files var OutputStreamWriter = java.io.OutputStreamWriter; var FileOutputStream = java.io.FileOutputStream; // Be careful because this could change on us depending on how many USB devices // are plugged in var serial_port = "/dev/ttyUSB0"; // Initialize a bunch of blank strings to store measurements var max_time_measurements, temp_and_pressure, wind_attrs, solar_and_precip = new String(); // Set up the writer var file = new FileOutputStream(serial_port); var output = new OutputStreamWriter(file); // Set up the streamer var fr = new FileReader(serial_port); var br = new BufferedReader(fr); // Write the measurement command to the serial port and flush to ensure the // buffer is empty for the next command. output.write("0M!\r\n"); output.flush(); // The sensor takes around 3 seconds to return 9 values, so we sleep for 4 // seconds to give it a generous margin RuntimeManager.sleep(4000); // Now we write our data commands to get it all. output.write("0D0!\r\n"); output.flush(); output.write("0D1!\r\n"); output.flush(); output.write("0D2!\r\n"); output.flush(); output.close(); // readLine will read the return values max_time_measurements = br.readLine(); solar_and_precip = br.readLine(); wind_attrs = br.readLine(); temp_and_pressure = br.readLine(); //split the 0D0! result var solar_and_precip_array = solar_and_precip.split("+"); solarRad.set(solar_and_precip_array[1]); precipitation.set(solar_and_precip_array[2]); lightningStrikes.set(solar_and_precip_array[3]); //split the 0D1! result var wind_attrs_array = wind_attrs.split("+"); windSpeed.set(wind_attrs_array[1]); windDirection.set(wind_attrs_array[2]); gustWindSpeed.set(wind_attrs_array[3]); //split the 0D2! result var temp_and_pressure_array = temp_and_pressure.split("+"); temp.set(temp_and_pressure_array[1]); vaporPressure.set(temp_and_pressure_array[2]); atmosphericPressure.set(temp_and_pressure_array[3]);

The code isn't the prettiest or most elegant but it does work. Just make sure you have the necessary variables created as data points and that they're settable and you're all good to go.

@tomatopi We are still working on documentation. I know it has been a very slow process but we are adding what we can to the doc sites (v4 and v5) as well as adding scripts to our script-examples in GitHub.