- This topic has 7 replies, 2 voices, and was last updated 6 years, 1 month ago by
.
-
Posts
-
I’ve installed RapidSCADA, added a MODBUS device successfully and everything is working in that regard. I’ve also added the configuration for writing to SQL, which is semi-functional, but I’m having some issues with it.
I want to capture current data every 10 minutes and export it to SQL. To do this, I’ve disabled all writing except for minute data, every 10 minutes. At this time, every 10 minutes or so, it will write 20 channels (even though I only have 10 active and only 10 show if I view minute data). Also, randomly, it will export the values for a mix of the channels. How can I get this so it’s only exporting the 10 active channels every 10 minutes, and nothing else?
ExportDB module executes SQL when it receives new data from a controller. To do your task, you should create other more complex SQL scripts.
If you have to control timing with SQL scripts, what’s the point of their being timing options in the file save parameters of the SCADAServer module? Are those specifically for local data?
SQL executes when data are coming from Communicator, but SCADA-Server saves all data to a disk periodically at the same moment. Value can change several times before saving to a disk.
I changed the delay in communicator to only poll at the interval I wanted, but there are more values in SQL being written.
For example, it will write the value of 20 sensors (even though only 10 are active) at the interval I want fairly consistently, but then it will skip a 10 minute interval, or in between intervals, a few other sensors will generate SQL data, but they are all on the same setting.
That doesn’t seem to have had a major effect, even after restarting all pertinent services.
Even with that change, it will write all 20 sensors (even though 10 are active in Administrator), then 10 minutes later it skips writing anything, then 10 minutes later it will write all 0 (impossible), and then 10 minutes later it will write actual values for all 20 sensors again, with the 10 inactive ones as 0.
I suppose, this issue requires a remote connection to analyze the logs and DB. But this is a commercial service. If you interested in the service, please contact me by email.
- You must be logged in to reply to this topic.