Forum Home › Forums › Understanding the Software › Problem with data adquisition
- This topic has 23 replies, 2 voices, and was last updated 10 months, 2 weeks ago by Mikhail.
-
AuthorPosts
-
May 10, 2023 at 10:18 am #12554feltduckParticipant
Hi,
I want to know if there is any way to be able to read the records from x days ago. when I have a cut instead of filling in the gap with the corresponding time
fills it with the consumption of the current hour.For example:
I have a power cut at 9:15 and it is restored at 15:00,the scada instead of consulting the data from 9:15 onwards and filling in the empty hours, takes
the current data and continues as if the data occurred at 9:30.May 11, 2023 at 10:50 am #12561MikhailModeratorHi,
Usually when controller is not available, the Communicator app sets data to undefined. If you provide screenshots of the settings and data, we could provide additional thoughts about that.
May 12, 2023 at 6:57 am #12569feltduckParticipantWhich settings do you want to see?
May 12, 2023 at 11:26 am #12573MikhailModeratorCommunicator settings, channels, user interface.
May 17, 2023 at 8:20 am #12623feltduckParticipantHi, sorry for the delay.
These are the communicator settings:
https://tinypic.host/i/ohOeKkAnd these the channels:
https://tinypic.host/i/ohOcsDI’m not using an user interface.
May 17, 2023 at 9:43 am #12625MikhailModeratorHi,
Also a screenshot of the device data form (from Communicator) is needed.May 17, 2023 at 10:01 am #12627feltduckParticipantHere it is:
https://tinypic.host/i/ohOmh4May 18, 2023 at 10:46 am #12638MikhailModeratorProbably, you need to change connection mode to individual and set IP address to the device properties if you don’t use an intermediate gate device between the PLC and PC.
- This reply was modified 11 months ago by Mikhail.
May 18, 2023 at 11:15 am #12645MikhailModeratorIf device communication was OK, and then the device become unavailable, the device data in Communicator should be changed to
---
. If not, let me know and provide communication line log.May 19, 2023 at 10:19 am #12650feltduckParticipantI need to set the connection on shared because I’m working with more than 1 device.
The communication is working well but when the SCADA stores the data in the BBDD it has a problem with the datetime.
E.g:
In this screenshot the datetime is at 10:00 when the real time is 12:15.
https://tinypic.host/i/ohzhpAThen at 12:30 it’ll store the data with the datetime at 10:15 in the BBDD.
May 19, 2023 at 2:58 pm #12653MikhailModeratorCould you tell what is “BBDD”?
What is the time zone?May 22, 2023 at 6:33 am #12668feltduckParticipantI’m sorry, BBDD it’s the acronym for data base on my language.
My timezone is Madrid GMT+2May 22, 2023 at 7:31 am #12670MikhailModeratorIn Rapid SCADA all data uses UTC timestamps. Some databases (like PostgreSQL) have special data type to work with timezone, some databases don’t have such data type.
If actual timestamps always differs by timezone offset, it’s OK and can be corrected in the SQL request.May 22, 2023 at 7:33 am #12671MikhailModeratorAlso check in log files that data queues of the module do not overflow.
May 22, 2023 at 8:11 am #12675feltduckParticipantOk, thanks for the information. The other question that I have is when a device get disconnected the data is stored like this:
https://tinypic.host/i/oW7LIq
I want to check the data that is stored in the device at that hour and replace it. -
AuthorPosts
- You must be logged in to reply to this topic.