i have done some testing of the 6800.
firstly, the test.
i decide to take the simple rout, i set up two cron jobs, one to update a uptime log file every five minutes the other to calculate Pi to 1000 places every three minutes. i also left both radios on. wlan1 i connected to my home router the and wlan0 i left broadcasting as an open ap. i also set up a shell to a aws instance i own so i could reverse shell back in to check up on the logs. i ran this test a total of two times, with full charges in between. the first test i did in two stages as i need the mark V for some actual work. first stage it had a three hour run on the battery, the second stage netted nearly six more hours for a total of about nine hours of uptime. the second test i ran over night at last look it was over eight hours... however when i went to check up on it after the battery died, upon boot using the wall power the log was missing data. i know the log was being written to as i had used the log to check at the eight hour mark. not sure what happened here. both time the battery was charged to full with three solid green lights that stayed solid for a good few hours after usage started. both times it took over 12 hours to get a full charge. not sure if i have a bad unit, i am expecting to much and my usage testing is to high or a combination of both. the boring stuff.
the script for Pi (found online)
#!/bin/bash
pi()
{
export x=`echo "scale=$scale; 4 * a (1)" | bc -l`
echo "$x"
}
if [ "$#" = "1" ]
then
scale="$1"
echo `time pi`
else
echo "Usage: $0 #"
fi
the cron entry for generating the uptime log file
*/5 * * * * uptime >> sd/uplog.log
the cron entry for calling picalc (what i named the script)
*/3 * * * * picalc >> /dev/null