//
// Sample Battery Driver config file
// At time of writing, battery driver supports up to 4 installed batteries.
// This config file should reside in $AUV_CONFIG_DIR, and the file name should be passed
// to batteryServer along with the -cfg flag. e.g. `$ battServer -cfg example_battery.cfg`
// Copyright MBARI 2020
// Laughlin Barker
//


// The batteries broadcast their status msgs about every 1.6s. Logging every msg results in
// logs that are ~11MB/hr, which means a 48h mission results in 0.5GB of battery log.
// Set the minimum logging period here. The driver will still receive and process all incoming
// msgs, but will only log on a 15s (or slightly greater) interval.
minLoggingPeriod_s = 15;

//Battery 1
b1Name  = Batt1;
b1IP    = 134.89.32.131;
b1Port  = 20003;
//Desired FET states at driver launch. Incorrect FET states will cause mission exit.
b1DischFET = 1;
b1AuxFET = 0;
b1Aux2FET = 0;

//Battery 2
b2Name  = Batt2;
b2IP    = 134.89.32.146;
b2IPort = 20003;
b2DischFET = 1;
b2AuxFET = 0;
b2Aux2FET = 0;


//NOTE: Up to 4 batteries can be configured. 
//      UNUSED BATTERIES SHOULD BE COMMENTED OUT.
//      Otherwise the driver will complain to Syslog periodically about having not received the
//      status updates from the batteries not connected on the system.

//Battery 3
//b3Name  = Batt3;
//b3IP    = 134.89.32.138;
//b3Port  = 20003;
//b3DischFET = 1;
//b3AuxFET = 0;
//b3Aux2FET = 0;

//Battery 4
//b4Name  = Batt4;
//b4IP    = 134.89.32.148;
//b4IPort = 20003;
//b4DischFET = 1;
//b4AuxFET = 0;
//b4Aux2FET = 0;