<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://nerdswithoutborders.net/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dave</id>
	<title>Nerds Without Borders - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://nerdswithoutborders.net/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dave"/>
	<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Special:Contributions/Dave"/>
	<updated>2026-04-20T12:50:49Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.5</generator>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_communications_board_v.0.44&amp;diff=553</id>
		<title>Turtle Sense communications board v.0.44</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_communications_board_v.0.44&amp;diff=553"/>
		<updated>2017-08-09T23:33:00Z</updated>

		<summary type="html">&lt;p&gt;Dave: Power Supply description&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Communication board v.0.44 is the controlling circuitry for Turtle Sense. It connects, via a coax cable cable, to one or more Smart Sensors. A piggybacked M2M plug-in telephony board made by Janus enables GPS and cellular communications.&lt;br /&gt;
* [[Turtle Sense Communication Board PCB Schematic v.0.43|PCB schematic]]&lt;br /&gt;
&lt;br /&gt;
==Microprocessor==&lt;br /&gt;
The microprocessor (U1) is identical to the one on the Smart Sensor board.  It controls all the operation of the device.  Programmed in C, it manages all the circuitry by:&lt;br /&gt;
* timing events&lt;br /&gt;
* controlling, reading and recording data from the accelerometer IC&lt;br /&gt;
* uploading data to the Comm Board&lt;br /&gt;
We selected the[http://www.ti.com/lit/ds/symlink/msp430fr5949.pdf Texas Instruments MSP430FR5949] because it is extremely low power and contains 64 K of FRAM memory.  The 3.0V power from the Comm Board comes into U1 on AVCC and DVCC.  The power ground connections are on AVSS and DVSS.  There are three 8 bit I/O ports in the chip, labelled P1.0-P1.7, P2.0-P2.7, and P3.0-P3.7, plus three other I/O pins labelled P4.0, P4.1, and P4.4.  Some of these ports are connected to the Janus phone board, the power supplies, and to the coax transceiver (U4 and U5).  Many other I/O pins are not used, but are available on optional headers.  There are two pins connected to an external crystal (X1).  X1, along with C1 an C2, provide the chip with a precise 32.768 KHz clock which is used for the timing functions in the program.  The chip also has other internal higher frequency clocks.  Another set of pins on the chip, labelled J.0-J.3, -RST, and Test, are used for programming the chip.  These pins are connected to a PC via the JTAG connector J2.&lt;br /&gt;
&lt;br /&gt;
==Power supply==&lt;br /&gt;
The Comm Board is powered from a battery pack of 3 [http://www.corunusa.com/ni-mh low self discharge rechargeable NiMH AAA batteries] or Eneloop equivalent.  The battery pack is about 4.2V fully charged and has a capacity of 800 milliamp-hours. The battery pack is kept charged by a small solar cell mounted behind a plexiglas window at the top of the PVC enclosure. The solar cell was custom made by _____ in China, and is rated 5.8V 38 mA. A charging circuit limits and equalizes the voltage on the three AAA cells. D6 supplies a voltage reference to op amp U6d, the output of which turns on Q1 whenever the battery voltage reaches 4.2V. Q1 then shunts any additional current from the solar cell to a pair of high brightness LEDs, D3 and D4. The two LEDs serve as indicators that the batteries are fully charged. Op amp U6a compares a fraction of the solar cell voltage to a fraction of the battery voltage. When the solar cell voltage is not sufficient to charge the batteries, U6a turns off Q2, thereby saving a small drain on the batteries from R25 and D6. Op amps U6b and U6c equalizes the voltages of the three batteries by either adding or subtracting a small amount of current from the two nodes between the batteries. &lt;br /&gt;
The battery pack powers four power supplies on the board: &lt;br /&gt;
* a 3.0V linear low power voltage regulator (U3) which powers the microprocessor (U1) and related circuitry on the board.&lt;br /&gt;
* a 5.0V switching voltage regulator (U2) which powers the Phone Board.&lt;br /&gt;
* another 3.0V linear regulator (U7) which supplies power to the sensors via the coax cable.&lt;br /&gt;
* another 3.0V linear regulator (U9) which supplies power for any auxiliary uses.  &lt;br /&gt;
The 3.0V regulator U3 is on at all times, and its output is filtered by capacitors C5 and C6. The higher powered 5.0V regulator U2 is only turned on when the phone board is needed, in order to conserve battery power.  Its output is filtered by C12, C13, C17, and C18. U2 is turned on by a positive signal (PhnPower) from the microprocessor U1. U7 is turned on by a positive signal (SnsrEn) from the microprocessor. U9 is turned on by a positive signal (AuxEn) from the microprocessor. An analog switch (U10) is used to monitor the battery voltage.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_communications_board_v.0.44&amp;diff=550</id>
		<title>Turtle Sense communications board v.0.44</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_communications_board_v.0.44&amp;diff=550"/>
		<updated>2016-07-01T05:25:48Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Microprocessor */ Start page and microprocessor section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Communication board v.0.44 is the controlling circuitry for Turtle Sense. It connects, via a coax cable cable, to one or more Smart Sensors. A piggybacked M2M plug-in telephony board made by Janus enables GPS and cellular communications.&lt;br /&gt;
* [[Turtle Sense Communication Board PCB Schematic v.0.43|PCB schematic]]&lt;br /&gt;
&lt;br /&gt;
==Microprocessor==&lt;br /&gt;
The microprocessor (U1) is identical to the one on the Smart Sensor board.  It controls all the operation of the device.  Programmed in C, it manages all the circuitry by:&lt;br /&gt;
* timing events&lt;br /&gt;
* controlling, reading and recording data from the accelerometer IC&lt;br /&gt;
* uploading data to the Comm Board&lt;br /&gt;
We selected the[http://www.ti.com/lit/ds/symlink/msp430fr5949.pdf Texas Instruments MSP430FR5949] because it is extremely low power and contains 64 K of FRAM memory.  The 3.0V power from the Comm Board comes into U1 on AVCC and DVCC.  The power ground connections are on AVSS and DVSS.  There are three 8 bit I/O ports in the chip, labelled P1.0-P1.7, P2.0-P2.7, and P3.0-P3.7, plus three other I/O pins labelled P4.0, P4.1, and P4.4.  Some of these ports are connected to the Janus phone board, the power supplies, and to the coax transceiver (U4 and U5).  Many other I/O pins are not used, but are available on optional headers.  There are two pins connected to an external crystal (X1).  X1, along with C1 an C2, provide the chip with a precise 32.768 KHz clock which is used for the timing functions in the program.  The chip also has other internal higher frequency clocks.  Another set of pins on the chip, labelled J.0-J.3, -RST, and Test, are used for programming the chip.  These pins are connected to a PC via the JTAG connector J2.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_communications_board_v.0.44&amp;diff=549</id>
		<title>Turtle Sense communications board v.0.44</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_communications_board_v.0.44&amp;diff=549"/>
		<updated>2016-07-01T05:02:12Z</updated>

		<summary type="html">&lt;p&gt;Dave: Create page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Microprocessor==&lt;br /&gt;
The microprocessor (U1) is identical to the one on the Smart Sensor Board.  It controls all the operation of the device.  Programmed in C, it manages all the circuitry by:&lt;br /&gt;
* timing events&lt;br /&gt;
* controlling, reading and recording data from the accelerometer IC&lt;br /&gt;
* uploading data to the Comm Board&lt;br /&gt;
We selected the[http://www.ti.com/lit/ds/symlink/msp430fr5949.pdf Texas Instruments MSP430FR5949] because it is extremely low power and contains 64 K of FRAM memory.  The 3.0V power from the Comm Board comes into U1 on AVCC and DVCC.  The power ground connections are on AVSS and DVSS.  There are three 8 bit I/O ports in the chip, labelled P1.0-P1.7, P2.0-P2.7, and P3.0-P3.7, plus three other I/O pins labelled P4.0, P4.1, and P4.4.  Some of these ports are connected to the Janus phone board, the power supplies, and to the coax transceiver (U4 and U5).  Many other I/O pins are not used, but are available on optional headers.  There are two pins connected to an external crystal (X1).  X1, along with C1 an C2, provide the chip with a precise 32.768 KHz clock which is used for the timing functions in the program.  The chip also has other internal higher frequency clocks.  Another set of pins on the chip, labelled J.0-J.3, -RST, and Test, are used for programming the chip.  These pins are connected to a PC via the JTAG connector J2.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=548</id>
		<title>Turtle Sense Smart Sensor board v.0.46</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=548"/>
		<updated>2016-07-01T01:56:55Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Transceiver */ Edited for description of phase 3 new circuit&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Smart Sensor v.0.46 is the sensor board which connects to the main [[Turtle Sense communications board v.0.43|Communications Board]].  The Smart Sensor contains a microprocessor, an accelerometer sensor IC, and a Transceiver IC.&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.46|PCB schematic]]&lt;br /&gt;
&lt;br /&gt;
==Microprocessor==&lt;br /&gt;
The microprocessor (U1) is identical to the one on the Comm Board.  It controls all the operation of the device.  Programmed in C, it manages all the circuitry by:&lt;br /&gt;
* timing events&lt;br /&gt;
* controlling, reading and recording data from the accelerometer IC&lt;br /&gt;
* uploading data to the Comm Board&lt;br /&gt;
We selected the[http://www.ti.com/lit/ds/symlink/msp430fr5949.pdf Texas Instruments MSP430FR5949] because it is extremely low power and contains 64 K of FRAM memory.  The 3.0V power from the Comm Board comes into U1 on AVCC and DVCC.  The power ground connections are on AVSS and DVSS.  There are three 8 bit I/O ports in the chip, labelled P1.0-P1.7, P2.0-P2.7, and P3.0-P3.7, plus three other I/O pins labelled P4.0, P4.1, and P4.4.  Some of these ports are connected to the accelerometer (U2), the moisture sensing circuit (C12-13 plus other parts), and to the coax transceiver (U3 and U4).  Many other I/O pins are not used, but are available on an optional header..  There are two pins connected to an external crystal (X1).  X1, along with C1 an C2, provide the chip with a precise 32.768 KHz clock which is used for the timing functions in the program.  The chip also has other internal higher frequency clocks.  Another set of pins on the chip, labelled J.0-J.3, -RST, and Test, are used for programming the chip.  These pins are connected to a PC via the JTAG connector J2.  Since the Smart Sensor is cast in polyurethane resin, after it is cast it cannot be programmed again.  However, many of the operating parameters can later be changed by downloading them from the Comm Board.&lt;br /&gt;
&lt;br /&gt;
==Accelerometer==&lt;br /&gt;
The accelerometer sensor IC (U2) is an [http://dlnmh9ip6v2uc.cloudfront.net/datasheets/BreakoutBoards/ADXL362.pdf Analog Devices ADXL362].  The accelerometer measures the forces (including gravity) acting on it in 3 axes, and also temperature.  The IC is extremely low powered and low noise.  The microprocessor controls an analog switch (U4) which switches the 3.3V power going to the accelerometer. 3.0V power is supplied to the chip from the microprocessor I/O pin P2.7.  The accelerometer has two power inputs, labeled Vio and Vs.  Vio is the power for the digital circuitry, and Vs powers the low level analog circuitry.  Vs is filtered from any digital noise on Vio by R7 and C7. The accelerometer communicates with the microprocessor via a standard 4-wire SPI interface.  These four signals are labeled /CS, CLK, MOSI, and MISO.  In addition the accelerometer has two interrupt lines (INT1 and INT2) going to the microprocessor.&lt;br /&gt;
&lt;br /&gt;
==Coax Transceiver==&lt;br /&gt;
The Smart Sensor has a [http://www.ti.com/lit/ds/symlink/sn74lvc1g240.pdf SN74LVC1G240 driver IC] (U4) and a [http://ww1.microchip.com/downloads/en/DeviceDoc/21696H.pdf MCP6541 receiver IC] (U3), identical to the ones on the Comm board.  Communication and 3.0V DC power are over a single wire (RG6 75 ohm coax cable).  The DC power is isolated from the AC serial communication signal by a bias T consisting of L1 and C8.&lt;br /&gt;
&lt;br /&gt;
The microprocessor sends a 1 MHz signal to the input of the driver (U4).  The microprocessor also sends a serial 115 kilobaud UART signal to the Enable input of the driver. Thus the output of the driver is a 1 MHz signal modulated by the UART signal.  The driver output is capable of driving at least 400&amp;#039; of RG6 cable.&lt;br /&gt;
&lt;br /&gt;
Serial UART signals are received by U3, which acts as a comparator. The non-inverting input filters the rectified incoming signal on the wire with a time constant of about 1 msec, which is a little longer than one byte of data.  The non-inverting input also has a small DC bias added to keep the output of the comparator in the correct state (logic high) when no signal is being received.  The inverting input of the comparator is filtered with a much shorter 2.7 usec time constant, which removes the 1 MHz carrier but retains the individual bit data.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=547</id>
		<title>Turtle Sense Smart Sensor board v.0.46</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=547"/>
		<updated>2016-06-30T23:29:01Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Accelerometer */ Edit for different U numbers and new power source.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Smart Sensor v.0.46 is the sensor board which connects to the main [[Turtle Sense communications board v.0.43|Communications Board]].  The Smart Sensor contains a microprocessor, an accelerometer sensor IC, and a Transceiver IC.&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.46|PCB schematic]]&lt;br /&gt;
&lt;br /&gt;
==Microprocessor==&lt;br /&gt;
The microprocessor (U1) is identical to the one on the Comm Board.  It controls all the operation of the device.  Programmed in C, it manages all the circuitry by:&lt;br /&gt;
* timing events&lt;br /&gt;
* controlling, reading and recording data from the accelerometer IC&lt;br /&gt;
* uploading data to the Comm Board&lt;br /&gt;
We selected the[http://www.ti.com/lit/ds/symlink/msp430fr5949.pdf Texas Instruments MSP430FR5949] because it is extremely low power and contains 64 K of FRAM memory.  The 3.0V power from the Comm Board comes into U1 on AVCC and DVCC.  The power ground connections are on AVSS and DVSS.  There are three 8 bit I/O ports in the chip, labelled P1.0-P1.7, P2.0-P2.7, and P3.0-P3.7, plus three other I/O pins labelled P4.0, P4.1, and P4.4.  Some of these ports are connected to the accelerometer (U2), the moisture sensing circuit (C12-13 plus other parts), and to the coax transceiver (U3 and U4).  Many other I/O pins are not used, but are available on an optional header..  There are two pins connected to an external crystal (X1).  X1, along with C1 an C2, provide the chip with a precise 32.768 KHz clock which is used for the timing functions in the program.  The chip also has other internal higher frequency clocks.  Another set of pins on the chip, labelled J.0-J.3, -RST, and Test, are used for programming the chip.  These pins are connected to a PC via the JTAG connector J2.  Since the Smart Sensor is cast in polyurethane resin, after it is cast it cannot be programmed again.  However, many of the operating parameters can later be changed by downloading them from the Comm Board.&lt;br /&gt;
&lt;br /&gt;
==Accelerometer==&lt;br /&gt;
The accelerometer sensor IC (U2) is an [http://dlnmh9ip6v2uc.cloudfront.net/datasheets/BreakoutBoards/ADXL362.pdf Analog Devices ADXL362].  The accelerometer measures the forces (including gravity) acting on it in 3 axes, and also temperature.  The IC is extremely low powered and low noise.  The microprocessor controls an analog switch (U4) which switches the 3.3V power going to the accelerometer. 3.0V power is supplied to the chip from the microprocessor I/O pin P2.7.  The accelerometer has two power inputs, labeled Vio and Vs.  Vio is the power for the digital circuitry, and Vs powers the low level analog circuitry.  Vs is filtered from any digital noise on Vio by R7 and C7. The accelerometer communicates with the microprocessor via a standard 4-wire SPI interface.  These four signals are labeled /CS, CLK, MOSI, and MISO.  In addition the accelerometer has two interrupt lines (INT1 and INT2) going to the microprocessor.&lt;br /&gt;
&lt;br /&gt;
==Transceiver==&lt;br /&gt;
The Smart Sensor has an [http://www.analog.com/static/imported-files/data_sheets/ADM3483_3485_3488_3490_3491.pdf ADM 3483 RS485 transceiver IC]  (U2) identical to the one on the Comm Board.  The two transceivers send and receive data over the sensor cable as differential twisted pairs.  That is, there are two wires for transmitting data (labeled Y and Z on the transceiver), and two wires for receiving data (labeled A and B on the transceiver).  The reason for this is to improve noise immunity on the cable and to allow faster data rates.  Note that the data pairs are crossed between the two transceivers - that is, the send pair on one transceiver is connected to the receive pair on the other transceiver.  The communication uses standard RS485 UART protocol at 115,200 baud.  A resistor (R8) is a termination resistor on the receive inputs of U2 in order to prevent signal reflections travelling back to the Comm Board transceiver outputs. The RS485 Transceivers in the circuitry are capable of driving a signal through several hundred feet of cable.  However, the response timing in the program may need to be adjusted if long lengths of cable are used.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=546</id>
		<title>Turtle Sense Smart Sensor board v.0.46</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=546"/>
		<updated>2016-06-30T23:22:04Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Microprocessor */ Edit for phase 3 newer version of chip.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Smart Sensor v.0.46 is the sensor board which connects to the main [[Turtle Sense communications board v.0.43|Communications Board]].  The Smart Sensor contains a microprocessor, an accelerometer sensor IC, and a Transceiver IC.&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.46|PCB schematic]]&lt;br /&gt;
&lt;br /&gt;
==Microprocessor==&lt;br /&gt;
The microprocessor (U1) is identical to the one on the Comm Board.  It controls all the operation of the device.  Programmed in C, it manages all the circuitry by:&lt;br /&gt;
* timing events&lt;br /&gt;
* controlling, reading and recording data from the accelerometer IC&lt;br /&gt;
* uploading data to the Comm Board&lt;br /&gt;
We selected the[http://www.ti.com/lit/ds/symlink/msp430fr5949.pdf Texas Instruments MSP430FR5949] because it is extremely low power and contains 64 K of FRAM memory.  The 3.0V power from the Comm Board comes into U1 on AVCC and DVCC.  The power ground connections are on AVSS and DVSS.  There are three 8 bit I/O ports in the chip, labelled P1.0-P1.7, P2.0-P2.7, and P3.0-P3.7, plus three other I/O pins labelled P4.0, P4.1, and P4.4.  Some of these ports are connected to the accelerometer (U2), the moisture sensing circuit (C12-13 plus other parts), and to the coax transceiver (U3 and U4).  Many other I/O pins are not used, but are available on an optional header..  There are two pins connected to an external crystal (X1).  X1, along with C1 an C2, provide the chip with a precise 32.768 KHz clock which is used for the timing functions in the program.  The chip also has other internal higher frequency clocks.  Another set of pins on the chip, labelled J.0-J.3, -RST, and Test, are used for programming the chip.  These pins are connected to a PC via the JTAG connector J2.  Since the Smart Sensor is cast in polyurethane resin, after it is cast it cannot be programmed again.  However, many of the operating parameters can later be changed by downloading them from the Comm Board.&lt;br /&gt;
&lt;br /&gt;
==Accelerometer==&lt;br /&gt;
The accelerometer sensor IC (U3) is an [http://dlnmh9ip6v2uc.cloudfront.net/datasheets/BreakoutBoards/ADXL362.pdf Analog Devices ADXL362].  The accelerometer measures the forces (including gravity) acting on it in 3 axes, and also temperature.  The IC is extremely low powered and low noise.  The microprocessor controls an analog switch (U4) which switches the 3.3V power going to the accelerometer.  The accelerometer has two power inputs, labeled Vio and Vs.  Vio is the power for the digital circuitry, and Vs powers the low level analog circuitry.  Vs is filtered from any digital noise on Vio by R7 and C7.  The output of U4 is normally connected to the 3.3V switch input.  A logic high pulse from the microprocessor connects the 3.3V accelerometer power to ground to reset it.  The accelerometer communicates with the microprocessor via a standard 4-wire SPI interface.  These four signals are labeled /CS, CLK, MOSI, and MISO.  In addition the accelerometer has two interrupt lines (INT1 and INT2) going to the microprocessor.&lt;br /&gt;
&lt;br /&gt;
==Transceiver==&lt;br /&gt;
The Smart Sensor has an [http://www.analog.com/static/imported-files/data_sheets/ADM3483_3485_3488_3490_3491.pdf ADM 3483 RS485 transceiver IC]  (U2) identical to the one on the Comm Board.  The two transceivers send and receive data over the sensor cable as differential twisted pairs.  That is, there are two wires for transmitting data (labeled Y and Z on the transceiver), and two wires for receiving data (labeled A and B on the transceiver).  The reason for this is to improve noise immunity on the cable and to allow faster data rates.  Note that the data pairs are crossed between the two transceivers - that is, the send pair on one transceiver is connected to the receive pair on the other transceiver.  The communication uses standard RS485 UART protocol at 115,200 baud.  A resistor (R8) is a termination resistor on the receive inputs of U2 in order to prevent signal reflections travelling back to the Comm Board transceiver outputs. The RS485 Transceivers in the circuitry are capable of driving a signal through several hundred feet of cable.  However, the response timing in the program may need to be adjusted if long lengths of cable are used.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=545</id>
		<title>Turtle Sense Smart Sensor board v.0.46</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_board_v.0.46&amp;diff=545"/>
		<updated>2016-06-23T03:55:22Z</updated>

		<summary type="html">&lt;p&gt;Dave: Start page - needs text editing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Smart Sensor v.0.46 is the sensor board which connects to the main [[Turtle Sense communications board v.0.43|Communications Board]].  The Smart Sensor contains a microprocessor, an accelerometer sensor IC, and a Transceiver IC.&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.46|PCB schematic]]&lt;br /&gt;
&lt;br /&gt;
==Microprocessor==&lt;br /&gt;
The microprocessor (U1) is identical to the one on the Comm Board.  It controls all the operation of the device.  Programmed in C, it manages all the circuitry by:&lt;br /&gt;
* timing events&lt;br /&gt;
* controlling, reading and recording data from the accelerometer IC&lt;br /&gt;
* uploading data to the Comm Board&lt;br /&gt;
We selected the[http://www.ti.com/lit/ds/symlink/msp430fr5739.pdf Texas Instruments MSP430FR5739] because it is extremely low power and contains 16 K of FRAM memory.  Newer versions of this chip contain more memory and will likely be used in future versions.  The 3.3V power from the Comm Board comes into U1 on AVCC and DVCC.  The power ground connections are on AVSS and DVSS.  There are three 8 bit I/O ports in the chip, labelled P1.0-P1.7, P2.0-P2.7, and P3.0-P3.7.  Some of these ports are connected to the accelerometer (U3) and to the transceiver (U2), and many others are not used.  There are two pins connected to an external crystal (X1).  X1, along with C1 an C2, provide the chip with a precise 32.768 KHz clock which is used for the timing functions in the program.  The chip also has other internal higher frequency clocks.  Another set of pins on the chip, labelled J.0-J.3, -RST, and Test, are used for programming the chip.  These pins are connected to a PC via the JTAG connector J2.  Since the Smart Sensor is cast in polyurethane resin, after it is cast it cannot be programmed again.  However, many of the operating parameters can later be changed by downloading them from the Comm Board.&lt;br /&gt;
&lt;br /&gt;
==Accelerometer==&lt;br /&gt;
The accelerometer sensor IC (U3) is an [http://dlnmh9ip6v2uc.cloudfront.net/datasheets/BreakoutBoards/ADXL362.pdf Analog Devices ADXL362].  The accelerometer measures the forces (including gravity) acting on it in 3 axes, and also temperature.  The IC is extremely low powered and low noise.  The microprocessor controls an analog switch (U4) which switches the 3.3V power going to the accelerometer.  The accelerometer has two power inputs, labeled Vio and Vs.  Vio is the power for the digital circuitry, and Vs powers the low level analog circuitry.  Vs is filtered from any digital noise on Vio by R7 and C7.  The output of U4 is normally connected to the 3.3V switch input.  A logic high pulse from the microprocessor connects the 3.3V accelerometer power to ground to reset it.  The accelerometer communicates with the microprocessor via a standard 4-wire SPI interface.  These four signals are labeled /CS, CLK, MOSI, and MISO.  In addition the accelerometer has two interrupt lines (INT1 and INT2) going to the microprocessor.&lt;br /&gt;
&lt;br /&gt;
==Transceiver==&lt;br /&gt;
The Smart Sensor has an [http://www.analog.com/static/imported-files/data_sheets/ADM3483_3485_3488_3490_3491.pdf ADM 3483 RS485 transceiver IC]  (U2) identical to the one on the Comm Board.  The two transceivers send and receive data over the sensor cable as differential twisted pairs.  That is, there are two wires for transmitting data (labeled Y and Z on the transceiver), and two wires for receiving data (labeled A and B on the transceiver).  The reason for this is to improve noise immunity on the cable and to allow faster data rates.  Note that the data pairs are crossed between the two transceivers - that is, the send pair on one transceiver is connected to the receive pair on the other transceiver.  The communication uses standard RS485 UART protocol at 115,200 baud.  A resistor (R8) is a termination resistor on the receive inputs of U2 in order to prevent signal reflections travelling back to the Comm Board transceiver outputs. The RS485 Transceivers in the circuitry are capable of driving a signal through several hundred feet of cable.  However, the response timing in the program may need to be adjusted if long lengths of cable are used.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=544</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=544"/>
		<updated>2016-06-23T03:42:44Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Parts lists */  Added version number to text&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a solar cell control circuit for recharging three onboard AAA cells, a coax transceiver circuit, and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings.  The PVC pipe is anchored in a bucket filled with concrete.  The concrete base and RG6 coax cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards.&lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the RG6 coax cable and connector for the turtle egg sensor, and one cell antenna for the communications tower.  The units should be able to operate continuously running on three low self-discharge NiMH Batteries, which are kept charged by a small solar cell in the top of the PVC enclosure.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Comm%20Unit%200.43%20--%20Bill%20of%20Materials%20--%20Completely%20filled%20PCB.xls Turtle Sense Communications 0.43 board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Smart%20Sensor%200.46%20--%20Bill%20of%20Materials%20--%20PCB%20Assembly%20only.xls Turtle Sense Smart Sensor 0.46 board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of Phase 3 System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.46|Smart Sensor PCB 0.46 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.46|Smart Sensor PCB 0.46 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.44|Communications PCB 0.44 schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.44|Communications PCB 0.44 description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_Phase_3_System&amp;diff=543</id>
		<title>Block Diagram of Phase 3 System</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_Phase_3_System&amp;diff=543"/>
		<updated>2016-06-23T02:18:41Z</updated>

		<summary type="html">&lt;p&gt;Dave: New page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense Block Diagram Phase 3]]&lt;br /&gt;
[[File:System Diagram Phase 3 - As Built.jpg|795px]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.44&amp;diff=542</id>
		<title>Turtle Sense Communications PCB Schematic v.0.44</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.44&amp;diff=542"/>
		<updated>2016-06-23T01:15:20Z</updated>

		<summary type="html">&lt;p&gt;Dave: Added JPG file of schematic - changed from v.43 to v.44&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense Communications board v.0.44|Circuit description]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.44 Page 1.jpg|795px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.44 Page 2.jpg|795px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.44 Page 3.jpg|795px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.44 Page 4.jpg|795px]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=541</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=541"/>
		<updated>2016-06-23T01:13:25Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Schematics and System design */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a solar cell control circuit for recharging three onboard AAA cells, a coax transceiver circuit, and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings.  The PVC pipe is anchored in a bucket filled with concrete.  The concrete base and RG6 coax cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards.&lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the RG6 coax cable and connector for the turtle egg sensor, and one cell antenna for the communications tower.  The units should be able to operate continuously running on three low self-discharge NiMH Batteries, which are kept charged by a small solar cell in the top of the PVC enclosure.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Comm%20Unit%200.43%20--%20Bill%20of%20Materials%20--%20Completely%20filled%20PCB.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Smart%20Sensor%200.46%20--%20Bill%20of%20Materials%20--%20PCB%20Assembly%20only.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of Phase 3 System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.46|Smart Sensor PCB 0.46 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.46|Smart Sensor PCB 0.46 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.44|Communications PCB 0.44 schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.44|Communications PCB 0.44 description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_4.jpg&amp;diff=540</id>
		<title>File:Turtle Sense Comm Unit 0.44 Page 4.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_4.jpg&amp;diff=540"/>
		<updated>2016-06-23T01:09:18Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_3.jpg&amp;diff=539</id>
		<title>File:Turtle Sense Comm Unit 0.44 Page 3.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_3.jpg&amp;diff=539"/>
		<updated>2016-06-23T01:08:21Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_2.jpg&amp;diff=538</id>
		<title>File:Turtle Sense Comm Unit 0.44 Page 2.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_2.jpg&amp;diff=538"/>
		<updated>2016-06-23T01:07:36Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_1.jpg&amp;diff=537</id>
		<title>File:Turtle Sense Comm Unit 0.44 Page 1.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.44_Page_1.jpg&amp;diff=537"/>
		<updated>2016-06-23T01:06:55Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.43&amp;diff=536</id>
		<title>Turtle Sense Communications PCB Schematic v.0.43</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.43&amp;diff=536"/>
		<updated>2016-06-22T23:17:53Z</updated>

		<summary type="html">&lt;p&gt;Dave: Added JPG file of schematic&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense Communications board v.0.43|Circuit description]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 1.jpg|795px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 2.jpg|795px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 3.jpg|795px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 4.jpg|795px]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=535</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=535"/>
		<updated>2016-06-22T23:08:55Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Schematics and System design */  Add pages for phase 3&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a solar cell control circuit for recharging three onboard AAA cells, a coax transceiver circuit, and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings.  The PVC pipe is anchored in a bucket filled with concrete.  The concrete base and RG6 coax cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards.&lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the RG6 coax cable and connector for the turtle egg sensor, and one cell antenna for the communications tower.  The units should be able to operate continuously running on three low self-discharge NiMH Batteries, which are kept charged by a small solar cell in the top of the PVC enclosure.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Comm%20Unit%200.43%20--%20Bill%20of%20Materials%20--%20Completely%20filled%20PCB.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Smart%20Sensor%200.46%20--%20Bill%20of%20Materials%20--%20PCB%20Assembly%20only.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of Phase 3 System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.46|Smart Sensor PCB 0.46 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.46|Smart Sensor PCB 0.46 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.43|Communications PCB 0.43 schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.43|Communications PCB 0.43 description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.25a&amp;diff=534</id>
		<title>Turtle Sense Communications PCB Schematic v.0.25a</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.25a&amp;diff=534"/>
		<updated>2016-06-22T22:32:53Z</updated>

		<summary type="html">&lt;p&gt;Dave: Undo revision 530 by Dave (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense communications board v.0.25a|Circuit description]]&lt;br /&gt;
[[File:Turtle Sense Comm PCB schematic v0.25a pg1.jpg|800px|Communications board v.0.25a page 1.]]&lt;br /&gt;
[[File:Turtle Sense Comm PCB schematic v0.25a pg2.jpg|800px|Communications board v.0.25a page 2.]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_System&amp;diff=533</id>
		<title>Block Diagram of System</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_System&amp;diff=533"/>
		<updated>2016-06-22T22:30:38Z</updated>

		<summary type="html">&lt;p&gt;Dave: Undo revision 523 by Dave (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense Block Diagram v.0.25]]&lt;br /&gt;
[[File:Turtle_Sense_0.25_Block_Diagram.jpg|795px|Smart Sensor 0.25.]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.25a&amp;diff=530</id>
		<title>Turtle Sense Communications PCB Schematic v.0.25a</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Communications_PCB_Schematic_v.0.25a&amp;diff=530"/>
		<updated>2016-06-22T21:28:11Z</updated>

		<summary type="html">&lt;p&gt;Dave: Added JPG file of schematic&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense communications board v.0.43|Circuit description]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 1.jpg|800px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 2.jpg|800px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 3.jpg|800px]]&lt;br /&gt;
[[File:Turtle Sense Comm Unit 0.43 Page 4.jpg|800px]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_PCB_Schematic_v.0.24&amp;diff=529</id>
		<title>Turtle Sense Smart Sensor PCB Schematic v.0.24</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_Smart_Sensor_PCB_Schematic_v.0.24&amp;diff=529"/>
		<updated>2016-06-22T21:17:01Z</updated>

		<summary type="html">&lt;p&gt;Dave: Added JPG file of schematic&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense Smart Sensor board v.0.26|Circuit description]]&lt;br /&gt;
[[File:Smart Sensor 0.46.jpg|795px]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_4.jpg&amp;diff=528</id>
		<title>File:Turtle Sense Comm Unit 0.43 Page 4.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_4.jpg&amp;diff=528"/>
		<updated>2016-06-22T21:08:06Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_3.jpg&amp;diff=527</id>
		<title>File:Turtle Sense Comm Unit 0.43 Page 3.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_3.jpg&amp;diff=527"/>
		<updated>2016-06-22T21:07:24Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_2.jpg&amp;diff=526</id>
		<title>File:Turtle Sense Comm Unit 0.43 Page 2.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_2.jpg&amp;diff=526"/>
		<updated>2016-06-22T21:06:37Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_1.jpg&amp;diff=525</id>
		<title>File:Turtle Sense Comm Unit 0.43 Page 1.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.43_Page_1.jpg&amp;diff=525"/>
		<updated>2016-06-22T21:05:54Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Smart_Sensor_0.46.jpg&amp;diff=524</id>
		<title>File:Smart Sensor 0.46.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Smart_Sensor_0.46.jpg&amp;diff=524"/>
		<updated>2016-06-22T21:05:07Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_System&amp;diff=523</id>
		<title>Block Diagram of System</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_System&amp;diff=523"/>
		<updated>2016-06-22T20:20:49Z</updated>

		<summary type="html">&lt;p&gt;Dave: Added JPG file of Block Diagram&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense Block Diagram Phase 3]]&lt;br /&gt;
[[File:System Diagram Phase 3 - As Built.jpg]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:System_Diagram_Phase_3_-_As_Built.jpg&amp;diff=522</id>
		<title>File:System Diagram Phase 3 - As Built.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:System_Diagram_Phase_3_-_As_Built.jpg&amp;diff=522"/>
		<updated>2016-06-22T20:13:07Z</updated>

		<summary type="html">&lt;p&gt;Dave: System Diagram Phase 3 As Built&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;System Diagram Phase 3 As Built&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=521</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=521"/>
		<updated>2016-06-22T00:26:35Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Parts lists */  Start Phase 3 edits - links to Excel parts lists&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a solar cell control circuit for recharging three onboard AAA cells, a coax transceiver circuit, and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings.  The PVC pipe is anchored in a bucket filled with concrete.  The concrete base and RG6 coax cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards.&lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the RG6 coax cable and connector for the turtle egg sensor, and one cell antenna for the communications tower.  The units should be able to operate continuously running on three low self-discharge NiMH Batteries, which are kept charged by a small solar cell in the top of the PVC enclosure.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Comm%20Unit%200.43%20--%20Bill%20of%20Materials%20--%20Completely%20filled%20PCB.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Smart%20Sensor%200.46%20--%20Bill%20of%20Materials%20--%20PCB%20Assembly%20only.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.24|Smart Sensor PCB 0.24 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.24|Smart Sensor PCB 0.24 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.25a|Communications PCB 0.25a schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.25a|Communications PCB 0.25a description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense&amp;diff=520</id>
		<title>Turtle Sense</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense&amp;diff=520"/>
		<updated>2016-06-21T23:55:38Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Phase Three Goals */  add link and changed to description&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;;Using high tech sensors and cell phone networks to protect sea turtle hatchlings&lt;br /&gt;
[[File:HIOC turtle sense logo.jpg|right]]&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
[[File:Hawaii turtle 2.JPG|400px|right]]&lt;br /&gt;
Sea turtles have existed for 100 million years, but in the last century, the impacts of man through accidental capture in fishing nets, habitat destruction, pollution, and plastics in the ocean have significantly reduced populations by as much as 95%.   Six of the seven species nest in the warmer beaches of the US, and all of these are protected by the Endangered Species Act of 1973.  Although volunteer groups and park personnel can identify egg-laying sites almost immediately, the hatching date (when they emerge onto the beach) cannot be predicted—it will happen sometime in a six-week period beginning 50 days after the eggs are laid.  All 100 to 150 of the sea turtle hatchlings in a nest usually appear simultaneously (mostly at night) on some unpredictable date during that six-week period.  The hatchlings “boil” out of the sand and begin a dash to the ocean, one of the most touching sights in nature.&lt;br /&gt;
&lt;br /&gt;
Beginning at 50 days after the eggs are laid, the National Park Service (NPS) at the Cape Hatteras National Seashore fences off a lane from the nest to the ocean and forbids other access to that lane until either the hatchlings appear or the 100 days has elapsed.  This long protection period creates conflicts with other uses for beach access, such as fishing and vehicular movement for recreation and safety.  Conflicts are inevitable, often leading to lawsuits.&lt;br /&gt;
&lt;br /&gt;
== Project Objective==&lt;br /&gt;
[[File:Baby sea turtles make their way toward the water.jpg|thumb|400px|left|This project is developing technology to help protect sea turtle hatchlings at their first crisis:  emerging from the egg and making it to the ocean.  Hatching happens on an unpredictable day sometime during a six-week window beginning 50 days after the eggs are laid.  Predicting the hatching date to within a few days is the goal of this project.]]&lt;br /&gt;
The goal of the project is to develop simple, inexpensive technology for determining when a &amp;quot;boil&amp;quot; will occur with as much accuracy and reliability as possible.  The current design employs a sensor that measures egg motion either as the embryos agitate in the egg or as the sea turtle hatchlings begin to pip out of the eggs or both. The results, perhaps including modeling, will hopefully be able to predict hatching dates (arrival on the beach) to a reliable one-to-three-day window, a significant improvement over the current six-week window.  Developing a reliable technology for predicting hatching will allow the NPS to create a new protocol for protecting the nests, thus freeing up access to the beaches for a significantly longer time.&lt;br /&gt;
&lt;br /&gt;
There are several possible beneficial side effects of the technology:&lt;br /&gt;
* The technology can be used to help develop ecotourism around the hatching of sea turtles. Once people (especially young people) experience the hatching of these creatures, they may be much more likely to think positively about the welfare of sea turtles in the future.&lt;br /&gt;
* If local people can develop an income around this ecotourism activity, they may be less averse to the obstructions to beach vehicles and foot traffic. &lt;br /&gt;
* The technology might be useful for scientists studying sea turtles and might be adaptable for the study of other egg-laying species.&lt;br /&gt;
&lt;br /&gt;
All the designs and software code will be published on this website and will be available for use worldwide.  All data created by the system will be made available to researchers worldwide.&lt;br /&gt;
&lt;br /&gt;
== History ==&lt;br /&gt;
The device began with an idea from Eric Kaplan, founder of a company that develops Bluetooth wireless technology test equipment.  Kaplan sold his company to his employees and later founded the Hatteras Island Ocean Center (www.hioceancenter.org), a nonprofit, 501(c)(3) ecology education center on Hatteras Island in North Carolina.  Kaplan saw the need for this technology and approached his childhood friend Tom Zimmerman, an IBM Research–Almaden (San Jose, CA) electrical engineer for assistance.  Zimmerman designed the sensor package in 2013 as a public service commitment from IBM.  Tom recruited his college buddy, Samuel Wantman a retired software designer, and they worked on developing the first phase of the design with support from IBM and from the National Park Service.  Britta Muiznieks, a biologist with the NPS has been coordinating the Park&amp;#039;s involvement.  The first phase of the project was a very quick and inexpensive hack of cell phones with a simple custom circuit board to test the viability of the project.  The devices were tried in a few nests in 2013, but unfortunately it was too late in the season to get any data from viable nests.  Even so, there was enough learned to make everyone involved in the project believe that there was the potential to make the technology work.&lt;br /&gt;
&lt;br /&gt;
Wantman took over management of the project in 2014, as Zimmerman had to return to other commitments at IBM.  Additional volunteers were recruited, including David Hermeyer a retired electrical engineer and Charles Wade a retired IBM Research manager.  Phase Two of the project involves developing a more robust custom sensor embedded in a plastic sphere the same size and shape as a turtle egg, with industry standard technology for transmitting data over cell phone networks.  Installation has begun on multiple sensors that the NPS is funding for field testing in 2014.  The project inspired Samuel Wantman to start Nerdswithoutborders.net to help organize the project, recruit volunteers, and inspire other projects.  All of the Turtle Sense project members, with the exception of the NPS employees, donate their time.  The Hatteras Island Ocean Center is the sponsoring non-profit institution that administers receipt and disbursement of funds for materials and other expenses.&lt;br /&gt;
&lt;br /&gt;
==Phase One (2013 Turtle Season)==&lt;br /&gt;
[[file:PingPongSensor.jpg|right|thumb|300px|A ping-pong ball sensor assembly placed in a sea turtle nest (field tests 2013).  The cable coming from the sensor leads to the communications tower for the cell phone connection.]]&lt;br /&gt;
Phase One was a proof-of-concept field test undertaken during the 2013 turtle season.  A motion-and-temperature sensor (Analog Devices ADLX362, 3-Axil, Digital Output MEMS accelerometer), soldered to a Sparkfun “breakout board,” was soldered to a CAT5 cable.  The board was sealed in a Ping-Pong ball by filling it with “aquarium safe” silicone caulk. The Ping-Pong ball, about the size and shape of the sea turtle eggs, was placed in the sea turtle nest by National Park Service (NPS) rangers. The other end of the cable attached to the &amp;quot;egg&amp;quot; assembly was electrically connected to a hacked cell phone that was programmed with a very small, low-powered TI MSP430 microprocessor.  The phone sent out text messages with the motion and temperature data every two hours.  The cell phone was protected from the elements by a communications tower made from 4&amp;quot; PVC pipe and pipe fittings.   &lt;br /&gt;
&lt;br /&gt;
Turtle eggshells are thick and leathery, so the hatchlings need considerable effort to emerge from the egg.  After leaving the egg, the hatchlings remain in the nest for two-to-four days before exiting (usually) as a group onto the beach.  All the resulting motions should activate the accelerometer sensor and thus provide data to the phone network.  Though the first device had its problems, field tests done at Hatteras in October 2013 were positive. The signal from the sensor close to a single hatchling was eight times larger than the background signal, giving hope for more extensive tests planned for 2014.&lt;br /&gt;
&lt;br /&gt;
==Phase Two Description==&lt;br /&gt;
&amp;#039;&amp;#039;See also: [[Turtle Sense/Phase Two]]&lt;br /&gt;
&lt;br /&gt;
Planning for Phase Two began during the implementation of Phase One.  Samuel Wantman and David Hermeyer began working on the design for a more robust solution in the Fall of 2013.  Units were installed by the NPS starting in June of 2014.  About a dozen nests were monitored and predictions were made as to when the hatchlings would emerge.&lt;br /&gt;
&lt;br /&gt;
Several problems were identified during Phase One that we tried to address in Phase Two:&lt;br /&gt;
*The sensors had reliability problems communicating with the cell phones because of the long distance between the sensor and the microprocessor in the communications unit.  This is being addressed in two ways.  The sensor was mounted on a very small (1 inch by 1 inch) circuit board inside the &amp;quot;egg&amp;quot; that goes in the nest.  The board also contains a microprocessor and a RS485 transceiver that allows reliable communication over very long cable lengths.&lt;br /&gt;
[[file:PhaseTwoCommBoard.jpg|left|400px|thumb|The 2014 communications assembly contains the circuit board, power supply, a microprocessor, an M2M cell phone board and RS485 transceiver.  Inset is a quarter for size reference.]]&lt;br /&gt;
*The cell phone, having been designed with a human interface, was often unpredictable.  Occasionally messages would pop up prompting a human reply (like a notification that the phone was charging).  This made programming the device difficult because of all of the possible messages and the timing of their appearance are not predictable.  At one point, the devices stopped working because the cellular service provider required all its users to upload new operating software.  An appropriate user response was not possible in field-installed pre-programmed units.  Because of this problem, we adopted industry standard M2M (Machine to Machine) methods of sending data over a cellular network.&lt;br /&gt;
*Text messages and disposable cell phones were not a cost-effective way to send large amounts of data.  Phase Two uses FTP protocols with devices and data plans that have much less expensive data charges.&lt;br /&gt;
*Hacked cell phones would be difficult to mass produce, so the new design uses off-the-shelf, plug-in cell phone boards and custom circuitry that can be mass produced.&lt;br /&gt;
*Phase One used single-use D cell alkaline batteries.  Phase Two uses rechargeable NiMH AA batteries and achieves longer battery life, as the package is carefully designed for low energy needs.  &lt;br /&gt;
*Most of the turtle-specific calculations are now done in the microprocessor embedded with the sensor in the &amp;quot;egg.&amp;quot;  The communication system is designed so that it can be modified for other sensors. &lt;br /&gt;
*The silicone filling the ping-pong balls that housed the sensors in Phase One never cured.  For Phase Two, we made a casting of a ping-pong ball (which is the same size and shape as a turtle egg), and used it to cast solid polyurethane &amp;quot;eggs&amp;quot; around the sensor circuit boards.  The polyurethane is fully set in less than a day, does not out-gas, and is very hard and durable.&lt;br /&gt;
&lt;br /&gt;
== Phase Two results==&lt;br /&gt;
[[File:2015 - NH003 (7-28 final) sensor AA0006.png|250px|thumb|In 2015 we started to automate the graphing of data, and used the graphs to successfully predict emergence of hatchlings]]&lt;br /&gt;
===2014 season===&lt;br /&gt;
:&amp;#039;&amp;#039;For more detail, see:&lt;br /&gt;
* [https://www.dropbox.com/s/g1yrkai0npe0p91/2014%20Turtle%20Sense%20final%20report.pdf?dl=0 National Park Service -- Turtle Sense 2014 final report]&lt;br /&gt;
* [[Turtle Sense / Project logs]]&lt;br /&gt;
&lt;br /&gt;
===2015 season===&lt;br /&gt;
We successfully monitored nests at the Cape Hatteras National Seashore. For a record of predictions please go to [https://groups.google.com/forum/?pli=1#!forum/turtlesense our Google Group]&lt;br /&gt;
&lt;br /&gt;
For graphs of the nests that were monitored see:  [[Turtle Sense / 2015 Season Results]]&lt;br /&gt;
&lt;br /&gt;
==Phase Three Description==&lt;br /&gt;
&amp;#039;&amp;#039;See also: [[Turtle Sense/Phase Three]]&lt;br /&gt;
===Phase Three Goals===&lt;br /&gt;
Work on phase three began after the end of the 2014 season.  The goals of Phase Three are:&lt;br /&gt;
*To refine our hardware so that it is easier and cheaper to manufacture, more reliable, and easier to maintain.&lt;br /&gt;
*Extend the firmware so that it has better error handling, can be updated in the field, and offers more features and usable data.&lt;br /&gt;
*Create a working, somewhat complete website which does the following: automates the process of predicting hatching, reports predation events and over-washes; generates alerts for users; centralizes necessary data entry; and, allows open access of data for researchers and wildlife managers.&lt;br /&gt;
*Test the equipment and features in several different environments.&lt;br /&gt;
*Attend conferences to publicize our work and find additional organizations to team up with, and find additional volunteers to assist the project.&lt;br /&gt;
*Create a plan to get the technology included in protocols that are acceptable to the US Fish and Wildlife service.&lt;br /&gt;
&lt;br /&gt;
Most of the technical work to make this happen will be done during 2015. The phase two equipment will be used until the phase three equipment is ready.&lt;br /&gt;
&lt;br /&gt;
==Phase Three Progress==&lt;br /&gt;
Work is underway modifying the Turtle Sense hardware and software.&lt;br /&gt;
===Hardware===&lt;br /&gt;
* A moisture detector is being added to the smart sensor &amp;quot;egg&amp;quot;.&lt;br /&gt;
* The power supply of the unit is changing from 8 AA rechargeable batteries that just last for a season to a solar cell that will charge 3 AAA batteries.  Preliminary tests indicate that this will be cheaper to produce, and last for many years -- as long as the life of the batteries -- before needing servicing.  Initial testing is very positive.  There is enough light on a very overcast day to keep the units running, and even without any light the units will continue running for several weeks.&lt;br /&gt;
* Connections between the comm unit and the sensors will be made with coax cable.  This will allow the connections to be modified and repaired in the field, greatly reduce the expense and time involved in creating the devices, and allow multiple sensors to be connected to the same comm unit.  Power and two way communication will all use the same wire.&lt;br /&gt;
* Expansion ports will be added for USB/SD support, Bluetooth and other wireless capabilities, and auxiliary connections for controlling and interfacing with other field equipment.&lt;br /&gt;
* Since the batteries will not need annual servicing, the comm units will only have one sealed chamber instead of two.  This will simplify the construction and installation of the devices&lt;br /&gt;
* Upgraded microprocessors will expand available memory from 16K to 64K while lowering power usage.&lt;br /&gt;
&lt;br /&gt;
===Software===&lt;br /&gt;
* Expanded memory provides space for better error handling, increased data storage, and user code.&lt;br /&gt;
* A protocol will be developed for interfacing with multiple sensors&lt;br /&gt;
* Tools and libraries will be help others customize the hardware and software for other applications&lt;br /&gt;
&lt;br /&gt;
==Data==&lt;br /&gt;
[[File:Screenshot 2014-07-03 01.jpg|thumb|right|400px|Data from the first report of the 2014 season]]&lt;br /&gt;
The Turtle Sense units constantly monitor and analyze motion to create a profile of its magnitude over time.  The motion detector measures the change in acceleration (or &amp;quot;jolt&amp;quot;) multiple times per second.  The magnitude is squared and summed.  After six minutes, the results are stored in a record along with a temperature and orientation reading, and the process starts over.  The sum that results is roughly the total energy recorded in the nest during the period.  This process allows us to compress several thousand readings into approximately 32 bytes of information.  We lose but we suspect that those details are not important.  The 240 records created each day give us a very good idea of what is happening in the nest.  Once 40 days have passed, we restart the process of summing every minute to get more detailed data.&lt;br /&gt;
&lt;br /&gt;
There has been some research that indicates that before emerging from the nest in a &amp;quot;boil,&amp;quot; turtles that have hatched congregate underground near the top of the nest.  It is thought that this motion stimulates the hatching of the turtles that haven&amp;#039;t yet emerged.  Our sensors, situated at the top of the nest, were able to record some noticeable disturbances several days before the turtles boil.  We were able to see these disturbances in the data in almost all of the nests that we monitored in the 2014 season and were able to predict the date of the boil within a window of a few days.&lt;br /&gt;
&lt;br /&gt;
Predictions from the data in 2014 were made by human observation of graphed data.  We will be generating algorithms to predict hatching from our data and refining them to come up with a reliable automated process for predicting hatching a few days in advance.&lt;br /&gt;
&lt;br /&gt;
==Funding and Impact==&lt;br /&gt;
[[File:NH007-Post Hurr Arthur-exclosure (2) cropped small.jpg|thumb|left|300px|A few days after the first units of Phase Two were installed, Hurricane Arthur hit. The units reported regularly before and after the storm without any problems. This picture was taken the day after the storm. Notice how all the text was sandblasted off the sign in the forefront. Cape Hatteras Lighthouse is just behind the dune.]]&lt;br /&gt;
The National Park Service has been funding the project since it began.  Labor is being provided by NerdsWithoutBorder.net     volunteers.  Additional support has come from:&lt;br /&gt;
* [http://ibm.com IBM -- grants]&lt;br /&gt;
* [http://www.janus-rc.com/ Janus Remote Communications -- a generous discount on their M2M plug-in boards]&lt;br /&gt;
* [http://www.screamingcircuits.com/ Screaming Circuits -- a donation of the labor toward the production of circuit prototypes]&lt;br /&gt;
* [http://www.telit.com Telit -- publicity]&lt;br /&gt;
* [http://www.fte.com Frontline Test Equipment, Inc. -- a donation of communications testing equipment]&lt;br /&gt;
* [http://www.corun.com/ent  Hunan Corun New Energy Co.,LTD -- a donation of rechargeable NiMH batteries]&lt;br /&gt;
&lt;br /&gt;
We are seeking funding and volunteers to expand the program. &lt;br /&gt;
&lt;br /&gt;
Success in this project would provide widespread, international advantages.  As noted above, the stress could be lessened between the protection agencies and the fishing industry, recreational users, and tourism advocates, all of whom desire more beach access. More effective international protection will be available, since the protection resources can be concentrated close to the hatch date instead of being stretched over six weeks. With a tighter hatching schedule, the public would have the opportunity to observe the hatchlings heading for the sea, an observation available only randomly now.  This would improve the public support of the turtles. NPS will use the hatch dates in on-site announcements and information centers, and the Hatteras Island Ocean Center will disseminate the information in their programs.  Much of the research on sea turtle eggs and hatchlings in the world could benefit from more accurate predictions of the hatch date.  For example, studies that require capturing hatchlings for research could be done with much greater efficiency. Also, the sensor/cell network could be adapted for measurements of other species, including birds.  Given its modest cost and energy efficiency (long battery life), it may have other uses in environmental studies. All the design information will be available to the public on the wiki http://nerdswithoutborders.net. If the project is successful equipment will be made available at cost or perhaps below cost if sponsors come forward.&lt;br /&gt;
&lt;br /&gt;
[[Image:Britta2013.jpg|right|300px|thumb|Britta Muiznieks, a wildlife biologist at the NPS Cape Hatteras Seashore in NC with a protected turtle nest. The 4&amp;quot; PVC pipe assembly tower was used in the 2013 testing. A smaller 3&amp;quot; structure holds the 2014 package because the electronics are smaller and AA rechargeable batteries have replaced D cells. Vandal-proofing is one aspect of the design. Britta does the field research for the NPS.]]&lt;br /&gt;
&lt;br /&gt;
==Press==&lt;br /&gt;
===Radio===&lt;br /&gt;
*NPR&amp;#039;s Here &amp;amp; Now:&lt;br /&gt;
**[http://hereandnow.wbur.org/2014/08/25/turtles-outer-banks Part One (Aug 2014)]&lt;br /&gt;
**[http://hereandnow.wbur.org/2014/11/04/sea-turtles-sensors Part Two (Nov 2014)]&lt;br /&gt;
&lt;br /&gt;
===Print===&lt;br /&gt;
* [http://hamptonroads.com/2014/08/plan-hatched-could-help-keep-beaches-open Article at PilotOnline.com (Virginia-Pilot) (August 2014)]&lt;br /&gt;
* [http://islandfreepress.org/2014Archives/08.21.2014-ItMakesTurtleSenseGivingCellPhonesToTurtles.html Article in Island Free Press(Aug 2014)]&lt;br /&gt;
* [http://outerbanksvoice.com/2013/08/29/high-tech-could-help-predict-sea-turtle-hatches/ Article in Outer Banks Voice (August 2013)]&lt;br /&gt;
* [http://outerbanksvoice.com/2014/08/10/small-ocean-center-incorporates-an-expansive-natural-theater/ Another mention at the Outer Banks Voice]&lt;br /&gt;
===Web===&lt;br /&gt;
* [http://www.engadget.com/2014/11/13/north-carolina-sea-turtles/?ncid=rss_truncated Engadget.com]&lt;br /&gt;
* [http://spectrum.ieee.org/tech-talk/geek-life/hands-on/technologists-hatch-turtle-sense-system-with-ecology-and-economy-in-mind Tech-talk at IEEE Spectrum]&lt;br /&gt;
* [http://www.psychologytoday.com/blog/the-green-mind/201409/sensing-turtles Article at PsychologyToday.com]&lt;br /&gt;
* [http://hackaday.com/page/8/ Blog at hackaday.com]&lt;br /&gt;
* [http://www.nextgov.com/emerging-tech/2014/08/remote-sensors-mean-more-sea-turtles-fewer-beach-closures-hatteras/90545/ Article at nextgov.com (August 2014)]&lt;br /&gt;
* [http://online.wsj.com/article/PR-CO-20140515-910765.html Telit press release in the Wall Street Journal (May 2014)]&lt;br /&gt;
* [http://www.iotworld.com/author.asp?section_id=3153&amp;amp;doc_id=563269 Blog at iotworld.com]&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
*[http://www.hioceancenter.org/ Hatteras Island Ocean Center website]&lt;br /&gt;
*[http://hackaday.io/project/2264-Turtle-Sense Entry for the Hackaday Prize at hackaday.io]&lt;br /&gt;
*[https://www.youtube.com/watch?v=b_bWmOsYJz4 Video about the project at YouTube]&lt;br /&gt;
*[[Turtle Sense/People]] -- People involved in this project. &lt;br /&gt;
&lt;br /&gt;
==Contact us==&lt;br /&gt;
If you would like to help with this project, make suggestions, or offer a critique, please email: admin@nerdswithoutborders.net.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=519</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=519"/>
		<updated>2016-06-21T21:20:50Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Other components */  Start Phase 3 edits&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a solar cell control circuit for recharging three onboard AAA cells, a coax transceiver circuit, and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings.  The PVC pipe is anchored in a bucket filled with concrete.  The concrete base and RG6 coax cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards.&lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the RG6 coax cable and connector for the turtle egg sensor, and one cell antenna for the communications tower.  The units should be able to operate continuously running on three low self-discharge NiMH Batteries, which are kept charged by a small solar cell in the top of the PVC enclosure.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Communicator%20PCB%20v.0.25%20--%20Bill%20of%20Materials.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Smart%20Sensor%20PCB%20v.0.23a%20--%20Bill%20of%20Materials.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.24|Smart Sensor PCB 0.24 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.24|Smart Sensor PCB 0.24 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.25a|Communications PCB 0.25a schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.25a|Communications PCB 0.25a description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=518</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=518"/>
		<updated>2016-06-21T21:15:51Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Hand-held registration unit */  Omit this section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a solar cell control circuit for recharging three onboard AAA cells, a coax transceiver circuit, and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings.  The PVC pipe is anchored in a bucket filled with concrete.  The concrete base and RG6 coax cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards.&lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the cable and connector for the turtle egg sensor, one antenna for the communications tower (the hand held unit has an extra antenna for GPS.)  The units should operate for roughly 4 months running on 4 or 8 low self-discharge NiMH Batteries.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Communicator%20PCB%20v.0.25%20--%20Bill%20of%20Materials.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Smart%20Sensor%20PCB%20v.0.23a%20--%20Bill%20of%20Materials.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.24|Smart Sensor PCB 0.24 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.24|Smart Sensor PCB 0.24 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.25a|Communications PCB 0.25a schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.25a|Communications PCB 0.25a description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=517</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=517"/>
		<updated>2016-06-21T21:12:13Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Communications tower board */  Start Phase 3 edits&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a solar cell control circuit for recharging three onboard AAA cells, a coax transceiver circuit, and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings.  The PVC pipe is anchored in a bucket filled with concrete.  The concrete base and RG6 coax cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards.&lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
A communications board is mounted in a small hand-held unit so that it can be taken in the field when nests are first discovered.  This allows park service personnel to carry just the light-weight sensors and the hand-held unit to the nest sites.  Later, the much heavier and bulkier communications towers can be brought in.  The Hand-Held units have GPS capability.  They are programmed to test the sensors to make sure they are functioning properly, get a GPS reading, check for good cell reception, and get the local time and date from the cellular network.  The date, time and GPS location are sent to the sensor, so that all this information will be available to the communications tower when it eventually connected.&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the cable and connector for the turtle egg sensor, one antenna for the communications tower (the hand held unit has an extra antenna for GPS.)  The units should operate for roughly 4 months running on 4 or 8 low self-discharge NiMH Batteries.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Communicator%20PCB%20v.0.25%20--%20Bill%20of%20Materials.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Smart%20Sensor%20PCB%20v.0.23a%20--%20Bill%20of%20Materials.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.24|Smart Sensor PCB 0.24 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.24|Smart Sensor PCB 0.24 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.25a|Communications PCB 0.25a schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.25a|Communications PCB 0.25a description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=516</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=516"/>
		<updated>2016-06-21T21:03:57Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Smart Sensor */  Start edits for Phase 3&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also a moisture sensing circuit connected to the microprocessor, which measures changes in the capacitance of the moist or dry sand surrounding the sensor ball. A coax transceiver circuit connects to the communications tower via a RG6U cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a RS485 telemetry chip and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings anchored in a bucket filled with concrete.  The concrete base and Cat 5 cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards. &lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
A communications board is mounted in a small hand-held unit so that it can be taken in the field when nests are first discovered.  This allows park service personnel to carry just the light-weight sensors and the hand-held unit to the nest sites.  Later, the much heavier and bulkier communications towers can be brought in.  The Hand-Held units have GPS capability.  They are programmed to test the sensors to make sure they are functioning properly, get a GPS reading, check for good cell reception, and get the local time and date from the cellular network.  The date, time and GPS location are sent to the sensor, so that all this information will be available to the communications tower when it eventually connected.&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the cable and connector for the turtle egg sensor, one antenna for the communications tower (the hand held unit has an extra antenna for GPS.)  The units should operate for roughly 4 months running on 4 or 8 low self-discharge NiMH Batteries.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Communicator%20PCB%20v.0.25%20--%20Bill%20of%20Materials.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Smart%20Sensor%20PCB%20v.0.23a%20--%20Bill%20of%20Materials.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.24|Smart Sensor PCB 0.24 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.24|Smart Sensor PCB 0.24 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.25a|Communications PCB 0.25a schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.25a|Communications PCB 0.25a description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Smart_Sensor_0.42.jpg&amp;diff=484</id>
		<title>File:Smart Sensor 0.42.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Smart_Sensor_0.42.jpg&amp;diff=484"/>
		<updated>2015-08-23T03:27:52Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_4.jpg&amp;diff=483</id>
		<title>File:Turtle Sense Comm Unit 0.42 page 4.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_4.jpg&amp;diff=483"/>
		<updated>2015-08-23T03:25:57Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_3.jpg&amp;diff=482</id>
		<title>File:Turtle Sense Comm Unit 0.42 page 3.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_3.jpg&amp;diff=482"/>
		<updated>2015-08-23T03:25:15Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_2.jpg&amp;diff=481</id>
		<title>File:Turtle Sense Comm Unit 0.42 page 2.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_2.jpg&amp;diff=481"/>
		<updated>2015-08-23T03:24:01Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_1.jpg&amp;diff=480</id>
		<title>File:Turtle Sense Comm Unit 0.42 page 1.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_1.jpg&amp;diff=480"/>
		<updated>2015-08-23T03:22:34Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_1.png&amp;diff=479</id>
		<title>File:Turtle Sense Comm Unit 0.42 page 1.png</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_Comm_Unit_0.42_page_1.png&amp;diff=479"/>
		<updated>2015-08-23T03:21:17Z</updated>

		<summary type="html">&lt;p&gt;Dave: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=478</id>
		<title>Turtle Sense/Phase Three</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense/Phase_Three&amp;diff=478"/>
		<updated>2015-08-23T02:48:47Z</updated>

		<summary type="html">&lt;p&gt;Dave: Copied from Phase Two page - needs editing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==People==&lt;br /&gt;
*[[User:Dave]] -- Electrical engineering / Mechanical engineering&lt;br /&gt;
*[[User:Sam]] -- Project manager / Embedded Software&lt;br /&gt;
*[[User:Tom]] -- Engineering support&lt;br /&gt;
*[[User:Eric]] -- Fundraising / Community liaison&lt;br /&gt;
*[[User:Chuck]] -- Sea Turtle community outreach / Materials&lt;br /&gt;
*[[User:Chris]] -- Web Server Admin&lt;br /&gt;
*[[User:Mark]] -- Web Application Development&lt;br /&gt;
*[[User:Britta]] -- National Park Service Biologist&lt;br /&gt;
*[[User:Trebor|User:trebor]] -- Web visualizations&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
When nests are discovered by park personnel, they are uncovered, the eggs counted, and a DNA sample is taken.  At that time, a smart sensor the size of a turtle egg is placed on top of the turtle nest before the excavated sand is filled back in to cover the site.  The smart sensor measures motion and temperature in the nest, and the data collected is used to predict when hatching is imminent.  The smart sensor is connected to a communications tower which sends out regular reports on the activity in the nest using M2M technology.  The text file reports are FTP&amp;#039;d to a website directly from the communications tower. During Phase Two we created test units, one registration units, 8 communications towers and 24 smart sensors for installation in the Outer Banks of North Carolina startin in the Spring of 2014. Many of the sensors can be used in more than one nest per season, so Data can be collected from roughly 40 nests per season. The data is analyzed as it is collected to attempt to predict imminent hatching.&lt;br /&gt;
&lt;br /&gt;
===Commercial options===&lt;br /&gt;
Before developing the system, other commercially available data recording systems were evaluated to see if anything that would meet our requirements was available.  None of the options we found were not low enough power to fit our needs, and none provided the data we were hoping to collect.  The closest matches we found would have required as much or almost as much custom engineering on our part to make it work, and there was no cost benefit to going that route.&lt;br /&gt;
*[[Chuck&amp;#039;s research on data recorders]]&lt;br /&gt;
&lt;br /&gt;
==Hardware components==&lt;br /&gt;
===Smart Sensor===&lt;br /&gt;
The Phase One design used plastic ping-pong balls (not good ping-pong balls, but cheap plastic knock offs) and a temperature/motion sensor pre-installed on a small circuit board ([https://www.sparkfun.com/products/11446 Qty 1 Price=$14.95]).  Assembly involved cutting a small slot in a ball, putting in some silicone caulk, inserting a sensor board attached to a cable into the caulk, and then filling the rest of the ball with caulk.  A  ball cut in half covered the slot and makes a thorough seal with the silicone.  This design was abandoned for several reasons.  The silicone did not fully set, even after a few months in the field.  The sensor was unreliable, which may have been because it was connected directly to the microprocessor via the long Cat 5 cable and communications were using a very slow bit-banged SPI connection.  To improve communications we decided to put transceivers on both sides of the cable.  By adding a microprocessor to the sensor, most of the processing could happen in the sensor assembly.  The transceivers are on for just a few seconds a day, for the upload of information from the sensor to the comm tower.  This results in a Smart Sensor with very small power requirements.&lt;br /&gt;
&lt;br /&gt;
The Smart Sensor has a 3-axis motion sensor (accelerometer) and temperature sensor connected to a very low power TI MSP430FR series microprocessor.  There is also an RS485 transceiver chip which connects to the communications tower via a shielded Cat5e cable.  The smart sensor can be programmed to take readings 12.5, 25, 50, 100, 200 or 400 times every second.  Each reading is compared with the previous reading to determine the change in acceleration -- or &amp;quot;jolt&amp;quot;.  Rather than record each jolt, the sensor counts how many readings have reached approximately 25 different magnitude levels.  These magnitude levels (which we call &amp;quot;bins counters&amp;quot;) are in a logarithmic scale.  Each bin is the square root of 2 larger than the previous one.  We keep count for a variable amount of time (between 1 and 6 minutes) and then start a new set record with a new set of bins.  This allows us to track how much motion there was at multiple magnitudes over time.&lt;br /&gt;
&lt;br /&gt;
===Communications tower board===&lt;br /&gt;
Since it is not possible to make telemetry connections under wet salty sand, the smart sensors are connected to a communications tower.  The design is based around creating a custom processing mother board connected to an off-the-shelf telemetry board. The communications board has a very low power  TI MSP430FR series microprocessor which controls and monitors the activity of the smart sensor and controls the telemetry board.  There is also a power supply, a RS485 telemetry chip and connectors for future expansion.  The electronics are mounted inside a 3 inch PVC pipe and fittings anchored in a bucket filled with concrete.  The concrete base and Cat 5 cable are buried in the sand. The  The tower sends text reports to our web space via an FTP connection using the telemetry board.  The frequency of the reports starts out a one a day when the nests are new and not very active.  Later the frequency increases to 6 times a day as the nest becomes more active.  Since the communications tower only makes one to 6 reports a day, The microprocessor turns the telemetry board on and off, so that it consumes no power when it is not being used.&lt;br /&gt;
&lt;br /&gt;
====Telemetry board====&lt;br /&gt;
We are using [http://www.janus-rc.com/terminuscf.html plug in Terminus boards] made by Janus. One board works with AT&amp;amp;T, T-mobile and many international GSM networks.  Another works with Verizon.  The boards are interchangeable so both will plug into our motherboard.  The cost is roughly $140 qty 1 and are [http://www.janus-rc.com/terminuscf.html available from the manufacturer, Janus].  Janus has generously offered us a discount on their boards. &lt;br /&gt;
&lt;br /&gt;
===Hand-held registration unit===&lt;br /&gt;
A communications board is mounted in a small hand-held unit so that it can be taken in the field when nests are first discovered.  This allows park service personnel to carry just the light-weight sensors and the hand-held unit to the nest sites.  Later, the much heavier and bulkier communications towers can be brought in.  The Hand-Held units have GPS capability.  They are programmed to test the sensors to make sure they are functioning properly, get a GPS reading, check for good cell reception, and get the local time and date from the cellular network.  The date, time and GPS location are sent to the sensor, so that all this information will be available to the communications tower when it eventually connected.&lt;br /&gt;
&lt;br /&gt;
===Other components===&lt;br /&gt;
The only other components necessary are the cable and connector for the turtle egg sensor, one antenna for the communications tower (the hand held unit has an extra antenna for GPS.)  The units should operate for roughly 4 months running on 4 or 8 low self-discharge NiMH Batteries.    Also, anyone creating these devices will need the hardware necessary for programming the microprocessors.&lt;br /&gt;
&lt;br /&gt;
==Cellular service==&lt;br /&gt;
We arranged for cellular service through m2mAIR which is part of TELIT, the manufacture of the cellular modules used in the Janus plug-in boards.  This service is cost effective for hosting a large number of devices, as they can all be in the same account with one monthly fee.  The devices are also charged for the data used by each device, but the quota is pooled (shared) between all the devices, and the data rate charges can be modified month by month.  During periods of little or no activity, the data plans can be throttled back to keep the fees to a minimum.&lt;br /&gt;
&lt;br /&gt;
==Web design and Database==&lt;br /&gt;
All reports are uploaded to our web-space. The reports are comma separated text files with headings and labels, so they can be read by people as well as computers.  We are beginning work on a database to store all the data.  When reports are uploaded, the communications units also check the webspace for a new parameter file and download it if it is found.  The parameter file has settings that effect the behavior of the devices.  Here are some of the things that can be changed:&lt;br /&gt;
&lt;br /&gt;
*The frequency of reporting during inactive days&lt;br /&gt;
*The frequency of reporting during active days&lt;br /&gt;
*The number of inactive days&lt;br /&gt;
*The number of records per report&lt;br /&gt;
*How frequently samples are read by the sensor (12.5, 25, 50,100, 200 or 400 times per second)&lt;br /&gt;
*All of the other settings possible for the sensor&lt;br /&gt;
*Whether reports are verbose (labels on all the fields) or just data&lt;br /&gt;
*Whether temperatures are calibrated&lt;br /&gt;
&lt;br /&gt;
Work has started on designing a database to collect all the data in the reports, and a website to give people access to the data.  This work is just in its preliminary stages in anticipation of Phase 3.&lt;br /&gt;
* [[Turtle Sense/Website design]]&lt;br /&gt;
* [[Turtle Sense/Database design]]&lt;br /&gt;
&lt;br /&gt;
==Embedded code==&lt;br /&gt;
There are essentially three devices that need embedded code.  The smart sensor, the communications tower units, and the hand-held registration units.  All three of these devices use the same microprocessor, and two of them use the same circuit board.  A good deal of the embedded code is shared in the three applications..&lt;br /&gt;
&lt;br /&gt;
All the code was written in C using TI&amp;#039;s Code Composer Studio which is free for developers of code that is smaller than 16K.&lt;br /&gt;
&lt;br /&gt;
The code is fully documented and can be seen on GITHUB:&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/Turtle-Sense-Smart-Sensor Smart Sensor embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-Comm-Head Communications tower embedded code]&lt;br /&gt;
*[https://github.com/NerdsWithoutBorders/TurtleSense-HandHeld-communicator Registration unit embedded code]&lt;br /&gt;
&lt;br /&gt;
==Parts lists==&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Communicator%20PCB%20v.0.25%20--%20Bill%20of%20Materials.xls Turtle Sense Communications board parts]&lt;br /&gt;
* [https://dl.dropboxusercontent.com/u/26861868/Turtle%20Sense%20Public%20Files/Turtle%20Sense%20Smart%20Sensor%20PCB%20v.0.23a%20--%20Bill%20of%20Materials.xls Turtle Sense Smart Sensor board parts]&lt;br /&gt;
* [[Turtle Sense Other parts]]&lt;br /&gt;
&lt;br /&gt;
==Schematics and System design==&lt;br /&gt;
* [[Block Diagram of System]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor PCB Schematic v.0.24|Smart Sensor PCB 0.24 schematic]]&lt;br /&gt;
* [[Turtle Sense Smart Sensor board v.0.24|Smart Sensor PCB 0.24 description]]&lt;br /&gt;
* [[Turtle Sense Communications PCB Schematic v.0.25a|Communications PCB 0.25a schematic]]&lt;br /&gt;
* [[Turtle Sense communications board v.0.25a|Communications PCB 0.25a description]]&lt;br /&gt;
&lt;br /&gt;
==Circuit Board Fabrication==&lt;br /&gt;
* [[Turtle Sense -- Manufacturing the Communicator and Smart Sensor printed circuit boards|Manufacturing the Communicator and Smart Sensor printed circuit boards]]&lt;br /&gt;
&lt;br /&gt;
==Assembly Instructions==&lt;br /&gt;
* [[Turtle Sense cable assembly instructions|Cable assembly instructions]]&lt;br /&gt;
* [[Turtle Sense casting instructions for Smart Sensor and connectors|Casting instructions for Smart Sensor and connectors]]&lt;br /&gt;
* [[Turtle Sense communicator PVC housing assembly instructions|Communicator PVC housing assembly instructions]]&lt;br /&gt;
* [[Turtle Sense communicator housing final assembly|Communicator housing final assembly]]&lt;br /&gt;
==User Guide ==&lt;br /&gt;
* [[Turtle Sense nest site installation instructions|Nest site installation instructions]]&lt;br /&gt;
* [[Turtle Sense nest monitoring instructions|Nest site monitoring instructions]]&lt;br /&gt;
* [[Turtle Sense equipment maintenance instructions|Equipment maintenance instructions]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_System&amp;diff=420</id>
		<title>Block Diagram of System</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Block_Diagram_of_System&amp;diff=420"/>
		<updated>2014-10-19T19:34:58Z</updated>

		<summary type="html">&lt;p&gt;Dave: Create page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*[[Turtle Sense Block Diagram v.0.25]]&lt;br /&gt;
[[File:Turtle_Sense_0.25_Block_Diagram.jpg|795px|Smart Sensor 0.25.]]&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_0.25_Block_Diagram.jpg&amp;diff=419</id>
		<title>File:Turtle Sense 0.25 Block Diagram.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Turtle_Sense_0.25_Block_Diagram.jpg&amp;diff=419"/>
		<updated>2014-10-19T19:30:36Z</updated>

		<summary type="html">&lt;p&gt;Dave: Turtle Sense 0.25 Block Diagram&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Turtle Sense 0.25 Block Diagram&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=373</id>
		<title>Turtle Sense nest site installation instructions</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=373"/>
		<updated>2014-09-16T00:05:59Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Removing the Sensor and Communication Tower */  Add photos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
These step-by-step instructions are meant for someone who has never installed a sensor or communication tower into a turtle nest.  The sensors and communication heads/towers are the two main components of this remote monitoring system.  These systems are capable of detecting nest hatching activity before any external signs of hatching (I.e. depression or emergence) are evident.&lt;br /&gt;
&lt;br /&gt;
==Installing a Sensor==&lt;br /&gt;
[[File:Nest_Installation_Fig1.jpg|right|thumb|300px|Figure 1 - Sensor and cable placement on top of turtle eggs.]]&lt;br /&gt;
[[File:Nest_Installation_Fig2.jpg|right|thumb|300px|Figure 2 - Trench leading from turtle nest to sign post for cable.]]&lt;br /&gt;
[[File:Nest_Installation_Fig3.jpg|right|thumb|300px|Figure 3 - Testing and registering the sensor with the hand held device.]]&lt;br /&gt;
[[File:Nest_Installation_Fig4.jpg|right|thumb|300px|Figure 4 - Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.]]&lt;br /&gt;
[[File:Nest_Installation_Fig5.jpg|right|thumb|300px|Figure 5 - Sign post with terminal end of cable ready to be laid in trench.]]&lt;br /&gt;
At Cape Hatteras National Seashore, turtle patrols are conducted daily from May 1-Sept 15, or 2 weeks after the last sea turtle nest or crawl is found.  Once a nest has been located, the biological technicians conducting the patrols determine whether or not the nest needs to be relocated.  According to the NCWRC guidelines, a turtle nest should be allowed to incubate at its original location if there is any reasonable likelihood of survival and relocation should only be considered as a last resort in terms of nest management.&lt;br /&gt;
The ping-pong ball shaped sensor should be placed on the top of and in the middle of the nest.  Usually the sensor can replace the egg that is removed for the DNA study.  The cable should be coiled one time around the inside of the top of the nest cavity (Fig. 1).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Figure 1.  Sensor and cable placement on top of turtle eggs.&lt;br /&gt;
Next, dig a trench for the cable and the terminal end of the sensor.  The trench should be deep enough so that it will not be uncovered by the wind and/or storm events (Figure 2).&lt;br /&gt;
                  	&lt;br /&gt;
Figure 2.  Trench leading from turtle nest to sign post for cable.&lt;br /&gt;
Prior to burying the sensor and cable, the sensor should be registered with the hand held device (Figure 3).  &lt;br /&gt;
&lt;br /&gt;
Figure 3.  Testing and registering the sensor with the hand held device.&lt;br /&gt;
The hand held device 1) determines if the sensor is functioning properly, 2) determines if there is adequate cell tower reception, and 3) registers the time and placement (i.e. GPS location) of the sensor.  See [https://www.youtube.com/watch?v=4z2kcYOHgsw YouTube video for detailed information on the hand held device and sensor registration (https://www.youtube.com/watch?v=4z2kcYOHgsw)].   Once the registration is completed, the terminal end of the sensor is protected with the provided pill bottle.  The seam of the bottle is wrapped with Parafilm to prevent moisture from corroding the sensor terminal (Figure 4).  Only after the registration is complete (and the sensor is registered) should the cable be covered with sand.&lt;br /&gt;
&lt;br /&gt;
Figure 4.  Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.&lt;br /&gt;
&lt;br /&gt;
To make it easier to remember where the terminal end of the cable is located, the cable should be buried and then wrapped around the back, RIGHT (if facing the dune) turtle sign (Fig. 5).&lt;br /&gt;
&lt;br /&gt;
== Constructing a Communication Tower ==&lt;br /&gt;
[[File:Nest_Installation_Fig6.jpg|right|thumb|300px|Figure 6 - Supplies needed for communication tower construction.]]&lt;br /&gt;
[[File:Nest_Installation_Fig7.jpg|right|thumb|300px|Figure 7 - Leveling and stabilizing PVC with masking tape.]]&lt;br /&gt;
[[File:Nest_Installation_Fig7b.jpg|right|thumb|300px|Figure 7b - Completed construction of the communication tower.]]&lt;br /&gt;
Because of the weight of the communication towers (i.e. cement bases) they will have to be built on site.  Following is a list of supplies that are needed to build a tower (Fig. 6) :&lt;br /&gt;
*3&amp;quot; PVC (pre-cut to desired length-10 ft.pipe cut into thirds.)-if not pre-cut you will need something to cut it with.&lt;br /&gt;
*3.5 gal buckets&lt;br /&gt;
*Tub for mixing cement&lt;br /&gt;
*Quikcrete (60 lbs.)&lt;br /&gt;
*Shovel &lt;br /&gt;
*Level (optional)&lt;br /&gt;
*Masking tape (optional) – used for setting the PVC.&lt;br /&gt;
*Drill&lt;br /&gt;
*2&amp;quot; hole saw.&lt;br /&gt;
*Sanding drum for drill (or a Dremel tool) to sand down the edges of the hole in the PVC.  I use the hole as a handle when carrying it in the field.&lt;br /&gt;
&lt;br /&gt;
Figure 6.  Supplies needed for communication tower construction.&lt;br /&gt;
After mixing the Quikcrete with water, pour it into the buckets.  One 60 lb. bag of Quikcrete should be sufficient for two bases.  Insert the pre-cut PVC into the cement, level the PVC and stabilize with masking tape (Fig. 7).&lt;br /&gt;
&lt;br /&gt;
Figure 7.  Leveling and stabilizing PVC with masking tape.&lt;br /&gt;
After the cement has dried for 2-3 days, drill a 2” hole at the base of the tower.  The hole will need to be large enough to be able to pass the terminal end of the sensor through the opening (Fig 8).  It is also recommended that 4-6 small drainage holes be made just above the cement level in the bucket  to prevent water accumulation.&lt;br /&gt;
&lt;br /&gt;
Figure 7b. Completed construction of the communication tower.&lt;br /&gt;
&lt;br /&gt;
==Installing a communication tower and communication head ==&lt;br /&gt;
[[File:Nest_Installation_Fig8.jpg|right|thumb|300px|Figure 8 - Communication tower and head for sensor data transmission.]]&lt;br /&gt;
[[File:Nest_Installation_Fig9.jpg|right|thumb|300px|Figure 9 - Attaching the terminal end of the sensor to the communication head.]]&lt;br /&gt;
[[File:Nest_Installation_Fig10.jpg|right|thumb|300px|Figure 10 - Communication head/tower installed and transmitting data.]]&lt;br /&gt;
Upon receipt of the communication heads, they should be attached to a sensor to insure that no damage occurred during shipping.  Confirm with Nerds Without Borders that they are receiving data from this sensor/comm head.  After approximately 50 days (or less) of incubation, locate the terminal end of the sensor that should be wrapped around the back, right sign of the closure.  Uncoil the cable and dig a hole for the concrete tower base.  The lip of the bucket should be buried just below the surface of the sand (Fig. 8).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 8.  Communication tower and head for sensor data transmission.&lt;br /&gt;
&lt;br /&gt;
Feed the terminal end of the sensor through the hole at the base of the tower to the top of the tower.  Leave plenty of cable slack at the top of the tower so that it is possible to lay the communication head on the ground while it is attached to the sensor (Fig 9).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 9.  Attaching the terminal end of the sensor to the communication head.&lt;br /&gt;
&lt;br /&gt;
If this is a one person install, having the slack will make it easier to wrap the pill bottle (housing the connection) with Parafilm after connecting the two cables.  Both the seam (where cap connects to the bottle) and the base of the bottle (where the coomunication head cable enters the bottle) should be wrapped with Parafilm.  Once the communication head has been connected to the sensor, the communication head can be attached to the communication tower by tightening the set screw at the base of the communication head.  To prevent rust issues with the set screw, cover it with a piece of white (if available) electrician’s tape.  Confirm the install of the communication head with Nerds Without Borders.  Rake out any tracks/depressions around the communication tower  (Fig 10).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 10.  Communication head/tower installed and transmitting data.&lt;br /&gt;
&lt;br /&gt;
==Removing the Sensor and Communication Tower==&lt;br /&gt;
[[File:Nest_Installation_Fig11.jpg|right|thumb|300px|Figure 11 - Live hatchlings encountered above the sensor.]]&lt;br /&gt;
[[File:Nest_Installation_Fig12.jpg|right|thumb|300px|Figure 12 - Make sure towers with communication heads are fastened securely during transport to prevent damage.]]&lt;br /&gt;
The nest should be excavated 72 hours after the first emergence of turtle hatchlings.  Follow normal procedures for conducting an excavation.  If more than 15 live hatchlings are encountered the nest, the nest should be gently re-covered with sand and the hatchlings allowed to emerge on their own. Note the exact time an excavation was started do that hatchling vs human movement of the sensor can be distinguished.  If less than 15 live hatchlings are encountered during excavation, document the number of live hatchling encountered above, below, or level with the sensor (Fig. 11). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 11.  Live hatchlings encountered above the sensor.&lt;br /&gt;
Note if the cable or sensor appeared to impede hatchling emergence in any way.  Pull up the buried cable and follow it to the communication tower.  Do NOT detach the sensor from the communication head for at least 6 hours after the excavation.  This will allow the final data from the sensor to be sent and prevent the loss of this data.  The communication head and sensor can be removed from the tower but the connection between the communication head and sensor should not be broken.   If traveling with the communication head still installed on the communication tower, make sure the tower is fastened securely in the vehicle so that the communication head is not damaged during transport (Fig 12).   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 12.  Make sure towers with communication heads are fastened securely during transport to prevent damage.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=372</id>
		<title>Turtle Sense nest site installation instructions</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=372"/>
		<updated>2014-09-16T00:02:34Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Installing a communication tower and communication head */  Add photos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
These step-by-step instructions are meant for someone who has never installed a sensor or communication tower into a turtle nest.  The sensors and communication heads/towers are the two main components of this remote monitoring system.  These systems are capable of detecting nest hatching activity before any external signs of hatching (I.e. depression or emergence) are evident.&lt;br /&gt;
&lt;br /&gt;
==Installing a Sensor==&lt;br /&gt;
[[File:Nest_Installation_Fig1.jpg|right|thumb|300px|Figure 1 - Sensor and cable placement on top of turtle eggs.]]&lt;br /&gt;
[[File:Nest_Installation_Fig2.jpg|right|thumb|300px|Figure 2 - Trench leading from turtle nest to sign post for cable.]]&lt;br /&gt;
[[File:Nest_Installation_Fig3.jpg|right|thumb|300px|Figure 3 - Testing and registering the sensor with the hand held device.]]&lt;br /&gt;
[[File:Nest_Installation_Fig4.jpg|right|thumb|300px|Figure 4 - Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.]]&lt;br /&gt;
[[File:Nest_Installation_Fig5.jpg|right|thumb|300px|Figure 5 - Sign post with terminal end of cable ready to be laid in trench.]]&lt;br /&gt;
At Cape Hatteras National Seashore, turtle patrols are conducted daily from May 1-Sept 15, or 2 weeks after the last sea turtle nest or crawl is found.  Once a nest has been located, the biological technicians conducting the patrols determine whether or not the nest needs to be relocated.  According to the NCWRC guidelines, a turtle nest should be allowed to incubate at its original location if there is any reasonable likelihood of survival and relocation should only be considered as a last resort in terms of nest management.&lt;br /&gt;
The ping-pong ball shaped sensor should be placed on the top of and in the middle of the nest.  Usually the sensor can replace the egg that is removed for the DNA study.  The cable should be coiled one time around the inside of the top of the nest cavity (Fig. 1).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Figure 1.  Sensor and cable placement on top of turtle eggs.&lt;br /&gt;
Next, dig a trench for the cable and the terminal end of the sensor.  The trench should be deep enough so that it will not be uncovered by the wind and/or storm events (Figure 2).&lt;br /&gt;
                  	&lt;br /&gt;
Figure 2.  Trench leading from turtle nest to sign post for cable.&lt;br /&gt;
Prior to burying the sensor and cable, the sensor should be registered with the hand held device (Figure 3).  &lt;br /&gt;
&lt;br /&gt;
Figure 3.  Testing and registering the sensor with the hand held device.&lt;br /&gt;
The hand held device 1) determines if the sensor is functioning properly, 2) determines if there is adequate cell tower reception, and 3) registers the time and placement (i.e. GPS location) of the sensor.  See [https://www.youtube.com/watch?v=4z2kcYOHgsw YouTube video for detailed information on the hand held device and sensor registration (https://www.youtube.com/watch?v=4z2kcYOHgsw)].   Once the registration is completed, the terminal end of the sensor is protected with the provided pill bottle.  The seam of the bottle is wrapped with Parafilm to prevent moisture from corroding the sensor terminal (Figure 4).  Only after the registration is complete (and the sensor is registered) should the cable be covered with sand.&lt;br /&gt;
&lt;br /&gt;
Figure 4.  Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.&lt;br /&gt;
&lt;br /&gt;
To make it easier to remember where the terminal end of the cable is located, the cable should be buried and then wrapped around the back, RIGHT (if facing the dune) turtle sign (Fig. 5).&lt;br /&gt;
&lt;br /&gt;
== Constructing a Communication Tower ==&lt;br /&gt;
[[File:Nest_Installation_Fig6.jpg|right|thumb|300px|Figure 6 - Supplies needed for communication tower construction.]]&lt;br /&gt;
[[File:Nest_Installation_Fig7.jpg|right|thumb|300px|Figure 7 - Leveling and stabilizing PVC with masking tape.]]&lt;br /&gt;
[[File:Nest_Installation_Fig7b.jpg|right|thumb|300px|Figure 7b - Completed construction of the communication tower.]]&lt;br /&gt;
Because of the weight of the communication towers (i.e. cement bases) they will have to be built on site.  Following is a list of supplies that are needed to build a tower (Fig. 6) :&lt;br /&gt;
*3&amp;quot; PVC (pre-cut to desired length-10 ft.pipe cut into thirds.)-if not pre-cut you will need something to cut it with.&lt;br /&gt;
*3.5 gal buckets&lt;br /&gt;
*Tub for mixing cement&lt;br /&gt;
*Quikcrete (60 lbs.)&lt;br /&gt;
*Shovel &lt;br /&gt;
*Level (optional)&lt;br /&gt;
*Masking tape (optional) – used for setting the PVC.&lt;br /&gt;
*Drill&lt;br /&gt;
*2&amp;quot; hole saw.&lt;br /&gt;
*Sanding drum for drill (or a Dremel tool) to sand down the edges of the hole in the PVC.  I use the hole as a handle when carrying it in the field.&lt;br /&gt;
&lt;br /&gt;
Figure 6.  Supplies needed for communication tower construction.&lt;br /&gt;
After mixing the Quikcrete with water, pour it into the buckets.  One 60 lb. bag of Quikcrete should be sufficient for two bases.  Insert the pre-cut PVC into the cement, level the PVC and stabilize with masking tape (Fig. 7).&lt;br /&gt;
&lt;br /&gt;
Figure 7.  Leveling and stabilizing PVC with masking tape.&lt;br /&gt;
After the cement has dried for 2-3 days, drill a 2” hole at the base of the tower.  The hole will need to be large enough to be able to pass the terminal end of the sensor through the opening (Fig 8).  It is also recommended that 4-6 small drainage holes be made just above the cement level in the bucket  to prevent water accumulation.&lt;br /&gt;
&lt;br /&gt;
Figure 7b. Completed construction of the communication tower.&lt;br /&gt;
&lt;br /&gt;
==Installing a communication tower and communication head ==&lt;br /&gt;
[[File:Nest_Installation_Fig8.jpg|right|thumb|300px|Figure 8 - Communication tower and head for sensor data transmission.]]&lt;br /&gt;
[[File:Nest_Installation_Fig9.jpg|right|thumb|300px|Figure 9 - Attaching the terminal end of the sensor to the communication head.]]&lt;br /&gt;
[[File:Nest_Installation_Fig10.jpg|right|thumb|300px|Figure 10 - Communication head/tower installed and transmitting data.]]&lt;br /&gt;
Upon receipt of the communication heads, they should be attached to a sensor to insure that no damage occurred during shipping.  Confirm with Nerds Without Borders that they are receiving data from this sensor/comm head.  After approximately 50 days (or less) of incubation, locate the terminal end of the sensor that should be wrapped around the back, right sign of the closure.  Uncoil the cable and dig a hole for the concrete tower base.  The lip of the bucket should be buried just below the surface of the sand (Fig. 8).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 8.  Communication tower and head for sensor data transmission.&lt;br /&gt;
&lt;br /&gt;
Feed the terminal end of the sensor through the hole at the base of the tower to the top of the tower.  Leave plenty of cable slack at the top of the tower so that it is possible to lay the communication head on the ground while it is attached to the sensor (Fig 9).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 9.  Attaching the terminal end of the sensor to the communication head.&lt;br /&gt;
&lt;br /&gt;
If this is a one person install, having the slack will make it easier to wrap the pill bottle (housing the connection) with Parafilm after connecting the two cables.  Both the seam (where cap connects to the bottle) and the base of the bottle (where the coomunication head cable enters the bottle) should be wrapped with Parafilm.  Once the communication head has been connected to the sensor, the communication head can be attached to the communication tower by tightening the set screw at the base of the communication head.  To prevent rust issues with the set screw, cover it with a piece of white (if available) electrician’s tape.  Confirm the install of the communication head with Nerds Without Borders.  Rake out any tracks/depressions around the communication tower  (Fig 10).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 10.  Communication head/tower installed and transmitting data.&lt;br /&gt;
&lt;br /&gt;
==Removing the Sensor and Communication Tower==&lt;br /&gt;
The nest should be excavated 72 hours after the first emergence of turtle hatchlings.  Follow normal procedures for conducting an excavation.  If more than 15 live hatchlings are encountered the nest, the nest should be gently re-covered with sand and the hatchlings allowed to emerge on their own. Note the exact time an excavation was started do that hatchling vs human movement of the sensor can be distinguished.  If less than 15 live hatchlings are encountered during excavation, document the number of live hatchling encountered above, below, or level with the sensor (Fig. 11). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 11.  Live hatchlings encountered above the sensor.&lt;br /&gt;
Note if the cable or sensor appeared to impede hatchling emergence in any way.  Pull up the buried cable and follow it to the communication tower.  Do NOT detach the sensor from the communication head for at least 6 hours after the excavation.  This will allow the final data from the sensor to be sent and prevent the loss of this data.  The communication head and sensor can be removed from the tower but the connection between the communication head and sensor should not be broken.   If traveling with the communication head still installed on the communication tower, make sure the tower is fastened securely in the vehicle so that the communication head is not damaged during transport (Fig 12).   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 12.  Make sure towers with communication heads are fastened securely during transport to prevent damage.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=371</id>
		<title>Turtle Sense nest site installation instructions</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=371"/>
		<updated>2014-09-15T23:57:35Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Constructing a Communication Tower */  Add photos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
These step-by-step instructions are meant for someone who has never installed a sensor or communication tower into a turtle nest.  The sensors and communication heads/towers are the two main components of this remote monitoring system.  These systems are capable of detecting nest hatching activity before any external signs of hatching (I.e. depression or emergence) are evident.&lt;br /&gt;
&lt;br /&gt;
==Installing a Sensor==&lt;br /&gt;
[[File:Nest_Installation_Fig1.jpg|right|thumb|300px|Figure 1 - Sensor and cable placement on top of turtle eggs.]]&lt;br /&gt;
[[File:Nest_Installation_Fig2.jpg|right|thumb|300px|Figure 2 - Trench leading from turtle nest to sign post for cable.]]&lt;br /&gt;
[[File:Nest_Installation_Fig3.jpg|right|thumb|300px|Figure 3 - Testing and registering the sensor with the hand held device.]]&lt;br /&gt;
[[File:Nest_Installation_Fig4.jpg|right|thumb|300px|Figure 4 - Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.]]&lt;br /&gt;
[[File:Nest_Installation_Fig5.jpg|right|thumb|300px|Figure 5 - Sign post with terminal end of cable ready to be laid in trench.]]&lt;br /&gt;
At Cape Hatteras National Seashore, turtle patrols are conducted daily from May 1-Sept 15, or 2 weeks after the last sea turtle nest or crawl is found.  Once a nest has been located, the biological technicians conducting the patrols determine whether or not the nest needs to be relocated.  According to the NCWRC guidelines, a turtle nest should be allowed to incubate at its original location if there is any reasonable likelihood of survival and relocation should only be considered as a last resort in terms of nest management.&lt;br /&gt;
The ping-pong ball shaped sensor should be placed on the top of and in the middle of the nest.  Usually the sensor can replace the egg that is removed for the DNA study.  The cable should be coiled one time around the inside of the top of the nest cavity (Fig. 1).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Figure 1.  Sensor and cable placement on top of turtle eggs.&lt;br /&gt;
Next, dig a trench for the cable and the terminal end of the sensor.  The trench should be deep enough so that it will not be uncovered by the wind and/or storm events (Figure 2).&lt;br /&gt;
                  	&lt;br /&gt;
Figure 2.  Trench leading from turtle nest to sign post for cable.&lt;br /&gt;
Prior to burying the sensor and cable, the sensor should be registered with the hand held device (Figure 3).  &lt;br /&gt;
&lt;br /&gt;
Figure 3.  Testing and registering the sensor with the hand held device.&lt;br /&gt;
The hand held device 1) determines if the sensor is functioning properly, 2) determines if there is adequate cell tower reception, and 3) registers the time and placement (i.e. GPS location) of the sensor.  See [https://www.youtube.com/watch?v=4z2kcYOHgsw YouTube video for detailed information on the hand held device and sensor registration (https://www.youtube.com/watch?v=4z2kcYOHgsw)].   Once the registration is completed, the terminal end of the sensor is protected with the provided pill bottle.  The seam of the bottle is wrapped with Parafilm to prevent moisture from corroding the sensor terminal (Figure 4).  Only after the registration is complete (and the sensor is registered) should the cable be covered with sand.&lt;br /&gt;
&lt;br /&gt;
Figure 4.  Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.&lt;br /&gt;
&lt;br /&gt;
To make it easier to remember where the terminal end of the cable is located, the cable should be buried and then wrapped around the back, RIGHT (if facing the dune) turtle sign (Fig. 5).&lt;br /&gt;
&lt;br /&gt;
== Constructing a Communication Tower ==&lt;br /&gt;
[[File:Nest_Installation_Fig6.jpg|right|thumb|300px|Figure 6 - Supplies needed for communication tower construction.]]&lt;br /&gt;
[[File:Nest_Installation_Fig7.jpg|right|thumb|300px|Figure 7 - Leveling and stabilizing PVC with masking tape.]]&lt;br /&gt;
[[File:Nest_Installation_Fig7b.jpg|right|thumb|300px|Figure 7b - Completed construction of the communication tower.]]&lt;br /&gt;
Because of the weight of the communication towers (i.e. cement bases) they will have to be built on site.  Following is a list of supplies that are needed to build a tower (Fig. 6) :&lt;br /&gt;
*3&amp;quot; PVC (pre-cut to desired length-10 ft.pipe cut into thirds.)-if not pre-cut you will need something to cut it with.&lt;br /&gt;
*3.5 gal buckets&lt;br /&gt;
*Tub for mixing cement&lt;br /&gt;
*Quikcrete (60 lbs.)&lt;br /&gt;
*Shovel &lt;br /&gt;
*Level (optional)&lt;br /&gt;
*Masking tape (optional) – used for setting the PVC.&lt;br /&gt;
*Drill&lt;br /&gt;
*2&amp;quot; hole saw.&lt;br /&gt;
*Sanding drum for drill (or a Dremel tool) to sand down the edges of the hole in the PVC.  I use the hole as a handle when carrying it in the field.&lt;br /&gt;
&lt;br /&gt;
Figure 6.  Supplies needed for communication tower construction.&lt;br /&gt;
After mixing the Quikcrete with water, pour it into the buckets.  One 60 lb. bag of Quikcrete should be sufficient for two bases.  Insert the pre-cut PVC into the cement, level the PVC and stabilize with masking tape (Fig. 7).&lt;br /&gt;
&lt;br /&gt;
Figure 7.  Leveling and stabilizing PVC with masking tape.&lt;br /&gt;
After the cement has dried for 2-3 days, drill a 2” hole at the base of the tower.  The hole will need to be large enough to be able to pass the terminal end of the sensor through the opening (Fig 8).  It is also recommended that 4-6 small drainage holes be made just above the cement level in the bucket  to prevent water accumulation.&lt;br /&gt;
&lt;br /&gt;
Figure 7b. Completed construction of the communication tower.&lt;br /&gt;
&lt;br /&gt;
==Installing a communication tower and communication head ==&lt;br /&gt;
Upon receipt of the communication heads, they should be attached to a sensor to insure that no damage occurred during shipping.  Confirm with Nerds Without Borders that they are receiving data from this sensor/comm head.  After approximately 50 days (or less) of incubation, locate the terminal end of the sensor that should be wrapped around the back, right sign of the closure.  Uncoil the cable and dig a hole for the concrete tower base.  The lip of the bucket should be buried just below the surface of the sand (Fig. 8).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 8.  Communication tower and head for sensor data transmission.&lt;br /&gt;
&lt;br /&gt;
Feed the terminal end of the sensor through the hole at the base of the tower to the top of the tower.  Leave plenty of cable slack at the top of the tower so that it is possible to lay the communication head on the ground while it is attached to the sensor (Fig 9).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 9.  Attaching the terminal end of the sensor to the communication head.&lt;br /&gt;
&lt;br /&gt;
If this is a one person install, having the slack will make it easier to wrap the pill bottle (housing the connection) with Parafilm after connecting the two cables.  Both the seam (where cap connects to the bottle) and the base of the bottle (where the coomunication head cable enters the bottle) should be wrapped with Parafilm.  Once the communication head has been connected to the sensor, the communication head can be attached to the communication tower by tightening the set screw at the base of the communication head.  To prevent rust issues with the set screw, cover it with a piece of white (if available) electrician’s tape.  Confirm the install of the communication head with Nerds Without Borders.  Rake out any tracks/depressions around the communication tower  (Fig 10).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 10.  Communication head/tower installed and transmitting data.&lt;br /&gt;
&lt;br /&gt;
==Removing the Sensor and Communication Tower==&lt;br /&gt;
The nest should be excavated 72 hours after the first emergence of turtle hatchlings.  Follow normal procedures for conducting an excavation.  If more than 15 live hatchlings are encountered the nest, the nest should be gently re-covered with sand and the hatchlings allowed to emerge on their own. Note the exact time an excavation was started do that hatchling vs human movement of the sensor can be distinguished.  If less than 15 live hatchlings are encountered during excavation, document the number of live hatchling encountered above, below, or level with the sensor (Fig. 11). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 11.  Live hatchlings encountered above the sensor.&lt;br /&gt;
Note if the cable or sensor appeared to impede hatchling emergence in any way.  Pull up the buried cable and follow it to the communication tower.  Do NOT detach the sensor from the communication head for at least 6 hours after the excavation.  This will allow the final data from the sensor to be sent and prevent the loss of this data.  The communication head and sensor can be removed from the tower but the connection between the communication head and sensor should not be broken.   If traveling with the communication head still installed on the communication tower, make sure the tower is fastened securely in the vehicle so that the communication head is not damaged during transport (Fig 12).   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 12.  Make sure towers with communication heads are fastened securely during transport to prevent damage.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=370</id>
		<title>Turtle Sense nest site installation instructions</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=370"/>
		<updated>2014-09-15T23:50:55Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Installing a Sensor */  Add another photo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
These step-by-step instructions are meant for someone who has never installed a sensor or communication tower into a turtle nest.  The sensors and communication heads/towers are the two main components of this remote monitoring system.  These systems are capable of detecting nest hatching activity before any external signs of hatching (I.e. depression or emergence) are evident.&lt;br /&gt;
&lt;br /&gt;
==Installing a Sensor==&lt;br /&gt;
[[File:Nest_Installation_Fig1.jpg|right|thumb|300px|Figure 1 - Sensor and cable placement on top of turtle eggs.]]&lt;br /&gt;
[[File:Nest_Installation_Fig2.jpg|right|thumb|300px|Figure 2 - Trench leading from turtle nest to sign post for cable.]]&lt;br /&gt;
[[File:Nest_Installation_Fig3.jpg|right|thumb|300px|Figure 3 - Testing and registering the sensor with the hand held device.]]&lt;br /&gt;
[[File:Nest_Installation_Fig4.jpg|right|thumb|300px|Figure 4 - Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.]]&lt;br /&gt;
[[File:Nest_Installation_Fig5.jpg|right|thumb|300px|Figure 5 - Sign post with terminal end of cable ready to be laid in trench.]]&lt;br /&gt;
At Cape Hatteras National Seashore, turtle patrols are conducted daily from May 1-Sept 15, or 2 weeks after the last sea turtle nest or crawl is found.  Once a nest has been located, the biological technicians conducting the patrols determine whether or not the nest needs to be relocated.  According to the NCWRC guidelines, a turtle nest should be allowed to incubate at its original location if there is any reasonable likelihood of survival and relocation should only be considered as a last resort in terms of nest management.&lt;br /&gt;
The ping-pong ball shaped sensor should be placed on the top of and in the middle of the nest.  Usually the sensor can replace the egg that is removed for the DNA study.  The cable should be coiled one time around the inside of the top of the nest cavity (Fig. 1).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Figure 1.  Sensor and cable placement on top of turtle eggs.&lt;br /&gt;
Next, dig a trench for the cable and the terminal end of the sensor.  The trench should be deep enough so that it will not be uncovered by the wind and/or storm events (Figure 2).&lt;br /&gt;
                  	&lt;br /&gt;
Figure 2.  Trench leading from turtle nest to sign post for cable.&lt;br /&gt;
Prior to burying the sensor and cable, the sensor should be registered with the hand held device (Figure 3).  &lt;br /&gt;
&lt;br /&gt;
Figure 3.  Testing and registering the sensor with the hand held device.&lt;br /&gt;
The hand held device 1) determines if the sensor is functioning properly, 2) determines if there is adequate cell tower reception, and 3) registers the time and placement (i.e. GPS location) of the sensor.  See [https://www.youtube.com/watch?v=4z2kcYOHgsw YouTube video for detailed information on the hand held device and sensor registration (https://www.youtube.com/watch?v=4z2kcYOHgsw)].   Once the registration is completed, the terminal end of the sensor is protected with the provided pill bottle.  The seam of the bottle is wrapped with Parafilm to prevent moisture from corroding the sensor terminal (Figure 4).  Only after the registration is complete (and the sensor is registered) should the cable be covered with sand.&lt;br /&gt;
&lt;br /&gt;
Figure 4.  Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.&lt;br /&gt;
&lt;br /&gt;
To make it easier to remember where the terminal end of the cable is located, the cable should be buried and then wrapped around the back, RIGHT (if facing the dune) turtle sign (Fig. 5).&lt;br /&gt;
&lt;br /&gt;
== Constructing a Communication Tower ==&lt;br /&gt;
Because of the weight of the communication towers (i.e. cement bases) they will have to be built on site.  Following is a list of supplies that are needed to build a tower (Fig. 6) :&lt;br /&gt;
*3&amp;quot; PVC (pre-cut to desired length-10 ft.pipe cut into thirds.)-if not pre-cut you will need something to cut it with.&lt;br /&gt;
*3.5 gal buckets&lt;br /&gt;
*Tub for mixing cement&lt;br /&gt;
*Quikcrete (60 lbs.)&lt;br /&gt;
*Shovel &lt;br /&gt;
*Level (optional)&lt;br /&gt;
*Masking tape (optional) – used for setting the PVC.&lt;br /&gt;
*Drill&lt;br /&gt;
*2&amp;quot; hole saw.&lt;br /&gt;
*Sanding drum for drill (or a Dremel tool) to sand down the edges of the hole in the PVC.  I use the hole as a handle when carrying it in the field.&lt;br /&gt;
&lt;br /&gt;
Figure 6.  Supplies needed for communication tower construction.&lt;br /&gt;
After mixing the Quikcrete with water, pour it into the buckets.  One 60 lb. bag of Quikcrete should be sufficient for two bases.  Insert the pre-cut PVC into the cement, level the PVC and stabilize with masking tape (Fig. 7).&lt;br /&gt;
&lt;br /&gt;
Figure 7.  Leveling and stabilizing PVC with masking tape.&lt;br /&gt;
After the cement has dried for 2-3 days, drill a 2” hole at the base of the tower.  The hole will need to be large enough to be able to pass the terminal end of the sensor through the opening (Fig 8).  It is also recommended that 4-6 small drainage holes be made just above the cement level in the bucket  to prevent water accumulation.&lt;br /&gt;
&lt;br /&gt;
Figure 7. Completed construction of the communication tower.&lt;br /&gt;
&lt;br /&gt;
==Installing a communication tower and communication head ==&lt;br /&gt;
Upon receipt of the communication heads, they should be attached to a sensor to insure that no damage occurred during shipping.  Confirm with Nerds Without Borders that they are receiving data from this sensor/comm head.  After approximately 50 days (or less) of incubation, locate the terminal end of the sensor that should be wrapped around the back, right sign of the closure.  Uncoil the cable and dig a hole for the concrete tower base.  The lip of the bucket should be buried just below the surface of the sand (Fig. 8).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 8.  Communication tower and head for sensor data transmission.&lt;br /&gt;
&lt;br /&gt;
Feed the terminal end of the sensor through the hole at the base of the tower to the top of the tower.  Leave plenty of cable slack at the top of the tower so that it is possible to lay the communication head on the ground while it is attached to the sensor (Fig 9).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 9.  Attaching the terminal end of the sensor to the communication head.&lt;br /&gt;
&lt;br /&gt;
If this is a one person install, having the slack will make it easier to wrap the pill bottle (housing the connection) with Parafilm after connecting the two cables.  Both the seam (where cap connects to the bottle) and the base of the bottle (where the coomunication head cable enters the bottle) should be wrapped with Parafilm.  Once the communication head has been connected to the sensor, the communication head can be attached to the communication tower by tightening the set screw at the base of the communication head.  To prevent rust issues with the set screw, cover it with a piece of white (if available) electrician’s tape.  Confirm the install of the communication head with Nerds Without Borders.  Rake out any tracks/depressions around the communication tower  (Fig 10).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 10.  Communication head/tower installed and transmitting data.&lt;br /&gt;
&lt;br /&gt;
==Removing the Sensor and Communication Tower==&lt;br /&gt;
The nest should be excavated 72 hours after the first emergence of turtle hatchlings.  Follow normal procedures for conducting an excavation.  If more than 15 live hatchlings are encountered the nest, the nest should be gently re-covered with sand and the hatchlings allowed to emerge on their own. Note the exact time an excavation was started do that hatchling vs human movement of the sensor can be distinguished.  If less than 15 live hatchlings are encountered during excavation, document the number of live hatchling encountered above, below, or level with the sensor (Fig. 11). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 11.  Live hatchlings encountered above the sensor.&lt;br /&gt;
Note if the cable or sensor appeared to impede hatchling emergence in any way.  Pull up the buried cable and follow it to the communication tower.  Do NOT detach the sensor from the communication head for at least 6 hours after the excavation.  This will allow the final data from the sensor to be sent and prevent the loss of this data.  The communication head and sensor can be removed from the tower but the connection between the communication head and sensor should not be broken.   If traveling with the communication head still installed on the communication tower, make sure the tower is fastened securely in the vehicle so that the communication head is not damaged during transport (Fig 12).   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 12.  Make sure towers with communication heads are fastened securely during transport to prevent damage.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=369</id>
		<title>Turtle Sense nest site installation instructions</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=Turtle_Sense_nest_site_installation_instructions&amp;diff=369"/>
		<updated>2014-09-15T23:40:36Z</updated>

		<summary type="html">&lt;p&gt;Dave: /* Installing a Sensor */  Add photos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
These step-by-step instructions are meant for someone who has never installed a sensor or communication tower into a turtle nest.  The sensors and communication heads/towers are the two main components of this remote monitoring system.  These systems are capable of detecting nest hatching activity before any external signs of hatching (I.e. depression or emergence) are evident.&lt;br /&gt;
&lt;br /&gt;
==Installing a Sensor==&lt;br /&gt;
[[File:Nest_Installation_Fig1.jpg|right|thumb|300px|Figure 1 - Sensor and cable placement on top of turtle eggs.]]&lt;br /&gt;
[[File:Nest_Installation_Fig2.jpg|right|thumb|300px|Figure 2 - Trench leading from turtle nest to sign post for cable.]]&lt;br /&gt;
[[File:Nest_Installation_Fig3.jpg|right|thumb|300px|Figure 3 - Testing and registering the sensor with the hand held device.]]&lt;br /&gt;
[[File:Nest_Installation_Fig4.jpg|right|thumb|300px|Figure 4 - Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.]]&lt;br /&gt;
At Cape Hatteras National Seashore, turtle patrols are conducted daily from May 1-Sept 15, or 2 weeks after the last sea turtle nest or crawl is found.  Once a nest has been located, the biological technicians conducting the patrols determine whether or not the nest needs to be relocated.  According to the NCWRC guidelines, a turtle nest should be allowed to incubate at its original location if there is any reasonable likelihood of survival and relocation should only be considered as a last resort in terms of nest management.&lt;br /&gt;
The ping-pong ball shaped sensor should be placed on the top of and in the middle of the nest.  Usually the sensor can replace the egg that is removed for the DNA study.  The cable should be coiled one time around the inside of the top of the nest cavity (Fig. 1).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Figure 1.  Sensor and cable placement on top of turtle eggs.&lt;br /&gt;
Next, dig a trench for the cable and the terminal end of the sensor.  The trench should be deep enough so that it will not be uncovered by the wind and/or storm events (Figure 2).&lt;br /&gt;
                  	&lt;br /&gt;
Figure 2.  Trench leading from turtle nest to sign post for cable.&lt;br /&gt;
Prior to burying the sensor and cable, the sensor should be registered with the hand held device (Figure 3).  &lt;br /&gt;
&lt;br /&gt;
Figure 3.  Testing and registering the sensor with the hand held device.&lt;br /&gt;
The hand held device 1) determines if the sensor is functioning properly, 2) determines if there is adequate cell tower reception, and 3) registers the time and placement (i.e. GPS location) of the sensor.  See [https://www.youtube.com/watch?v=4z2kcYOHgsw YouTube video for detailed information on the hand held device and sensor registration (https://www.youtube.com/watch?v=4z2kcYOHgsw)].   Once the registration is completed, the terminal end of the sensor is protected with the provided pill bottle.  The seam of the bottle is wrapped with Parafilm to prevent moisture from corroding the sensor terminal (Figure 4).  Only after the registration is complete (and the sensor is registered) should the cable be covered with sand.&lt;br /&gt;
&lt;br /&gt;
Figure 4.  Parafilm is wrapped around the seam of the pill bottle to protect the terminal end of the sensor from corrosion.&lt;br /&gt;
&lt;br /&gt;
To make it easier to remember where the terminal end of the cable is located, the cable should be buried and then wrapped around the back, RIGHT (if facing the dune) turtle sign (Fig. 5).&lt;br /&gt;
&lt;br /&gt;
== Constructing a Communication Tower ==&lt;br /&gt;
Because of the weight of the communication towers (i.e. cement bases) they will have to be built on site.  Following is a list of supplies that are needed to build a tower (Fig. 6) :&lt;br /&gt;
*3&amp;quot; PVC (pre-cut to desired length-10 ft.pipe cut into thirds.)-if not pre-cut you will need something to cut it with.&lt;br /&gt;
*3.5 gal buckets&lt;br /&gt;
*Tub for mixing cement&lt;br /&gt;
*Quikcrete (60 lbs.)&lt;br /&gt;
*Shovel &lt;br /&gt;
*Level (optional)&lt;br /&gt;
*Masking tape (optional) – used for setting the PVC.&lt;br /&gt;
*Drill&lt;br /&gt;
*2&amp;quot; hole saw.&lt;br /&gt;
*Sanding drum for drill (or a Dremel tool) to sand down the edges of the hole in the PVC.  I use the hole as a handle when carrying it in the field.&lt;br /&gt;
&lt;br /&gt;
Figure 6.  Supplies needed for communication tower construction.&lt;br /&gt;
After mixing the Quikcrete with water, pour it into the buckets.  One 60 lb. bag of Quikcrete should be sufficient for two bases.  Insert the pre-cut PVC into the cement, level the PVC and stabilize with masking tape (Fig. 7).&lt;br /&gt;
&lt;br /&gt;
Figure 7.  Leveling and stabilizing PVC with masking tape.&lt;br /&gt;
After the cement has dried for 2-3 days, drill a 2” hole at the base of the tower.  The hole will need to be large enough to be able to pass the terminal end of the sensor through the opening (Fig 8).  It is also recommended that 4-6 small drainage holes be made just above the cement level in the bucket  to prevent water accumulation.&lt;br /&gt;
&lt;br /&gt;
Figure 7. Completed construction of the communication tower.&lt;br /&gt;
&lt;br /&gt;
==Installing a communication tower and communication head ==&lt;br /&gt;
Upon receipt of the communication heads, they should be attached to a sensor to insure that no damage occurred during shipping.  Confirm with Nerds Without Borders that they are receiving data from this sensor/comm head.  After approximately 50 days (or less) of incubation, locate the terminal end of the sensor that should be wrapped around the back, right sign of the closure.  Uncoil the cable and dig a hole for the concrete tower base.  The lip of the bucket should be buried just below the surface of the sand (Fig. 8).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 8.  Communication tower and head for sensor data transmission.&lt;br /&gt;
&lt;br /&gt;
Feed the terminal end of the sensor through the hole at the base of the tower to the top of the tower.  Leave plenty of cable slack at the top of the tower so that it is possible to lay the communication head on the ground while it is attached to the sensor (Fig 9).  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 9.  Attaching the terminal end of the sensor to the communication head.&lt;br /&gt;
&lt;br /&gt;
If this is a one person install, having the slack will make it easier to wrap the pill bottle (housing the connection) with Parafilm after connecting the two cables.  Both the seam (where cap connects to the bottle) and the base of the bottle (where the coomunication head cable enters the bottle) should be wrapped with Parafilm.  Once the communication head has been connected to the sensor, the communication head can be attached to the communication tower by tightening the set screw at the base of the communication head.  To prevent rust issues with the set screw, cover it with a piece of white (if available) electrician’s tape.  Confirm the install of the communication head with Nerds Without Borders.  Rake out any tracks/depressions around the communication tower  (Fig 10).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 10.  Communication head/tower installed and transmitting data.&lt;br /&gt;
&lt;br /&gt;
==Removing the Sensor and Communication Tower==&lt;br /&gt;
The nest should be excavated 72 hours after the first emergence of turtle hatchlings.  Follow normal procedures for conducting an excavation.  If more than 15 live hatchlings are encountered the nest, the nest should be gently re-covered with sand and the hatchlings allowed to emerge on their own. Note the exact time an excavation was started do that hatchling vs human movement of the sensor can be distinguished.  If less than 15 live hatchlings are encountered during excavation, document the number of live hatchling encountered above, below, or level with the sensor (Fig. 11). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 11.  Live hatchlings encountered above the sensor.&lt;br /&gt;
Note if the cable or sensor appeared to impede hatchling emergence in any way.  Pull up the buried cable and follow it to the communication tower.  Do NOT detach the sensor from the communication head for at least 6 hours after the excavation.  This will allow the final data from the sensor to be sent and prevent the loss of this data.  The communication head and sensor can be removed from the tower but the connection between the communication head and sensor should not be broken.   If traveling with the communication head still installed on the communication tower, make sure the tower is fastened securely in the vehicle so that the communication head is not damaged during transport (Fig 12).   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fig. 12.  Make sure towers with communication heads are fastened securely during transport to prevent damage.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Nest_Installation_Fig12.jpg&amp;diff=368</id>
		<title>File:Nest Installation Fig12.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Nest_Installation_Fig12.jpg&amp;diff=368"/>
		<updated>2014-09-15T23:21:20Z</updated>

		<summary type="html">&lt;p&gt;Dave: Nest_Installation_Fig12&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nest_Installation_Fig12&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
	<entry>
		<id>http://nerdswithoutborders.net/index.php?title=File:Nest_Installation_Fig11.jpg&amp;diff=367</id>
		<title>File:Nest Installation Fig11.jpg</title>
		<link rel="alternate" type="text/html" href="http://nerdswithoutborders.net/index.php?title=File:Nest_Installation_Fig11.jpg&amp;diff=367"/>
		<updated>2014-09-15T23:20:37Z</updated>

		<summary type="html">&lt;p&gt;Dave: Nest_Installation_Fig11&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nest_Installation_Fig11&lt;/div&gt;</summary>
		<author><name>Dave</name></author>
	</entry>
</feed>