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.

Yes, not using the NoSQL module will help, because the NoSQL module tries to store all pointValues (including Image pointValues) but the support for images was never added. i believe using MySQL or H2 will solve the problem. It is a fairly simple thing to add the functionality from the SQL Point Value Dao to the NoSQL if that gets traction. We'll keep you posted.

Update, After a bit of digging around on Google, it turns out that it was simply the fact that TCP/IP connections were not enabled by default within SQL Express. Enabled, and now working :-)

quality field means in pointvalues database table direct indicate one point is good or bad in a exact timestamt. in ALL loggingType, if one timestamt no value,this can indicate it communication error. in on_change type,we can use use "No Change" or "No Update" event detectors to indicate it communication error. but when query pointvalue in api,chart,report ,just query data from pointvalue table,we don't join the event detectors to indicate one point is bad or good in a exact timestamt.

The "Device Name" field on a data point is used throughout Mango to provide a searchable, meaningful name other than the data source and endpoint, since one coordinating data source may gather data from lots and lots of devices. The naming conflict that you mention is there, I suppose, but after a moment's adjustment you realize 'device' is a very large category.

Hi Joel, Would running as a service in this manner mean that mango would start with the PC, prior to anyone logging in? Thanks, Darragh

Yes indeed! I would encourage you to go into your Mango/overrides/properties/env.properties or Mango/classes/env.properties and change the swagger.enabled=false to swagger.enabled=true Then you can reboot Mango, login, then navigate to http://localhost:port/swagger and get a page with all the endpoints. I bet you're interested in /v1/events/list and /v1/events/active-summary

Doing the update as we speak! :-)

Hi Jenny, If I'm understanding you correctly, you would like to only send messages for certain values and conditions. This can be accomplished by using a Script, and then using points on the Scripting Data Source as output for the publisher. So your script could be... AutoWindowDoorController - Windows1Status ==> context point p if( p.value == 1 && !alarmActive.value ) { publishAlarm.set(true); alarmActive.set(true); } else if( p.value != 1 ) { alarmActive.set(false); } And create a settable, binary point called 'publishAlarm' on the script and publish it instead. Have a second settable binary point called alarmActive, to prevent updating the published point each time the script runs. The Twilio publisher was envisioned working with a Meta Point or a script, which is why there are the features to do multiple replacements as suggested in the Twilio Publisher's help documents. I removed your image so that the settings for your Twilio account aren't visible to everyone wandering by. The "Type" column is a read-only display of what module the point comes from. It looks like I may need to check that it's still working.....

By default Mango will use the system time of the computer it is installed on. On the System settings page you can see what that time zone is. If you want to set it to a different time zone you can do this in the env.properties file or you can do it individually for each user on the user management page.

Using the Mango Persistent TCP data source and publisher is pretty ideal for this. There are a number of things you can publish to a central Mango for monitoring such as a random or incrementing value. Also the Internal data source values such as JVM memory usage, and task lists. There is also a little known data source called the Log4J Data Source which allows you to turn system log messages into Alphanumeric data points. You can have an Error level and a Warning level data point publishing to the monitoring Mango. You can then have a change event detector on this so if there are any Errors that show up in the log file they will be sent to the main server and you will be notified. It's also our longer term plan to offer a hosted solution specifically for doing this monitoring and alarming and we'll probably package these features up into a simple to install and configure module so you don't need to do much for set up.

Interesting idea. We don't currently have any other way to run these reports. The event detector idea would be very useful unfortunately they are not 'modularized' yet, meaning we can't add new event handlers via a module so that is out of the question. However you could get crafty with a Process event handler. Here is the basic idea: The Excel Reports uses its extension of the REST API so you could use Curl or something else to GET the URL: {YourMangoHost}/rest/v1/excel-reports/run/{xid-of-your-report} This would run the report just as if you were to run it from the web ui.

Hello Ua, In response to your scaling issue. I have taken Joel's advice previously and have used the Meta data source to good affect. Our data loggers supply a raw value from 0 to 20000 representing 0 to 20 mA from the sensor. The data could actually be just about anything, i.e 0 - 20 mA = 0 - 100 Bar or 0 - 60 meters per second etc... it all depends on the sensor attached. We have created a data source for the data logger and then another meta data source that uses the raw data as its source. In the meta data source we apply the following script: [image: ngD0Q6L.jpg] Just change the first 4 numbers to change the scaling factor. The above example will move the decimal point to the left one place. But the script will work with any scaling required not just factors of ten. Also we have named the data source as raw under the VAR column, hence raw.value in the equation. Just change the equation to match your naming convention. I hope this helps. Cheers Brian

Yes, You can : go to edit data point, go to second section of data point details - Property Template and click to edit templates , change what You want and save as new templates. In fact You can save many templates for more groups of data points

No problem. I've just realised that crontab will not allow for updates faster than one minute, so you might like to just make it HH:MM and forget about the seconds. You might also like to set the point properties to 'do not log' with a cache size of 1 as there is likely no benefit to storing these values on disk or more than one record in memory. Cheers

Hard to say what is going on but it sounds like a networking issue. Are all the devices on the same subnet? You can check on the system setting under the BACnet local device options and try some different configurations there with the local binding address.

You would need to write a new Data Source Module for Mango using that Api. This will require a Java developer to write the code.

Address Already In Use means there is something else using port 8080 or what ever power you have Mango configured for. Open your /classes/env.properties file and change the port number. Also ready the instructions in the file about coping the file to /overrides/properties so your changes persist during an upgrade. Let me know if that works. Joel.