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.

I did the following step if I remember correctly.

Add one data point (offset=0) for Modbus IP publisher. I works. Add two more data points. Only offset=0 is working. The other data points are 0. Remove all data points, except offset=4 and set to offset 0. It works again. Add back the previous data point which was offset=0 to offset=4. It works.

Do something like steps 4 for others to make it work. It seems to me that the data points has to set to offset=0 and then change to other offset value to make it work. But I am not very sure.

ray,

Thanks for pointing this bug out. I have created an issue for it in our Code repository: http://github.com/infiniteautomation/ma-core-public/issues/147

It will be fixed in the next release.

Hey,

I want to run Mango on Kubuntu 13.10.

I installed/moved to described points following files/applications:

librxtxSerial.so: save in <jdk1.6-home>/jre/lib/i386 RXTXcomm.jar: save in <jdk1.6-home>\jre\lib\ext apache-tomcat-6.0.20.tar.gz mango-1.12.5.tar.gz

Well, I have a feeling there could be a better solution, but you might be able to solve this using a point link. The idea would be

Select from your database into the value point. Create a second SQL point that sets a timestamp value to some useful place in your database. Create a point link from the value point to the timestamp point, and use the pointlink to turn it into something like ('src Pnt Name', timestamp) to set that value into the database (via the second SQL point). Build you select to reference that stored timestamp so that you get the right point.

It's not the most elegant solution, but it should ensure that you're getting new-er values while still ensuring you're not just getting the new-est.

Yes - this should help.
Will let you know.

Thanks!

I tried it on both ver. 2.2 and 2.06. It came with the same result.

Hi Joel,
The session time out is set to 2880. I have tried setting up a timer triggering a browser reset but this doesn't help. Only the mobile app is affected.

Cheers,
Matt.

Thanks for your help Joel. Seems to work a treat. It would be nice if all this could be integrated into the data point down the track though. It would make scalability much less if an issue as for each data source you wouldn't need 2 extra points per event.

Cheers,
Matt.

This is for sure possible but your question is very general. We would need to have details about how we need to interface with the files and what Mango needs to do. I would assume there would be some documentation you can provide?

Joel.

Thank you for the workaround and I think it will be a good temporary solution.

Please consider a permanent fix in the next coming release.

BR,
Ricardo

ok. thankyou

Hi all,

I am using Mango to get MODBUS data from various sources, including RTU's residing on Xbee nodes via a Digi Connectport X4.

I would like to POST data to the Etherios cloud using the Mango HTTP sender publisher, and have successfully tested this using HTTP POST with a Python Script.

However, I am unsure as to the format of the Static Parameters in the Mango HTTP sender properties.

The path is http://<hostname>/ws/DataPoint/one
I need to add the following snippet of the HTTP POST method to a KEY:

<DataPoint>
<staticId>one</staticId>
<data>42</data>
</DataPoint>

I cannot use just the two entries:
KEY=data and Value=42
KEY=staticId and Value=one
Somewhere I need to add the "DataPoint" header

Obviously the value "42" would be where I put the Mango point "Parameter name", but
I am first trying to send just a static value.

The "staticId" is the Etherios Data stream ID, and remains constant.

Can anyone shed some light on this?

Sending the data (what I'm thinking of as the request) is not the issue. You could send any data by using the Point Identifier in the data point details as the Device ID # and setting values to that point. Unless the data returning from the device also is fixed (which would probably make it uninteresting) the checksum will not be fixed and we'll still have a problem of telling one message from the next, or knowing if we've finished reading a message.

Hi Joel,

I have tried clearing cache and have even used another browser. The user icon in Dglux only has the option to logout. This is true on both internal and public IP's.

Thanks

Duncan

It would be really easy to remove the share button from the User Interface, you should be able to do that in the .jsp file but this would remove it for admins as well. You could always use the Import / Export to update the shares. We are planning on making some improvements to the User Management system in Mango and could probably include this as an option.

Thanks for the idea,

Joel.

We have an service for Mango that works under Ubuntu and might help you with your application. I've attached the file for review.

The only thing that we are aware of is that depending on which user starts Mango the GUID can be different. This is something we plan to resolve. I'm not sure what would have happened in the OS update that would have changed the GUID. When you purchase a license and if you need to Move your installation to another computer or your GUID were to change it's not a problem, we will issue you a new license for no charge in this case.

In general once Mango is installed and running with a service the GUID will never change.

Joel.

Attachment: download link

You can modify these properties in com.serotonin.m2m2.vo.AbstractVO in the 'validate' method

This is not a DGBox forum.

Any object type CAN have a Description property, but it is optional. Similarly, there is nothing wrong with the fact that your code asks info on vendor object types, what was wrong was that when it got the unknown object response, it stopped any further requests. It should, if anything, report that error in the results, and carry on. If you are only asking for objects returned by an object_list request, you SHOULDN'T ever see that error, but BACNet manufacturers are notorious for not checking everything out, and bugs like this exist everywhere. The error just needs to be handled gracefully.

In the case of those bugged devices, those points are AV's, but are not being reported as such properly in the object_list. I'm in communication with the manufacturer about getting the firmware fixed.

OK, glad to see my data was still there. Thanks for the help!

Les