Hopefully tomorrow, if regression testing is successful. It will have higher Bluetooth transmit power, and a number of bug fixes. No download of the time-series flight data is available to the phone yet; we have been focused on getting a clean baseline for people to use before completing the work on the downloads.
One change I'm making to the default deployments is for the main chute deployments. Advance warning: the following explanation is going to get pretty deeply into the details. The challenge of the main chute deployment logic is getting it to ignore transient pressure spikes that often happen when the apogee charge fires due to imperfect av-bay sealing. The previous method I used for this is to check for the apogee channel to have been fired, which becomes true 1.50 seconds after the apogee event, at which point a transient would be done. This approach unfortunately depends on the apo channel being used for the apogee charge, which will usually be the case, but I'd prefer not to count on that. If someone were to use the apo channel for some other function, then it would be bad for that choice to cause a problem for the main chute deployment.
Over the last few months I have been adjusting the filtering and persistence check for the barometric velocity, which I use to determine if the main chute should be deployed early in the event of an apogee deployment failure. This is implemented in the default settings, using the secondary criteria for the main chute. The baro velocity check needs to ignore pressure transients from apogee pressure leaks, or sunlight hitting the baro sensor, or other transients, all of which I have experienced in my own flights. I applied the same filtering methods to the "pressure increasing" flight event, so now it is also ignores transient pressure measurements. This means that I can use it as one of the default criteria for deploying the main chute. Now the main chute logic is independent from whatever function the apo channel is being used for.
While I'm here, a quick status update. All the Blue Ravens from the first production run of 250, plus 8 of the first 10 units from the second production run (750 units) are sold. The next 100 units from the 2nd production run will be available sometime this week, possibly as soon as tomorrow. The rest of the production run (640 units) will be available later this month.
