Tracker2 updates

I created a script to generate the special telemetry parameter messages which sets up the meaning of all the telemetry readings. This includes the name of the value (PARM), the UNIT of the value (volts, degrees etc) The equation which is applied to the value to translate it back to the original measurement (EQNS) and the meaning of the digital bits (BITS)

:VK6AHR-3 :PARM.Temp,Supply,ADC0,Cnt,HDOP,-,-,-,-,-,-,JP,PR
:VK6AHR-3 :UNIT.DegC,Volt,None,#,HDOP,,,,,,,ON,#
:VK6AHR-3 :EQNS.0,1.9608,-273,0,0.07843,0,0,1,0,0,1,0,0,1,0
:VK6AHR-3 :BITS.11111111,HARG's digipeater status

The first colon means the payload is a MESSAGE, which has to be to ourselves for the telemetry parameters. In our case the first channel is "Temp" (internal temperature of Tracker2) units of "DegC", with the equation values of 0,1.9608,-273 (quadratic). Also all our digital bits are non-inverted hence the 11111111. BITS also lets you describe what the telemetry is for.
By default the T2 monitors internal temp and supply voltage analogues, an event counter which uses the fourth analogue, the HDOP reported by the GPS receiver (GPS not required for a digipeater) as well as the profile jumper and the interrupt/counter input digital bits (the last two bits) There is also a user defined analogue, the third reported analogue value (ADC0 input pin) which is up to the user to interface and supply the EQNS for (the other EQNS are available on the Opentracker wiki) I tested with an IR photo-diode via a resistor to the on-board 5V and it works.

To get all the above in a script requires using the "SECOND" event, incrementing a counter and beaconing those messages at different times to spread the load. To beacon any one of those messages, enter them into the 'T' field of the script editor preceded by the BEACON command (shorten to BEA) so that it looks like this:

"BEA :VK6AHR-3 :BITS.11111111,HARG's digipeater status"

The spaces are important! (one after BEA: and the callsign MUST be padded out with trailing spaces to exactly 9 characters)

Click "Execute T" This creates a script entry which will beacon the message at the appropriate time. Unfortunately there doesn't appear to be a way to copy and paste the script so I can't show you the whole script.

You don't need to send these messages very often. aprs.fi will remember them forever until you change them. A local station's software should remember them as well. We're sending them once an hour. There shouldn't be any reason to send them any more often than every 30 minutes.

The end result of all of this is that you will have a telemetry history which means something to anybody who cares to look. Otherwise it's just a bunch of numbers that means something only to those in the know.

I also added a startup event which beacons a status packet of "T2 back online." This more or less puts a marker in to indicate when the T2 has been reset or powered up. Handy for me anyway.