TX321 program converted to TX325 program (CR1000, CR3000, CR800-series)

This appendix discusses modifying a program for a CR3000, CR1000, or CR800-series data logger to use a TX325 instead of a TX321. It also discusses the TX325 features and commands that are not supported in the older data loggers and the interfaces required to connect the TX325 to an older data logger.

Some TX325 features and commands are not supported in the older data logger operating system (OS) because of memory size limitations of older data loggers.

The TX321 had a CS I/O interface, so the commands (GOESData) output data to the CS I/O port. The TX325 only has an RS-232 port, so the new commands that were added use the RS-232 interface on the data logger. This means that it will not be possible to connect to the RS-232 with LoggerNet, and another interface will need to be used for that. Campbell Scientific recommends using an SC32B, and connect the computer RS-232 (or USB to RS-232 adapter) to the SC32B and to the data logger CS I/O. Additionally, if the data logger has an Ethernet interface, the data logger may use an IP link to connect to the computer. An RS-232 interface is require If the data logger OS need to be updated.

The TX325 uses different CRBasic commands from the TX321. Often, the commands are similar, but not all functions are available. It is highly recommended to download the example program available at www.campbellsci.com/downloads/tx325-example-program-cr3000-cr1000-cr800 . This appendix provides the changes that need to be made to a data logger program that allows it to use a TX325 instead of the TX321. It is important to copy/paste or work from the online example, only using this appendix as a guide.

When using a TX321, the configuration parameters for the GOES radio may have been set either using the Device Configuration Utility software, or by using the GOESSetup() CRBasic instruction. A Device Configuration page is not available for the TX325 when it is connected to an older data logger. With an older data logger, the configuration parameters for the GOES radio must be set programmatically using the EnviroSatRandomSetup and EnviroSatSTSetup commands. The following are the three methods available for adding it to a program:

1. The EnviroSatRandomSetup and EnviroSatSTSetup commands can be coded with the arguments directly in the program, which is convenient when the user has only one station.

2. The configuration settings can be listed in a ConstTable, which allows them to be configured by changing the site specific settings from a template file that is used at multiple sites. Once the Boolean ApplyAndRestart is set to true, those changed constants will be applied and the program recompiled. If an archived copy of the program is kept that is running (and we recommend that you do), you will need to download it using File Control or do a Backup Datalogger (using the Device Configuration Utility software) and save it so that you know which site it applies to.

3. A file can declare and define the configuration variables and can include the measurement algorithms. The advantage to this is that as the measurements evolve, the same template file can more likely be used at multiple sites, since it does not include site specific parameters. If the program attempts to be compiled without finding the file, the compile will fail, since the variables used in the EnviroSatRandomSetup and EnviroSatSTSetup commands won't be found.

The following is an example of an include file named IncludeFile.CR1. It can have any suffix such as .CR8 or .text. It will simply require changing the filter in the file selector for the file to Send in File Control.

'GOES configuration settings for MySite

Const dcp_platform_id As Long = &h01234567

Const rt_baud_rate = 300

Const rt_channel = 195

Const rt_count = 2 'we can only send two messages max in a 2 minute RT interval.

'We can send more if our RT interval is larger.

 

Const rt_interval As String = "00_02_00"

Const st_baud_rate = 300

Const st_channel = 195

Const st_interval As String = "00_01_00_00"

Const st_message_window_size As Long = 10

Const st_offset As String = "00_45_50"

Use File Control to send it to the CPU drive. Uncheck Run Now and Run On Power-up, as it will not compile.

In the main file, add the following line before the BeginProg command:

Include "CPU:IncludeFile.CR1"

Send the main file. It should pull in IncludeFile.CR1 and compile without error.

The TX325 status is sent as an array of 37 values. Allocate and set aliases as follows or similarly:

Public tx_325_status(37) As Long

Public tx_325_status_results As String * 30

Public tx_325_time_status As String * 50

Public reported_month As Long

Public reported_day As Long

Commands used with the TX321 were named similar to GOESStatus(GOES_RCode1(1), 2) The similar, but not equivalent, command that has been added to operating systems for the older data loggers is: EnviroSatStatus(tx_325_status).

Code similar to the following may be appropriate for retrieving status and interpreting it:

Sub GetTX325_StatusAndProcess 'This section of CRBasic code polls the TX325 radio and 'converts some diagnostic data into human readable values.

 

EnviroSatStatus(tx_325_status)

 

'everything done from here is to help make things human readable

 

If ((Hex (radio_gps_health) = &h00) AND (status_result = 0)) Then

gps_health = "Have valid GPS position fix."

EndIf

 

If ((radio_failsafe_status = 0) AND (status_result = 0)) Then

failsafe_status = "TX325 is idle."

EndIf

 

'rt_tx_data_result_code = -99

If (st_tx_data_result_code = -99) Then

EndIf

 

If (rt_tx_data_result_code = -99) Then

random_transmission_status = "Logger has not tried to send Random data."

EndIf

 

'convert millivolts to volts

current_radio_battery_voltage = radio_battery_voltage * .001

current_radio_battery_during_last_tx = radio_battery_during_last_tx * .001

current_battery_voltage_before_last_tx = radio_battery_voltage_before_last_tx * .001

 

If (status_result <> 0) Then Erase (tx_325_status())

 

EndSub

When using the older data logger operating systems the status is only available as a response from the EnviroSatStatus command. Campbell Scientific recommends calling EnviroSatStatus when current information is needed. The following program exerts does this adding a trigger when the command is used to set the data logger clock:

 

' Run following commands everyday at 12 hours and 13 minutes.

If (Time_733m_24h OR set_clock_from_GPS) Then set_clock_from_GPS = False

 

' Ensure the returned time is valid.

If (GOES_Time(4) >= 0 AND GOES_Time(4) < 24 AND GOES_Time(5) >= 0 _

AND GOES_Time(5) < 60 AND GOES_Time(6) >= 0 AND GOES_Time(6) < 60)

Then

Setting the data logger clock to match the GPS time can also be accomplished by adding the status values to the Numeric Display in LoggerNet and toggling set_clock_from_GPS to True.

Save this Numeric Display configuration by clicking Numeric Display > Options…> Setup> Save config. By saving the configuration, users can easily access it at a field site to determine if the TX325 is operating as expected.

The previous code calls the following subroutine:

'This subroutine converts day of year (DOY) to months and years

Sub ConvertDayOfYear (_day_of_year As Long, _year As Long, _month As Long, _day As Long)

Else

EndIf

 

If leap_year = FALSE Then

EndIf

 

ElseIf leap_year = TRUE Then 'Are we in the month of January

EndIf

EndSub

 

Transmitting data

To edit the old program to transmit data, replace the GOESData() CRBasic instruction with the EnviroSatData() instruction. Refer to the CRBasic Editor help to determine the changes that need to be made to the parameters.

The GOESData(), GOESGPS(), GOESSetup(), and GOESStatus() CRBasic instructions are not compatible with the TX325. Replace these instructions with the EnviroSat() instructions for the required functionality.

Connection to the data logger RS-232 with LoggerNet

Once a program has been run that sends data to the TX325 through the RS-232 port, the RS-232 port will remain configured at 9600 baud, even after a power cycle. To use the RS-232 interface for LoggerNet at its normal baud rate, do the following:

1. Connect the SC32B to the data logger CS I/O port.

2. Connect to the data logger with the Device Configuration Utility software.

3. Select the File Control tab, select the running program, then click Stop. Backup the data logger if desired.

4. Select Deployment> Com Ports Settings > ComPort RS-232.

5. Set the Baud Rate to 115200 Auto, then click Apply.

   CAUTION:

   Do not run the program again until the RS-232 port is no longer needed.

6. Connect to the data logger RS-232 port from the computer running LoggerNet.

   CAUTION:

   Do not use the SC32B.

7. Load an OS or other desired task.

After loading and running the program using the RS-232 port to transfer data to a TX325, it will again be set to 9600 baud and will not be able to reliably communicate with LoggerNet until the program has stopped from running. When sending a large file like the OS, it will transfer much faster at 115200 rather than 9600 baud.