I would say that I should have confirmation that all reported issues are resolved by this weekend. I have already received confirmation that "test devices" have solved all issues. I just need to verify that the fixes put into the test devices work as expected on production level devices.

I am not saying that all reported issues were issues with the TwinSync either (actually very few were). I have been solving many problems including installation, throttle mechanical setup, radio programming, RFI noise from ignition systems, manual and documentation issues, etc. The field/beta testers in general have been fantastic in reporting any issue that an in-experienced modeler may hit even though the field testers in general have been in the "expert" or above class and I thank all of you that I have been working directly with and are actively using the TwinSync.

So I think everyone would like to hear about all issues found and the solutions...

The following are issues that have been found:
- low RPM hunting or oscillations on big gas engines - Resolved a couple of weeks ago for electronic ignition engines. Report I got today is that that same fix resolves it on Magneto equipped engines but spark RFI was continuing to cause what appeared to be an issue. Should be verified fix by this weekend. Also we found much better results are achived with two magnets on engines that will never exceed about 10K RPM at low RPM.
- The above hunting or oscillation has also resulted in upcoming recomendations on using expanded end points for gas engines, a new programmable "sync engagement point" on new software, and mechanical recomendations for non-linear (differential) throttle push rod setup for GAS engines (i.e. a lot of servo movement producesvery little throttle arm movement below 1/2 stick). The reason being is that 1% servo movement can result in a 300+ rpm change on some gas engine setups.
- Multiplex radios run a frame rate sufficiently slow than all other radios to result in what the TwinSync interprets as transmitter signal loss and does a PCM lock out and kills both engines. This algoritm was completely changed so that 6 pulses in a row have to be missed and it will operate with a frame rate as low as 20Hz. (Multiplex is about 33Hz and 40hz is standard in the industry).
- Sensor mounting. Seems simple but it is not and sensor wires can pick up RFI interference from spark systems. Sensor faces and not tops must face magnets which requires bending the sensors as they come from the factory. Plastic spinners or no spinners takes some fore thought (I am thinking about offering an optical upgrade). Sensor wire must be kept away from Gas engines and their ignition system due to spark noise. Non-conductive sensor mounts should be used.
- the varity of engine response, rpm range, and servo speeds have resulted in my adding a response time adjustment and more recently this response time varies based on RPM range. Why slow response times for glow users or high performance gas engines to meet the slow response times of big magneto and flywheel gas engines. Factory default will probably be glow engines for now. Gas engine users will probably need to make some response time program changes. Feedback is welcome here but Glow is the bulk of the users. If I make the fatory default for gas engines glow, will work fine but sync time, dead stick, and sagging engine response times will suffer. Gas guys will see "hunting" at low RPM and have to add a second magnet and change the response time setting.
- I am planning on adding what I call a "dead band". The dead band is a target RPM range in which the device declares the engines are "in sync" and stops moving the servos. Beta devices out there now are set at 100 rpm. Early devices were set to no dead band and moved the servos unless both engines were measured at the "same" rpm which was about 10 rpm at 5000rpm and 50rpm at about 20,000RPM. No servo and carb can hit these targets and this resulted in some hunting that could only be observed with brushless motors or big gas engines.

So in general no issues with the device were found with glow. All issues were Gas engine related except manual/documentation and the multiplex radio issue.

As a result, I have continued to hold all requests for software updates that have come in the last week and RC Showcases' inventory until I get final confirmation that everything is solved....

I am traveling this week with work and hopefully will have confirmation before or over this weekend that everything is resolved. I will do a major post and/or a new thread when I release product for general distribution and ship RCS's inventory...

This has been a challenge... There is more electronic technology in this device than in the first moon landing - no joke...

As for the frequency hopping transmitter- it is not legal in the US and probably not in the EU either. Besides, I have a better idea for solving that issue anyway - i.e. that's probably why that can only be offered as a kit. This kit could keep your plane flying while crashing other planes at your club.

I haven't decided if my next project will be a multi-axis heading-hold solid-state gyro or a scale light flashing device (i.e. do I want something simple or the 8th wonder of the world)... That is a surprise but it will be sold through RCS and is not that far off - I will tell no more...

If you want your TwinSync to ship the same day you order it from RC Showcase you are probably 1-2 weeks away from that point.

One other reminder is that I am increasing prices after their introductory inventory is sold out...