Forum Replies Created
-
Posts
-
If writing an event is not properly finished because of power outage, new events will be successfully written in the file when server continue operating.
An exception situation like “Event marker not found” occurs when an event file is corrupted, i.e. contains invalid data.
If you need this issue solved, publish the corrupted file to be possible to analyze it it’s possible to restore them or not. If the problem occurs often, a special module can be developed to check and restore corrupted event files before the Server service starts.Merged to https://rapidscada.org/download/lang_pack/lang_pack_2.2.zip
Thank you.Likely, the directory that are set by default does not exist. Choose the correct directory by clicking the Browse button.
Please check the selected “Trend table directory”. Does it contain data files?
Can you view historical data via the web interface?MQTT Publisher sends data tag by tag. Payload format is configurable. I suggest to try. It does not require much efforts.
In the next release
zh-Hanswill be added to the drop-down list. Do you have a script to rename all the files in the translation back to *.zh-Hans.xml?This line of code filters the culture list. May be all cultures should be added to the list without any filtering.
It looks like there is not data in the archive.
Try opening the default archive written by the HelloWorld project.Use the TrendTableViewer utility to view data.
First of all, we need sample data to reproduce the issue.
Please do the following:
1. Save the damaged file.
2. Make sure that new events cannot be added to that certain damaged file.
3. Share the damaged file using a cloud drive, so we can reproduce the issue.Try the Modbus parser https://rapidscada.net/modbus/ to find mistakes in requests.
