Of course, we at MTH closely monitor the OGR forum. It is invaluable as a source of feedback for our company and products. Forum members are highly engaged customers and very knowledgeable. Your experiences with our newly released WIU and app(s), Wi-Fi DCS collectively, are of particular interest.
We see that some of you are having issues with reading or adding engines and erratic behaviors that result. Of course, we were surprised since neither internally or in external beta testing did we have these results. Of course, it is nearly impossible for us to simulate all of the various applications out there. That's not a cop out, just an unfortunate reality. So, before I go any further, we sincerely apologize for the difficulty some of you are experiencing.
That said, we are pleased to announce we have duplicated the issues some of you are experiencing with reading and adding engines, engines becoming inactive, etc., etc. It is a very odd firmware bug and was difficult to find. Without going into technical depths, there is a difference in timing between the app/module and DCS remote with respect to how certain commands are handled. This timing issue adversely effects the read and add engine processes in certain configurations. Interestingly, because it's a timing issue, if you are working with a few or many engines, the problem doesn't appear. You have to be in the sweet spot, or should we say, sour spot, for the bug to bite.
The good news is, we have identified and corrected the issue. Revised module firmware and app updates will be coming soon. We are testing the changes now so, please be patient. Clearly, we need to be thorough lest we create a new and different issue.
Thank you for the feedback. Without the detailed discussions on the forum, it would have taken much longer to identify and address the unexpected timing issue. As a result, Wi-Fi DCS will continue to improve.
Thanks again and we hope you enjoy Wi-Fi DCS. This is just the beginning. We have much more in store for you on down the line.
MTH
