Note that this is just a pre soft-launch of the project and more info will be coming a bit later. We’re already designing the electronics part but more specific info about it cannot be shared yet because in-depth nRF9160 specs are still under NDA.
Note that RuuviTracker will not replace RuuviTag but will complement it. RuuviTracker will be also capable to listen nearby RuuviTags and act as a cellular gateway.
Let’s discuss. Any comments, ideas, suggestions?
Yah, the Grove sensor connector is an attractive standard. Re external power - a common port (micro USB, USB-C) would be great for powering it from both wall and automotive sources, though I bet y’all have that covered.
Will we be able to swap SIM cards to the provider of our choice / need?
Hm, and what programming environments will be supported?
I’m looking forward to a cellular gateway with Ruuvi quality behind it.
What kind of common port do you mean @mikewhitten ?
Eventually, we’d like to have eSIM and an integrated global data plan but global Cat-M and NB-IoT plans are still not widely available. Also because NB-IoT roaming functionality is not yet fully standardised, user changeable SIM card is the best way to start with.
Both of the main chips are from Nordic Semi, so similar programming tools are supported than seen on RuuviTag. @otso will dive into the software side. Maybe Zephyr would be one option?
Re the common port, @lauri, I was thinking of the external power port. Micro USB is perhaps the most common. USB-C is up and coming; don’t know if it’s overkill. I’m thinking USB because there are adapters to get USB power from just about everywhere; most flexible.
Yay on the user changeable sim.
Re software… for utter maker friendliness Arduino comes to mind. I see Sandeep Mistry has a port to Nordic going; don’t know if that’d apply. MicroPython? Amazon’s FreeRTOS? Truth be told I’m out of my depth here; just coming at it from a “what’s popular in the maker world” POV. For hardcore deployments I assume one would want to go native Nordic.
Ah yeah, my bad. USB is definitely the way to go. I thought you were talking about a combined port. I otherways would prefer USB-C but it may not fit the board and it’s more complex and expensive part compared to the micro.
I just went through RuuviTracker project history and realised there has been 5 different (!) PCB designs. And now we’re working with the sixth one I need to write a comprehensive blog post about the project and its history…
A historical video clip (2012) of the first RuuviTracker revision:
Audio recording or Desibelmeter would propally drop to the “interesting prototyping” feature bucket and not to the features integrated right on board.
A gyroscope is definitely something I’ll consider to add. Today, those don’t even consume enormous amounts of power
@mikko_petajaniemi This is something we’ve considered but it’s probably not something many would need. But a buzzer or piezo element would be. Does someone has (SMD) sound elements with tiny footprints to suggest?
STMicroelectronics has interesting Time-of-Flight sensors we’re aiming to support on RuuviTracker. Having a ToF sensor onboard would enable many fill-level uses. For example intelligent bins: RuuviTracker could inform when a bin is full and should be emptied.
An expansion port will be included, yeah. But even the device will be open-source and can be used to build many different things, our aim is to keep different product variants as minimal as possible and but have many features onboard by default. Even it would mean a few euros higher price tag. Then for those who would like to purchase larger quantities and price optimisation will be needed, unnecessary components can be left unassembled.
I need to write a comprehensive blog post about the project and its history…
