Sign in or 
Share this
Data Conversion Utility
ATTENTION: Please read this entire chapter before proceeding with converting any Ambient data. This document covers the conversion for Ambient systems only.
Note: The conversion of ATX systems has to be done in house by Agilaire.
Important: The AirVision service under Services has to be started in order for the conversion to run properly. Running the conversion with the AirVision service stopped will cause problems with the database.
Before running the conversion, keep in mind that you should never run a conversion or make drastic changes to the data folder that the Ambient software uses. Copy the contents of the data directory into a backup folder, then the conversion can be ran on the contents of the backup folder. This is a precaution to make sure the original data folder does not get damaged; as we advise that you continue to run the Ambient system in parallel to the new AirVision system for a few months to ensure that everything is operating properly.
If the conversion runs into any problems it will give an error, which will stop the conversion. To minimize the chance of getting errors during the conversion, look at the files in the backup folder and make sure the data files are in sets. If you only have one data file it will need to be removed to keep the conversion from stopping with an error on that file.
The data files should be in sets so there will be two files per each data set that will have the name of the files duplicated, but will have two different extensions. One file will have the extension of .dat and the other file will have the extension of .inx.
Minute files begin with M and the format is the two digit logger ID, the two digit year, and the three digit Julian day. Auxiliary begins with AUX, Hourly begins with HLY, Daily begins with DLY, and Calibration begins with CAL; and the format for all of these files is the two digit year and the two digit month. Raw files are only for hourly and auxiliary and they begin with RWH and RWA, and the format is the same as the validated files.
AirVision does not communicate with 8800 loggers, so any site that is setup as an 8800 the conversion will skip over and those settings will not be imported into AirVision. To have data from an 8800 site added to AirVision it must first be changed over to an 8816 in the Ambient software. This means that all of the settings have to be removed from the 8800 setup starting with the least significant settings such as alarm and digital settings, then the calibrations, then the parameters, and then the sites last. You will then have to put all of those settings back in under the 8816 set up keeping all of the settings identical to as they were before, such as the names and ID’s so that the data will match correctly to the channels and sites that is belongs too.
However, keep in mind that if the 8800 logger is still in use at the site AirVision will not collect data from that site until the 8800 logger is physically replaced with an 8832.
The conversion utility needs to be installed and ran on the server where the database is located. To install the utility browse the cd and open the EdasConversionSetup folder, and double click on the setup.exe file. After installing the conversion utility into the default directory, open Windows Explorer and browse on the C:\ drive to Program Files | Agilaire LLC | Edas Conversion | and find the file AirVisionConversion.exe, and double click to open the utility.
NOTE: It is best for the configuration to remain selected during the whole conversion process to make sure that all channels are converted for those channels that may only have a small amount of existing data. Start with a small amount of one data type, such as one days worth of hourly data, to begin with to make sure the conversion does not run into any issues. Then work your way up to a week, then to a month, and possibly up to three months. When raw data is selected the conversion will run slower.
If you convert the configuration without converting some data along with it, nothing will be converted even though it will say it was successful. Convert each data type in small increments of one month to three months to keep from hanging up the conversion. If you do not have a large number of sites and parameters you could possibly convert up to six months at a time For example, convert the configuration and hourly data only for six months and then the configuration and minute data only for one to three months at a time because minute data has double the files to convert.
Data has to exist for the parameters to be converted into AirVision. If data does not exist the parameter will be skipped over and won’t be converted.
If the units for a parameter in the Ambient software does not match any of the units in the units list in AirVision, the units will not be converted and the units field in AirVision will be filled in with none. The user will then need to manually select the units from the drop down list in the Site/Parameter screen after logging into AirVision.
If data still exists in the Ambient database that is no longer linked to a site and parameter, it will not have channel to link up with once converted into the SQL database, so SQL will create a generic channel for the data to be linked to. If this occurs and you do not want the generic channels and data showing in AirVision, Agilaire can provide you with a script that can be edited to remove those channels and the data.
2.1 Running Standard or Enterprise SQL Server 2005 or 2008
If you are running the full version of SQL Server fill in the information needed which is explained below. If you are running SQL Express continue to the next section for instructions.
AirVision Database Connection
SQL Server Instance – This field defaults to localhost, which is the local server. If this utility cannot connect to the database you can change it to the correct name of your SQL instance.
Database – This field defaults to the AvData database which is the database that Air Vision uses. So this field really needs to remain with the default name in order for AirVision to function properly.
E-DAS Ambient Data Directory – Click the browse button and select the path to where the data backup folder is located.
Data Types – Check the box beside of Configuration and a data type that you want to convert to the AirVision Database. Converting one data type at a time in small increments is best.
Date Range to Convert Data – Enter in the Start Date and End Data of the range of the data that is to be converted. Keep in mind the larger the date range the longer it will take for the conversion to complete. If you choose to all of the data at once you will probably have to leave it to convert over multiple hours to possibly multiple days. You can also convert in even smaller section than mentioned to make it easier to correct any errors it may in counter.
Options
Use Site long name if they exist? – Click to check the box if you want the existing long site name to be used in the new database.
Append Logger ID to front of Site name? – Click to check the box if you want the logger ID to appear at the beginning of the site name in the new database.
Append Channel number to front of Parameter name? – Click to check the box if you want the channel number to appear at the beginning of the parameter name in the new database.
When ready to run the conversion click the Convert button.
When the conversion is complete it will put a text line such as this example in the gray area at the bottom of the conversion screen.
2.2 Running SQL EXPRESS 2005 or 2008
If you are running SQL Express some changes have to be made to allow the utility to connect to the database. After installing the conversion utility open the Windows Explorer and browse on the C:\ drive to Program Files | Agilaire LLC | Edas Conversion | and find the file AirVisionConversion.exe.config and double click to open it.
Once the file is open find the entries of localhost and FURROW, which have been highlighted in the example below to help you locate each entry. Replace each of the four entries with the name of the computer along with \SQLEXPRESS.
For example, if the computer name is airmonitoring, then you would replace each of the four entries with airmonitoring\SQLEXPRESS. Be sure to not make any other changes to the file. Do not add in any other characters or spaces, and do not take out any previously existing characters or spaces, as this can cripple the operation of the conversion utility. Once the correct changes have been made save the changes and close the file.
To find the name of the computer, right click on the My Computer icon on the Windows Desktop | Properties | Computer Name tab, and find Full computer name:. The name given before the first period in the path is the computer name. The name given after the first period is the domain name which is not needed for this step.
While in the same Edas Conversion folder find the file AirVisionConversion.exe, and double click to open the utility.
AirVision Database Connection
SQL Server Instance – This field defaults to localhost, but has to be changed to the same computer name \SQLEXPRESS that was used when editing the AirVisionConversion.exe.config file. Example; airmonitoring\SQLEXPRESS.
Database – This field defaults to the AvData database which is the database that Air Vision uses. So this field really needs to remain with the default name in order for AirVision to function properly.
E-DAS Ambient Data Directory –Click the browse button and select the path to where the data backup folder is located.
Data Types – Check the box beside of Configuration and a data type that you want to convert to the AirVision Database. Converting one data type at a time in small increments is best.
Date Range to Convert Data – Enter in the Start Date and End Data of the range of the data that is to be converted. Keep in mind the larger the date range the longer it will take for the conversion to complete. If you choose to all of the data at once you will probably have to leave it to convert over multiple hours to possibly multiple days. You can also convert in even smaller section than mentioned to make it easier to correct any errors it may in counter.
Options
Use Site long name if they exist? – Click to check the box if you want the existing long site name to be used in the new database.
Append Logger ID to front of Site name? – Click to check the box if you want the logger ID to appear at the beginning of the site name in the new database.
Append Channel number to front of Parameter name? – Click to check the box if you want the channel number to appear at the beginning of the parameter name in the new database.
When ready to run the conversion click the Convert button.
When the conversion is complete it will put a text line such as this example in the gray area at the bottom of the conversion screen.
Note: The conversion of ATX systems has to be done in house by Agilaire.
Important: The AirVision service under Services has to be started in order for the conversion to run properly. Running the conversion with the AirVision service stopped will cause problems with the database.
Before running the conversion, keep in mind that you should never run a conversion or make drastic changes to the data folder that the Ambient software uses. Copy the contents of the data directory into a backup folder, then the conversion can be ran on the contents of the backup folder. This is a precaution to make sure the original data folder does not get damaged; as we advise that you continue to run the Ambient system in parallel to the new AirVision system for a few months to ensure that everything is operating properly.
If the conversion runs into any problems it will give an error, which will stop the conversion. To minimize the chance of getting errors during the conversion, look at the files in the backup folder and make sure the data files are in sets. If you only have one data file it will need to be removed to keep the conversion from stopping with an error on that file.
The data files should be in sets so there will be two files per each data set that will have the name of the files duplicated, but will have two different extensions. One file will have the extension of .dat and the other file will have the extension of .inx.
Minute files begin with M and the format is the two digit logger ID, the two digit year, and the three digit Julian day. Auxiliary begins with AUX, Hourly begins with HLY, Daily begins with DLY, and Calibration begins with CAL; and the format for all of these files is the two digit year and the two digit month. Raw files are only for hourly and auxiliary and they begin with RWH and RWA, and the format is the same as the validated files.
AirVision does not communicate with 8800 loggers, so any site that is setup as an 8800 the conversion will skip over and those settings will not be imported into AirVision. To have data from an 8800 site added to AirVision it must first be changed over to an 8816 in the Ambient software. This means that all of the settings have to be removed from the 8800 setup starting with the least significant settings such as alarm and digital settings, then the calibrations, then the parameters, and then the sites last. You will then have to put all of those settings back in under the 8816 set up keeping all of the settings identical to as they were before, such as the names and ID’s so that the data will match correctly to the channels and sites that is belongs too.
However, keep in mind that if the 8800 logger is still in use at the site AirVision will not collect data from that site until the 8800 logger is physically replaced with an 8832.
The conversion utility needs to be installed and ran on the server where the database is located. To install the utility browse the cd and open the EdasConversionSetup folder, and double click on the setup.exe file. After installing the conversion utility into the default directory, open Windows Explorer and browse on the C:\ drive to Program Files | Agilaire LLC | Edas Conversion | and find the file AirVisionConversion.exe, and double click to open the utility.
NOTE: It is best for the configuration to remain selected during the whole conversion process to make sure that all channels are converted for those channels that may only have a small amount of existing data. Start with a small amount of one data type, such as one days worth of hourly data, to begin with to make sure the conversion does not run into any issues. Then work your way up to a week, then to a month, and possibly up to three months. When raw data is selected the conversion will run slower.
If you convert the configuration without converting some data along with it, nothing will be converted even though it will say it was successful. Convert each data type in small increments of one month to three months to keep from hanging up the conversion. If you do not have a large number of sites and parameters you could possibly convert up to six months at a time For example, convert the configuration and hourly data only for six months and then the configuration and minute data only for one to three months at a time because minute data has double the files to convert.
Data has to exist for the parameters to be converted into AirVision. If data does not exist the parameter will be skipped over and won’t be converted.
If the units for a parameter in the Ambient software does not match any of the units in the units list in AirVision, the units will not be converted and the units field in AirVision will be filled in with none. The user will then need to manually select the units from the drop down list in the Site/Parameter screen after logging into AirVision.
If data still exists in the Ambient database that is no longer linked to a site and parameter, it will not have channel to link up with once converted into the SQL database, so SQL will create a generic channel for the data to be linked to. If this occurs and you do not want the generic channels and data showing in AirVision, Agilaire can provide you with a script that can be edited to remove those channels and the data.
2.1 Running Standard or Enterprise SQL Server 2005 or 2008
If you are running the full version of SQL Server fill in the information needed which is explained below. If you are running SQL Express continue to the next section for instructions.
AirVision Database Connection
SQL Server Instance – This field defaults to localhost, which is the local server. If this utility cannot connect to the database you can change it to the correct name of your SQL instance.
Database – This field defaults to the AvData database which is the database that Air Vision uses. So this field really needs to remain with the default name in order for AirVision to function properly.
E-DAS Ambient Data Directory – Click the browse button and select the path to where the data backup folder is located.
Data Types – Check the box beside of Configuration and a data type that you want to convert to the AirVision Database. Converting one data type at a time in small increments is best.
Date Range to Convert Data – Enter in the Start Date and End Data of the range of the data that is to be converted. Keep in mind the larger the date range the longer it will take for the conversion to complete. If you choose to all of the data at once you will probably have to leave it to convert over multiple hours to possibly multiple days. You can also convert in even smaller section than mentioned to make it easier to correct any errors it may in counter.
Options
Use Site long name if they exist? – Click to check the box if you want the existing long site name to be used in the new database.
Append Logger ID to front of Site name? – Click to check the box if you want the logger ID to appear at the beginning of the site name in the new database.
Append Channel number to front of Parameter name? – Click to check the box if you want the channel number to appear at the beginning of the parameter name in the new database.
When ready to run the conversion click the Convert button.
When the conversion is complete it will put a text line such as this example in the gray area at the bottom of the conversion screen.
2.2 Running SQL EXPRESS 2005 or 2008
If you are running SQL Express some changes have to be made to allow the utility to connect to the database. After installing the conversion utility open the Windows Explorer and browse on the C:\ drive to Program Files | Agilaire LLC | Edas Conversion | and find the file AirVisionConversion.exe.config and double click to open it.
Once the file is open find the entries of localhost and FURROW, which have been highlighted in the example below to help you locate each entry. Replace each of the four entries with the name of the computer along with \SQLEXPRESS.
For example, if the computer name is airmonitoring, then you would replace each of the four entries with airmonitoring\SQLEXPRESS. Be sure to not make any other changes to the file. Do not add in any other characters or spaces, and do not take out any previously existing characters or spaces, as this can cripple the operation of the conversion utility. Once the correct changes have been made save the changes and close the file.
To find the name of the computer, right click on the My Computer icon on the Windows Desktop | Properties | Computer Name tab, and find Full computer name:. The name given before the first period in the path is the computer name. The name given after the first period is the domain name which is not needed for this step.
While in the same Edas Conversion folder find the file AirVisionConversion.exe, and double click to open the utility.
AirVision Database Connection
SQL Server Instance – This field defaults to localhost, but has to be changed to the same computer name \SQLEXPRESS that was used when editing the AirVisionConversion.exe.config file. Example; airmonitoring\SQLEXPRESS.
Database – This field defaults to the AvData database which is the database that Air Vision uses. So this field really needs to remain with the default name in order for AirVision to function properly.
E-DAS Ambient Data Directory –Click the browse button and select the path to where the data backup folder is located.
Data Types – Check the box beside of Configuration and a data type that you want to convert to the AirVision Database. Converting one data type at a time in small increments is best.
Date Range to Convert Data – Enter in the Start Date and End Data of the range of the data that is to be converted. Keep in mind the larger the date range the longer it will take for the conversion to complete. If you choose to all of the data at once you will probably have to leave it to convert over multiple hours to possibly multiple days. You can also convert in even smaller section than mentioned to make it easier to correct any errors it may in counter.
Options
Use Site long name if they exist? – Click to check the box if you want the existing long site name to be used in the new database.
Append Logger ID to front of Site name? – Click to check the box if you want the logger ID to appear at the beginning of the site name in the new database.
Append Channel number to front of Parameter name? – Click to check the box if you want the channel number to appear at the beginning of the parameter name in the new database.
When ready to run the conversion click the Convert button.
When the conversion is complete it will put a text line such as this example in the gray area at the bottom of the conversion screen.
|
rdykes |
Latest page update: made by rdykes
, Feb 18 2010, 5:04 PM EST
(about this update
About This Update
Edited by rdykes
1982 words added view changes - complete history) |
|
Keyword tags:
None
More Info: links to this page
|
There are no threads for this page.
Be the first to start a new thread.
