No, but you didn’t like the comment that people have to play with devices to find out what the channels mean. (you said -:: “play to see what it does” dont seem like a good advice). Someone needs to do this, and if you are not wanting to do this, then it falls on someone else. I got the impression that as you didn’t like my advice, you expected me to provide better statements? If you are buying a commercial system, then I think you can expect to have this for the devices that are supported by said system, but here, we expect that people do spend some time to “play” and understand what the device does for themselves.
As I said above, the binding can’t show what it doesn’t know. If it knew there were missing channels, then, well, they wouldn’t be missing . If there is a failure in the detection, then this is printed in the logs. In the longer run, I plan to improve the management of transactions to make this more tolerant, but this is a lot of work and at the moment, it’s not quite at the top of the list (although it’s not far off). When this is done, I hope that this issue will largely go away.
Thanks, and I appreciate that. I hope that once I can get you the sniffer that we can find some of the issues that are causing you problems, so I do appreciate that you are wanting to help .