diadem csv problem with importing

[RichElswick]

I am opening a CSV file and it is only importing the last Channel as a text channel, but it is a numeric channel, not a text.

To generate the CSV file, I am parsing a hex file into the csv file.

I am at the end of my wits as I cannot even change the format of the channel over to a different type.  I am about to setup the perl parsing script to generate something other than a csv file, so I can try to fix this.

I have attached a sample script.

Thanks for the help.
Rich

[Walter_Rick]

Hi RichElswick,

The import is working correct. Comma Separated Value means to separate the values in a row, but you add a comma behind the last value of a row. Correct is the following:

Time,IntmdVltBattVlt,IntmdVltBattCrnt
0.0008,40.18,-0.04
0.0011,40.19,-0.04
0.016,40.19,-0.04
0.036,40.17,-0.02
0.056,40.15,-0.04
0.076,40.19,-0.04

Greetings

Walter

[RichElswick]

My appologies for posting the wrong file.  Even once the comma is removed at the end of the first line, it does not work.  I know this, because I added the comma to try to get it to work.

Thanks.

[RichElswick]

I have attached another of the files, which I am having problems with.  Remove the .txt extension to make it back to the .csv and try it out.

Not sure why it is occuring.  I can import it as the .txt file ans specify it, so I am going to use that as a work around for now, but I would like to find out why it isn't working right.

Thanks again.

[Walter_Rick]

Hi RichElswick,

I didn't have any problem with your CSV file. I've done my test with DIAdem 9.1 SP2b. If you have still problems top import a CSV file please, explain a little bit more detailed which kind of problem you have.

Greetings

Walter

[nandini]

DIAdem SP2 is available on our website at http://digital.ni.com/softlib.nsf/websearch/7fe5c870a7b4345d86256fc00031ef32

Thanks
Nandini
NI

[RichElswick]

I am using the same version with SP 2 Ver 9.10.2345
USI - 1.1.1.2245 what ever that is.

[Otmar]

I downloaded your CSV file and removed the space behind the last number

Old:
0.3113,[space]20,[space]20,[space]17,[space]18,[space]17,[space]17[space][EOL]

Modified:
0.3113,[space]20,[space]20,[space]17,[space]18,[space]17,[space]17[EOL]

and then tried loading the file again. Once I had removed the [space] in front of the [EOL] the CSV import in DIAdem worked fine.

I use DIAdem

9.10.2260 Service Pack 2
USI 1.1.1.2254

We can build you a Data Plugin that gets around this effect, or maybe you can remove the [space] from the application that writes this type of file to disk.

Let us know if we can help you any further,

    Otmar (otmar.foehner@ni.com, (512) 683-5452 )

[AndreasH_Ha]

Hi Rich,

In addition to what Otmar proposed, I'd like to check with you about the file in general. From your messages I read that your data file has a different format and that you already convert it to DIAdem to read it. So before we look into a DataPlugin for your csv file,why don't you give us an idea of what your primary (hex?) data file looks like. Perhaps we can skip the step to create a csv file and read the primary file directly.

Andreas Haub

National Instruments

[RichElswick]

Here is an attached example file.

It is data recorded by CANalyzer and just records the raw values, which have to then be decoded to be understood.  Of course, the decoding varies as software revisions occur, so I would end up having to be able to change the DataPlugin or request it to be changed whenever we work with some new version of the software.

I will have to look into the requirements (NDA) for sharing the decoding information.

Thanks!