RFC DiSEqC support?
Added by Joakim Hernberg about 12 years ago
Hello,
I just recently fixed the diseqc 1.1 support. Before in 1.1 mode it would only send the command to the uncommited switch, and in 1.0 mode only to the commited switch. It needs to send both according to the specification. The spec actually allows up for up to 16 lnbs, but since the actual messages allows for 64 lnbs, and as it seems that there is also gear out there that goes far beyond 16 lnbs, I've upped the support to 64 lnbs...
At the moment it's simply an extension of the existing configuration and is implemented as switchport 0-63. The idea has been brought up that it might be better to separately specify the uncommited and commited ports, my idea would be in that case that the uncommited switch input port would be specified as between 1 and 16, and the commited port in the standard way of A/A, A/B, B/A and B/B. So you would specify a specific lnb as uncommited 1 - commited A/B or uncommited 16 - commited B/B, etc.
I am split on the issue and see each approach as having it's own merit, but wanted to ask the community at large if there is a clear preference?