Close

Does this project spark your interest?

Become a member to follow this project and don't miss any updates

Open Source Science Tricorder

Science in your hand. A pocket-sized instrument capable of visualizing and exploring the world around you.

This project was created on 06/07/2014 and last updated 19 days ago.

Description
It is my deep belief that knowledge brings about positive change.

We could live in a world where the same instrument that can show a child how much chlorophyll is in a leaf could also show how them much pollution is in the air around us, or given off by one's car. As an educator and a researcher, I feel that if people could easily discover things about their worlds that were also important social topics, that they would then make positive social choices, like reducing their emissions, or petitioning for cleaner industry in their communities.

By having access to general inexpensive sensing tools, people can learn about healthy leaves, clean air, clouds and the water cycle, energy efficient homes — and visualize abstract concepts like spectra or magnetism.

As a tool for exploration, we can discover things around us that we don't already know. And that's what it's about. Little discoveries, everywhere.
Details

Finals Video

Semifinals Prototype Video

Concept Video

Hardware and System Design

The Arducorder Mini is an Arduino-compatible handheld sensing device, and the next iteration of my open source science tricorder-like device project that's designed to be easy to use, have a large array of sensors, and easy to share sensing discoveries. The Arducorder Mini is designed to foster a community of open source users and development, and is ChipKit MAX32 compatible, which is a port of the Arduino platform to the much more powerful PIC32 family, and makes use of a PIC32MX795F512L with 128k of RAM, 512k of flash, a zippy 80Mhz processing speed, and a fantastic set of peripherals for interfacing to sensors.

The current prototype is designed to use a 1.5" OLED with 128x128 pixels and 16-bit colour, a touch interface, and connectors for 5 modular sensor boards that each contain several sensors. The sensor boards are designed to be interchangeable and upgradable, so that a large number of configurations are possible with different sensing capabilities and price points.

While the Arducorder Mini is being designed with a wide array of sensing capabilities off-the-shelf, it's also designed to be easy for folks to tinker with and upgrade. Accessibility is a central goal of the project -- If you're familiar with Eagle CAD and have ever made an Arduino shield, it should be easy to design your own sensor board. Using OSHPark and Digikey, the parts cost for a new sensor board (PCB and header, not including sensors) is about $5, which is even less than most protoboards!

Sensing Capabilities

The current prototype has been designed to include the following sensing capabilities:

Atmospheric Sensors

  • Ambient Temperature and Humidity: Measurement Specialties HTU21D
  • Ambient Pressure: Bosch Sensortec BMP180
  • Multi-gas sensor: SGX-Sensortech MICS-6814

Electromagnetic Sensors

  • 3-Axis Magnetometer: Honeywell HMC5883L
  • Lightning sensor: AMS AS3935
  • X-ray and Gamma Ray Detector: Radiation Watch Type 5
  • Low-resolution thermal camera: Melexis MLX90620 16×4
  • Home-built linear polarimeter: 2x TAOS TSL2561
  • UV: Silicon Labs Si1145
  • Spectrometer: Hamamatsu C12666MA micro-spectrometer, with NeoPixel light source

Spatial Sensors

  • Inertial Measurement Unit: Invensense MPU-9150 9-axis (3-axis accelerometer, gyro, and magnetometer)

Other Sensors

  • Microphone: Analog Devices ADMP401

Check out the project logs for the current build progress, and stay tuned!

GitHub Repository and Source Files

The source files are available on the Arducorder Mini GitHub Repository as the development progresses. The hardware is licensed under Creative Commons By-Attribution Share-Alike 4.0 International, and the firmware and libraries are available under various open licenses. Please see the licenses file included with the source for more information.

Gerbers and Parts List

While the major parts are listed below, the Arducorder is a modular ecosystem of seven boards -- including the motherboard, capacitive touch interface board, and five modular sensor boards. The hardware folder of the Github repository contains the latest Eagle source files, and gerber files that can be uploaded directly to OshPark. While the Eagle files contain internal parts lists, this source directory will also maintain PDFs of schematics and separate parts listings.

Contributions

In addition to the device, this project has developed open source Arduino-compatible libraries for a light weight live tile based graphical user interface, supporting tools, open libraries for new sensors including the Radiation Watch Type 5 and Hamamatsu micro spectrometer, additions to the Adafruit MPR121 library to support capacitive touch wheels, and a port of the Adafruit CC3000 WiFi module to the Chipkit MAX32 platform. I have also greatly expanded the Plotly library for Arduino, which now supports multiple streams, much faster transfer speeds, and sending normal (non-streaming) plots. I have also partially updated the ChipKit IDE I2C and Client/Server libraries to partial Arduino...

Read more »

Components
  • 1 × PIC32MX795F512 Microprocessors, Microcontroller
  • 1 × HTU21D Sensors / Temperature, Thermal
  • 1 × BMP180 Sensors / Pressure
  • 1 × MICS6814 Sensors / Gas
  • 1 × HMC5883L Sensors / Hall Effect, Magnetic
  • 1 × AS3935 Sensors / Special Functions
  • 1 × Radiation Watch Type 5 Radiation Sensor
  • 1 × TSL2561 Sensors / Ambient Light
  • 1 × SI1145 UV Sensor
  • 1 × Hamamatsu C12666MA Micro Spectrometer

See all components

Project logs
  • Project Video, and Plotly data!

    a month ago • 1 comment


    The project video is up! It's been a very busy few weeks building the final revision boards, putting together an enclosure, and adding the final features to the software. I'm absolutely thrilled at the results, and I hope it helps you make little discoveries -- everywhere.

    Connectivity with Plotly

    The Arucorder Mini now interfaces with Plotly -- a website that's like social media for data, that I've absolutely fallen in love with. After hours of rearchitecting the Plotly Arduino library (with Chris from Plotly's help -- thanks Chris!), there is now a beautiful, fast library for Arduino that supports multiple streams, blazing fast transfers, and normal plotting functions. Please use it, and send me links to your amazing streams.

    The Arducorder now supports one touch uploading to Plotly -- you can literally pull the device out of your pocket, and in 20 seconds have sensor data streaming or spectra shared with friends on the other side of the planet. It's really incredible, and I'm pleased with the results.

    The data used in the video is all available on the Arducorder Mini Plotly profile. Here are direct links to some of the data, including:

    In addition, I will try to keep some of the data from the live streams used in the video active, including the atmospheric stream, magnetic field stream, radiation stream, and inertial measurement unit stream.

    Build Instructions and Acrylic Case

    I've tried to put together a case that would help draw people in, while being functional and easy to construct and disassemble for tinkering. Thanks to Connor and David from Xerocraft for helping me figure out the settings for precision laser engraving, and machining the delrin standoffs!

    Thanks to everyone for their kind words and helpful comments over the project! While designing and building the device is very rewarding, I feel like the real fun is just starting -- actually using the device, and having a reconfigurable scientific multitool to explore the world around us.

    I hope you enjoy the video, and thanks for reading!

  • Hardware Revisions -- Preparing for Release

    2 months ago • 6 comments

    After a marathon programming session, the different modules of the software came together wonderfully for the prototype video nearly two weeks ago -- it's been very exciting to see the Arducorder Mini hardware coupled with an attractive and intuitive user interface:


    Hardware Errata

    I tend to think of first prototypes as a sketch -- in hardware -- that's as close to the final project as time and experience afford, but with the knowledge that for a sufficiently complex project there will always be an errata, or list of items that need to be modified or corrected in the next revision. The idea here is to make our mistakes cheaply so that everything has the best possible chance of working the first time -- and to ensure that we have enough wiggle room to tinker with any critical bits that don't work the first time, so we can quickly narrow down any design changes for the next revision.

    With PCB turn times taking about two weeks, my recent focus has been revising the few issues that popped up when validating the hardware, and sending these new boards off to be made. It's my hope that if everything validates fine, that these boards will be the first official release candidate for the Arducorder Mini.

    Motherboard

    I confess that when I designed most of the first revision boards, I failed to include mount points on the motherboard and capacitive touch board that would allow the whole thing to be placed in an enclosure! This was a bit of an issue, since the motherboard is only 2-layers, and so densely populated that I had to increase the size a small amount (4mm in both width and height) to accommodate four M2 mounting holes. If I was willing to increase the PCB specifications to 4-layers the board would have been significantly less dense and made mounting much easier, but I'd like to keep the specifications as low as possible so that the boards can be made inexpensively, and the open source community can easily modify the designs with the free version of Eagle CAD. I remember years ago reading that when Stephen Hawking was writing A Brief History of Time, his publisher told him that his readership would be halved for every equation he placed in the book. I feel the same about open hardware -- for every barrier I place on people easily modifying the hardware -- expensive software, 4 layer boards, etc -- that it will reduce the reach by at least an order of magnitude. So I'm trying to keep it simple and accessible.

    Other than mechanical considerations -- the four mounting points, and switching to a connector for the capacitive touch board itself with mounting holes -- there are a few minor schematic changes for the motherboard:

    • Added I2C pullup resistors on motherboard
    • Fixed VCC/GND pin swap on two sets of the PIC32 pins
    • The OLED 13V booster VIN is now sourced from the 3.3V regulator instead of the battery. When sourced from the battery and the booster was disabled, the OLED 13V line would be equal to VBAT, causing a few pixels to stay on, and draining the battery a bit.

    These are largely minor changes, and the technical challenge is largely in rerouting big chunks of an existing board for the modifications.

    The capacitive touch wheel board also has largely mechanical modifications to allow it to securely mate with the motherboard, and to mount in a case. The parts have all been moved to the underside of the board (except for the two pushbuttons), leaving a flat surface for some acrylic to mate with for the touch wheel. I'm hoping to have the opportunity to camp out infront of the laser cutter at Xerocraft one evening in the next week or so to design an attractive case with the hardware in hand.

    To help the indicator LEDs for battery charging and programming to shine through to the front face of the enclosure, I've added the small notch along the length of the bottom of the capacitive touch board. Inventables has some back-surface laser-engravable acrylic that looks very interesting, so I've ordered a few pieces and I'm excited to see what some...

    Read more »

  • Tile-based User Interface, and Spectrometer Board!

    2 months ago • 1 comment

    User Interface Design

    Visualization and user interface design is a hobby that I really enjoy, and I've been lucky enough to have friends and colleagues who are usability and visualization folks that I've been able to periodically soak information up from.  The open source science tricorders present a really interesting UI problem -- where most mobile devices have at most a few different sensing modalities, here we have 12 different physical sensors, each of which measures between 1 and 3 different things!  What's more, while some of these measurements are single values (like temperature, say 24C), others are vector values (like the three separate 3-axis vectors coming from the MPU9150 -- one vector for acceleration, rotation, and magnetic field strength, giving nine values total, from a single sensor).  In the extreme case, the spectrometer returns a vector of 256 values. That's a lot of data!  I'm really not aware of any other device that comes close to having so many different kinds of sensing data pouring into it constantly, and while this is very exciting, it's also challenging -- we want folks to intuitively browse and navigate through that data very quickly. 

    I've spent the past few weeks researching design concepts for user interfaces by browsing popular design websites, and talking to some friends, and I think I've settled on a very intuitive, attractive, and useful interface design.  I'll confess that I've been working harder, not smarter about this in recent years -- I'd try and design very complicated things that looked like how other people had done mobile devices and visualization (like android phones), which is a fantastic amount of work for a single human being.  Starting this Arducorder mini project almost 4 months ago, and keeping it attractive and capable but tractable has finally helped me work smarter about this, and figure out a lightweight, usable and intuitive interface concept. 

    I like the idea of live tiles.  When done well, it reminds me of Danny Hillis's idea (30 years ago) about maximizing the amount of computing silicon active on a processor at any one time, but attractively applied to data visualization.  Instead of having icons that just take up space and give you a name, here you have tiles that display a live updating value.  This is powerful from a usability perspective -- instead of having to enter each application to obtain this information (which can consume a lot of time), the most important information is available at a glance from many applications.  While this has largely been applied to communication (e.g. messaging), web (weather/news), and I'm sure sensing applications, here we're going to construct an interface  made almost entirely of sensor data. 

    The really interesting aspect (if you're a data abstraction nerd, like me) is that if we consider only this special case -- visualizing sensor data through tiles -- then we can formulate the software engineering aspect of this very elegantly.  If each tile has a sensor data buffer behind it, then we can browse it's most recent data on the top of the tile, then activate the tile to display additional (historical) data and different visualizations.  If we abstract the sensor data buffer into a few different types, like continuous streaming data (from something like a temperature sensor or an accelerometer) and discretely sampled data (from something like a lightning sensor, that only activates when an event occurs), then we can get rid of the idea of an application.  The design concept becomes browsing sensor data buffers first through a high-level tile interface, and then activating an individual buffer and using a suite of generic visualization tools to better explore it. 

    Interface Implementation

    All of the software engineering aside, what the user sees is very attractive -- tiles with live data that they can browse through very quickly with...

    Read more »

View all 14 project logs

Build instructions
  • 1

    Step 1: Motherboard Assembly and Programming

    I designed all of the boards to be hand solder friendly, with leadless QFNs all on one side (that can be reflowed). If the other side has components, these are usually larger and easier to hand solder.

    Step 1 is to use your stencil to apply paste to the CC3000 side of the motherboard. Note that we'll occasionally switch between Revision 0 and Revision 1 motherboard pictures, but you should be using revision 1 (or the latest release, if a later revision exists at the time of reading).

    Populate the back components. I recommend leaving off the sensor headers until the end -- it'll make it easier for the board to fit into a holder while you solder the top components later.

    Reflow the bottom side. You may wish to pre-solder at least the mechanical mount points on the USB connector and battery connector to make sure they don't move (and end up angled) during reflow.

    Next, solder the top components. I do this by hand, starting with the PIC32, moving to the OLED connector, and then if everything looks good, stenciling the bottom of the board for the passives. Please take your time, it's not a race -- and if you bridge the connections it will make a mess of the board to clean up. For reference it takes me about an hour to solder all four sides of the PIC32, going slowly with very small amounts of solder paste. The OLED connector is similarly fine pitched, and the capacitive touch wheel connector is VERY fine pitched, so take it slow. The crystal will require a quick reflow with a hot air station to be properly hand soldered.

    Do not solder on the programming (ICD3) connector -- This is a one-time use connector, so the pins are offset such that the tension will let you quickly program the device, then remove the header so it's not in the way.

    Firmware

    Next we'll need to load the Chipkit bootloader onto the Arducorder Mini motherboard using a Microchip PIC programmer, like this ICD3. If you're not a PIC developer and don't need the debugger functionality, Microchip also has a programmer that's about a tenth of the cost, and here we're just using it to upload the bootloader -- afterwards we'll be uploading firmware using the Chipkit IDE over USB.

    If you're using the ICD3, you'll need a converter to go from the 6-pin phone connector to a regular 0.1" header (Sparkfun sells these). Note that only 5 pins are exposed on the motherboard -- the unused pin (opposite of MCLR) isn't included since space is at a premium.

    Don't forget to power the board from an external supply through the battery connector -- 3.3V from a regulated supply should to well. Ensure that you check for bridges before powering the board, and are using a power supply with a fuse and current meter so that it doesn't blow the whole thing to the moon if you've got a solder bridge.

    The Chipkit folks maintain a great set of documents on how to go about this process (which only takes a few minutes), as well as having the bootloader that you'll need to install:

    The abridged version is that in the new Microchip IDE this has been made super easy, and takes only a few clicks with their HEX programmer:

    Connect, Select bootloader, Program. If you see something like this output, then congratulations, the programmer can successfully commuicate with the PIC32 and has programmed the bootloader! If you don't see 'Target Detected', ensure that you've powered the board externally, and that the power switch is in the "ON" position. If those are the case, verify your soldering.

    CC3000 Firmware Update

    The Adafruit CC3000 library requires that the firmware on the CC3000 is updated in order to connect. This is a quick update and a good first test. Unconnect the programmer and connect a USB cable. Using the Chipkit IDE (Ideally version 0024 or later), load the driver patch sketch and allow it to update the CC3000 module firmware. You shouldn't require the Arducorder-modified Chipkit IDE (which updates a few of the libraries for better Arduino 1.x compatibility) for this operation.

    Finishing up soldering

    Now that everything's working, feel free to solder on the sensor board connectors:

    If you're eager to see /something/ on the screen, you can grab the latest Arducorder firmware (currently "test2k") as well as the updated Chipkit IDE (skip ahead to the main firmware step for the link). You will likely see something on the screen before it fails to find the sensor boards or capacitive touch wheel attached, and freezes -- but this will let you know that the screen is healthy and functioning.

    Congratulations! You now have a working Arducorder Mini motherboard! On to building the sensor boards.

  • 2

    Step 2: Sensor Boards

    Congratulations -- if you've successfully soldered the motherboard, then you'll likely have little issue putting together the sensor boards. They're very tiny, and about a 2 hour build per board. Because the process is similar for each board, here we'll just highlight any deviations to keep in mind. All of these boards have been designed to be relatively easy for an experienced surface mount solderer to put together -- one side has most of the parts and can be easily reflowed, and then the other side (usually just a connector, and perhaps a few passives) can be quickly hand soldered.

    The six sensor boards are: (1) the capacitive touch board, (2) the magnetometer/IMU board, (3) the atmospheric board, (4) the lightning sensor board, (5) the spectrometer/thermal camera board, and (6) the radiation sensor board. Of these, only the spectrometer board and radiation sensor board have special instructions.

    Spectrometer Board

    The spectrometer/thermal camera board houses the most high value sensors on the entire device, and individually represents most of the BOM. Ensure that you take care when assembling this board, and verify the voltages (both 3.3V and the 5V boost for the Hamamatsu micro spectrometer) before soldering the thermal camera and spectrometer.

    I very strongly recommend placing squares of kapton tape (or another non-conductive tape) under both the spectrometer and thermal camera before soldering. Their cans are conductive, and this will help avoid any of the other pins accidentally bridging with the case.

    Optional light source header: The spectometer board includes an optional 3 pin header for connecting your own light source. This header exposes 3.3v, GND, and an I/O pin. It's recommended that you solder a connector to this header, that you can attach LED boards to. The I/O pin should be used to drive a MOSFET that powers the LED -- the pin itself shouldn't be used to source any current (especially for something like a small incandescent bulb!)

    Filters: The two light sensors at the top right of the board have mount holes on either side. These are designed to allow user-configurable narrow band filters (or polarization filters) to attach, for user configurted applications. You'll need to laser cut or 3D print a tiny holder for your filters that affixes to this footprint, with M2 machine screws.

    Radiation Sensor Board

    The radiation backpack board allows the Radiation Watch Type 5 connector to the Arducorder Mini. This sensor board also contains an external comparator that allows the radiation sensor to be much more sensitive. You can experiment with different values for the calibration resistor, but a 2.7k 1% seems to have a good balance of signal-to-noise for me.

    In order to make the Type 5 extra sensitive, you will have to solder a piece of wire wrap to one of the test points. I recommend making a tiny loop at the end (with some tweezers), bending it 90 degrees, then hitting it with some solder paste. This connection has a very low voltage signal running through it, so be sure to do a good job soldering.

    The short piece of wire wrap solders to the backpack at TP1, which should be directly above the appropriate location on the Type 5.

    Congratulations! Feel free to connect this board up to an Arduino/Chipkit to test it out separately with the example firmware before continuing, if you'd like. The folks at Radiation Watch also have some Arduino-compatible Type 5 firmware that should work with this board (and takes the noise pin into account, if you're planning on vibrating the sensor).

    Cat in Digikey box interlude

    Magnetometer/IMU Board

    This board includes an I2C address solder junction for the MPU9050. Ensure that it's shorted as above (otherwise it may conflict with the MPR121).

    Atmospheric Board

    This is the first revision of the Atmospheric board -- you'll want to put together the second revision, with the mosfets for the gas sensor.

    Lightning / UV board

    You'll need to use hot-air reflow or reflow the board twice to properly reflow the tiny microphone on the back.

    Capacitive Touch Sensor board

    The latest revision of this board moves all the components except for two pushbuttons to the bottom side of this board. The whole thing can be easily reflowed without issue. The two LEDs/resistors beside the button are "do not populate" -- they're included incase you want to have a fancy glowing OK button, but are untested.

  • 3

    http://www.tricorderproject.org/arducorder/chipkit-mplab-ide-0023-arducorder.ziphttp://www.tricorderproject.org/arducorder/chipkit-mplab-ide-0023-arducorder.zip

    Step 3: Constructing the Case

    This beautiful case is constructed from laser cut acrylic -- part of which is engraved to make the touch wheel, and buttons. The side is easily manufactured by bending a long strip of acrylic with a normal hot air rework station.

    Laser cut the acrylic

    The enclosure is constructed from 1/8 inch (~2.9mm nominal) acrylic. The pattern files can be found on the Github repository under "mechanical".

    While the back pieces are standard cutting and engraving, the side requires bending, and the top requires essentially using the laser cutter as a mill. The top process is as follows:

    • Cut the top plate outline and M2 holes
    • Cut an outline around the touch wheel
    • Manually remove the plastic shroud on the acrylic, so the next engraving step won't leave any of the protective cover in the touch wheel engraving area
    • Engrave the touch wheel (on the top of the acrylic) to ~2mm depth
    • Carefully flip the top plate in place, using the acrylic sheet that it was cut from as a placement jig
    • Engrave the bottom of the acrylic for the two button lips, and the buttons themselves -- these should also be engraved to ~2mm depth
    • Cut the buttons

    You will need to experiment to find settings on your laser cutter that engrave to the required depth -- this will take a few minutes of experimenting. The settings that I use for our Trotec 60W cutter at Xerocraft are:

    Initial Cutting Step

    Touch Wheel Engraving

    Flip piece -- engrave buttons and button holes

    Final step -- cut buttons out

    Side Piece

    Cut out the bending jig out of 3mm MDF. There will be one extra middle piece that isn't required. The holes should snugly fit some number 6 screws, and hold the jig together. Don't forget to include a nut in the captive slot, so that you can securely hold the large side piece in place while you bend it.

    This step takes a bit of practice, so I recommend cutting out a view side pieces to practice on. Using your hot air rework station set to around 250C, heat the bends one at a time until they very slowly bend into beautiful curves. For the two long pieces, I attached a counter weight on either end for leverage (Just taping a small screwdriver to the ends). This helps gravity along a bit. Try not to force the pieces -- let gravity do the work, and it'll look better.

    It takes about 5 minutes per bend, or about 20 minutes total. If you have an actual acrylic oven meant for this, then you're job is a little easier -- although be careful not to bend the straight pieces, or it may end up looking more like a Picasso.

    Assemble

    Countersink the four holes on the top plate. Using four M2x16mm countersunk machine screws, bolt the capacitive touch wheel board to the motherboard. Place four 3mm high M2 spacers between the boards. The two middle bolts should have M2 nylon washers, and M2 locknuts.

    Attach four M2-tapped 5mm diameter delrin standoffs. You'll likely need to quickly machine these yourself, or purchase some nylon standoffs and tap them yourself. These act as the main fastener for the bottom two holes.

    Ensure these are snug, but not too snug. It's critical that the acrylic faceplace makes very good contact with the capacitive touch wheel for normal operation.

    Attach the battery, with the cable snaked over the top of the spectrometer board connector to take care of any slack. Attach the spectrometer board next, then the three side-mounted sensor boards.

    Next up, attach the radiation sensor board. This should snugly fit between the standoffs, keeping everything in place.

    Next we'll attach the first bottom plate -- this one snugly fits onto the four 5mm standoffs, and provides a lip for the side piece to rest on.

    Next we'll place the side piece on -- this should snugly fit around the top bottom plate

    Last, we'll install the bottom plate with the engraving. The four M2 holes here should also be countersunk. This acts as a retainer plate, very snugly keeping the sides together without any adhesive, so that you can take it apart to tinker without issue.

    Fasten with four M2x12mm countersunk machine screws.

    Plug in the USB cable, and view the beautiful LEDs telling you how great a job you did. Red means the battery is charging, green and blue mean serial communication over USB for firmware programming. If you haven't already, download the Arducorder-modified ChipKit IDE, which updates some of the Arduino libraries towards 1.X compatibility. Grab the latest firmware from the Github Repository (currently test2k) and program the device. The firmware is very large, and will take a few minutes to upload and verify.

    The firmware will display this splash screen during boot up. It should be on the screen for a few seconds while all the sensors are initialized.

    After booting, your Arducorder Mini should begin to display the tile interface. Go explore the world, and share your discoveries with your friends!

See all instructions

Discussions

willow.gray wrote 3 days ago null point

Please, take my money!
If I had the time and expertise to build one of these, I would. Sadly, I'm way more high-level software than the hardware side of things. So please, please, take my money!

Are you sure? [yes] / [no]

peter jansen wrote 3 days ago null point

I'm hoping to put together a long post in the next week or two (it's /very/ busy in the lab right now!) with a project postmortem, and part of it will talk about the folks having "i keep throwing money at the monitor but nothing's happening!" problems (which is somewhat overwhelming, and very kind -- thank you). i'm an academic researcher and scientist who just happens to be an okay electrical engineer, and so i'm good at solving scientific and engineering problems. for the first time, the problems that this project now faces are now much more business, regulatory, and legal issues rather than engineering issues, and i'm much less adept at finding answers to these. but i hope to have some answers shortly.

Are you sure? [yes] / [no]

Noman wrote 3 hours ago null point

Dear Dr. Jansen, thanks for replying, a sigh of relief. I shall wait for your long write up.

Are you sure? [yes] / [no]

Noman wrote 7 days ago null point

My screen crashed as I have thrown all my coins collection on it (kidding...).

Are you sure? [yes] / [no]

Gasump wrote 7 days ago null point

Just adding my vote for a pre-assembled PCB or a Kickstarter. If the latter, I'm sure you'll get funded in no time!

Are you sure? [yes] / [no]

andy wrote 8 days ago null point

Hi! Amazing project. Two things. First, you may want to consider a physical knob in future versions vs. the wheel to make it usable with gloves on.

Second, I'm throwing money at my screen but nothing is happening. Will I ever be able to buy at least pre-assembled PCBs? Thanks!

Are you sure? [yes] / [no]

Noman wrote 9 days ago null point

Dear Dr. Jansen, Wish I could hear from you more on this project. After competition is over, please share your thoughts and plans to take the tricorder project any further or manufacture or sell it? Are you planning to incorporate more sensors or BLE or improve interface/software?

Are you sure? [yes] / [no]

Noman wrote 13 days ago null point

Dear Jansen, It is sad but at-least you made it so far. Wish it won't effect your moral and dedication. We all would like to know when OSMT will be available on kickstarter and it definitely will be a huge success. Please also share your thoughts and further developments.

Are you sure? [yes] / [no]

Noman wrote 16 days ago null point

Dr. Jansen, best of luck. See you in space soon.

Are you sure? [yes] / [no]

jaromir.sukuba wrote 24 days ago null point

Hello Peter,
this is awesome project. I built already a small tricorder, but it is toy compared to your device. It is great not just as whole unit, but even the parts are interesting on itself.

I'm interested in the C12666MA sensor, but I'm unsure where to get it and what is important - how much it does cost. My favorite distributor channels (Mouser, Farnell, RS) doesn't seen to know about the sensor and dealing with manufacturer directly is usually pain in the S, especially when manufacturer is huge and one doesn't want to buy full truck of sensors.

Regarding the radiation sensor - I'm a bit unsure about what sensor you actaully used (FSX100-7 2.0?) and how it is connected - schematics https://github.com/tricorderproject/arducordermini/blob/master/hardware/sensorboard_radiation_rev0.pdf shows comparator and "clicker", but I can't find the detection diode itself and charge amplifier.
You also uploaded pulse width histograms of Ba133 and Cd109, exhibiting interesting differences. Did you investigate more about this, like corelation between energetic and width spectrum?

Sorry for asking questions that may be already answered - your project logs are really huge and informative, but I'm a bit overwhelmed by the amount of information.

Are you sure? [yes] / [no]

peter jansen wrote 24 days ago null point

Hi Jaromir,
No worries -- they're answered in the project logs and bill of materials, but I suspect that a lot of folks will focus onto these two parts, and I'm very happy to make finding the information about them easier.

The Hamamatsu microspectrometer is available off-the-shelf from Hamamatsu, but you'll need to contact them directly to order one. Last I checked they are about $250 in single quantity, which makes that single part worth nearly half the bill-of-materials cost, so folks have the option of making the "inexpensive-corder" by leaving it out. To the best of my knowledge Hamamatsu only sells directly to folks, and I think at least part of the reason is that they manufacture world-leading sensors for scientific and medical use, and don't want them to be misused for military purposes.

The radiation sensor is described in this project log, about half way down ( http://hackaday.io/project/1395/log/5858-sensor-board-megaupdate ). The radiation sensor is called the "Type 5" by Radiation Watch. Building noise-tight circuits that amplify the signal from a single subatomic photon to a 3.3V pulse absolutely blows my mind, and while they publish the schematics, you'll definitely want to purchase one directly from them -- the process of manufacturing these and making them noise resistant is non-trivial. They're about $70 each, last I ordered. The radiation backpack board (that you linked to above) connects to this Radiation Watch Type 5 at CN1 ("Radiation Watch Type 5 Header", center left) and at TP1 ("Type 5 Pre-comparator test point", top left). The stock Type 5 is good, but it can be made much more sensitive, and the board I designed basically gets its detection efficiency to just above the noise floor. You're right, the Type 5 does use the FSX100, which the datasheet shows has an incredible detection efficiency for low energy (on the order of ~10keV) x-rays, and quickly collapses to ~1% efficiency on the order of ~100keV. I think the folks at Radiation Watch calibrated the Type 5 for Cesium-137, which does have a lower energy emission around ~30keV, but also has lots of higher emissions >100keV to detect. I think the stock threshold is around 60-80keV, but with the modifications (and a R7=2.7k calibration resistor, this is in the build instructions), I think you can get it down to around 30keV, where the Barium-133 has lots of emissivity. The Cd-109 has lots of emissions around ~22keV, and while you see more of these, I think 22keV is buried under the noise threshold... so if you lower R7 you'll see more of these, but your baseline counts will be much much higher (ie. you'll have a much lower SNR that you'll have to characterize).

The energy sensitive histograms are definitely really interesting and exciting. The proper way to sense energy would be to integrate the area under the detection curve and report this out (instead of just having a comparator), but this would be a much more complicated and very fast circuit. The easier way is what I'm doing here, counting the pulse width, with the knowledge that higher energies will take longer to decay, so the pulse width will be longer (but of course this is just approximate, the two are only correlated, and right now we don't know what the coefficient is). I'd love it if there were a clear way to back out energy level (keV) from pulse width. It's clear that it's non-linear, and that there's some variability and overlap (e.g. 50keV might be 50uSec +/- 10uSec). Aside from that, I'd love a few hours with a few monochromatic sources to back out the relationship. It does look like the acrylic case acts as a beta particle blocker, and so a few peaks disappear when the histogram is taken in the case versus out -- so by selecting a few radioisotope check sources with different beta emissions, it might be possible to take a first look at backing this out without too much trouble. Also, for the radioisotope sources the detections are typically under 200uSec, but if you leave it out on a table for an hour pointed up just picking up background/cosmic, you'll very occasionally get a few REALLY big pulses, which are likely some high energy cosmic rays (I've seen one or two on a scope -- they were very big detections). So it seems clear that in the worst case there might be at least half a dozen or a dozen good spectral channels, and in the best case, the Cd109 and Ba133 histograms I posted at least hint that there might be much finer discriminations possible. There are lots of radiation enthusiasts out there with large collections of check sources, so I'm very interested to see what those folks with much more experience come up with.

Are you sure? [yes] / [no]

David wrote 23 days ago null point

I have a quote from Hamamatsu for Europe; the module alone costs 170 euro.

Are you sure? [yes] / [no]

jaromir.sukuba wrote 23 days ago null point

I take my hat off to you. Thanks for long and informative response.

Now it's getting clear about the spectrometer - the price is not bad (compared to near IR spectrometers I'm working on daily basis), but something sub 100USD would be sweet. Nevermind, now I've got new item on my TODO list :-)

Regarding the radiation sensor, I understood it now. Honestly, I could track the information back in your project logs, but your summary makes it much easier.
As I looked into X100 datasheet (by the way, sensor is available at Mouser - http://cz.mouser.com/ProductDetail/First-Sensor/X100-7-SMD/?qs=XT0h7XtgaRluHeOO0jzfWw%3D%3D, great - they have a good selection of sensors at Mouser, actually) the absorption of gamma photons varies quite wildly, peaking about 10keV and going down to approx. 2% at 100keV, decreasing further below 1% at 1MeV. Does it mean that some sort of spectrometry would be difficult anyway? My knowledge/experience is almost zero in here, but to me it looks like the analysator would have hard time telling whether impulse from detector is weak photon (good absorbed) or high energy photon (weakly absorbed). I'd like to be wrong here.

Are you sure? [yes] / [no]

peter jansen wrote 23 days ago null point

You're very welcome -- like you, I'm definitely excited for when micro spectrometers become sub $100 (they're close now, especially compared to a few years ago). But it's a new and enabling technology. It feels like not a month has gone by in the last 5 years where there's an announcement of a new spectrometer-on-a-chip product by company X, but they never end up working out the bugs or coming to market -- Hamamatsu is the only one that's made it, and that you can purchase (to the best of my knowledge). And it's a beautiful little instrument. If you just want to play, there's my Open Mini Spectrometer design, but the Hamamatsu is a real instrument and has orders of magnitude better performance in almost every measure.

If I remember correctly the X100-7 is most efficient at lower energies where the photoelectric effect dominates, and compton scattering dominates at the higher energies. If particle physics wasn't at 8:30am a decade ago, I might be able to tell you if those effects would have different energy profiles on a scope... :) It's very normal to have different detection efficiencies at different energies in spectroscopy, though -- you just take that into account as part of the "instrument function" to back out the likely physical signal (ie. multiply the counts at those inefficient 1% higher energies by 100x). The issue is of course is if there's a substantial spot where the signals from the two effects overlap, then you have to get a little more clever -- counting the peak heights, sampling the pulse profiles to back out which effect they came from, etc. But it's definitely possible that for x-rays your pulses may look one way, and for gamma rays they may look another. For proper spectroscopy you'd want to back all this out. If you're just interested in doing a classification task (like figuring out what radioisotope you're looking at), in the simplest case you could just build a library of what different radioisotopes histograms look like, and do vector-distance matching. But of course doing the work to get the spectroscopy histogram -> energy level function is more general and exciting.

Are you sure? [yes] / [no]

Androiders wrote 24 days ago null point

This is so cool :) Great job!

Are you sure? [yes] / [no]

David Baldwin wrote a month ago null point

This is absolutely amazing! Have you given any thought to, or do you plan on designing a premade kit for this device?

Are you sure? [yes] / [no]

Robert Hoffman wrote a month ago null point

Dr. Jansen,
I've been following you and the tricorder since April of 2012. I've never been so excited about a project like this, I thought the idea was both fascinating and awesome. I wish you the best of luck and I hope you are able to reach your dream of every kid owning one of these

Are you sure? [yes] / [no]

Jrsphoto wrote a month ago null point

Dr. Jansen, I've been following along for some time now and just wanted to say congrats on making the final 5! My favorite project of the bunch and I can't wait to see if you win! You've put a tremendous amount of thought, work, heart, and soul into this project and it really shows. Here's to seeing you in space!

Are you sure? [yes] / [no]

Noman wrote a month ago null point

Dear Dr. Jansen, please accept my heartiest congratulations. I am following the development since I first saw your blog entry (The Shape of Things to Come: the Mark 5 Arducorder) earlier this year and wished somehow I can buy or build this. Only I know how excited I am see this project come to reality and finally completed. Although competition is strong, I am sure you will have made your mark and will catch the first place easily. You know this little gadget will save me from buying half a dozen devices on my wishlist including Apollo Board (Approx $200), Type 4s Radiation Watch (Approx $100), Flir 1 ($350+shipping), Sensordrone ($200+sipping), A spectrometer (Min $500 plus), a weather-station with Lightening sensor ($150+) and an imu ($75+), so otherwise I have to spend $1575 plus shipping plus separate battery and charging solutions, extra weight, carry options and bulge in my pockets in addition to a fight with my life partner. The worth of this device is obvious and I would like to keep 3 accessory switchable boards along with as per my field requirement, including laser rangefinder (like lidar lite) , IR detector & communicator as well as a GPS (like navspark I already have). Please no sooner did you win the prize, tell me when you are going to launch and at what price or if I could buy the first prototype in this final video, really!

Are you sure? [yes] / [no]

relias36 wrote a month ago null point

Hello Peter, i just joined this site and found your project it looks very interesting. I'm a mechanical engineering student so i do not know much about making and designing computer hardware but I am still interested in trying to make one of these devices. Is there any way that i could use your board designs and have them built or could i possibly buy one from you?

Are you sure? [yes] / [no]

Robert Hoffman wrote a month ago null point

do you plan on trying to mass produce it?

Are you sure? [yes] / [no]

David wrote a month ago null point

Congrats on making the Top 5!

BTW, I'm really liking that Arduino-compatible Hamamatsu Spectrophotometer sensor. After the competition, if there any chance of seeing its code separated into a new Arduino Library?

Are you sure? [yes] / [no]

peter jansen wrote a month ago null point

Thanks David! It really is a beautiful little instrument. The driver is already standalone ( https://github.com/tricorderproject/arducordermini/blob/master/firmware/test2k/SensorSpecHamamatsu.cpp / h), and includes some example code at the top, with the exception that one of the methods does resample and export the data into a SensorBuffer() (a circular buffer storage class used by the Arducorder mini for efficiently storing data and graphing it). You could include this too, or just comment out that method and access the data directly.

I have standalone test beds that I use to write and validate the drivers before incorporating them into the main Arducorder Mini firmware (it takes a few minutes to compile and upload, and so the testbeds get that down to ~10 seconds), and either just before or shortly after the competition I'll try to package these as separate Arduino Libaries!

Are you sure? [yes] / [no]

peter jansen wrote 24 days ago null point

Update: these standalone examples are available here: https://github.com/tricorderproject/arducordermini/tree/master/firmware/examples

Are you sure? [yes] / [no]

Ryan Shill wrote 2 months ago null point

You should throw GPS on board for the Mark 6!

Are you sure? [yes] / [no]

peter jansen wrote a month ago null point

I've been thinking about this too. I removed it because it's large and everyone
carries around phones that are very good at map applications right now, but I
think it's important enough to warrant coming back. There isn't a lot of sensor
real estate left, but I have been thinking of replacing the microphone with the
Venus638, or even sneaking it on the back of the capacitive touch sensor board.
I designed something with the 638 in it last year, but I used a very small
antenna (and don't fully appreciate RF design, I work with much shorter
wavelengths), so maybe someone from the community with GPS experience can lend a
hand after things are less busy in a few weeks! The sensor boards are meant to
be part of an ecosystem that's easily modified or added to by the open source
community, with a minimum of effort. :)

Are you sure? [yes] / [no]

vipersan wrote a month ago null point

I think EVA-7M from u-blox is bit smaller, has higher sensitivity and consume less power.

Are you sure? [yes] / [no]

peter jansen wrote a month ago null point

Thanks! That looks like a wonderful chip -- 3.3V @ < 20ma draw while running, and only 7x7mm! Unfortunately it doesn't look like it's regular stock at any of the major distributors, and having to go through the manufacturer usually means a minimum order quantity and long lead times. I'm trying to keep it as easy for folks to source parts and build as I can -- hopefully a major distributor starts carrying these or a similar part!

Are you sure? [yes] / [no]

Noman wrote a month ago null point

Please also have a look at Venus868F. http://www.skytraq.com.tw/news/news2014Jul8.html it seems economical at $3 per module.

Are you sure? [yes] / [no]

n49o7 wrote 2 months ago null point

This is truly from the future.

Are you sure? [yes] / [no]

peter jansen wrote a month ago null point

One of the folks at Ars Technica once claimed in an article that I might be a time traveller from the future borrowing Berlinghoff Rasmussen's business model... I had no idea who it was, so we looked it up, and it made the lab mates and I laugh *so hard*. http://en.memory-alpha.org/wiki/Berlinghoff_Rasmussen

Are you sure? [yes] / [no]

vipersan wrote 2 months ago null point

Few suggestions:
- upgrade MLX90620 thermal camera to Flir Lepton,
- add 2-3 Mpix camera,
- HTU21D and BMP180 replace with BME280 (it's not yet in production, but maybe you can get engineering sample),
- add ALS (ambient light sensor) - IR / IR+visible sensor eg. MAX44009,
- add distance measurement feature.

Are you sure? [yes] / [no]

peter jansen wrote a month ago null point

Thanks. The challenge with most of these is a combination of size, cost, data, and tractability, and this is largely a device that's about balance. The standard configuration tries to strike a very good balance of sensor coverage with cost, while allowing folks who want extra functionality to design their own boards and modify the software very quickly. I would love to see someone design a small camera with a footprint on the order of 1-2cm sq with an integrated framebuffer that could be accessed over SPI. Similarly I'd love to see a small distance sensor with a good range, but right now many distance sensors have a large volume. Even the small maxbotics ultrasonic rangefinders would take up nearly the entire volume of the spectrometer/thermal camera board. That being said, it would take an hour of work to put together a sensor board that contained only the maxsonar, if one wasn't interested in the spectrometer/thermal camera. Eventually someone will make a very small distance sensor, and I would love to place it on the Arducorder Mini, or a future device.

Are you sure? [yes] / [no]

Jordatech wrote 2 months ago null point

Wow What An Awesome Open Source Instrumentation Project! Thank you for making this project so nicely documented! What type of design modifications and distribution costs would this project be looking at for a "3rd world" implementation?

Are you sure? [yes] / [no]

reciprocum wrote 2 months ago null point

This project is just perfect!
I wish all the hardware can be made available in a kit form as soon as possible.
Willing to support it right away if presented at kickstarter platform.

Are you sure? [yes] / [no]

Marcus Vinter wrote 2 months ago null point

I can't agree with you more.

Are you sure? [yes] / [no]

Kojote wrote 2 months ago null point

Jupp, same here

Are you sure? [yes] / [no]

matt venn wrote 22 days ago null point

+1 from me too

Are you sure? [yes] / [no]

Ronny wrote 2 months ago null point

Hey guys. What do you expect when the development process goes to rollout for public? I really would like to have that personally and in our store here in Switzerland.

Are you sure? [yes] / [no]

peter jansen wrote 2 months ago null point

Hopefully soon!

Are you sure? [yes] / [no]

Andrej Mosat wrote 2 months ago null point

Hi Peter, excellent project.
I was reading your questions on mini spectrometer page. One of them was: how to better connect the grating to the enclosure. I use double-sided automotive 3M foam tape, which just works. Maybe you already use the same system, but I could not find how you actually do it. You would also like to use 4mm optics, I might have some suggestions, but again, could not find exactly what the design requires, like the focal length. What is your workflow in programming / debugging / engineering the PIC32 ? It seems like Chipkit Max32 with the modified Arduino / PIC32 platform. Have you found a better diffraction grating? I have an answer to manufacturing of precise, cheap optical slits. What would be the quickest & plug-n-play way to obtain and test your mini spectrometer? Thank you!

Are you sure? [yes] / [no]

peter jansen wrote 2 months ago null point

Hi Andrej, the transmission for the open mini spectrometer is small enough that it just sits in place, and tends to stay (but you're absolutely right, in a real environment you'd want to use a dab of glue or something to keep it there). The open mini spectrometer is basically a pinhole camera, with the transmission grating at the end of a deep, wide slit, so there currently are no relay optics. This, of course, is non-ideal. If you'd like to experiment with making a better optical head, then the sources files are available at the link above -- I use oshpark for boards, and the parts are available at digikey. Unfortunately if you're not comfortable with soldering surface mount parts, there's currently nowhere that the boards are currently off-the-shelf. Maybe someone will post them on tindie!

Are you sure? [yes] / [no]

Steve Pomeroy (xxv) wrote 3 months ago null point

Sweet project. Have you considered using a pre-made GUI/OS layer? You could build on top of things like Linux, QT, Android, etc. and save a ton of dev time.

I suspect one of the things that really make a project like this shine are the way the data are interpreted and visualized, which would be pretty hard to do with an entirely hand-rolled GUI layer. Cheers!

Are you sure? [yes] / [no]

peter jansen wrote 2 months ago null point

Thanks Steve. Microcontrollers are very different than desktops, and have much more modest computational resources, so they're not usually able to run OS's, and the few that they can run are a little complicated to code for. The PIC32MX I'm using has the most RAM of almost any commodity microcontroller (128k), which is barely enough for a display backbuffer and some rolling buffers for the sensor data. :)

Developing an attractive and intuitive GUI from nothing but a pointer to video memory is a bit of work, but it's also a lot of fun, and very rewarding. Architecting it well in this case also means that folks will be able to customize it with very little background knowledge, and (more generally) that Arduino/ChipKit folks will have a lightweight GUI library that they can use for completely different projects.

Over the past few weeks I've been browsing through a lot of design concepts for ideas, and designed something like a Live Tile interface that's controlled through the scroll wheel. It's very intuitive, and looks beautiful, and feels very good on the actual device. There's still a bit of work to do (and the deadline is coming up), but I'll post pictures shortly! Stay tuned!

Are you sure? [yes] / [no]

justin.m.riddle wrote 3 months ago null point

This looks freaking incredible. When the first round is ready for purchase I'll be first in line. My dad is a superintendent of a golf course, and could use something like this to detect soil and water chemistry, weather conditions, and we could even build a sensor that interfaces with his irrigation system. So many possibilities! Good work, I'm very impressed. I'm guessing this is going to get you to space.

Are you sure? [yes] / [no]

peter jansen wrote 3 months ago null point

Thanks for your kind note. I hope you and your dad will get to have all sorts of fun with one, I'd love to see how it works out for that environmental monitoring task!

Are you sure? [yes] / [no]

Jasmine wrote 4 months ago null point

Hello Peter,

there are a few small things you can do to your documentation give your project the best chance of going through to the next round of The Hackaday Prize.

By August 20th you must have the following:
- A video less than 2 minutes long describing your project. I see you have a couple of videos. Put a link to the one you want our judges to watch most in the external links section.
- At least 4 Project Logs. You have this covered.
- A system design document. Is it this image https://static.hackaday.io/images/5974661405800489211.jpg?
- Links to code repositories, and remember to mention any licenses or permissions needed for your project. For example, if you are using software libraries you need to document that information. You can highlight these in the project details or external links section.

Thanks for entering. Good luck.
Jasmine

Are you sure? [yes] / [no]

peter jansen wrote 3 months ago null point

Thanks Jasmine, I think I've put everything up today, including the updated video, the system design diagram, and uploaded the current source snapshotto the GitHub repository!

Are you sure? [yes] / [no]

James wrote 4 months ago null point

maybe in a future version you could add a full-color lcd, and an infrared camera for monitoring heat, and plant chlorophyl levels.

Are you sure? [yes] / [no]

peter jansen wrote 4 months ago null point

Hi James, the OLED is a beautiful full 16-bit colour (the graphical user interface is just unfinished), there will be a low-resolution thermal camera, and the spectrometer may be able to monitor chlorophyl levels. :)

Are you sure? [yes] / [no]

[deleted]

[this comment has been deleted]

peter jansen wrote 4 months ago null point

I mean, you're not wrong -- if you don't value science based on observation and measurement, science education, or being generally interested in learning more about the world around you, then yes, this device will be of little use to you.

If you've taken high school chemistry or physics, you should know about measurement error, and that every measurement from every device has some accuracy and repeatability associated with it -- for example, 25C +/- 0.1C. This is a fundamental property of all sensors (electrical engineering), or the nature of measurement (physics), and is true of a one dollar sensor or a million-dollar instrument. That being said, nearly all of the sensors have been chosen to be particularly accurate, especially for their price point. I think there was an example floating around where the atmospheric pressure sensors are so accurate that, under ideal conditions, you could nearly measure someones height just by measuring the atmospheric pressure at their feet and head, and subtracting the two altitudes you infer from those pressures.

As to why I might be a trustworthy source on sensing and science education, Yes -- I do have a PhD, and have spent the last decade choosing to do academic research (for much less than one makes in industry), teaching, and donating my evenings to projects that help make it easier for folks to learn science -- because I love it, and think it does a world of good. But, as always, you should critically evaluate any source (including me) before you trust what they say.

All that being said, if (after taking time to sleep on it), you still don't understand why folks might find this project exciting, that's okay too. But now that you've (repeatedly) voiced your very strong opinion, I think there are lots of more productive things we can all do with our time.
Best wishes.

Are you sure? [yes] / [no]

[deleted]

[this comment has been deleted]

peter jansen wrote 4 months ago null point

I'm not sure what you mean -- the open source science tricorders I've been building for 7 years are clearly very real devices. In the case of this one, the Arducorder Mini, when complete it will have about a dozen different sensing modalities. It's basically a multitool for science, like a swiss army knife. So maybe your question becomes, where would you use a thermal camera? Where would you want to detect radiation? Where would you want to characterize the atmospheric conditions of an environment, or sense potentially harmful gasses? Where would you want to take the spectra of an object? And so on...

Are you sure? [yes] / [no]

Piotr S wrote 4 months ago null point

I fully support your Project.
Few things from my Point of View:
The Case Design should be more Handheld like an Remote
And when it comes to remotes. What about an IR Transmitter/Receiver Package?

Are you sure? [yes] / [no]

peter jansen wrote 4 months ago null point

Hi Piotr, the industrial design shows that the Arducorder Mini is handheld, like a phone or MP3 player?
Could you make a scientific use case for an IR transmitter/receiver? And what wavelength?

Are you sure? [yes] / [no]

Piotr S wrote 4 months ago null point

I was considering that IR waves are everywhere.
And you could use it to read signals from Remotes and other IR driven Devices.
With the Transmitter you could even copy those Signals.
Greetings and thanks for the Questions :)

Are you sure? [yes] / [no]

Fredwordsplat wrote 4 months ago null point

I Recommend A Voltage Detector With a Detachable Housing and Wireless InfraRed Communications. Like Doctor Bashir uses to Scan Humanoid lifeforms For Injurys.
Image of Scanner :


http://2.bp.blogspot.com/-NP06Lgv6zyA/UFAflMA_WhI/AAAAAAAADBk/LMVzn_71k3c/s1600/Improved+Star+Trek+Medical+Tricorder+Papercraft.jpg

Are you sure? [yes] / [no]

Fredwordsplat wrote 4 months ago null point

I Love The Thought of a Tricorder. I am both a programmer and a Trekker (Star Trek Super Fan!!). I Support This To The Max!!! Epic :)

Are you sure? [yes] / [no]

matt venn wrote 4 months ago null point

super inspiring!

Are you sure? [yes] / [no]

Gasump wrote 4 months ago null point

I agree with jixijenga; a modular sensor system would be a good idea, that way people can adapt the tricorder to their personal needs. For example - people living near a manufacturing plant that 'smells bad'. They could test for various gases/chemicals that could be harmful to their health. While I don't fear opening up and swapping components, I also think the plug in 'accessory' sensor block is a good idea. There is not much commonality in gas/chemical sensors formats so it would be more difficult to accommodate a wider range of possibilities in the instrument dimensions you are working - which I think is spot on!

But there are new electrochemical sensors (much better for specificity than MOS) available that are about the size of a thumbnail and only 4-5mm thick.

You are doing excellent work, keep it up!

Are you sure? [yes] / [no]

peter jansen wrote 4 months ago null point

Thanks Gasump! If you have a look at the project description, video, or the project logs, you'll see that the design is ultra modular with 5 modular sensor boards, 4 of which share a common footprint so that they can be interchanged in position. It should also be relatively easy for someone who's designed an arduino shield to put together their own sensor boards. All of the sensor boards are on the outward surfaces of the device, so if you're willing to make your own case mods, it should be possible to accomodate larger sensors of different dimensions (like those giant gas sensors you mention).

One of the current sensor boards (the atmospheric board) contains sensors for atmospheric temperature, pressure, humidity, as well as three gasses using a tiny sensor similar to the ones you mention -- have a look in the project log Step 2: Concept and Industrial Design for more information.

thanks!


Are you sure? [yes] / [no]

Boz wrote 5 months ago null point

Very similar, yet totally different to my project, I've upvoted it just for the awesomeness of what you're trying to achieve.

Are you sure? [yes] / [no]

Noman wrote 5 months ago null point

Anxiously waiting for the updates and checking project daily I found boards log. Breakout boards for sensors and compatibility of interfacing is cool. Another expansion option might be possible through a converter board that would enable any standard (if there are any standards for these) breakout sensor board from sparkfun or adafruit to plugin to device, or this may be expansion slot?
Capacitative touch wheel is another innovation added and it is impressive. You are not adding ultrasonic sensor due to size limitations but how about adding HB100 doppler motion sensor? Also will the mic would be able to listen to bats?
Sorry for too many questions but that's what strike my mind while reading through.

Are you sure? [yes] / [no]

peter jansen wrote 5 months ago null point

Hi Norman,
I'm hoping that after the device is completed, that instead of working on building these open source science tricorders, there can be more focus on building new sensing packages for them. I'd love a small distance sensor, but I'm not sure that there are any good options out there yet. The HB100 is interesting, but I think also much too large (I think it's nearly half the size of the Arducorder mini!). It also seems to only measure relative change in motion (like an accelerometer), rather than position.
There really are no standard pinouts for sensor boards from sparkfun or adafruit. But with such a low cost to spin your own sensor board, the barrier to creating your own sensor module is much smaller.

Are you sure? [yes] / [no]

Jixijenga wrote 5 months ago null point

Noman, Dr. Jansen,

Perhaps later iterations of the tricorder could have a modular sensor system? Like a plug and play type setup, you pop open the housing, unplug the board(s) and then plug in a different one. We've reached an understanding with technology now that upgrading one's computer isn't seen as a daunting and highly technical challenge anymore, it's largely switching out or adding components that conform to a standardized plug or socket. I think that any advancement in this tricorder could benefit greatly from having such a system, rather than defining the capabilities based on packages or defined variants. An end-user, no matter how uninformed they may be, could customize and configure their tricorder for use in their life. Perhaps people sharing a tricorder could have entirely different uses, and require constant switching of sensors.

Or maybe have a USB type getup, where the sensor packages or modules aren't just restricted to a tricorder and can be used in anything that accepts a USB device. I think that would be great, because while a handheld tricorder is cool, (very cool actually) giving basically anyone with a laptop the ability to emulate one would be even better. Especially for people who wouldn't be able to afford the purchase, or construction, of an entirely new device but would benefit from it's functionality. Perhaps the tricorder could have little "ports" where you plug in this small card-like sensor with a USB plug on the end. I'm sure such a modular and truly plug-and-play sensor would be very robust and durable, further enhancing the utility of the tricorder.

Are you sure? [yes] / [no]

Noman wrote 5 months ago null point

Dear Dr. Jansen, thanks for your kind and informative reply. Yes, BLE and IOS device attachment both have their drawbacks. TechBasic (Basic programming language) skips any need to know IOS programming, I found it easier to use than my aged Casio 880P. I suggested BBB as it is fully opensource and has a small footprint but larger as compared to your mini tricorder version, off-course. I can not wait to see Mini version come to life. I would like to contribute in kind for any component or anything holding it back to come to reality.

Are you sure? [yes] / [no]

peter jansen wrote 5 months ago null point

Hi Norman,
Thanks for your kind note, and those are good questions. There are a few main thing that limit making this into an open source sensing device that connects with your phone (I've thought about this a bunch of times, as a potentially simpler route to development). One of the main issues is the BLE bandwidth is very limited, only around 1k/second -- way too slow for some of the sensor data. There are also mechanical issues trying to make one device that could mount to different phones (and not obscure the camera), software issues (I'm not an iOS or android programmer), and cost issues (ideally I'd like to make these available for kids, and it'd be unfortunate if the kids also were required to have a $500 phone to pair the sensors with).

I've investigated using different platforms -- the gumstix, the new raspberry pi compute module, and the beagle bone black, just to name a few. The major issues are size and power draw. With this mini version with a motherboard designed from the bottom up for size, portability, modularity, and power efficiency, I've designed it to be small enough to comfortably fit in pocket, and ideally have a lengthy battery life (more than just the hour or so you're likely to get with any of the modules I listed above).

Are you sure? [yes] / [no]

Noman wrote 5 months ago null point

I am a tricorder enthusiast since childhood. Dr. Jansen, you has come a long way [4 Gen before this 5th Gen device creation! Cool] and doing a great job. Brilliant. To me it is more inspiring and motivating project than any of others.

I am just curious, how about using an "IOS device with TechBasic" as front end while MC+Sensors board connected through BLE doing sensing job? TechBasic is good at graphics and visualization of data. Also how about using BeagleBone Black as main board with LCD Cap?

Are you sure? [yes] / [no]

Similar projects