The HUI protocol has all the parameters we want to get at - there is just a default order of how they are served up. The Qcon would need a SW wrapper on top of the HUI protocol to allow the parameters to be all dumped in and then served how the user wants. This is especially tricky when we want the Qcon SW to recognize what Plugin is being served up - look at our custom mapping - and then parse the data and serve it to us how we want it. Totally doable but complicated. I too will be surprised if this device can do this - but will also be ecstatic if it can.