Arduino GPS and Accelerometer DIY paper- anyone try it 

I am attempting to build my own GPS and accelerometer device using Arduinos to track raccoons in order to get a better understanding of how their behavior changes in response to different predator cues. I am using the Foley and Sillero-Zubiri (2020) paper as a guide, and had hoped to deploy the devices for my field work this summer. However, the code seems to be out of date and I am having trouble getting the battery to last more than 24 hours using the code I have written. I am in Mississippi, so I am not sure if this is an environment thing (possibly too hot here to have the devices work), or a coding thing. Does anyone have any experience with Arduinos or this type of project? Are there other papers or others who do this sort of work that I could reference/contact? I am working with computer scientists to write an algorithm to infer raccoon behavior from the accelerometer data, so I need both the GPS and accelerometer to be working.

Foley et al 2020- Open‐source low‐cost modular GPS collars for monitoring and tracking wildlife.pdf


Are you using the same microcontroller they used in their project? If not, which microcontroller are you using? Could you also post/send the code you have written so far?

-charles

Rob Appleby
@Rob_Appleby  | He/him
Wild Spy
Whilst I love everything about WILDLABS and the conservation tech community I am mostly here for the badges!!
WILDLABS Author
WILDLABS Research Participant
Variety Hour Regular
Commenter level 4
Conversation starter level 3

Hi @jsstamn 

A couple of questions to follow on from @CBPerkins about the board/microcontroller you are using...

Are you using the same battery they specified (i.e. 4,400 mAh rechargeable Lithium ion battery pack)?

Also, is this the code you are using? If so, I can't see anywhere, from my brief scan, where there's any sleep period(s) specified, which, if I am right, will mean that the device is 'on', in at least some capacity, all the time. Even when doing 'nothing' of any real consequence, if as many elements as possible aren't put to sleep, a non-trivial amount of power can be used. At the very beginning of the script, the author alludes to this in these lines . .  . But notice that they are commented out (the // at the beginning of each line), so this isn't actually being used in their code. 

There is a pretty easy 'cheat' if needed, to put your device to sleep in between fixes etc., using this board. I am big fan of these, as they just make everything super easy and power usage goes down to around 20uA. You just have to write a code snippet that will send a brief signal from your Feather board to the Timer board 'Done' pin and it will all go to sleep. In fact, you don't even need to do that if coding isn't your thing, as you can use a resistor and a capacitor to again 'cheat' and just allow the timer board to power the Feather for say, 80 seconds, which is usually long enough to get and save a fix - but you can pretty much make it any period of time with the right combination of resistor and capacitor. Happy to explain it further if needed. 

The one limitation is that the Timer board has a maximum interval of two hours (i.e. it will come on every two hours), but you'd still save a bunch of power if you had your GPS fix, accelerometer and SD data save all done within 80-100 seconds...

There are a bunch of gifted coders on WILDLABS that could help re-write code for you also if needed, or, if they are all busy, I am happy to try and help...I am by no means good at coding, but I am happy to try!

All the best,

Rob