Close
0%
0%

Science Tricorder by Olympus Heavy Industries

A multi-mode scanner and data logger based on Adafruit Feather & Arduino

Similar projects worth following
This is a project I've been tinkering with for a couple years now and it actually started out as a non-functional prop. Modeled after the Tricorder devices seen in Star Trek and heavily inspired by similar projects found online. The ultimate goal is to create a functioning handheld sensor platform that can analyze, store and transmit all sensor data collected by the unit.

It’s been a hell of a journey learning how to build this thing, all started when I saw prop Tricorders at Star Trek cons in the mid ‘90s as a little kid. I’d never believe that I’d have one like this if I told past me of it…

I’ll post more as things happen

Planned features and revisions:

  • V6 (in progress) - 3d-printed chassis with a new mainboard and sensor array board assy to clean everything up and make it simpler to work on. I also need to design labelling for the door control panel and a unit label for the back of the chassis.
  • V7 - Create a new board set (mainboard, sensor assembly) and have the PCBs custom fabricated. This stage will still have the other breakout boards attach onto the mainboard and is primarilly to remove much of the wiring that needs to be soldered in place to make a unit functional.
  • V8 - Create another new board set that also removes many of the breakout boards by having the components soldered onto my custom PBCs. A few components like the Feather controller, TFT and RadiationWatch will still be breakouts since I still want a bit of flexibility (or these are too difficult to replicate).

All 3d-print files and PCB designs will be attached to the project page here.

Current scan data points:

  • Atmospheric:    Ambient temperature (averaged across 3 sensors), relative humidity, barometric pressure, Target Temp, GRIDeye temp (8x8 grid of IR thermal detectors)
  • Electromagnetic:    UV Index, IR intensity, RGB Color, Visible light intensity in Lux, UV intensity
  • Radiation:    Gamma/Xray detection
  • Gasses:       Carbon monoxide, Nitrogen dioxide, Ethanol, Hydrogen, Ammonia, Methane, Propane, Isobutane
  • Mechanical:    3-axis Accelerometer, 3-axis Digital Gyroscope, 3-axis Hall Effect Magnetometer

Currently, the Tricorder Version 6 is made up of the following:

This is now the 6th iteration of the Tricorder (the first was a prop build, not functioning), running v.o-10 code.

OHI Science Tricorder V6 Chassis - Release ver.7z

The current version of the chassis modeling for 3d printing. This one's also updated with the correct information about the hinges.

7-Zip - 5.24 MB - 02/16/2020 at 20:55

Download

OHI Science Tricorder V6 Chassis - Rev5 NOT FINAL.7z.7z

Rough-draft for the V6 Tricorder 3d-printable chassis, a work-in-progress

7-Zip - 1.96 MB - 08/24/2019 at 04:57

Download

OHI Science Tricorder V6 Chassis - Rev3 NOT FINAL.7z

Rough-draft for the V6 Tricorder 3d-printable chassis, a work-in-progress

7-Zip - 2.55 MB - 08/08/2019 at 02:31

Download

Tricorder Legacy Code (everything up to 4o-v9.rar

This is all of the code that I've written for the various iterations of the Tricorder over the past 2 years. Covers up to 4Ov9

RAR Archive - 79.19 kB - 06/09/2018 at 20:41

Download

OHITricorder-4O.10.7z

Updated 2018/06/04. Added functionality to Radiation scan mode and working further on UI changes.

7-Zip - 14.25 kB - 06/04/2018 at 22:50

Download

View all 7 files

  • 1 × Adafruit Feather M0 Adalogger (https://www.adafruit.com/product/2796 ) Primary microcontroller for the unit
  • 1 × Adafruit CAP1188 (https://www.adafruit.com/product/1602) Capacitive Touch controller
  • 1 × Adafruit 2.4" TFT LCD (https://www.adafruit.com/product/2478) Display
  • 1 × Adafruit DS3231 (https://www.adafruit.com/product/3013) Real time clock with battery backup
  • 1 × Adafruit TCA9548A (https://www.adafruit.com/product/2717) i2c Multiplexer

View all 16 components

  • Progress! Even if it's a little bit

    Queadlunn6 days ago 0 comments


    Started to wire the mainboard together, even if slowly. I'm currently working on getting all of the power stuff connected up first, then I'll do the data connections. I plan on getting the mainboard working first, then working on the sensor array assembly. Slow going but it's progress!

    Thanks to Mit Balkens (https://hackaday.io/MitBalkens) for pointing out the correct hinges, I've updated the Thingiverse page and the downloadable model pack here with the correct information.

  • My current to-do list for V6

    Queadlunn11/07/2019 at 16:36 0 comments

    Bit of a lag between updates, sorry. Going to be a bit slow, probably through the end of the year right now.

    My current to-do list:

    • Finish wiring new mainboard
    • Integrate Radiation Watch board
    • Build code for new MICS-6814 gas sensor and it's power regulator (get base 3 gas types working for now, will expand later)
    • Figure out flex cable between main body and door
    • Design labelling for the door panel touchpads and a unit label

  • Good enough to ship!

    Queadlunn10/01/2019 at 04:47 0 comments

    I finally have the 3d-printable design good enough to throw onto thingiverse and here and consider it 'good enough' to fully release.


    (Here's the thingiverse link: https://www.thingiverse.com/thing:3796426 )

    I've got the files zipped up and uploaded as 'OHI Science Tricorder V6 Chassis - Release ver.7z'

    It's pretty easy to assemble, you just need a small handful of hardware besides the internal electronics. Specific parts and notes are in the Readme file.

  • Now in 3d, the Return!

    Queadlunn08/24/2019 at 05:14 0 comments

    Gotten a lot further along with the 3d shell, the primary parts are at least mostly done and I'm working on test-printing and fine-tuning stuff now.


    The big things left are getting the interface panels for the body and door further along. The main body panel needs cutouts for the TFT and controls, the door panel needs holes for the capacitive wire.


    The mainboard simply slides into the body and the body's under part (violet-colored in the 3d model image) fixes it in place. The desing's working pretty well so far but it does need a lot of tweaking for ease of use and ease of printing.

    Uploaded the current rev of the models as

    OHI Science Tricorder V6 Chassis - Rev5 NOT FINAL.7z.7z

  • And for the rough-draft

    Queadlunn08/08/2019 at 02:35 0 comments


    Added (really) rough-draft files for the V6 3d-printable chassis:
    "OHI Science Tricorder V6 Chassis - Rev3 NOT FINAL.7z"

  • Now in 3d!

    Queadlunn08/07/2019 at 06:15 0 comments

    After quite a while I've started to work on the next version of the Tricorder! I've had the hardware partially built for a while now but I'm starting to get the casing worked out in 3d so I (and anyone that wants to) can print it. It's going to take a lot of work since it's my first 3d design like this. Once I test it out and can make some changes I'll upload an STL and the original 123dx files.

  • More Progress, building Version 6

    Queadlunn01/15/2019 at 05:22 0 comments

    After a long lag I'm working on the hardware for the next version of the Tricorder!

    It's not a huge change from the Version 5 to Version 6, more of cleaning up the current design that the Version 5 ended up with. The soldering work is about half done right now, I still need to finish up the sensor array, additional sensors and the door assembly.

    The current Version 5 will have some of it's sensors moved to the V.6 (the GridEYE, 9-DOF/ATM, UV sensors) and everything else will be the same sensors in smaller breakout boards.

    Changes with the Version 6:

    • Slightly re-designed, a bit wider and shorter to allow a touch more room
    • Different sensors for:
    •      Gas sensing, got the newer version of the sensor board
    •      LUX, IR sensors replaced with same IC but smaller breakout board
    • This Feather M0 has a Packet Radio for if I make any hand scanners in the future, still unsure of that

    Ultimately I want to keep the older version working, likely remaking the casing so I can fit bulkier sensors into it (like the shape of the TNG Medical Tricorder). Since both will be using the same Feather M0 boards I also want to write one firmware that will work on both units if possible.

    Right now I'm focusing on the hardware and will resume on the code afterwords.

  • Code updated to v10, a bit of work done...

    Queadlunn06/04/2018 at 22:58 0 comments

    Small update- Got a bit of work done on the code today, expanded the Radiation scan mode's functionality. Now it shows avg pulses/second, avg pulse strength (in uSv/h) along with the last pulse detected.

    Part of this was making a timer based off of the RTC to count how long the scan mode has been on, this could be useful in other modes later on as well.

    I also got a bit further on in building a framework to allow a more interactive UI. The ultimate goal is to have the ALT button switch the button pad's functionality to that of a D-PAD along with Confirm, Cancel and Back. This'll give me a lot more to work with, like highlighting scan elements or using a menu structure. A lot of work to do on this however...


    The updated code has been attached to the project, v10.

  • Bringing it up-to-speed

    Queadlunn04/13/2018 at 02:17 0 comments

    In the past year the external appearance of the unit hasn’t changed much, it’s all been internal hardware and code changes. As the photos show, the mainboard is getting to be a rat’s-nest of wiring with all of the changes and adaptation that I’ve done. The code, actually, is a lot cleaner than when I was at the same point last year. It’s able to do a fair bit more but isn’t using much more of the Arduino’s (Adafruit Feather M0 Adalogger) memory (still hovering around 30% at this point).

    The sensors in the unit haven’t changed a huge deal, I’ve gotten them to work a bit better though and have even been able to adapt the libraries for the Gas sensor to work with the M0 controller (more brute-force really but it works). The total sensor list is posted below.

    At the moment I’ve gotten 2 replacement sensor part. One to replace the Grideye sensor so it’s smaller (I can’t do surface-mount soldering yet) and one to replace both the atmospheric sensor board and the 9-depth-of-field sensor board that captures movement. The second will combine both the ATM and 9-DOF into one very small package, saving on the limited internal space within the Tricorder.

    There are a few things I want to add into the unit so far: GPS (for both location data and accurate clock updates), Haptics (feedback from button presses, sensor alarms), and finding a replacement and higher quality display are my biggest. The largest hurtle right now is getting the code solid, using the display to give clear and accurate readouts of the sensor data, and eventually rebuilding the mainboard and chassis. The chassis’ ABS/aluminum/polycarbonate construction is rock-solid (it’s been hanging out in my camera bag for the last year) but I want to clean it up since the off-square lines in the current one bother me a bit.

    My big inspiration for the project has been the Open Source Science Tricorder by Peter Jansen. It’s an incredible project and I have major respect to the creator.

View all 9 project logs

Enjoy this project?

Share

Discussions

Antonio Cesar de Oliveira wrote 6 days ago point

When analyzing your photos I realized that at some point you tried to use Grove's Mutichannel_Gas. It also has the MIC 6814 sensor, but it operates only through I2C.
I also noticed from your code that at some point you tried to use the LSM303 magnetometer.
Any reason for giving up those two options?

Thanks,

Cesar

  Are you sure? yes | no

Queadlunn wrote 6 days ago point

The LSM303 was probably the Adafruit breakout that I was using earlier in the project. The component works fine but I dropped it for components that combined multiple functions to save on space, like now I'm using a MPU9250 breakout that's less than a third of the size of the LSM303 but covers a lot more of the functionality.

Somewhat likewise, the Mutichannel Gas sensor works well and has it's own logic to interpret the MIC6814 and output as I2C but it's a large board that has to be modified to work with the unit and the code is taken apart and mostly works. I'm changing to a MIC6814 breakout and a small power booster board so I can build my own code for the sensor and lower the unit's price. Those Seeedstudio sensors are pretty spendy and quite large.

  Are you sure? yes | no

Antonio Cesar de Oliveira wrote 02/11/2020 at 01:45 point

There are some numbers that you add with mx, my and mz. How did you get that numbers?

You can see a photo in:

https://ibb.co/D77QtmG

  Are you sure? yes | no

Queadlunn wrote 02/11/2020 at 02:19 point

That's looking great!

Those values were in the originating library I think. I don't remember adding that in, it's probably from the example code I used.

  Are you sure? yes | no

Antonio Cesar de Oliveira wrote 02/10/2020 at 22:05 point

I managed to do the LCD and some sensors to work. The design of the screens was very well elaborated. I have some difficulty understanding the magnetic field values. What the symbols 

<-> and ˆv mean. How did you get the MPU9250 magnetic sensor calibration. Do you have any reference on that?

Thanks,

Cesar

  Are you sure? yes | no

Queadlunn wrote 02/10/2020 at 22:28 point

The "<->" symbol is just to represent magnetic force along the Y-axis of the device, likewise the ^/V is for force along the X-axis. It's not a great way of representing it, that's one of the things I need to change when I get a chance to work on the UI again. The readings themselves are expressed in teslas (symbol: T).

As to calibration, I think the library I'm using auto-calibrates on startup but I'm not sure.

Glad to hear that it's starting to work for you though! I'm honestly thrilled to see people building their own Tricorders! If you take photos please let me see how it turns out!

  Are you sure? yes | no

Mit Balkens wrote 02/07/2020 at 23:37 point

Please note that the hinges you have listed are actually not the correct hinges. As far as I can tell you are not using the 1"L x 7/8"W Brass hinges you listed, but rather the 3/4" x 1" Butt Hinge, Black variation of the hinges listed on this page: https://www.rockler.com/butt-hinges-for-small-boxes-3-4quot-height

  Are you sure? yes | no

Queadlunn wrote 02/10/2020 at 22:30 point

That does look accurate. I'll verify the measurements and update the notes.

Thanks for letting me know!

  Are you sure? yes | no

Antonio Cesar de Oliveira wrote 02/05/2020 at 18:54 point

At first, thanks again...

I am not very familiar with the components you used in your project. I'm using some Arduino logic but some doubts still persist. I'm trying to make it work with just a few components but without much success. I am using Feather MO with DS card, CAP1188, TCA9549 and the TCS34725, SI1145 and TSL2561 sensors. Everything looks ok, but I can't get anything to appear on the TFT display. It is possible to access the serial reading of each function but apparently the sensors do not provide data, that is, they always provide the same numbers.

I wonder if there is a dependency on some other component for the set to work.
In your notes you say that you use the I2C multiplex for the BME280, RTC and Grid Eye sensors, but in your code it seems that input 2 of the multiplex works for all sensors, except GriEye which is connected to input 2. I also couldn't understand right if the ultimate goal is to work with two UV sensors, SI1145 and VEML6070 or just one of them.

I would be very grateful for any information that could help me with this start.

  Are you sure? yes | no

Queadlunn wrote 02/05/2020 at 19:16 point

Think of the i2c interface as a tree, with the M0 as the trunk with the multiplexer and all other sensors not the 3 noted are on the same level up with those 3 downstream from the multiplexer.

Aside from the BME, RTC and GridEYE; all of the other sensors have unique i2c addresses so they don't need to be downstream from the multiplexer. That's the reason for the multiplexer, those 3 components are all on 0x68 (I think), so when the code needs to look at one of those parts it'll change the multiplexer to that part and take a reading.

For the TFT, doublecheck the pins used and the code/libraries in this article, I did have to change a few things to get it all to work.

  Are you sure? yes | no

Antonio Cesar de Oliveira wrote 02/01/2020 at 21:36 point

First of all I want to thank you for your kindness for answering the questions. Sorry if I am disturbing you ...

Now, even after seeing and reviewing the photos several times and reading their text, there are still some doubts. If you can clarify them I would appreciate it very much.
1- You inserted the IC TCA9548A I2C Multiplexer in the scketch, but I don't see it in any of the photos. Why do you need it? Is there an address conflict between the sensors? How many and which sensors occupy the same SDA and SCL bus?
2- Do you have some diagram of the connections between Feathr MO and the LCD display.
Even if you don't fully remember, any information about it will be useful and will save me a lot of time. I would really like to build this instrument and eventually insert other components.

Thank you,

Cesar

  Are you sure? yes | no

Queadlunn wrote 02/02/2020 at 00:00 point

No problems!


The i2c Multiplexer is in place to switch between the GRIDeye sensor, RTC and the BME280. In the photos for the Type-5, the multiplexer is near the front of the connection board, the RTC breakout is kind of laying on top of it. In the Type-6, it's in the gap between the Feather board and the connection board.

For the TFT, this is the pinout from the Feather for the Type-5:

Pin0- RX (nc)
Pin1- TX (nc)
Pin2- n/a (no external pin)
Pin3- n/a (no external pin)
Pin4- SD card CS (no external pin)
Pin5- Touch Interrupt
Pin6- TFT_CS
Pin7- SD card CD (no external pin)
Pin8- SD Red LED (no external pin)
Pin9-

Pin10-
Pin11-
Pin12-
Pin13- Feather red LED (not used)
Pin14- TFT_DC (as A0)
Pin15- Mainboard green LED Heartbeat (as A1)
Pin16- DATA_PIN for Neopixel
Pin17-
Pin18- Speaker pin (as A4)
Pin19- RGB sensor LED control
Pin20- SDA
Pin21- SCL
Pin22- MISO (TFT, SD)
Pin23- MOSI (TFT, SD)
Pin24- SCK (TFT, SD)


  Are you sure? yes | no

Antonio Cesar de Oliveira wrote 01/29/2020 at 23:19 point

I am an aficionado of building Tricorders. I have two personal projects that I recently built. Take a look at ;

https://nerdsdevulcano.blogspot.com

Your project caught my attention due to the degree of miniaturization. I will try to build it. Do you have any special advice ...?

Thanks,

Cesar

  Are you sure? yes | no

Queadlunn wrote 01/29/2020 at 23:23 point

As you develop the device, if you're working with many breakout boards do yourself a favor and try every layout for the mainboard & breakout boards as you can. It can save a lot of space. Finding parts that combine ICs can also save space (ie, combining multiple sensors onto one breakout).

Also, don't be afraid to drop functions related to hardware that will make the device bigger than you want. I haven't added GPS to my Tricorder yet since the antennas are relatively bulky.

Good luck with your build!

  Are you sure? yes | no

Antonio Cesar de Oliveira wrote 01/30/2020 at 12:15 point

Thank you for responding promptly. 

Your project offers a very high potential for miniaturization. You worked very well with the layout and the distribution of the components. I will try to work in your concept. I have a question about the FastLED library. The library suggested in your files is FastLED 3.1.0. However, it is generating some conflicts. In addition, when I include the zipped file, several other libraries are included, not just FastLED. On the other hand, when I try to use FastLED version 3.2.0 the conflict is minimized, but as in the first case, several other libraries are included.
This is strange because when I look at your original code it contains only FastLED. Is there anything I should know about this ...?   or I may be doing some thing wrong ...

Another issue is that the sketch uses 33% of the storage space. I don't know anything about Feather MO. What exactly does 33% mean? Does it mean that there are 67% of space available to do anything? or limited? Can the value of 33% go up when using the functions when the instrument is operational?

Thank you in advance for your collaboration ...

Cesar

  Are you sure? yes | no

Queadlunn wrote 01/30/2020 at 16:09 point

Couldn't find the 'reply' to your second comment so I hope you see this.

The library pack needs to be brought up to date. At this point I haven't really done any code work on the Tricorder in about a year so a lot can be updated or cleaned up. I remember there being some conflict with the Adafruit NeoPixel library at some point and that was the reason I switched to using the FastLED, though the actual usage for the LEDs in the device is so minimal that it could be changed out again fairly simply I think. As to FastLED's version compatabillity I can't say, it's been so long since I worked on this project's code...

For the ~33% of the memory storage space, that means the code is only using a third of the M0 microcontroller's memory, there's still a lot of space (relative to the current code) for more code to be stored for the programming.

  Are you sure? yes | no

josh034 wrote 10/30/2019 at 02:31 point

I was wondering if there are any other components needed besides the 16 you have specifically listed? I'm going to start gathering the parts a bit at a time and I don't want to miss anything. 

  Are you sure? yes | no

Queadlunn wrote 10/31/2019 at 23:20 point

The parts list in the article, with the addition of the parts list from the 3d-print readme should be 90% of the stuff needed aside from wiring and miscellaneous headers and such I think.

  Are you sure? yes | no

josh034 wrote 10/04/2019 at 03:41 point

I like the new case. It's a very neat, clean design. =)

  Are you sure? yes | no

josh034 wrote 10/03/2019 at 02:51 point

 Is the magnetic reed switch there to be an option for the power switch used in the earlier designs?

  Are you sure? yes | no

Queadlunn wrote 10/03/2019 at 04:26 point

In the v5 design there's a main power switch and a magnetic reed switch. V6 will have the same thing when I get it's new electronics soldered together.

  Are you sure? yes | no

josh034 wrote 09/16/2019 at 20:54 point

Thank you for responding so quickly. Again, sorry for so many questions. But the assembly guide would answer these. I should have waited for that. You have been very gracious in your replies. I will ask this, as it won't be in the guide. Do you plan on selling these in kit form, or anything like that? Now I will have patience and await the assembly guide. 🙂

  Are you sure? yes | no

Queadlunn wrote 09/17/2019 at 06:20 point

Not at this time. Maybe in the future, when I have my own PCBs designed but even then they'll take a good amount of soldering work to get operational.

  Are you sure? yes | no

josh034 wrote 09/16/2019 at 20:33 point

I have a three questions, if you don't mind. In the picture of an up close view of the screen with the system in ATM Mode, what is Target A and D? Is there a B and C somewhere? The other question is, is there anything under the keyboard, other that wires?  I couldn't decide, from looking at all the pictures, but I am guessing not. The last is about the carbon fiber in the 3d printing. What are the qualities of that particular material? Is it wear resistant, holds up to impact, etc? Sorry to have so many questions. But I really want one of these. And I'm trying to understand it all, but I have zero skills in electronics.

  Are you sure? yes | no

Queadlunn wrote 09/16/2019 at 20:44 point

ATM Target sensor A is an Average of the center 4 pixels of the GridEye sensor (an 8x8 thermal IR sensor), sensor D is the MLX90614, a Direct measurement.

Under the key panel is the Adafruit CAP1188, the wiring going from the Door assy to the main body is 2-wire 12c, an interrupt for the capacitive controller, +v and Gnd.

Carbon fiber PLA is, I'm assuming, the strongest material that my printer can work with in its current state. If I could print in ABS, Polycarbonate or other more resilient materials I probably would have gone with those.

I'll be doing another iterative chassis print and I think it's close to complete for this version. At that time I'll probobly do a write-up/guide covering assembly. The chassis is designed to be easy to assemble and doesn't require specific boards aside from the mainboard being a specific size and the capacitive breakout PCB (this could be changed too, with a bit of work). It'll likely require soldering work no matter what but the actual internals could be simplified a fair amount, at that point it'd just take minor soldering and changing the code.

  Are you sure? yes | no

josh034 wrote 09/13/2019 at 17:02 point

So it won't be that heavy. That would be easy to skip into a backpack or pocket if needed.

If I remember, you said somewhere you were going to finalize the printed material in carbon fiber?

  Are you sure? yes | no

Queadlunn wrote 09/13/2019 at 17:26 point

I'm going to print the final chassis assembly for the v6 unit with carbon fiber PETG or PLA, something like this:

https://www.matterhackers.com/store/l/3dxtech-carbonx-petg-3mm/sk/MKJ2V47R

I haven't used carbon fiber-filled print filament before but it should be fairly easy to tune my printer to work with it, I've already got an upgraded hotend and hardened nozzle installed.

  Are you sure? yes | no

josh034 wrote 09/12/2019 at 15:48 point

Understood. I knew from looking at the pictures space is at a premium. And speaking for myself. I like the current clam shell style. I would use it as an EDC device, so the clan she'll would be protective without an extra case. That does bring up a question. What is the weight of the two models you have: the green metal one vs the 3D printed one?

  Are you sure? yes | no

Queadlunn wrote 09/13/2019 at 05:49 point

The v5 Aluminum and ABS chassis one is 272g.

The v6 PLA-printed chassis is 190g but still missing some internals. This will be printed with different filament for the final build so maybe around 220g?

  Are you sure? yes | no

josh034 wrote 09/12/2019 at 02:06 point

Would you need to make major changes to  the design to accommodate the other two? And would you need switch to a D-pad style of controller? I ask that because I'm not sure where you would add another button to the current design.

  Are you sure? yes | no

Queadlunn wrote 09/12/2019 at 06:22 point

Physical space is always an issue in this design for the actual sensors. For the controls I do plan on moving away from the simple press-of-a-button mode switching to some semblance of a button-controlled UI but that's well down the line right now.

  Are you sure? yes | no

josh034 wrote 09/11/2019 at 17:38 point

Would it be possible to use one of the sensors for lightening detection?

  Are you sure? yes | no

Queadlunn wrote 09/11/2019 at 17:53 point

It's one that's been on the list of 'possible additions' I've had for a while now:

Lightning Flex Module (RF) - https://www.tindie.com/products/Fyberlabs/lightning-flex-module/
Magnetic Imaging Tile - 8x8 - https://www.sparkfun.com/products/14652
Adafruit Ultimate GPS Breakout - https://www.adafruit.com/product/746
Adafruit SGP30 Air Quality Sensor - https://www.adafruit.com/product/3709

The magnetic imaging tile is likely too much for this project in processing needs and physical size, and the GPS would likely be too large. The other two might work out later on though.

  Are you sure? yes | no

josh034 wrote 08/29/2019 at 14:57 point

Thank you for your answers. Sorry for all the questions. 

  Are you sure? yes | no

Queadlunn wrote 08/29/2019 at 18:46 point

No worries, I'm glad to answer questions about the project!

  Are you sure? yes | no

josh034 wrote 08/29/2019 at 14:05 point

I like your design.  I am anxious to see your design come to completion. 

Is it possible to upgrade the sensors and software without starting over from the square one?

  Are you sure? yes | no

Queadlunn wrote 08/29/2019 at 14:48 point

Upgrading should be fairly easy once a unit is completed. Since I'm currently designing the electronics around pre-made breakout boards for most components all that's needed to change/upgrade a sensor is to wire it in and update the Arduino code with what the new components need to do. Upgrading the Adafruit Feather also should be pretty easy as long as the microcontroller itself is the same, otherwise the pins would need to be updated and code changed to work properly. Some core components like the i2c multiplexer and clock will (eventually) be soldered to the mainboard whenever I can get my own PCBs designed.

  Are you sure? yes | no

josh034 wrote 08/29/2019 at 14:00 point

Ok. It sounds like the 3d prints will be pretty good too. Like I said, for myself, this would be an EDC device. So durability would be important. But it sounds like that won't be too bad. And if the circuit board stayed in place from an approximate 1 meter drop, then that is half the battle.

  Are you sure? yes | no

josh034 wrote 08/29/2019 at 00:39 point

I was thinking of this as an EDC item. So water resistance, or lack thereof, would be important. Another question is durability? Have you used one of your builds enough to know if that would be an issue?

  Are you sure? yes | no

Queadlunn wrote 08/29/2019 at 04:02 point

The older aluminum/abs casing is pretty sturdy, it's been carried around for a couple years in the bottom of bags and dropped a meter or so a number of times and seems pretty resilient.

The 3d-printed casing I'm working on I don't really know yet. I'm doing my best to design it for strength (and will print it with carbon fiber+PLA for the final version) but can't test it yet.

  Are you sure? yes | no

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates