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.

Thomas is exactly right with the exception that we don't support Derby anymore as the main Mango database. The SQL data source is very flexible and can be used to pull or insert data from a MS SQL database but Mango does not currently support MS SQL as the main database. Mango could certainly be made to with MS SQL as the main database but it means that every new release then needs to be tested on it as well. When you are using the NoSQL module with Mango there is a lot less load on the database so most people are very happy with using MySQL combined with the MangoNoSQL (Time Series Database).

We will do some testing on our side and see if we can reproduce something similar. It would be helpful if you could get a serial capture of when the network is slow and when it is fast so we can compare the differences.

@HWilson We found a bug in the 3.2.0 and 3.2.1 code which affects new installs. I will get a bug fix release out today, look for v3.2.2.

Hey Brad, from the logs you posted its definitely timing out on the read, i.e. its sending a command and not receiving a response. I know this will happen with AB PLCs when the session is invalid or something like that. I would try disabling points on your existing datasource until you can get it to work. I suspect its something to do with the payload sizes, i.e. the driver is requesting too much data at once or something. Its odd that it used to work and just stopped though. Unfortunately the AB datasources are provided by a 3rd party vendor - Deltamation, so we don't have access to the source code to debug or fix the issue. I will forward the issue onto them.

Hi Eightbit, I would assume that it is setting a modbus register with some value on a fixed interval. This would mean the watchdog client they supply has the fields to supply the connection (meaning the watchdog is the modbus master). If you could figure out what register / value is being set (and that is indeed what is happening), you could have Mango perform that action, probably through the Scripting data source calling .set() on the watchdog point, but there are options as well. I would expect it to be in the device's manual.

I would be very interested in implementing Z-Wave on mango, any one can help?

Why yes I do. That would explain everything. One day I will pay attention to all of the available options. One day.... Thanks for the help!

Thanks Phil, you are correct. Since my last post I converted my db from derby to H2 just to see if it would make a difference and tried the upgrade again and it seems to have worked. Les

Thank you for posting your results and investigation!

It sounds like you're expecting every user to have their name as a permissions group by default. But, it is easy to add the group to your users such that you can use the username as the permissions group.

I'd just like to add a request for a list of the directives for the ma-gauge-chart etc. Something like the AngluarJS website would be nice to be able to find a list of the directives. For example, I can find anything to set the minor ticks, only the major via interval.

Hi Phil, There is a complete implementation of mtcommect agent developed by mtconnect people. My idea is to develop a mango publisher to load data into the agent.

UltraEdit gives you a nice file explorer on the left and that makes navigation and selection easy. You just hit save and then it updates the file on the server. Have managed to get this all working nicely and editing the webpage has been a lot more enjoyable now.

Can you check that the property, "swagger.enabled=true" is in your env.properties file, which may either be at Mango/overrides/properties/env.properties or Mango/classes/env.properties

Poll times generally indicate the time it takes for the device to respond to all the request for data. The information here probably isn't enough for us to look at especially since we never see this on any other systems so it is quite odd. Generally our modbus networks run at 19.2k baud. You could capture the following system metrics during a time when the polls are slow just to see if something is going wrong on the MangoES: logs/ma.log file Screen shot from the Internal Metrics tab and work items tab Download JSON from the Threads tab on logging console Screenshot of running "top" in a ssh console JSON export of your Modbus Serial Data source and data points so we can review all the settings. These items will help us see if any kind of performance in Mango is causing your poll times to slow down. Thanks,

We are working on a new feature to have the browser refresh content when needed so that users never have to clear cache. This should be out in the next release in the next month or so.

My problem is I want to connect to the database where the handle is connected to the automata thanks for answering very friendly

It could be a typeo in a variable name, or perhaps a point was deleted that was in the context of a meta point. Something like... p1 = random numeric, script: return p7.value*2

Now it is working, Thank you

Hi Mohammad, There are a few ways to do it. Through Mango: There is a button, "Purge all events" in the "Purge Settings" section on the system settings page. If your events table is large, this could take a while. Through the SQL console: delete from userEvents; delete from events; And my suggestion would be to do it from the database shell, since this will be very very fast regardless of table size: Navigate to /opt/mango/bin/ Edit h2-web-console.sh to add the -webAllowOthers argument as instructed by the comment near the bottom, such that you can access it from your other computer. sudo ./h2-web-console.sh In your browser, navigate to the port defined in h2-web-console.sh, probably <Mango IP>:8081 Log in, your connection string will be /opt/mango/databases/mah2 and the username and password are probably blank, but if not they will be explicit in the H2 section of your env.properties, at either Mango/overrides/properties/ or Mango/classes Run the following command: SET FOREIGN_KEY_CHECKS=0; CREATE TABLE eventsNewTable LIKE events; DROP TABLE events; RENAME TABLE eventsNewTable TO events; CREATE TABLE userEventsNewTable LIKE userEvents; DROP TABLE userEvents; RENAME TABLE userEventsNewTable TO userEvents; SET FOREIGN_KEY_CHECKS=1; It's good to have Mango off while doing that, but not required as the operations are so fast (but some database errors will probably be thrown by Mango right when the command is run). 7. Ctrl + c the h2-web-console.sh And you're done!