Sorry for the lack of responses. Just so everyone knows the situation currently, here is where we are at: The firmware update (v1.0.0.2) has been in testing and everything has been working as expected. As posted last week, everything had been going according to schedule and all we were doing was testing to verify all bug fixes and feature updates were performing as anticipated. Everything was going perfectly smoothly, so the development team agreed that end of day Friday was completely plausible for a release. End of day Friday occurs and we hit what appears to be a minor hickup in communications between the AP Manager and the AP when plugged into certain PCs. This was one of the more final checks as 95% of the update was focused on AP to vehicle side of things. Problem seems minor, we'll try and finish tonight (Friday) and I went ahead and scheduled all the support staff to come in on Saturday to assist with phone calls so we could push a release out Friday night (late) if need be. Very late Friday night/early Saturday morning the problem turns out to be greater than originally thought. Call off support staff coming in on Saturday but development staff is back in the office first thing in the morning to continue work. Full day of work Saturday, and the resolution is still alluding us. When one issue is fixed on the PC side of communications, it causes another issue to arise on the AP side. Our guys were here all day Saturday working out the cause. This then carried over into Superbowl Sunday. While America sat on their couches eating chips and drinking beer, the guys were up here working out the issue so we could publish an update on Monday. All day yesterday (Monday) I was under the belief that everything was working, we just needed to finalize testing. We were all prepared to get the update out so I continued on to some of my other job functions which on Monday involves a lot of staff meetings and getting everyone prepared for the work week. End of day Monday rolled around, and we still had no update ready. With the developers hitting burn out again, they went home to get some rest and I finally did the same much later in the evening hungry and with my mind buzzing with contingency plans and frustrations. I should have hopped on the forum to update you all but instead ate a very late dinner, thanked my girlfriend for putting up with this craziness and went to bed. So today, Tuesday, I think we're in a similar boat. The fixes are all there, we're just running into issues with the deployment. I think we're close, but I've felt that way for several days now so I can't really commit to any timeframe. What I can say is the guys are trying extremely hard to get this done ASAP. Fortunately, it's the first deployment that'll be the hardest. Getting updates out after this should be a walk in the park (for my sanity I can only hope!). I'll continue to provide you guys updated, good or bad. Sorry for the delays, but as some other software developers on here have alluded to...software development sucks when it comes to setting release dates. I assure you though, it isn't for lack of effort! Thanks again, Trey @ COBB Upgrades: Feature Changes Faster AccessPORT-to-PC communications Faster AccessPORT startup time Faster map preparation for both Reflash and Realtime changes Added Reset ECU function, which is available in Uninstalled and Installed mode. Added Read Codes function to Uninstalled mode Added About function to Recovery mode Added firmware revision information to About Added ability to Reflash over uninstalled EcuTek ECUs Current Map function shows both Reflash and Realtime maps Bug Fixes Read Codes function now properly reads CELs and does not fail after first use Fixed sticky/laggy display of Boost inside Live Data Reflash operation properly clears Realtime map data AccessPORT no longer enters Recovery mode when it is not necessary