On Mon, 2007-09-24 at 13:35 -0400, Joe Subich, W4TV wrote: > > As I recall, TT also basically told their customers that, "This is > not > > a design flaw, this is how it is supposed to work." And further, > even > > argued back about what was and what was not necessary for their > > customer's satisfaction. > > Not only that ... TT do not learn from their mistakes. The same fight > is being repeated over the Omni VII! >
I am trying at the moment to add support for the OmniVII (without having access to an OmniVII) to a well known logging package however it appears that TT's programming reference manual may be wrong regarding the byte order and data required to set the frequency In addition to this it is just plain crazy to change the control format for a new radio in such a way that it is completely incompatible with previous radios from the same manufacturer, By all means add to the capabilities of a protocol but don't completely alter the basics Multiple Emails for further information on this to both TT and RFsquared have gone unanswered to date. hardly a good approach if you want your product to have widespread logging software support Thankfully with Elecraft the K3 will build on the K2 protocol (which in turn was built on the Kenwood protocol) and we all know how much more responsive Elecraft are to Queries. If anyone can help me with the orionVII serial protocol please contact me off list. 73 Brendan EI6IZ _______________________________________________ Elecraft mailing list Post to: [email protected] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com
