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.
Mangos network architecture for a big plant
-
Hy,
until now I used Mango to control just one "solar tracker" with a lot of dataPoint (more than 100) and problems concerning database growing too much.
Now I need to control 10 "solar tracker" from just one Mango gui, to achieve this I would like to use 2 Raspberry Pi 3 and a remote server, so on RPI_1 there's a Mango_1 controlling plant 1 to 5 instead on RPI_2 there's a Mango_2 controlling plant 6 to 10, I would like also to have a Mango_0 on remote server to collect data from Mango_1 and Mango_2 and to produce reports concerning all the plant of 10 "solar trackers" . I think that the main problem is how Mango_0 can collect data from Mango_1 and from Mango_2.
What do you think about this architecture? There's a way to improve it? Is it achievable?Thanks,
Antonio -
Hi Etantonio
Etantonio: until now I used Mango to control just one "solar tracker" with a lot of dataPoint (more than 100) and problems concerning database growing too much.
I suggest you look at your logging settings and set dead bands on your log entries. I have had systems with 2000+ points and no problem with my database size.
Etantonio: What do you think about this architecture? There's a way to improve it? Is it achievable?
Your architecture is fine, the best way to do this setup will be to use the Mango persistent TCP protocol to publish to your central server. Mango_0 could be a cloud server. Mango_1 and 2 will need a modem to sync data with the cloud server. I would recommend rather using the MangoES than the Pi 3 as it has proven its self to be very reliable. With the new cloud connect module you will be able to log into mango_1 and 2 remotely if any trouble shooting or configuration is required.
-
If you're concerned about a growing database, which is bizarre because the nosql database takes up very little space. Set up a USB on the mangoES to export your nosql and configuration backups to.
Judging by what you are saying, you want to use mango on the raspberry Pi or some sort of program to talk to the trackers. Do note that given how the free version works there is no mango tcp publisher as that is a paid module. Depending on how the pi's connect you could utilise the mangoES to talk to the pi's through a virtual serial socket or sending http requests via a mango script. The other way from the Pi's can be via socat or even a nodeJS based app. What you want to do is very straightforward However!
I feel more information is required to better accommodate what you want to achieve. Craig's idea has too many assumptions (IE what the client can afford, how critical the data is, what the guaranteed uptime is etc).
I personally use the orangePi with our systems and mango for on site control based assignments. And have no concerns whatsoever. -
Thanks for your answer, I'm working on Mango 2.8.4 and "Mango persistent TCP" seems to be free, a simple test with 2 datapoints seems to be ok.
MangoES is interesting but it seems to be too expensive for our project respect to a RPI, maybe it is due to some interface that we don't need (just an ethernet is required).
Mango_1 will be installed also on RPI_1 and Mango_2 will be installed on RPI_2 connected to a remote server running Mango with "Mango persistent TCP" datasource.
The "Mango persistent TCP" allows only to collect data on remote site, instead if I need to control the "solar trackers" I need to use a modbus publisher maybe.
-
@etantonio said in Mangos network architecture for a big plant:
Thanks for your answer, I'm working on Mango 2.8.4 and "Mango persistent TCP" seems to be free, a simple test with 2 datapoints seems to be ok.
I see, to me I had thought you were using the free version of mango 3 on the raspberry pis. It's good to keep all systems current so you don't need to concern yourself with possible data transfer/version issues (although I doubt the inifinite team would let that happen to the best of their ability)
As you are using older versions of mango, you will likely able to set up a persistent mango publisher tcp virtual datapoints back to the raspberry pi's. Setting the virtual datapoints can be used to fire commands on the remote units or activate scripts. Provides a greater degree of control to obtain desired behaviour.
Give that a whirl!
Fox
-
@MattFox And as an argument for staying on the latest, Persistent Publishers now have a setting "Allow data source to set values back" that should eliminate the need to set up a second publisher to send information back to the Pi / Remote Mango.
Also I would feel somewhat delinquent if I didn't addend in this thread the license agreement for Mango 3 one must agree to when starting a fresh instance does restrict use in commercial applications as a violation of the Personal, Evalution and Educational Use license agreement set forth.
-
@phildunlap said in Mangos network architecture for a big plant:
And as an argument for staying on the latest, Persistent Publishers now have a setting "Allow data source to set values back" that should eliminate the need to set up a second publisher to send information back to the Pi / Remote Mango.
Definitely agreed!
@phildunlap said in Mangos network architecture for a big plant:
Also I would feel somewhat delinquent if I didn't addend in this thread the license agreement for Mango 3 one must agree to when starting a fresh instance does restrict use in commercial applications as a violation of the Personal, Evalution and Educational Use license agreement set forth.
Thanks, I'll reread it to get my facts straight
-
That only applies to Free cores and Unlicensed cores. There is a low cost "Gateway" license in the store available for purchase that would legitimate the Mango_1 and Mango_2 (were they Mango 3) in this situation for the least money.
-
We have a license concerning Modbus Core, understanding license and prices is not so straight for Mango by my point of view.
-
For Mango 2 the point restrictions and the unique login were the core restrictions, and then one needed to buy licenses for modules with varying levels of restriction in the modules. The free core was not intended for commercial use, but the Mango/LICENSE file didn't address that, and the user didn't have to agree to a EULA that stated such upon using the software.
For Mango 3 free and unlicensed cores are restricted to personal, educational, or evaluation purposes. Module licenses (for Infinite Automation modules) are only on a few modules now, like Excel Reports or Cloud Connect. All non-free core licenses enable legitimate commercial use, and only functional restrictions like point count would apply depending on the type of license purchased.
Your purchase options for a particular instance can be assess by clicking the 'Register GUID' or 'Update license' button to open a store.infiniteautomation.com page for that instance on either the /modules.shtm or the /ui/administration/modules pages,
If you have some specific questions about the licensing I can try to answer those for you.
