chirpnets/chirp-nets-firmware

Firmware for Chirp Nets Mesh Network Device

Chirp Nets Firmware

Firmware for Chirp Nets Mesh Network Device

Running on Device

Currently the Chirp Nets Firmware supports a single hardware configuration, using a nRF52 microcontroller with built in bluetooth transciever and a RFM69 915Mhz radio transciever

1. Setup Your nRF52 Board

This can be completed by following the instructions layed out by Adafruit on the nRF52 featherwing learning page

2. Download the LowPowerLibs RFM69 Library into your Ardiuno Folder

The library for the RFM69 radio board can be found on our fork Download the library and unzip it into the /Ardiuno/Libraries directory

3. Compile Firmware

The code for this configuration is contained within the nrf52-rfm69 folder.

To run this code on a device, open the combined.ino file in the Ardiuno IDE and add the .h and .cpp files in the directory to the sketch. You can now upload to the device and connect the Chirp Nets mobile application

If you have any issues or question feel free to open a github issue and we should respond promptly

chirp-nets-firmware's Issues

Remove getToAddress() from physical device code

as of #7 , getToAddress() is no longer required, but is still inside the physical device code

Add Node to Node Messaging (DMs)

Currently there are only group messages. DMs would be a nice add on.

ADD ENCRYPTION!!!!! NODE TO NODE

It is real spooky that we currently dont use encryption from node to node. Need an elegant implementation of something like AES-128 or AES-256.

Migrate the CPP to single location

Migrate the CPP to single location and have build scripts to pull all correct files together pre compile.

Add Checksum Functionality in BLE

We had this functionality at one point. Would be nice to reimplement it with the current state of the repo.

Nice To Have: Make Simulator Dynamic

As of #7, Simulator is capable of simulating 4 devices to test the routing. However, for more robust testing the simulator may be changed to take a variable number of devices as command link arguments.

The code that operates the devices would also need to be wrapped in a loop that would iterate over each device.