Recommended Posts

I'm attempting to use the command line to process some encrypted .RLD files using SymphoniePRO Desktop. I've created a site file and saved the encryption password to it via the SymphoniePRO Desktop UI, and I've verified the encryption password has been saved, as I can import files without the prompt for the encryption password. This seems to demonstrate the site file retains the encryption password, but it doesn't work when processing via the command line. The context I'm using to process the files is:

The documentation states that the /site switch uses scaling information from the site file, but nothing is mentioned about an encryption password. This is leading me to think the encryption password doesn't get retrieved from the site file when command line processing, and it might not be possible to process files in this way. Can anyone verify this, and if it indeed isn't possible to do, are there any plans to implement this in an upcoming release of SymphoniePRO Desktop?

Share this post

Link to post

Share on other sites

We automatically load encrypted data from RWDs using Symphonie Data Retriever with the following steps, and we were hoping to be able to repeat this with RLDs and SymphoniePRO Desktop:

User creates a site file with encryption password

When a new RWD file comes in, open file with SDR command line interface and extract logger serial number (SDR auto matches to the site file and uses stored encryption password)

Append serial number to file name (serial numbers are unique, site numbers are not, so we're making sure to have unique filenames via serial+site number)

Send file down the chain to be recognized by its serial+site number and parsed to the correct site in our SQL-based system

Since we have files coming in from a lot of different loggers and sources, we need a way to create unique names for the files. Without the command line version of SymphoniePRO automatically matching to a site file, it makes it programatically quite difficult to determine which site file and encryption password belong to each incoming RLD file.

Sorry for that long explanation, but hopefully it makes sense in what we're trying to do. It sounds like it isn't currently possible to operate like this with the command line version of SymPRO Desktop, so unless there are plans to develop this functionality or some sort of workaround, we're going to have to get creative on our end.

2. A way to extract logger SN from an RLD file without decrypting it, via command line

Which would be preferable? I'll have to discuss with our SymphoniePRO/software team to determine if/how/when either of these could be implemented, but neither sound unreasonable to me. Feel free to email support@nrgsystems.com to discuss further.