Dave, I can live with being nuts
I get your point! The communication link from the Android to the plane are in fact two-way! The data are sent as packets back and forth. 99% of the data flows from the plane to the ground, the other way it is just some "heart beat" messages that are currently sent, but this can be extended!
Only problem with that is latency and real time speed of the communication. But for "non-flying surfaces" it would be more than enough! I will keep this in mind as a possibility for the future.

As Oli writes Xicoy uses their own protocol. The "Serial measures adapter" Xicoy makes is not a JetCat "converter". It only gives me the opportunity to query some parameters from the ECU, but (very) far from the same parameters as the JetCat ECU does. The Xicoy adapter makes it possible for the ASSI device to get all the important parameters such as fuel left, RPM, EGT etc. The ASSI device constantly monitors what engine type (Xicoy/JetCat) is connected and switches between the needed protocols instantly.
The AMT support requires another firmware in the ASSI as the protocol to the AMT is very much different to the one from Xicoy adapter and JetCat ECUs

Hope this explains it well enough