Changing the .prn file

[Scott]

Hi,

I've recently been trying to change the .prn file to match a custom data source that I have.  The data source has been tested and verified using the example .prn file:

1 Parm1 50.0 2
2 Parm2 50.0 2
3 Parm3 50.0 2
4 Parm4 50.0 2
5 Parm5 50.0 2
6 TIME$_DAY 50.0 1
7 TIME$_MILLISEC 1000.0 1

I would like to change it to something along these lines:

1 source.one 0.0 2
2 source.two 0.0 2
3 source.three 0.0 2
4 source.four 0.0 2
5 source.five 0.0 2
6 source.majortime 50.0 1 SystemParamType = MajorTime
7 source.minortime 1000.0 1 SystemParamType = MinorTime

When I change the file and run the CDS verification tool, the CDS crashes after spitting out:

Attempting to obtain parameter attributes from file (prn)
Completed parameter attribute import from file (prn) for data source = 0; total parameters = 6
Completed parameter attribute import from file (prn) for data source = 0; aggregate rate = 50.000000
Data source init succeeded
Starting config structure validation...
Time to perform config structure validation = 3.030464
Starting parameter defaults validation...
[CDS-352] Unable to locate parameter = Parm1 in Iads control database of data source = 0
[CDS-352] Unable to locate parameter = Parm2 in Iads control database of data source = 0
[CDS-352] Unable to locate parameter = Parm3 in Iads control database of data source = 0
[CDS-352] Unable to locate parameter = Parm4 in Iads control database of data source = 0
[CDS-352] Unable to locate parameter = Parm5 in Iads control database of data source = 0
Processed 0 total inactive parameters...
Processed 5 total data source parameters...

It seems like the CDS is not recognizing the change to the prn file.

[Adam Chant]

Scott,

You’ll probably want to send the logs files to iadssupport(at)symvionics (dot) com so we can better assess what may be incorrectly configured.

Off the top of my head I would speculate that possibly the path to the PRN file is pointing to an old version, or that you have not followed the steps to generate a confi file that reflects the parameters in the prn..

Send us the logs and we can take a look .

 

Adam Chant

Symvionics, Inc.

IADS Application Engineer

(661) 273-7003 x 210

--
You received this message because you are subscribed to the Google Groups "IADS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iads+uns...@googlegroups.com.
To post to this group, send email to ia...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/iads/-/b4_D3GBloHgJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Kathy Rodittis]

Hi Scott

 

It looks like you need to change the parameter names in your IADS config file to match the new names ( source.one, source.two ) in your .prn file.

 

I’m sorry about the crash. I’m sure Mike would like to try and reproduce this so if you could send us your config and prn files, we’d really appreciate it.

 

Thanks

-Kathy

 

From: ia...@googlegroups.com [mailto:ia...@googlegroups.com] On Behalf Of Scott
Sent: Monday, February 25, 2013 2:41 PM
To: ia...@googlegroups.com
Subject: [IADS] Changing the .prn file

 

Hi,

--

[Scott]

Yes, I also believe this is the case.  I have attempted to change the IADS config file by hand unsuccessfully; which is probably what is causing the crash.  I remember someone mentioning that there was a tool to generate the config files from the .prn.  I don't think it was included in the DEV kit I am using.  Would you mind pointing me to a location where I could find this utility?

[Adam Chant]

Base config files can be created from the Parameter Attributes Viewer located in the IADS Programs Directory. In the latest version of IADS it would be under the IADS Tools sub folder and called the IADS Parameter Attributes Viewer. There has to be a BTD file created from the PRN to create a config from.

 

1.       Open the Parameter Attributes Viewer

2.       Go to File > Open Parameter database

3.       Browse to the directory with the BTD file

4.       Select the BTD File and verify the Parameters are correct in the Left window of the Parameter Attributes Viewer

5.       Go To Tools > Create Config File

6.       Select Option for Aperiodic Parameters and the config will be created

7.       Save the config file in a directory that can be referenced at start-up

 

If you have run IADS and successfully validated then IADS should have automatically created a valid BTD file to create a PRN from.

 

Adam Chant

Symvionics, Inc.

IADS Application Engineer

(661) 273-7003 x 210

 

To view this discussion on the web visit https://groups.google.com/d/msg/iads/-/hoeRoyZ2hPUJ.

[Scott]

Ahhh ok.

I was able to create a BTD file from the PRN, and subsequently a config file.  After re-validating, I ran a test on our data source.

I updated:
  source.one at 300Hz,
  source.majortime at 50Hz
  source.minortime at 1000Hz

I believe I should have seen a data file for source.one, but instead I ended up with a data file for source.minortime.  The ID's are all being sent correctly, so I'm not sure of what is causing the problem.

P.S.
The CDS validation crash I was experiencing earlier was fixed by adding a new line at the end of the prn file.

[Jim Bretz]

Scott,

 

What version of Iads are you running?

 

Jim

To view this discussion on the web visit https://groups.google.com/d/msg/iads/-/3ujTvzqrutQJ.

[Scott]

Hi Jim,

We are only running the CDS and the Data File Viewer to verify our data source.

The CDS is version 7.3.4
The data file viewer is version 1.4

[Mike Burt]

Hi Scott:

 

If you are not seeing a data file being created for source.one typically that means the parameter was either not defined in the ParameterDefaults table in the IADS config file or not defined in the prn file (which you would have seen an indication on the CDS console window)...please check for typos on either end (i.e. config and prn). If you are seeing a data file being created but contains no data content (i.e. file size = 1024) that means the IADS server is not sensing the tag id for source.one as specified in the prn file...maybe check for any typos in the tag id. If after reviewing you are still not seeing a problem in the setup please zip up and forward the Logs folder located in the LOCATION1 directory specified in the CDS startup file (please send to the iadssupport address as specified in an earlier post) .

 

We are still trying to figure out the crash problem...if you can forward the prn file that was triggering the problem that may expedite the situation.

 

Thanks

 

[Scott]

Hi Mike,

The parameter defaults table is not getting updated properly by the parameter attributes dialog.  I've sent the log directory to the iads support email.  Please let me know what xml values I should add in the config file.

Thanks

[Scott]

Mike,

Thanks for your response.  The config file you gave me worked on the second iteration of testing.  It looks like the CDS added a whole bunch of xml after the first iteration.

[Mike Burt]

Scott:

 

We were able to reproduce the crash and have developed a fix which will be available in the next release but in the mean time the workaround is to add a blank line after the last parameter entry at the end of the prn file...as you had already done in your case.

 

Thanks for all the feedback.