|
|
|
Coming soon!
Many thanks to Mango users who provided their
code, feedback, suggestions, and funding.
Changes in version 1.9.0 can be found here.
|
- High performance data transfer
-
A new high-performance data source and publisher combination has been added to Mango. The Serotonin
Persistent TCP data transfer uses a persistent socket connection between field instances of Mango
and central instance. It is able to replicate field points on the central instance, and very
efficiently keep the central instance up to date. Also, it will periodically synchronize all data
such that no point values go missing while a central point is disabled. Special thanks to AES
Corporation for commissioning this enhancement.
- Point value insert performance
-
The performance of point value inserts for MySQL implementations has been dramatically increased -
roughly 50 times faster than it used to be when processing large amounts of data. Special thanks to
AES Corporation for commissioning this enhancement.
- Multiple remote views
-
Multiple remote views can now be safely placed on a single page, or shown in tabs within the same
browser. Special thanks to AES Corporation for commissioning this enhancement.
- Safe mode
-
A feature has been added such that on startup all data sources, point links, scheduled events,
compound events, and publishers will be automatically disabled. Using this, a badly behaved Mango M2M
instance can be brought under control for troubleshooting. Simply put a file named "SAFE"
(capitalization is necessary) in the application directory and (re)start the instance.
- BACnet discovery
-
An alternate BACnet discovery mechanism has been added for cases where broadcasts do not get routed
(and traditional discovery is therefore not possible). This mechanism accepts an ip, port, and remote
device id, and creates an object list request, allowing users to automatically create points from the
response.
- Style attribute for simple point components
-
Simple point components have been enhanced with a style attribute field. Thanks to Gergely Posztos of
Debaru Ltd. for this enhancement.
- Back-dated point values
-
Historical point values (i.e. back-dated from the present value of a point) are now better handled.
Such values were previously (and erroneously) made the present value. Note that the incorporation of
such values into point event detectors, interval loggers, etc. has not be done since this is
considered to be an exception case, and such code would likely have a significant negative performance
impact.
- Point value PK
-
The identifier for point values in four tables has been changed from integer (4-byte) to long (8-byte)
to accommodate very large databases.
- Data source copying
-
When copying a data source, the status (disabled/enabled) of a point is preserved. Previously, the
status of points was explicitly set to disabled.
- Reports
-
The data source name has been added to the point name in all reports. Also, image charts in emailed
reports are added with content ids that are unique across all report emails, not just within an
email. This helps prevent problems in email clients that cache images by content id.
- Under consideration: OPC XML data source
-
The possibility of implementing a data source for OPC XML communication is being evaluated. If you
are interested in assisting this development, please contact us.
- Under consideration: GEO-positioning data
-
We are examining the requirements for being able to include latitude/longitude as a data type. In
addition, linking to Google Maps or such as a renderer or charting type is also being assessed. Again,
if you are interested in assisting this development, please contact us.
|
|
