#
#  Test log configuration
#

FlushRate: 2      #flush files every 2 seconds

raw file:  /tmp/test-%F.raw   #raw log
data file: ~/test.data        #structured log

#start:  7/4/11 23:15         #start time for structured log
#end:  7/9 19:59:49           #end time for all logging

1 minute 5 seconds           #for test, we just log this short time

sensor:  labjack
  analog:  tension(lbf)
    mode: diff
    channel:  3
    resolution: 8         #highest streaming resolution
    -0.5minV  0.5maxV     #voltage range input
OR
    labjackGain: 10			# Labjack gain (1, 10, 100, 1000)	
    format:  %.8g
    offset:   -0.0039     #input voltage corresponding to zero Engr units      
    EngrUnits/V:   20.983     #lbf / volt
  analog:  battery voltage(V)
    mode: diff
    channel:  3
    resolution: 8         #highest streaming resolution
    -0.5minV  0.5maxV     #voltage range input
OR
    labjackGain: 10			# Labjack gain (1, 10, 100, 1000)	
    format:  %.8g
    offset:   -0.0039     #input voltage corresponding to zero Engr units      
    EngrUnits/V:   20.983     #lbf / volt

  analog:  battery amperage(A)
    mode: diff
    channel:  3
    resolution: 8         #highest streaming resolution
    -0.5minV  0.5maxV     #voltage range input
OR
    labjackGain: 10			# Labjack gain (1, 10, 100, 1000)	
    format:  %.8g
    offset:   -0.0039     #input voltage corresponding to zero Engr units      
    EngrUnits/V:   20.983     #lbf / volt

  streamRate: 20hz
:labjack

Sensor: microstrainG3(buoy)	#This is the accel on the buoy.  I added the (buoy) so we can specify the physical location but you could use a key/value if that works better (or anything else that works)
      sampleRate: 20 Hz
	Command: 	C2		# I wouldn’t put which bytes are which values in the .cfg file, the user will just screw that up.  Seems like we should agree on the messages we might need and you should keep track of what bytes are what value in those messages
		value:	AccelX(G)	#These are the values you’d get from the C2 message
		value:	AccelY(G)	
		value:	AccelZ(G)	
	Command: 	CE		
		value:	Roll(rad)	#These are the values you’d get from the CE message
		value:	Pitch(rad)	
		value:	Yaw(rad)	
	Command: 	C5		
		value:	M1-1		#These are the values you’d get from the C5 message
		value:	M1-2	
		value:	M1-3	
		value:	M2-1		 
		value:	M2-2	
		value:	M2-3	
		value:	M3-1		
		value:	M3-2	
		value:	M3-3	

Sensor: microstrainInertiaLink(ESP) #This is the accel in the ESP, same data format as G3 just an older model
      sampleRate: 20 Hz
	Command: 	C2		# I wouldn’t put which bytes are which values in the .cfg file, the user will just screw that up.  Seems like we should agree on the messages we might need and you should keep track of what bytes are what value in those messages
		value:	AccelX(G)	#These are the values you’d get from the C2 message
		value:	AccelY(G)	
		value:	AccelZ(G)	
	Command: 	C5		
		value:	M1-1		#These are the values you’d get from the C5 message
		value:	M1-2	
		value:	M1-3	
		value:	M2-1		 
		value:	M2-2	
		value:	M2-3	
		value:	M3-1		
		value:	M3-2	
		value:	M3-3	

Sensor: uBlox6(buoy)	#This is the GPS on the buoy
      sampleRate: .01 Hz
	NEMAString: 	GGA