[Mikhail]

Hello,
The question is duplicated.

[Mikhail]

Hello,
If you have issues with displaying the above data, please provide screenshots.

Can I export this excel data via WebStation?

Yes, Webstation allows to export historical data to Excel.

[Mikhail]

maybe it should be highlighted in the document regarding these data types

You right. Currently, the documentation for v6 is not ready. Nuances of the algorithms should be added to the docs.

[Mikhail]

@zzz, do you get data from Communicator to ScadaServer successfully?

[Mikhail]

Let me try later today since I have my own Mqtt server locally and on the cloud.

@kumajaya, if you already have tried the MQTT publishing data source, could you share the experience?

[Mikhail]

Writing of 0 data points completed successfully in 1 ms
It looks like no channels are associated with the archive.

[Mikhail]

InfluxDB2 is supported.
In ScadaServer.txt there are statuses of archives. Is the MinCopy archive displayed as ready?

In ScadaServer.log how many channels for archiving? For example
Number of active channels for archiving: 271

[Mikhail]

In my test project, I setup 77 channels, all as Integer type, none got recognized, until they are all set to Double. and they all are immediately recognized by Communicator.

The Modbus driver uses the double type for all its tags. Channel data type must match a tag data type. The behavior looks as expected.
Currently all existing drivers use the Double type. However, if someone writes a custom driver, he can use integer tags.

[Mikhail]

ScadaCommon.dll is a new name for ScadaData.dll
You can find new file formats here.

[Mikhail]

Hello,
Thank you.
Do you use GitHub? If so, you could add the development to a public repository.

[Mikhail]

For the ScadaWeb project try publishing to a folder.

[Mikhail]

Could you provide screenshots?
Is it possible to reproduce the issue on the default HelloWorld project?

Data type of channel and device tag (provided by a driver) must match. It should affect only certain tag. If it corrupt other tags, it may be a bug.

[Mikhail]

If you use PostgreSQL archives, pgAdmin converts selected data to local to make it handy for a user.

[Mikhail]

It seems that rapidscada is using UTC time to store data

That’s right. Timestamps converted to local time only in the web application.
Log files uses the server’s time zone, however, it does not affect the logic.

[Mikhail]

Screenshots and logs may help.

I tested the MQTT data source with the following parameters:

ClientID = 
DataLifetime = 60
DetailedLog = False
DeviceFilter = 
MaxQueueSize = 1000
Password = C8080E774B59B0C6694063BDE2428352
Port = 1883
ProtocolVersion = Unknown
PublishFormat = 
QosLevel = 0
Retain = False
RootTopic = Communicator/
Server = broker.mqtt-dashboard.com
Timeout = 10000
UndefinedValue = NaN
Username = 

Communication channel options:

ClientID = 
Password = C8080E774B59B0C6694063BDE2428352
Port = 1883
ProtocolVersion = Unknown
Server = broker.mqtt-dashboard.com
Timeout = 10000
Username = 

[Author]

Posts