# PEACH Sync'up call

Date: 13th of September 2016

present:
* Keoma
* Diego
* Thomas
* Ana

Starting at 3:25 PM

# NEWS

### Diego's visit to Paris

* added SHT31-D sensors
    * two version of the SW: one to test whether works, other for the field (connects to the network)
* Should we add a "height" field to SOL type SHT-31?
    * OK, interesting way to deferenciate the sensors

### Thomas and Keoma's visit to Berkeley

* Deployment of SOL in the Southern Sierra. Internet connection should arrive soon.
    * ETA? no estimate, "next couple of weeks"
    * http://www.snowhow.io/
* Deployment of SOL in the Botanical Garden
    * http://www.solsystem.io/
    * New errors: 
        * https://github.com/realms-team/solmanager/issues/81
        * https://github.com/realms-team/solmanager/issues/80
          Could it come from too much trafic with the Dust manager?
          NO, not on the mesh, possibly on the Python side

### Gridtics work on sensors

    * issues with cables and connections

    * building 4 sensors per mote: 

    * building shield cover for sensors

    * we have to document the sensors connection, hardware tests, 


### Carlos deployment in Junin

    * only one mote was programmed with Diegos version ???

    * installation of 20 shield covers 


### Websites (and super logos !)

    * SaveThePeaches

    * http://solsystem.io/

    * http://snowhow.io/

    * http://smartmarina.org/


# Sol improvements

    * better crash handling

    * solserver support for multiple sites

    * now using SNAPSHOTS to draw the map (solmanager also displayed)

    * added supervisord script that starts a "screen"


# NEXT STEPS

How can we work on the firmware ?

    * Diego has no motes - no budget for the time being

    * Keoma can work on it ? - Keoma will


What is the firmware current state ? Does it uses multi-MTtlv ? it uses multi

# TODO

    * The firmware should display the version name at startup

    * We can use MAJOR.MINOR.PATCH.BUILD format

    * Change the "netid"

    * Change the mote "join duty cycle"


# Bootstarping a node

    * verify on the lab:

    * reprogram the node using the interface board and a computer

    * ISP: follow the 5 steps

    * open a serial terminal (on particular serial port) (using putty or minicom)

    * we need to open the 3rd port (COM4 or /dev/ttyUSB2)

    * 9600 baudrate

    * this gives you access to the board CLI interface where you can run commands

    * first test: type enter to check it works. You should see a ">" sign.

    * when the mote is turned on, it prints the firmware name/version on the CLI interface

    * finally, we need to set up the network identifier (netid)

    > mset netid XXX

        * Power cycle the node

           > mget netid

        * Verify that the netid is correct


    * verify on the field:

    * switch on the mote next to the manager

    * on the CLI of the mode you should see: "joining" and then "operational"

    * after a couple of seconds:

    > minfo

    This will give you information about the mote

    * you can also double check at the manager CLI to see

    > sm

    * turn the mote off, go to the final position, turn on the mote again

    * by following the same process, verify again that the node is connected