Vaisala 555 What Do I Do NowVaisala 555 What Do I Do Now That I've Got One? If you are upgrading from Handar 540 to Vaisala 555 or are installing a new 555, you may want to do the "Steps to Update Firmware", "Saving Your Configuration Table in your DCP" and "Setting Up a DCP Before Going to the Field". Steps to Update Firmware Check to see what the latest version of Firmware is on the DCP. This should be done any time you get new software from Vaisala or when you get a DCP that is different than the one you had before (change out at the Depot). On Line Menu View Program >555 To check version, look in upper right hand corner and make sure it is the latest version. To find out what the most recent version is, call RSSU Depot at 208-387-5475 and verify. If it is not, go to step II. If it is, you can stop now. Updating the firmware will delete the program on the DCP. If you don't have a copy of the program you are about to delete, you should do step II below before you update your firmware. ESC to On Line Menu. On Line Menu Archive 555 Pgm Path: C:\HNDR555\WRK Yes to overwrite previously saved program Y Now that you have the program archived, you can do the firmware update. ESC to On Line Menu On Line Menu Update Firmware Path: C:\HNDR555\PGM Select the most recent version (example 4.09) Say Y warning message ESC to On Line Menu On Line Menu to load program back into DCP Load Program>555 Archived Program Path: C:\HNDR555\pgm Select File Saving Your Configuration Table on Your DCP This should be done at initial installation for each of your DCP's in case one of the DCP configuration files gets corrupted. A saved copy will help restore the table from your laptop. On Line Menu Configuration table Retrieve configuration file from 555 Drive Path: C:\HNDR555\PGM 555 DAB S/N: 0000???? (example 00002622) Look on the board that is on the lid of the DCP and find the 4 digit serial number. Use this for the name of the file when you store it. This can be found later in the pgm files (example:0000####.cfg) ESC to On Line Menu Setting Up a DCP Before Going To The Field This part can be done in the office hooked up to the DCP before it is taken to the field. Turn the DCP on and hook the programming cable to the DCP and computer. Or you can use these steps if you need to load a new program that you've received via e-mail or on a disk. On Line Menu Program Control Stop Mode ESC to On Line Menu On Line Menu [note: do NOT use "file" and "load" to load a program into the DCP] Load pgm >555 Assembled pgm Path: C:\HNDR555\pgm Select file Working With The DCP In The Field Auto Run Program If your DCP has an auto run program and you are setting it up for the first time, you just need to connect the GPS, turn on the DCP, check in 10-15 minutes to make sure it is in the run mode. If you are at the site to do annual maintenance: disconnect GPS unit, retrieve archived data (optional), check telemetry configuration, alter parameters, force scan, then turn DCP back on with GPS connected, make sure in 10-15 minutes that it is in the run mode. If you do not have Auto Run Program Hook up the programing cable and turn on the DCP. On Line Menu Retrieve archived data This will download the existing data from your DCP to your laptop (if you want it). ESC to On Line Menu On Line Menu Date and time set Make sure time is correct on the DCP. If the laptop has correct time, put an X in the box and this will change the time on the DCP to what the laptop has. OR "enter time" from your watch if your laptop time is not correct GMT. ESC to On Line Menu On Line Menu Telemetry Config GOES-- Note: you will want to write down this information in case you need to put it back into your DCP (example: if you change out DCP). Verify that this information is correct. NESDIS Transmitter ID (example 325EAC8) Primary Xmit Channel (example 030) First Transmit Time (example 00:29:00 - this is the 1st one of the day, not the next time of transmit) Transmit Interval (example 01:00:00 for hourly or 03:00:00 for 3hrly) Transmit Window Size (example 00:00:15 for hourly or 00:01:00 for 3hrly) Secondary Xmit Channel (example 000) Unit Load Factor (60 sec/unit) (example 0.00) On Line Menu Alter Parameters - Note: you must be in the stop mode to change these. Rain (example .00 if you want to zero out the bucket count) Clock error (example -10 if clock has drifted by 10 seconds. This field access. value is not often used.) WWV Lock-ons (example 0 if you want to zero out the WWV tries) GPS Acquisitions (0 this out) BP Elevation (example 1800 feet) Solar Radiation Calibration (example 75.0) - change only if sensor is changed Inst Start Time (example 00-00:27:00, two minutes less than transmit time) Avg Start Time (example 00-00:17:00, ten minutes less than instant start time) WWV start time (example 16:00:00 GMT) - the time each day that WWV turns on GPS Scan Interval (example 00-06:00:00) - how often the GPS would turn on ESC to On Line Menu On Line Menu Station ID This will set the tones for your radio (if you have installed radio capability in the DCP). Type in 4 characters and a space, then enter. This sequence of numbers (tones), when tranmitted by a radio with DTMF keypad, will cause the RAWS station to transmit current weather data back to the user. ESC to On Line Menu Force Scan Before you do a forced scan, be sure to disconnect the WWV clock (if present) or else it is included in the forced scan. The WWV clock takes 3 minutes to force scan if not disconnected first. All Measures (Write down sensor readings. Note: The tipping bucket will show 0 tips until you put it to run mode.) ESC to On Line Menu Program Control Run Mode ESC to On Line Menu Force Scan All Measures (Compare with the sensor readings you wrote down during the first scan and be sure they match. You can now tip the tipping bucket and the tips will show, but be sure to go back to on line menu and alter parameters to set the tips back to 0.) ESC to On Line Menu Hook up WWV clock (if present) SDI-12 Commands Use these steps to make sure WWV clock is working. On Line Menu SDI 12 Note: When using the following SDI-12 commands, the "X" represents the address of the sensor. If the sensor is on address "0", you would use a zero in place of the "X". If the sensor is on address "1", you would use a one in place of the "X". ?! - This identifies the sensor. This will show the address of your sensor. X! - This identifies sensor communications. It should respond with a 0 if you type in 0! It would respond with a 1 if you type in a 1! XI! - (use a capitol I) This shows the model number and software version. It should respond back with (example) 010 Handar 541A 2.46. XM! - (use a capitol M with a zero) This will force a lock on the WWV receiver and takes about 3 minutes. Xs! - (use a small s) This shows the number of tries the WWV had. The response should be (example) 0 tries=001@5m=0001 10m=000 15m=00 frequencies (5m, 10m, or 15m) XS3! - (use a capitol S and three) This sets the WWV counter tries back to zero. You are now done and you can get out of the SDI 12 part of the menu. Disconnect the computer from the DCP. Verify data after first tranmission. For more information about the interagency RAWS program, contact USFS Program Manager Linnea Keating or BLM Remote Sensing Fire Weather Support Unit Manager Herb Arnold.