ANU online

 

RSES Home Page The Australian National University 
Research School of Earth Sciences 
Geodynamics Group

Quirks of the PCON

Written by Paul Tregoning pault@rses.anu.edu.au

 

Contents


  Decision Criteria
 
Time and Alarm settings
 
Known Problems
 
 

Criteria


Back to Contents

Time and Alarm settings

  • The PCON maintains the time setting via an on-board Realtime clock powered by a dedicated lithium battery. We run all clocks on UT time. The PCON time can be set from the DSCC (or any of the COM ports) by sending the appropriate ASCII command to one of the COM ports.

  •  
  • If the PCON clock gets corrupted (ie there is an illogical time for either the real time or the alarm time) then the PCON will recognise this, set the time to 00:00:00 and the alarm time to 12:34:56. It will then power up the DSCC.

  •  
  • Written into the DSCC code is a check of the PCON alarm time. If it is 12:34:56 then the DSCC software assumes that it has been woken because the PCON time was corrupted. The DSCC resets the PCON time according to its own value. It sets the alarm time according to a default value listed in an input file (controllable by a user) and then shuts itself down (ie issues a PU 02 command to the PCON).

Back to Contents

Known Problems

  • If the PCON receives a command via any of the COM ports while it is in the process of logging diagnostic data it will freeze. Recovery is possible only by disconnecting ALL external power sources to the PCON (ie removing all battery connections to the card frame) or pulling out the PCON circuit board. It is therefore imperative that the DSCC software leave sufficient time between issuing a log data command (LL) and the subsequent command. At present, this is done by calling a simple FORTRAN program, which counts for X seconds, before permitting the DSCC software to continue running. To not do so is at your own peril .....

  •  
  • In 2001 the GPS receiver at LDBF switched itself off at the on/off switch despite our precautions of having the PCON shut down the system if the battery voltages fall to 11.5 Volts. The GPS went off during the phone call to RSES. We suspect that starting the phone and/or actual data transmission caused the battery voltage to drop below 10.4 V (the level at which the GPS will switch itself off) within 1 sec (the sampling time of the PCON). Therefore, our catch for this problem failed. Our current fix to this problem is a software fix on the DSCC - we do not send a command to power up the phone unless the battery voltage is above 12 V. We believe (but have no real proof) that the batteries will not plummet to less than 10.4 V during a normal phone call if they start out at above 12 V.

  •  
  • At present, the PCON decides whether the heaters need to be turned on/off. The temperatures for the decisions are hard-wired into the PCON EEPROM and only Norm Schram can change them. This is causing considerable problems at the BVLK site in 2002 where it is clear that the insulation is not working as well as it should be and the three heaters are draining the batteries, possibly resulting in less GPS data being collected than otherwise could have been. A suggested change to PCON code is that the heaters have default temperature criteria but that they are changeable by a serial port command. Alternatively, there could be a command to disable the heaters completely - or each heater individually.

Back to Contents

Return to  RSES Antarctic GPS Home Page

Last modified:2002 March 18  pault@rses.anu.edu.au