Problem with data adquisition

[feltduck]

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.

[Mikhail]

Hi,

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.

[feltduck]

Which settings do you want to see?

[Mikhail]

Communicator settings, channels, user interface.

[feltduck]

Hi, sorry for the delay.
These are the communicator settings:
https://tinypic.host/i/ohOeKk

And these the channels:
https://tinypic.host/i/ohOcsD

I’m not using an user interface.

[Mikhail]

Hi,
Also a screenshot of the device data form (from Communicator) is needed.

[feltduck]

Here it is:
https://tinypic.host/i/ohOmh4

[Mikhail]

Probably, 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.

[Mikhail]

If 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.

[feltduck]

I 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/ohzhpA

Then at 12:30 it’ll store the data with the datetime at 10:15 in the BBDD.

[Mikhail]

Could you tell what is “BBDD”?
What is the time zone?

[feltduck]

I’m sorry, BBDD it’s the acronym for data base on my language.
My timezone is Madrid GMT+2

[Mikhail]

In 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.

[Mikhail]

Also check in log files that data queues of the module do not overflow.

[feltduck]

Ok, 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.

[Author]

Posts