AddPacket() causes unexpected behavior

Description

When trying to unlock heartRate for 100Hz ppg, a bug was encounteredwhile using addPacket()

check out

Lines 3305 to 3308 in 299e166

    
           //const char* IIR_FILT_TYPETAG = "RM\0"; //respiration removed 
        
           //addPacket(timestamp, IIR_FILT_TYPETAG, respIirFiltData, dataSize, true); 
        
           //const char* FIR_FILT_DATA = "FF\0"; //fir filtered 
        
           //addPacket(timestamp, FIR_FILT_DATA, iirFiltData, dataSize, true);

When additional packets were added to send intermediate data to the oscilloscope, the EmotiBit goes into an un-expected state.
- The EmotiBit will connect to WiFi and start blinking the blue LED as expected, BUT, it unresponsive to serial and does not get detected by the EmotiBit Oscilloscope.
- Sometimes the EmotiBit connects to the WiFi and then the blue light stops blinking. The Feather is not detected by the Oscilloscope nor is it responsive to Serial.

Probable causes

Maybe, at 100HZ, we are exceeding the memory allocated for _outDataPackaets
- Weirdly, increases the reserved size from 2048 to 3072 does not solve the issue

	//const char* IIR_FILT_TYPETAG = "RM\0"; //respiration removed
	//addPacket(timestamp, IIR_FILT_TYPETAG, respIirFiltData, dataSize, true);
	//const char* FIR_FILT_DATA = "FF\0"; //fir filtered
	//addPacket(timestamp, FIR_FILT_DATA, iirFiltData, dataSize, true);