Add thread sleep delay timing control to emotibitCommSettings

[produceconsumerobot]

Plan:

File input

emotibitCommSettings.json>wifi>advertising>threadSleep_usec emotibitCommSettings.json>wifi>data>threadSleep_usec

Code logic

If (threadSleep < 0) { // do nothing, not even yield } else if (threadSleep == 0) { std::this_thread::yield(); } else { std::this_thread::sleep_for(threadSleep) }

Addl info

https://www.quora.com/What-is-the-difference-between-sleep-0-and-sched_yield#:~:text=Yield()%20allows%20another%20thread,the%20next%20thread%20to%20run.

Thread.Yield() allows another thread to run on the current processor while Thread.Sleep(0) allows another thread of equal priority to run, or keeps on the current thread. Thread.Sleep(1) allows the operating system to select the next thread to run.

https://stackoverflow.com/questions/17325888/c11-thread-waiting-behaviour-stdthis-threadyield-vs-stdthis-thread

Additional code changes

Move parsing of emotibitCommSettings.json into EmotiBitWiFiHost

[produceconsumerobot]

Testing from within VS:

Testing from exe

[produceconsumerobot]

Tests to run

Independent variables

Basic tests

• 1 EmotiBit, 1 oscilloscope, 1 computer
  • Matrix ThreadSleep CPU
  • 0, 0 RTT
  • Target TS RTT

    Multi-EmotiBit tests

• 3 EmotiBits, single oscilloscope
  • Target TS CPU
• 3 EmotiBits, 3 oscilloscopes, 1 computer
  • Target TS CPU
• 3 EmotiBits, 1 oscilloscopes per 3 computers
  • Target TS CPU

    Many-EmotiBit Tests

• 10 EmotiBits, 10 oscilloscope, 1 computer
  • Target TS CPU
• 10 EmotiBits, 5 oscilloscope per 2 computers
  • Target TS CPU

    MCU Tests

• M0 vs ESP
  • Target TS
  • CPU
  • RTT

Dependent variables

• Perfmon CPU https://techcommunity.microsoft.com/t5/windows-powershell/average-cpu-usage-over-a-few-seconds/m-p/4027458
• RTT

[produceconsumerobot]

ToDo:

• Code tidyup
• PR