Messages posted by: mlohbihler

Mango doesn't (yet) support the parsing of arbitrary data streams. Is the data formatted in any particular protocol, or is it something proprietary?

The data is GPS coordinates? Mango supports binary, numeric, multistate, string, and image, but not (yet) lat/long. You could, however, store each component as its own point.

1) Create a meta point that calculates the difference between the two points
2) Add a high limit detector on to the meta point
3) Add an event handler to the high limit detector that turns on your pump.

You are already getting data and reports? What is it you want Mango to do for you?

Oh, and make sure you have a build.properties file. See "sample-build.properties" for an example.

Make sure you run the "createConfigFiles" target before "deploy".

Good question, and honestly i don't know. It's a complete guess, but i would first suspect the router since the device should report in it's details whether it supports segmentation or not. If you have traces of the communication it would help in troubleshooting.

Sounds good Mike. Let me know how that goes.

Also, v1.8.0 is out now, which has the configurable min/max settings for logging. You might give that a go too.

Did you create the tables before running Mango, or let Mango create the tables itself? Mango automatically checks if the users table is missing and if so creates all tables. Otherwise it checks what version the database is and upgrades if necessary.

If you ran the create script yourself, the database will not have been properly set up, which would result in this error.

I use axis because i know it better, and it has ANT support (which i couldn't find in less than 5 minutes for JAX). But if someone else is doing the work it doesn't matter to me.

I can work with patches or real source. Doesn't much matter. Also, if you've added message_de properties please provide the en equivalents (because you don't want to trust my - i.e. Google's - de to en translations).

Anytime is fine. Or are you asking when i'll get it done?

Of course. The problem is that i have no equipment to test with, so you will need to officially support this data source.

Mango is primarily intended to act as a server.

I gave this a bit of thought. The idea would be to make a queue in the point locator, and when a set point occurs add some sort of message to the queue. When a request arrives, add the contents of the queue to the response. There are a couple of issues though:

1) There is no concept of confirmation of receipt. To address this, items in the queue would need to be marked as "sent", but not yet "confirmed". The next request received from the device would provide the confirmation. (This would also provide a channel for error responses to be returned to Mango.)

2) A set point action becomes potentially long-running, and also interlaced with regular point reads. Let's say a point currently has the value 10. I set it to 15, causing a message to be queued for the device. (The little wrench icon is now indefinitely displayed beside the point, indicating a set in progress. This itself becomes a nuisance since everywhere else set points occur synchronously - this approach is asynchronous.) When the next request is received from the device, let's say the point value is 7. This value will presumably be saved first even though the set point of 15 was apparently issued earlier. This effect could cause non-intuitive behaviour from the data source.

Sorry, you're kind of on your own with this. If there were sample code around it probably would have gotten done already...

Hi Fred,

That's a good question. I don't believe there are any specified requirements in this regard.

But when we look at the WhoHas service, there is a device id range (meaning your device id should be consistent), and there is a Choice object which can be either object identifier or name. So, theoretically either should do, but for maximum compatibility they should probably both remain the same for your object.