I am not the expert but very interested as everyone.

I don't think there is already a tool to do that.
We should play first with the DBimport tool to know the format and the limitations.
Then create a tool to generate this kind of files for DBImport.

And most important thing at the end; A beautiful kb article because all the customers want to do that. All the time we say, keep the proprietary format for a while and then use only HDS...

It woudl be better if we can say:"no problem apply the kb article xxx"

I have started a little tool, put it on GitHub and "open-sourced" it.
Feel welcome to contribute!

Here is the link:
https://github.com/ak-arcinfo/Prop2HdsConverter

Hi Armin,

Finally what method did you choose?
Data Export --> csv --> SQL ??

Hi Nico,

I was not able to take advantage of DataExport because this effort was for a PcVue 11.0 project and the trend export consequently was limited to 12.000 trend records. (Meanwhile this limitation has been removed in one of the 11.1 Update versions...)

Finally, the tool that I linked in my previous post directly parses the proprietary archive files and creates one csv-file for trends and one csv-file for logs from each individual histo *.dat file. The insert into SQL Server needs to be performed manually or by a PowerShell loop or similar...

Johannes will continue to maintain this tool. Maybe in the future we can have direct insert into SQL Server database tables without the intermediate csv-export/-import step.

Thanks Armin. I will try to work on it as soon as possible.

Is it compatible with binary files or only ascii?
Is it compatible with old format before PcVue 10 without UTC?
Is it compatible with very old format and idx index?
Is it compatible with text attributes?

Is it compatible with binary files or only ascii?

Only ASCII...

Is it compatible with old format before PcVue 10 without UTC?

No.

Is it compatible with very old format and idx index?

No idea. Is the format of the dat-files still the same?

Is it compatible with text attributes?

For the non-default HDS columns, we would probably have to make things a little bit more generic. But generally, it would not be a big effort, I guess. Could be added when required.

Feel free to participate in this project by contributing to the Github project that was linked in one of the previous posts.

The project will be intagrated with PcVue tools ?

It will be usefull to inform more people that this kind of tools exist.

A lot of customer ask sales team for this.

I know that's a often requested function but I think we must be very carefull before presenting this feature to customers.

By the way, I think we plan doing it in PcVue (i dont know when...).

So far, that's still an only internal tool.

Nico

Hello,

I worked on the program (under Visual studio 2015 express) and I added:
- Transfer to the SQL database (CSV file transfer is too long )
- Time delay
- Correspondence of event number ( in an editable init file)
- Correspondence of event title ( in an editable init file)
- it's compatible with old format before PcVue 10 without UTC

I will try to comment further as soon as possible. Meanwhile, you can tell me the different bugs

Project: http://gofile.me/6ly85/DPZZ1Ki4
Release: http://gofile.me/6ly85/PdkFOTre

Hi Olivier,

Thank you for your contribution!
Could you please make a pull request on the github repository of the project so that I can accept the merge?

Thanks!

For your information, the archive format has been changed for the 11.2
Changes are:
- Add systematically the quality for each record
- If variable is NS the value is still written (no more ?)

That applies to proprietary and free archives and for Trends only.

Nico

Thanks Armin for this good topic !!!

I you ask me, the best way is to :

1. Use DataExport to export data from proprietary archives (binary/texte).
+ able to read all PcVue archives formats/versions (also the next one).
+ easy to export ALL your archives with SCADA basic instructions (in multiple csv files).
- need to browse HDSTrend.dat for each variable to export from SCADA basic script

2. Parse CSV files created by DataExport to modify EventCode/Date.
3. Import CSV file in SQL Server with a bulk insert instruction if possible.

--------

Note that Chrono format is really easy to convert with C/C++/JAVA/C#/ADA/... but not in TSQL or VBA.

DateTime dt = DateTime.FromFileTimeUtc(iChrono);
ctrl_tbxDateTime.Text = dt.ToUniversalTime().ToString("o");

Arnaud

Thanks Arnaud,

I just add a detail: We have the VBA code to convert chrono date.
We have also the SQL dll to convert chrono date in TSQL

Nico