September 4, 2016 at 3:53 am #1577
Can you suggest some server configuration (system requirement), so as to establish a robust and statble server, I mean will it work better with windows based system like win 10 or with windows server editions, or linux based system , have you tested the most stable configuration.
Regards,September 5, 2016 at 6:46 am #1581
The most tested OS with Rapid SCADA is Windows. I recommend Windows Server 2012 R2 in case of industrial application. If your system is small, Windows 10 is enough.
How many input signals and active users is planned?October 7, 2016 at 4:03 am #1635
So far set up looks gud…
We are planning to test this software ….
so far it is working gud with small set up of 3-4 devices…
will it be equally good with, large set up of say , 1000 devices with about 15000 (input +output) signals.???
what would be server requirement then..?? (CPU+RAM)
any suggestion? for about 10 active clints (web user).
ThanksOctober 7, 2016 at 8:33 am #1636
Rapid SCADA is tested in the lab with 10000 input channels and works well on Pentium i3 and 4GB RAM. Active communication between Server and Communicator may require more resources.
Some additional questions:
1. What OS is planned?
2. What frequency of polling is really needed?October 7, 2016 at 10:28 am #1637
Considering other fourum query.. please comment on following configuration:-
1) Windows Server 2012 R2. (I think server 2016 is better have you test it??)
2) Intel i5 quad core 3Ghz or higher.
3) 16 GB or higher RAM.
4) 1 TB HDD.
5) Frequency of polling :- ( not actually decided yet) any optimum suggestion from your side as per system capability??? How much you think it can handle…??
Regards,October 7, 2016 at 11:30 am #1638
1) Both are good choice.
Server 2016 is not tested with Rapid SCADA, but I’m sure, it will work well. In case of any issues with it, I can help you.
2-4) Very good.
5) I forget to ask about communication protocols. Could you describe how devices will be connected?
I think, from 10 to 100 parallel polling threads (communication lines) have to work.
It would be wonderful if you share stats when you launch the system.October 8, 2016 at 3:58 am #1639
5) communication protocol will be through TCP gateways.
—> Nothing is finalyse yet… still we are exploring the available options… mean while i am trying to test the stability and reliability and capability of rapid scada…
—-> As one single communication line can communicate with say up to 25 devices… (polling frequency 30 sec to 5 mins distributed among devices) I think up to 90 communication lines may be used… some lines will be loaded with less number of devices.
—-> please explain your last point…
“I think, from 10 to 100 parallel polling threads (communication lines) have to work.
It would be wonderful if you share stats when you launch the system”
How loading is determined on your system…. It will be on TCP protocol.(via TCP gateway)
Regards,October 8, 2016 at 8:19 am #1640
polling frequency 30 sec to 5 mins distributed among devices
This is not high load.
1. After you configure Rapid SCADA, you should start the whole process and watch for CPU, RAM, HDD and network load.
2. Test responsiveness of the web app by serfing data views. Compare first open time of a view if Communicator is running or not. First open time after restart application pool of IIS.
3. Explore logs of the web app and SCADA-Server service (you should switch to detailed log).October 8, 2016 at 1:19 pm #1641
Probably, the first list item above is difficult to implement, because devices are installed for a long period of time. In this case you need a software simulator of devices, that can respond for requests.
You must be logged in to reply to this topic.