ADCON MODULE Version 1.1.7 FOR IRRIMAX 9.1.2
The IrriMAX Data Exchange Adcon Module download extends Data Exchange with the ability to download moisture and salinity readings from an Adcon A840 Telemetry Gateway, or from the addVANTAGE server software. It is invoked by choosing "Adcon Server" from the Source combo-box in Data Exchange.
This module is controlled by the licensing within IrriMAX and will only operate with IrriMAX 9.1 or later. Adcon Module Version 1.1.5 or earlier must be used for IrriMAX version 9.0 or earlier. /////
ADCON MODULE 1.1.7 FOR IRRIMAX 9.1
The IrriMAX Adcon Module extends Data Exchange with the ability to download readings from an Adcon A840 Telemetry Gateway, or from the addVANTAGE server software. It is invoked by choosing "Adcon Server" from the Source combo-box in Data Exchange.
The module will identify all sensors in the Adcon configuration and output them to a destination database. The names of soil moisture and salinity sensors in the Adcon configuration should conform to the naming convention described in the Adcon Module manual so that probe and depth information can be retrieved.
Typically the Adcon Module is used with "Configuration Only" selected to create an empty IrriMAX database (.SDB file). This database can then be edited to remove any unwanted sensors, but the
logger name, site names and the addresses of the remaining sensors should not be changed. Thereafter, the Adcon Module can be used to periodically import new readings to this database.
Use of the Adcon module is controlled by your IrriMAX software license. To use the module, you need to be issued an IrriMAX Site Key that includes the Adcon option.
To obtain an appropriate IrriMAX license, contact Sentek or send an email to [email protected]
This software is provided subject to the IrriMAX Software License Agreement. Refer to the file "license.txt" in the IrriMAX installation folder.
CHANGES IN VERSION 1.1.7
- Removed error "Could not get maximum slots from server". The module now assumes a maximum of 100 slots if the server does not supply the value.
CHANGES IN VERSION 1.1.6
- Updated support libraries to match IrriMAX 9.1. Please check
the System Requirements below for supported operating systems.
CHANGES IN VERSION 1.1.5
- Hitting F1 when a control has focus now invokes the online Help.
NEW FEATURES IN VERSION 1.1
- Makes use of the custom sensor support added in IrriMAX 7.0 to download from all sensors, not just moisture and salinity.
- When downloading from all RTUs into the one database, it is no longer necessary that they all have the same slot interval.
- One of the following operating systems:
Windows Vista with Service Pack 2 or later (all editions except
Windows Server 2003 with Service Pack 2 or later (all editions)
Windows Server 2003 R2 or later (all editions)
Windows Server 2008 with Service Pack 2 or later
Windows Server 2008 R2
Windows XP with Service Pack 3 (except Starter Edition)
- IrriMAX 9.1 or later. Upgrades for IrriMAX are available on the Sentek web site.
1. Sensor values must fall within the minimum-maximum range defined in the Adcon configuration, otherwise they are converted to the 'invalid' value for that sensor. This is to prevent large spikes from appearing in the graph for some sensors.
If no readings are appearing for a particular sensor, check that the minimum and maximum are set correctly in the Adcon configuration.
2. Sensor types whose values are supposed to be accumulated (e.g. Rainfall) can provide incorrect values when drawn as an IrriMAX bar graph unless they are placed in their own exclusive database, or their name contains the text "(SUM)". This is because of a difference in the way the Adcon Server and IrriMAX store their readings.
IrriMAX database records consist of a single timestamp with a value for each sensor at that time. The values for all the sensors are combined into a single record. In contrast, the Adcon Server
supplies data for each sensor individually. The readings for each sensor potentially have different timestamps or even different sampling intervals to those of the other sensors.
It is important to create full records in the IrriMAX database so that gaps don't appear in the line graphs. The module attempts to combine the downloaded readings from different sensors into full records, but the timestamps are not always synchronized. Two techniques are used to resolve this:
a) All readings that fall within a 60 second period are combined into one record. If there is more than one reading for a particular sensor within that time, only the most recent is kept.
b) If a record is incomplete, the readings for the missing sensors are carried over from the previous record.
This works well for sensors whose data is best represented as a line graph, but is wrong for those sensors whose readings should be accumulated because the total will potentially be missing the
'combined' readings and also include the 'carried over' readings.
Any sensor that requires that its readings be accurately summed together should therefore be identified by including "(SUM)" in the name, or be downloaded into a database containing only that
sensor, so that the process described above does not occur.
Note that the text "(SUM)" will be removed from the sensor name before it is output by the Adcon Module.
Notwithstanding any of the above, the module will automatically recognize sensors with the following names as accumulating sensors:
3. Downloading from all RTUs to the same database, or downloading certain combinations of sensors, can cause the database to contain a large number of redundant readings if the timestamps are not well synchronized.
If the module cannot effectively combine sensors into records with common timestamps there can be an excessive number of 'carried over' readings generated. These will be visible as a
'stair step' effect in the graph under high zoom level, where a sensor does not change value for several records.
The 'carried over' readings add to the database size and have an impact on the performance of IrriMAX. Care should be taken when deciding which sensors to include in a given database. Soil
moisture and salinity should be kept together, but it might be beneficial to put the other sensor types in a separate database.
4. The Adcon module will ignore any sensor named "Data Delay".
5. Changes made to the Adcon configuration may cause the automatically-generated sensor addresses to change. If the sensor addresses change it will no longer be possible to correctly update
any existing IrriMAX databases that were based on the previous Adcon configuration.
6. The Adcon module cannot retrieve the unit of measurement for any sensor from the Adcon Server. If required, the unit needs to be entered manually into the database using the Logger Configuration dialog within IrriMAX or Database Manager. Note that this can only be done while there are no readings within the database. Use the 'configuration only' option in the Adcon module to create the database without readings.
7. If the A840 has more than 16 RTUs configured you cannot download from all RTUs into a single database. You will get the message "More than 16 sites found. Readings cannot be merged into a single destination." You will need to create a separate database for each RTU.