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.

With this said, perhaps you could take this name and have it display in the "Compound event detector" section instead of the code. This would aide in the ability to review compoind events without knowing the codes....

This may be in a newer version, please forgive me if it is. I was wondering if there is a way to have the alarm page automatically update upon an alarm. If a user leaves up the alarm screen, and an alarm is activated while the screen is loaded, the new alarm does not show up (unless you refresh)… If you wanted to leave up a screen, showing you active alarms, currently it has to be manually refreshed…

:) Seriously, don't get me wrong, the functionality is all good. Maybe a way to keep the interface clean is to have some kind of "advanced" button that exposes the extra options or something. We'd have to consider how that would behave when you return to the page later on (i.e. decided whether to expose it by default depending upon options chosen...).

Hi Matt, I did come across that snippet that assigns the settable property. Now I see that I should be using input registers instead of holding registers for the points which are read only. I was thinking of input register as "input to the PLC" which would make them writable and holding registers as "output from the PLC". A checkbox/radio might still desirable in the datasource edit screen for setting the default permissions on a point but using "input register" instead of "holding register" as the register range will sort me out. Thanks for your assistance, Craig

It would be nice if the title of the pages in mango would change to reflect what is being viewed. Perhaps it could include the name of the view, watchlist, datapoint or datasource being viewed/edited. It would make it easier to use the forward/backward history drop downs on the browser and easier to keep track of multiple tabs or windows.

Hi Craig, This is interesting, but likely not something we'll get to soon. If you need help or pointers, etc., let us know.

change order in drop down lists like the one in the views page. I agree it could be easier to find the point you are looking for in the drop down list. The filter by data source option in the edit graphical view page would be handy everywhere that drop down list of points occurs (like in the data point edit GOTO drop down at the top) Another option might be to display the node's parent folder names before the dataPoint name in the select drop down. This way I wouldn't have to include the location and datasource name in every point's name to be able to tell them apart. For example if I am monitoring a temperature on several motors I have to call the temperature data point "locationID - dataSourceID - temperature" so that I don't have 10 data points called 'temperature' in the drop down. I might have got everything wrong but I would like to make the "Graphic views" as superuser and then publish them to other users who can't edit the views. just watch values or change set points, acknowledge alarms and so on. This would be convenient for me too.

Wish Item :) It would be nice if you could package mango to install tomcat, java, files, and mango in one easy executable. Again, this is why I gave up initially and it may help those less tech-ie.

That library has a couple of issues. It is written in C/C++ and so does not easily work with Java, and would almost certainly restrict Mango's cross-platform ability. Second, it is released under the GPL license, which means it could only be included in the Open Mango product, not the commercial version.

Please see http://mango.serotoninsoftware.com/forum/posts/list/74.page

All of that code is based upon HTML/CSS, yes. When done, that's what it will be.

Indeed it is a wishlist, and your point is valid. It's true though: the background and all of the point view images would need to be scaled, and the effects on the (un-scalable) text renderings would need to be taken into account. (Sure, text can be scaled, but only in a very quantized way compared with the granularity of image scaling.) Overall it is a tricky thing to make work properly, but still possible.