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.

The message could come from multiple places, but in general it means that the TCP connection to your modbus equipment was closed, and not by Mango. When you are using the keep-alive, Mango detects the condition and attempts a re-connect upon the next polling. If the stream was closed during a poll, the remainder of the poll will fail. Overall it indicates network problems.

Hi CAHA, It's a two step process (assuming you have Mango already pulling data from your sensor). Edit the point by adding a point event detector (either a high limit, a low limit, or both in your case), and save. Then, head over to the event handlers page and add an email handlers to your event(s). That's it. The division between events and handlers allows 1) events to generated in arbitrary ways, and 2) events to be handled in multiple ways.

I upgraded from tomcat 5.5.17 to the latest 6.x and this problem has disappeared.

Of course!

I had to enable logging on the data point edit page and all is working properly now. Thanks

The discussion board software apparently removes things it considers suspicious. The content of the <a> link should be: href="#" onclick="mangoLogin()"

How much memory does your host system have? You can adjust the maximum heap size of your instance with options such as -Xmx. (Which you can set in your Tomcat start scripts. Look for the JAVA_OPTS setting.) I believe the default max heap size in Java is 64MB. If you wanted to change this to 256MB, you would add the option "-Xmx256M".

Hi Josh, No, there is currently no way to "lock" a chart open. Interesting idea though..

I meant to post a reply earlier but I forgot. I rebooted the server and it went away. It must have been some kind of persistent little fluke because I had tried that already.

UPDATE! After working for some long hours with the mfg :(, I determined that it might work better if I use SNMP.... Success!!! :D In about 10 minutes I had the whole thing working better than our current software! I'll be playing with it over the weekend and most likely complete the conversion to this next week. I do have another question, but I think it might belong in another category or at least it's own thread. Thanks again for all the help!

I have now received an escalation notice. It came out of the blue yesterday when i wasn't working on mango but it happened to still be running. Thanks for the list of things to check and breakpoint suggestions. I have all the log level settings in log4j.xml set to DEBUG as I understand this is the most verbose setting but I didn't see anything about email being sent although it does generate a lot of output and I could have missed it. It might be a couple days before I get back to this but I'll keep you posted Craig

No, you're not doing anything wrong. There are image renderers for graphical views for numeric and binary, but for multistate there is only the basic renderer. We will add a such a thing for the next release.

Looks like I will have to buy the commercial version Thanks Keith

If you are experiencing out of memory errors, it indicates that, for the way that you are using Mango, your Java VM needs to be configured to use more available memory. (Java by default will not consume unlimited amounts of RAM; startup options need to be set to determine the maximum memory it will use. The usual default max memory is 64M). Depending upon how you start Mango, you need to add a Java option to set the maximum heap size. For example, if you use the Tomcat startup scripts you can set the JAVA_OPTS variable. See your startup script for details. The option to add is -Xmx followed by the desired memory amount. For example, to set the max memory to 500M use the following: JAVA_OPTS=-Xmx500M General information on JVM tuning can be found here: http://edocs.bea.com/wls/docs61/perform/JVMTuning.html

TCP/UDP within Mango is supported by Java. Pretty typical stuff. As for communicating with your devices, Mango is capable of using many protocols (with new ones being added frequently). With respect to your list (although i'm not sure what the "server" part of "server/http..." is), Mango can receive HTTP requests with point data in the parameters, and can also talk to SQL databases. Each protocol implements its own ways of communicating different types of data, so there is no quick answer to your question about "communication structure". Once the data gets to Mango though, each data stream becomes a "point", which has a data type. Current data types supported are binary, multistate, numeric, and alphanumeric. I'm not sure what exactly you're looking for in an answer, but i'm pretty sure Mango can do whatever you need to do with that data. As for GPS data, we have been considering adding complex data types (such as lat/long) for some time. We're basically just waiting for enough users to say they want it.

Data in blob fields are Java object serializations. The only practical way of viewing them is using Java code to deserialize. The only objects that are serialized in this way are data source and data point definitions, which are very application specific anyway. For background... Originally, tables were defined for each type of data source and point such that the information was stored in a more traditional way, i.e. each distinct piece of data in a distinct field. However, as more data source types were added to Mango it quickly became a significant maintenance issue. The current storage technique of using blob has a number of strong advantages, with really the only downside being the fact that - as you've noticed - the content is inaccessible via SQL.

Hi Roberto, Mango can read from an external database using the SQL data source. Out of the box it can connect to a MySQL database, but others can be implemented by finding the appropriate driver (usually just a jar file that you can add to WEB-INF/lib). If you are on a Windows platform, it is possible to use an ODBC/JDBC driver to connect Mango to and ODBC data source. In Windows you can then set up various things - like flat files, Excel spreadsheets, Access databases - as your ODBC sources. Might be worth a try. By finding the appropriate drivers (which are typically easy to find), you can also connect Mango directly to Oracle, MS SQL Server, Postgres, etc. Your alternative to having a database intermediary is to connect directly to your A/D converter processing board, assuming it supports some communications protocol like Modbus, BACNet, 1-wire, etc. Do you know? Once you've decided on a connectivity strategy, i can help you with the details.

Hi Craig, No, the device id currently does not have any other purpose than to check against the white list. If you have multiple devices of the same type which all deliver the same information (multiple wind sensors for example), you can create separate HTTP receiver data sources for each, and be able to segregate their data using the device id.

That is likely related to something else. Please try again and see if they appear now. If not, please make note of the icon URL.

Hi, If you have recently updated your Mango M2M installation, be sure that you followed all of the upgrade instructions on the [url=http://mango.serotoninsoftware.com/download.jsp]download page. In particular, check that you have properly installed the RXTX libraries that have replaced JavaComm.