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.

However you want.

P.S. thanks again for contributing. You rock.

After years of using prepared statements in many databases, i have to admin i have no idea. It never came up.

:) Thanks.

Re linking, there's a bit of an icon clash that has been a small thorn in the paw for a while now, but there's still no good solution.

A system event would probably be simpler.

I ended up using net-snmp locally on the box, and passing an exec command. Then via mango, use SNMP data source to query the values. An expensive hack, but works fine on a small scale.

-Dan

Hi Matthew,

I happens only for a few pages. I don't have admin rights to install the software on my pc. I will be able to do this soon and post the results.

Thanks!
this seemed like one of those problems where there is a lot more to it than appears on first glance, so I asked before diving in.

I meant create a "meta" data source, create a point in it, and give it any old script to give the point a value.

The only thing potentially wrong that i could see in the code is possible failure to create the Javascript engine, which would be an environmental thing, probably to do with the JVM. Of course, if you're not using the most current Mango version (1.6.4) that could be an issue too.

Sure, that works. :)

I wonder if any user manual (http also OK) would be available before installing full software. This time Google did not help me :shock:

This would be very helpfull for me as I have existing (other) system running in measurement-PC and I would like to make swap as short as possible

Thanks

This post has been superseded by this one: http://mango.serotoninsoftware.com/forum/posts/list/185.page.

Hi Nik,

I've personally had some issues with Ubuntu, but i'm far from being able to say for sure that's the problem. Still, i suggest trying Fedora or a Windows host for Mango to see if your serial ports stick around longer.

Also, make sure data sources and testers aren't competing for the port in the case that you have multiple data sources running. Only one running data source can own a serial port at a time. Note also that the node scanner owns the port while it is scanning.

Thanks I'll do that tomorrow :-)

Hi Dusky,

It's hard to say without knowing more about the queries you are doing. (If, however, you are asking if there are connection pooling facilities available, the answer currently is no.)

It sounds like you are doing row-bases querying. If so, it may be possible for you to use "union" clauses to combine your queries into one. This should work if your data types are all the same.

For example, you might do something like this:

select id, value from table1 union select id, value from table2 union...

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