Updated from ArduinoJson 5 to latest.

[JaeminBBQ]

Description

Updating the ArduinoJson library to the latest version and added free_memory() to display during bootup.

Requirements

• ArduinoJson version 6

Issues Referenced

• Fixes #31

Documentation update

Documentation should be changed under: Keeping EmotiBit up-to date => Update firmware using Arduino IDE => Library List where "ArduinoJson (version 5.13.5, not v6.x.x)" should be replaced with "ArduinoJson" since it is the latest version.

PR to documentation change.

• https://github.com/EmotiBit/EmotiBit_Docs/pull/113

Notes for Reviewer

• https://github.com/EmotiBit/EmotiBit_FeatherWing/pull/39 (Existing PR on upgrade) The ArduinoJson Library must be updated to 6, the changes will not work with version 5. The free memory function was added to the function where emotibit data is displayed. This was only added in the case a featherwing m0 is used.

Testing

Results

Test to make sure config.txt file is still being parsed as expected.	Parse Results	Comments
	The config.txt is parsed correctly but missing values are stored as a string "null" rather than an actual null value. This get around this, an if statement is used to set "null" strings to "".

Test to make sure the info.json file created when a recording is started is the same as the one created with the currect release.

Info.json diff results	Comments
	The only difference is in char 263, line 1
	The difference is the firmware version
	Previous firmware version

The library update reduces the memory used by the EmotiBit which was checked using the free memory function as seen here.

Memory Before	Memory After

Feature Tests

Add the test heading from "EmotiBit Feature Test Protocol" here.

Steps to test

Import the steps from the EmotiBit Feature Test Protocol for quick access for the reviewer

Shared files

• Firmware binary: 1.8.1.fix-JsonLibUpdate.1.zip

• Other files.

Checklist to allow merge

• [x] All dependent repositories used were on branch master
• Software
  • [ ] Get approval from the reviewer
  • [ ] Passed testing on Windows
  • [ ] Passed testing on macOS (for major changes/GUI changes/ PRs adding files distributed with the EmotiBit software)
  • [ ] Passed testing on linux (ubuntu) (for major changes/GUI changes/ PRs adding files distributed with the EmotiBit software)
  • [ ] Update software bundle version in ofxEmotiBitVersion.h
• Firmware
  • [x] Set testingMode to TestingMode::NONE
  • [x] Set const bool DIGITAL_WRITE_DEBUG = false (if set true while testing)
  • [x] Update version in EmotiBit.h
  • [x] Update library.properties to the correct version (should match EmotiBit.h)
• [ ] doxygen style comments included for new code snippets
• [x] Required documentation updated

[nitin710]

Review 01

Pretty straight forward. Please see my comments below (some process changes, some code changes and comments on testing results).

• I see that the version was not bumped in this FW branch. When making a fix/improvement, we usually change the firmware by adding a identifier. The rules to create this identifier are listed in the CFL standard github workflow. Currently, if someone installs the linked firmware binary, to them, there will be no difference between this "still in dev firmware" to the one linked in the latest release because they are both v1.8.1. This can be quite dangerous since we don't yet have complete traceability of the dependencies.
  • This may have been a miss-communication since the doc (pointed above) does not have an explicit example.
  • The usual flow is to change the FW version which can be found here https://github.com/EmotiBit/EmotiBit_FeatherWing/blob/9705ef7c1d689be9ed483571017b0c0c1bfa07ad/EmotiBit.h#L53
  • Can you make this change and also update the linked binaries? Let make sure we don't spread different firmwares with same version!
• I think there should be 2 more tests to be run
  • Test to make sure cofig.txt file is still being parsed as expected. (I think this is implicit since you tested streaming, but lets make it explicit here)
  • Test to make sure the info.json file created when a recording is started is the same as the one created with the currect release.
  • I think the steps are
    • capture recording with current latest release (v1.8.1)
    • capture recording with this fw patch
    • compare the info.json files
    • You may consider using a diff tool like kdiff3 to make your life easier in the comparison.
  • We are expecting everything to be the same except the firmware version in the files.
  • Please update the PR with the results.
• Can you also make the required documentation changes in the docs repo? I think the steps are
  • Create a branch (in EmotiBit_docs), make the changes
  • Create a PR.
  • Link that PR here.
  • RE the change, lets state it explicitly which version of ArduinoJSON we are using. This will prevent any support issues if ArduinoJSON makes a breaking change.
• https://github.com/EmotiBit/EmotiBit_FeatherWing/pull/278#discussion_r1230900333

Some notes about PR organization:

• Just a semantic thing, but Added free_memory() to display during bootup is currently floating in the PR description. Probably nesting it under an appropriate heading is better. Remember, the description is the first thing a reviewer (or anyone else) will read when coming to this PR. making it super clear what the PR does will help avoid confusion.
• In the Results section, its better to have a table or a itemized list to highlight the tests run. Lets conform to this requirement and structure the results section accordingly.
  • Also, move the memory test details into the testing results section.
• The Feature Tests section should hold the test headings to any tests linked from the EmotiBit Feature test protocol doc. If you did not add any feature tests, then it is OK to leave that section blank.
• If you want the reviewer to test something, Adding some instructions in the "steps to test" section can be helpful.

I have not personally run the code yet. I will wait to test it after you make the changes (at least till you bump the firmware version).

Also, please feel free to add/update examples to any docs you may have referenced to create this PR. For example, adding an example about how to change the firmware version in the CFL standard github workflow will be helpful!

Review complete. @JaeminBBQ

[JaeminBBQ]

• [x] Can you make this change and also update the linked binaries? Let make sure we don't spread different firmwares with same version!
• [x] Test to make sure cofig.txt file is still being parsed as expected. (I think this is implicit since you tested streaming, but lets make it explicit here)
• [x] Test to make sure the info.json file created when a recording is started is the same as the one created with the currect release.
• [x] Can you also make the required documentation changes in the docs repo? I think the steps are
• [x] https://github.com/EmotiBit/EmotiBit_FeatherWing/pull/278#discussion_r1230900333

Review Checklist

• [x] Just a semantic thing, but Added free_memory() to display during bootup is currently floating in the PR description. Probably nesting it under an appropriate heading is better. Remember, the description is the first thing a reviewer (or anyone else) will read when coming to this PR. making it super clear what the PR does will help avoid confusion.
• [x] In the Results section, its better to have a table or a itemized list to highlight the tests run. Lets conform to this requirement and structure the results section accordingly.
• [x] Also, move the memory test details into the testing results section.

[nitin710]

Changed implementation for handling non-existent field in config file. Link to comment: https://github.com/EmotiBit/EmotiBit_FeatherWing/pull/278/files#r1232736934

Tests run

1. ✔️ incomplete/wrong config file handling (missing SSID field changed to "") For a config file with contents

   {
   "WifiCredentials": [
   {
     "ssid": "brainwaves2.4",
     "password": "brainwaves"
   },
   {
     "password": "emotibitRocks" // notice missing SSID field
   },
   {
     "ssid": "redacted",
     "password": "redacted"
   }
   ]
   }

   

2. ✔️ Differences between info.json files

   • raw info files.zip
   • FW version was changed
   • 
   • Filename was changed
   • 
   • floating point value of the EDA constants seem to be different, but its not a huge deal
   • 

[nitin710]

@JaeminBBQ I made some minor changes in the code, take a look at this comment. I also tested it working for config files and info files. Looks good!

Let merge to master. Remember to complete the FW merge checklist in the PR description ☝🏽 .Make sure to pull before you make the changes to avoid conflicts.