README.txt ========== Data supporting the conference paper: Wireless sensor monitoring of Paddington Station Box Corner URI: doi:10.1680/tfitsi.61279.209 (paper) https://www.repository.cam.ac.uk/handle/1810/254928 (dataset) This data consists of displacement and inclination sensor data from an excavation at a construction site at Paddington, London between 17/02/2014 and 17/08/2014 and transmitted using a wireless sensor network. Accompanying this data is a location of each of the sensors within the construction site. A portion of this data has been used to generate the figures presented in the paper "Wireless sensor monitoring of Paddington Station Box Corner". Archive structure: ------------------ paddington-wsn-data.zip README.txt (this file) Data/ paddington-2014-02-17-1.csv paddington-2014-02-17-2.csv paddington-2014-02-17-4.csv ... Figures/ Fig2/ Fig2a/ Fig2b/ Fig6/ Fig7/ Fig8/ Fig9/ Fig9a/ Fig9b/ Fig9c/ The dataset consists of all the data in the Data directory. Subsets of this data, together with wither the MATLAB scripts used to process the data, or MS Excel .xlsx files and Origin Project .opj files used to generate the figures for the paper, are also presented in the Figures/Fig6 and Figures/Fig7 directories. These do not form part of the dataset as such, but are included as an example of how the dataset can be used. Sensor and Relay node positions ------------------------------- The Figure/Fig6 directory contains STL files showing the placement of the wireless sensors (without Node IDs) on site in a 3D model. The Figures/Fig7 directory contains the MATLAB script Pad_WSN_topology.m which contains coordinates of each of the sensor and relay nodes by node ID. Data format: ------------ Within the Data directory are a number of different .CSV files with names constructed as follows: paddington-yyyy-mm-dd-t.csv where yyyy-mm-dd are the year, month and day that the data was collected, and t is the type of data collected. Note that although the file suffix is .csv, the fields in the .csv files are actually separated by semicolon ';' characters and not by commas ','. Format of '-1.csv' files: Example ================================================ Logging started at: 17/02/2014 00:00:54 ================================================ 2014-02-17 00:00:54;/aaaa:0:0:0:200:1111:2222:101;5500;54;26985;26985;259 2014-02-17 00:05:57;/aaaa:0:0:0:200:1111:2222:101;5500;55;26985;26985;259;260;261 2014-02-17 00:07:06;/aaaa:0:0:0:200:1111:2222:103;5500;64;26985;257;26985;261;260 2014-02-17 00:10:57;/aaaa:0:0:0:200:1111:2222:101;5500;56;26985;26985;259;260;261 2014-02-17 00:12:10;/aaaa:0:0:0:200:1111:2222:103;5500;65;26985;257;26985;261;260 2014-02-17 00:17:13;/aaaa:0:0:0:200:1111:2222:103;5500;66;26985;257;26985;261;260 2014-02-17 00:21:05;/aaaa:0:0:0:200:1111:2222:101;5500;58;26985;26985;259;260;261 The -1.csv files contain details of the neighbouring nodes that each node is aware of. Field 1: The date and time in YYYY-MM-DD HH:mm:ss format. Field 2: A '/' character followed by the IPv6 address of the sensor that sent the message Field 3: An IP port number in decimal (always 5500 in our application) Field 4: A one byte seqence number (0 to 255) Fields 5+: A list of node IDs in decimal. (A node's ID is the last two bytes of its IPv6 address.) Format of '-2.csv' files: Example ================================================ Logging started at: 18/02/2014 00:14:34 ================================================ 2014-02-18 00:14:34;/aaaa:0:0:0:200:1111:2222:101;5500;86;-21684;22638;4123;24;-26094;5;253;0;253;0;15018;0;0;5910;17056;0 2014-02-18 00:19:39;/aaaa:0:0:0:200:1111:2222:101;5500;87;-21671;22640;4123;24;-26081;5;253;0;253;0;15020;0;0;5910;17056;0 2014-02-18 00:24:44;/aaaa:0:0:0:200:1111:2222:101;5500;88;-21668;22642;4123;24;-26078;5;253;0;253;0;15022;0;0;5910;17056;0 2014-02-18 00:28:14;/aaaa:0:0:0:200:1111:2222:103;5500;98;-14060;20600;2392;24;-16670;10;185;0;185;1;15042;1;1;5054;17489; 2014-02-18 00:29:46;/aaaa:0:0:0:200:1111:2222:101;5500;89;-21663;22644;4123;24;-26073;5;253;0;253;0;15024;0;0;5911;17065;0 2014-02-18 00:33:14;/aaaa:0:0:0:200:1111:2222:103;5500;99;-14043;20604;2393;24;-16655;10;186;0;186;1;15044;1;1;5055;17493;0 The -2 .csv files contain network stack statistics. Field 1: The date and time in YYYY-MM-DD HH:mm:ss format. Field 2: A '/' character followed by the IPv6 address of the sensor that sent the message Field 3: An IP port number in decimal (always 5500 in our application) Field 4: A one byte seqence number (0 to 255) Field 5: 2-byte received IP packet count Field 6: 2-byte sent IP packet count Field 7: 2-byte forwarded IP packet count Field 8: 2-byte dropped IP packet count Field 9: 2-byte received ICMP packet count Field 10: 2-byte sent ICMP packet count Field 11: 2-byte dropped ICMP packet count Field 12: 2-byte ICMP type error count Field 13: 2-byte ICMP type error count Field 14: 2-byte received UDP packet count Field 15: 2-byte sent UDP packet count Field 16: 2-byte dropped UDP packet count Field 17: 2-byte UDP check error count Field 18: 2-byte received ND6 packet count Field 19: 2-byte sent ND6 packet count Field 20: 2-byte dropped ND6 packet count Format of '-4.csv' files: Example ================================================ Logging started at: 18/02/2014 04:07:01 ================================================ 2014-02-18 04:07:01;/aaaa:0:0:0:200:1111:2222:109;5500;124;3;692;251 2014-02-18 04:51:56;/aaaa:0:0:0:200:1111:2222:13;5500;188;2;0;25026;15193;15555;5139;2349 2014-02-18 04:52:39;/aaaa:0:0:0:200:1111:2222:6;5500;174;1;0;25363;16742;31423;5092;2267 2014-02-18 05:19:18;/aaaa:0:0:0:200:1111:2222:106;5500;114;3;686;254 2014-02-18 05:26:59;/aaaa:0:0:0:200:1111:2222:13;5500;195;2;0;25027;15193;15554;5139;2367 2014-02-18 05:34:25;/aaaa:0:0:0:200:1111:2222:106;5500;117;3;686;254 2014-02-18 05:54:34;/aaaa:0:0:0:200:1111:2222:106;5500;121;3;686;254 2014-02-18 05:59:04;/aaaa:0:0:0:200:1111:2222:107;5500;53;3;681;251 2014-02-18 08:11:21;/aaaa:0:0:0:200:1111:2222:4;5500;7;1;0;25302;17542;31454;5132;2418 The -4.csv files contain sensor readings. Field 1: The date and time in YYYY-MM-DD HH:mm:ss format. Field 2: A '/' character followed by the IPv6 address of the sensor that sent the message Field 3: An IP port number in decimal (always 5500 in our application) Field 4: A one byte seqence number (0 to 255) Field 5: The type of sensor node. 1 = LPDT displacement node 2 = tilt sensor node 1 = relay node Fields 6+: Sensor specific data (see below) For LPDT displacement nodes: Field 6: 1-byte error indicator (0 = no error) Field 7: 2-byte battery indicator Field 8: 2-byte raw LPDT voltage Field 9: 2-byte raw LPDT reference voltage Field 10: 2-byte temperature reading (SHT11) Field 11: 2-byte humidity reading (SHT11) For tilt sensor nodes: Field 6: 1-byte error indicator (0 = no error) Field 7: 2-byte battery indicator Field 8: 2-byte raw X-axis tilt Field 9: 2-byte raw Y-axis tilt Field 10: 2-byte temperature reading (SHT11) Field 11: 2-byte humidity reading (SHT11) For relay nodes (type 3) Field 6: 2-byte battery indicator (from ATmega128RFA1) Field 7: 2-byte temperature reading (from ATmega128RFA1) The calibration data necessary to convert raw tilt or LPDT readings to real-world units are in the Figures/Fig2/Fig2a and Fig2b directories respectively.