C# loaddatafile

[DavidSkilbeck]

Hi, is it possible to load a data file in to the history of a point with c#. I have an example of loading a data value.

Thanks,

[tfranklin]

It should be the same process but calling a different method. 

1. The file must be accessible by the user running the script
2. The format of the file is drastically different than LoadDataValue, as there is no quality and the date is broken into separate columns.  If you need to include quality or a different reason, I'd advise using LoadDataValues

I'd reference this article here, but keep in mind that the Resource Center is going away. 

https://tprojects.schneider-electric.com/telemetry/display/public/CS/Importing+History+Using+LoadDat...

The below is shamelessly copied from the article above.

Spoiler

LoadDataFile

 LoadDataFile( FileName{String} )

The LoadDataFile method takes a filename as its single parameter. This is the name of a local CSV on the main server. Some points to note about the files to be imported:

• Each line of the CSV file specifies a single record and has the format: YYYY,MM,DD,HH,MM,SS,Value
• The file must be in ANSI format.
• To insert comments into the file start the line with a semi-colon.
• Reason is set to 0 (Current Data) on import.

[AndrewScott]

The online help has two examples of using the LoadDataFile method, plus details of how to specify quality:

See https://tprojects.schneider-electric.com/GeoSCADAHelp/Geo%20SCADA%202020/Default.htm#ServerAdministr... (bottom of page)

[tfranklin · Accepted solution]

The more you know.  Thx

Looks like reason is still defaulted to 0 though.

Depending on the use case you may still consider LoadDataValues for the extra reason code parameter.

*Edited -- I RTFM*

[AndrewScott]

The 'reason for logging' for each record is fixed as "Current Data" (0) when using LoadDataFile method.

[DavidSkilbeck]

Hi, yes the line below is exactly one of things I was trying to determine.

Is there a big time saving with LoadDataFile to make it worth while investing the extra time and effort as to using LoadDataValues.

I already have code that iterates through with LoadDataValues.

"Depending on the use case you may still consider LoadDataValues for the extra reason code parameter"

I would still like to see the LoadDataFile work with C#.

But maybe at a later date.

Thanks,

[BevanWeiss]

There were performance benefits, I think when I last did anything with the LoadDataFile it was on the order of 2-10x faster.

But the restrictions, and the requirement to generate the file in a particular format really meant that it wasn't worth it.

The overall process needed more steps, and hence it actually took longer in real world times.

Issues were things like:

1. the file needing to exist on the server, so the data couldn't just come from the client
2. file format isn't very standard from other platforms, so needed an entire process to generate it
3. not able to customise the reason code
4. not able to simultaneously 'process' the data (i.e. if the value was the same, LoadDataFile would import it always, with LoadDataValues we could easily have code do compression / skipping during loading

I'd say if LoadDataValues is working for you, it's easiest to just keep that as the backend load mechanism, and then you can easily tweak your front end loading code to do the things you want (like loading data from the client etc)