Have sent off 19 MTS300 and MTS310 back to Crossbow for rewiring (2-3 week turn around). Have installed Moteworks v2 rel B. So for time being focusing on application of MTS400 (3 off) and the A/D sensor boards….
Alvise found this when looking for reviews on the new laptop he is getting…. nothing like seeing other peoples experiences. I like the quote from the guy who posted this *It is only a matter of time until such an incident breaks out on a plane*…
Animated gif showing some time stamps of ad hoc routing over the duration of a 2 day trial – note changes in routing patterns – probably due to changes in battery strength and physical changes in space (people, obstructions etc).
Met with Dan Hill today talking about interactivity in the built environment and away days – an unusual mix… the conversation reminded me to look up: Getting started with “Getting Things Done” | 43 Folders
This is a screenshot of a 24 hour cycle of 20 motes measuring temp, light, battery, mic, accel and mag. Motes are micaz, sensor boards are MTS300 and 310’s. Gateway is an MIB510 connected via serial to USB converter. Data being captured into Postgres db on sony laptop. Code on
The 20 node network gave some interesting trends but weird results. Not sure why there is so much fluctuation in temperature and seems a little too periodic…. lodged a request with the support desk…
Finally got all 20 nodes up and running. 1 gateway and 19 nodes with either MTS300 or MTS310 sensor boards. Had it running overnight – moteview crashed a couple of times will need to try and figure out why. Need to go and review data to see how valid it
Found these from posting to Make site – what an excellent use of *spare* bits and pieces…. the blinky bugs
1 gateway and 4 sensor motes running. Having trouble deciphering code to get all sensors working. Have tried to use the XMesh samples as my base. Used the tutorial file (containing the temp only code) and expand it to include the other stuff. All the examples seem to be slightly