Voudas, I do agree, and I think integrated basic wifi control plus flashair would be quite a good combination to use m200... but unfortunately,we now know it won't never be like that.
It could be like that, you showed Z a way to easy implement everything they declined to implement with WiFi and do even more, Z-Developers and Z-VIP just have to understand itâ€¦
With the FlashAir you enable the M200 for WiFi, nothing to deal with for Z, so that's easy going.
The FlashAir connects a file service (available to the customers network) to the printers SD-Card interface and the rest is easy going too.
Back in the 80s when Multiprocessing for home users was far away, we used add-on software like DesqView to enable concurrent DOS-Sessions. It was like using multiple CMD-Sessions on Windows wich was not available at this time (and later on not useable for a long time).
Those sessions share the same disk, just like the M200 and the customers network on the FlashAir SD. That way files can be managed on that disk and of course a control mechanism to control the M200 is also easy to implement.
To do that just some kind of semaphore processing is needed, that's nothing special, just some files that Z-Suite could create and write on the SD and the M200 firmware recognize as control orders and processes it accordingly. This can happen almost in realtime (when idle the printer could check the SD in intervals, when printing the intervals are at the point when next print data is retrieved from the SD).
Such a mechanism could be implemented in a few days of programming, the FlashAir could be an optional accessory to the M200 and the functions just enabled dynamically if the connection is available.
If Z has not to deal with WiFi (that's the customers part to setup) and they find the path to the M200 open by such a setup (Z-Suite can easily recognize that connection), the M200 could be opened for features that are beyond the competitions abilities (think of an integrated pronterface/printrun).
It's really easy.