Preload the BT Module

[eyuan-creare]

Define how you will be preloading the BT module...both the firmware level (V5?) and the BT settings and BT name... we're in BLE mode now, so this is really important

[eyuan-creare]

From @biomurph:

I am expecting the BT module to come pre-loaded with the Melody firmware. I have a question about it sent to my supplier. If you look at the top of the module, the sticker says the version number listed as 'MEL x.x.x'

On Digikey's website, the version in the product image is MEL 6.1.5, but that doesn't mean much. We had all MEL 5.x.x in the Rev D run When I get the confirmation of the firmware version from the factory, I will let you know and we can address it. I will be renaming the BT module as 'Tympan E nnnn'. Where 'nnnn' is the unique id from the module itself.

[chipaudette]

My perspective:

• Firmware: The firmware in the near term (ie, any ASA deliveries) must be V5.5, as described and saved in our Tympan BC127 repo.

• Configuration; After ensuring the correct firmware is present, the BLE comms with the Tympan app might be functional, but I'm not sure. It might be necessary to run some sort of updated version of the Tympan_Rename sketch. The specific code in this sketch needs to be nailed down. The primary concern is that we now leave the BC127 in its COMMAND mode, which is the opposite of what we used to do (we used to leave it in DATA mode). I do not have a straight-from-digikey BC127, so I cannot confirm if this sketch sets all the necessary BT configuration parameters to be compatible with the TympanRemote App.

• BT Name: We used to set the BT name as Tympan XXXX or whatever and everyone was happy. But, with the switch to BLE, the phone usually displays not the full bluetooth name but some shorter BLE-specific name. The BLE name is only seven characters, which is super-duper annoying. My RenameTympanBT sketch above has a certain convention for renaming the BT module. If someone feels strongly about a different convention, feel free to alter the sketch and commit it to the repo.

As documentation, below are the two BC127 settings that we need to set, from the V5 docs:

• NAME=value

  • Friendly Name: Last 6 symbols of the name XXXXXX are the last 6 symbols of the Bluetooth address. Example: BlueCreation-XXXXXX.

• NAME_SHORT=value

  • Short Name: used for Melody Smart Advertisements, maximum of 7 characters, where XXXXX are the last 5 hex digits of the Bluetooth address. Example: BCXXXXX `

[biomurph]

From what I understand, we will need to make the change to two names. One is the NAME which we already do. We'll call these ones Tympan E-XXXX as we have?

The other is NAME_SHORT for this, could we just use TYMXXXX that way we preserve the unique id?

[chipaudette]

@biomurph, I believe that the naming convention that you're suggesting is exactly what the latest rename sketch (as linked in my earlier comment) does. Similar thinking!