Discussion:

- Data recording rate:

1) Attachment location: It is likely that our attachment location on the underside of the tail had a negative impact on the recording rate. To avoid rectrix breakage and undue bouncing when flapping, we decided to center the loggers’ weight as close to the base of the tail as possible: loggers placed on top of the tail would have covered the uropygial gland therefore we chose to attach them on the underside, between the undertail coverts and the rectrices, with the GPS antenna pointing up.

2) GPS fix time: The location of GPS satellites at the time of recording might have prevented successful logging. Indeed, while GPS devices used by the general public have an ample supply of power that allows them to always be in communication with the network’s satellites (“hot start”), low-power wildlife tracking devices only activate GPS communication at the time of logging (“cold start”). Thus the amount of time required for a successful GPS logging (which is limited a priori to optimize power consumption) is affected by the location of GPS satellites at the moment of the cold start. The 4-minutes limit on GPS fix might have been to short.

- Data recovery rate: Several possibilities exist for the lack of transmission:

1) Waterproofing failure: tests were performed to ensure that the waterproofing technique used in this study was resistant enough to sustain repeated immersions.

2) Death of tracked bird: The chicks of all tracked petrels were observed alive and in good condition in two visits in June and July, suggesting that tracked birds did not die during the tracking period.

3) Early loss of logger: Though the type of tape attachment I used in this study (which I reinforced with epoxy and a zip-tie) has been successful with other seabird, it is possible that rectrices broke off. I chose this technique instead of a dorsal attachment to keep the loggers from rubbing against the roof of rocky burrows, and to avoid the possibility of entanglement in hanging roots.

4) Early drain of logger battery:  Remote-download GPS loggers such as Mataki-LITE have two main drains of power: 1) activating the GPS module to listen to communications from the network’s satellites, and 2) using the UHF radio to communicate with the base-station and, later, upload tracking data. I had written the logging script to optimize battery use through a geofence and a low-voltage mode. Based on recovered tracking data, it appears that none of the functioning loggers had entered the low-voltage mode during the ca 10 days at-sea though two of them had battery levels below the low-voltage threshold at the time of uploading data to the base-station (Table B.2). Since logger battery levels are only recorded when they send a heartbeat to the base station, it is unclear if these low battery levels had been reached earlier during the tracking period without triggering the low-voltage mode, had triggered the low-voltage mode but GPS data were not recorded, or resulted from a power drain due to radio communications.

5) Not enough time within range of base-station: It is possible that the loggers that did not transmit tracking data were not able to contact their respective base-stations despite having sufficient battery voltages. Radar surveys and camera-trapping at breeding colonies showed that Black-capped Petrels may reach speeds up to 70km/h when arriving at colonies and enter their burrows instantly. Upon leaving the nest, petrels stay <5 minutes outside the burrow. Pre-deployment trials showed that loggers placed at a burrow’s entrance were able to communicate with base-stations but loggers placed inside a burrow’s tunnel were not. The 2-minute heartbeat activated inside the 25-km geofence to optimize power should have been sufficient to upload tracking data but loggers that had failed to trigger the 25-km geofence (or that had already entered the low-voltage mode) were less likely to be within range of the base-station (~200 m) for long enough to send a successful heartbeat.

Recommendations:

Mataki-LITE tags have a steep learning curve but they very adaptabile and cheap (for remote-download tags) so I hope these lessons-learned will prove useful for everybody. 

- Future deployments may benefit from an attachment above the tail, ensuring that the uropygial gland is not covered; to avoid undue stress to the rectrices, the center of gravity of the logger should be as close to the rump as possible. Try dorsal deployments on birds nesting in large sod burrows.

- Although it is possible to extend the time period allocated to successfully log a GPS location, this would drastically increase power consumption. Therefore, try to improve attachment location before extending the GPS “ON time”.

- Simultaneous logging of GPS locations and battery levels, and GPS logging frequency may have to be decreased to optimize power consumption.

- Wider geofence radius and a higher heartbeat frequency in low-power mode.

Feel free to start the conversation and share your own scripts, deployment techniques and fixes!

Thanks,

Yvan

Hi Yvan,

Glad you have chosen Xerius as from what I have seen their equipment is excellent and I was very impressed with their telemetry knowledge. We have one of their goniometer units and this has enabled us to locate a number of our downed satellite tagged birds.

As for making up dummy tags and testing harnesses then another option is Polymorph, especially if you are working on a limited budget after paying for a number of tags! You just drop the beads  into boiling water and mould into the shapes you require easily making holes and grooves etc. It sets rapidly and as you say the addition of nuts and bolts get you to your required weights.

https://www.maplin.co.uk/p/mindsets-polymorph-250g-n14at

Hi Kai - I asked for a UK supplier, but thanks.

Hi everyone -

I had a recommendation for http://www.wyremicrodesign.co.uk/. Apparently used successfully for a couple of projects, and designed/built some bespoke readers. The owner can be contacted on phil.rycroft@wyremicrodesign.co.uk.

I went with Francis Scientific Instruments in the end, as they've been reliable and helpful on past projects. You can contact Mike (Francis) on fsilog@btconnect.com.

Cheers, Ollie