TenTec
[Top] [All Lists]

[TenTec] Eagle Update

To: Discussion of Ten-Tec Equipment <tentec@contesting.com>
Subject: [TenTec] Eagle Update
From: "Henry, John" <jhenry@tentec.com>
Reply-to: Discussion of Ten-Tec Equipment <tentec@contesting.com>
Date: Fri, 5 Nov 2010 10:01:48 -0400
List-post: <tentec@contesting.com">mailto:tentec@contesting.com>
Posting here the same that I posted in
http://groups.yahoo.com/group/TenTec_Eagle/

The discussion was regarding the new manual online at the TenTec
download page for the Eagle, V1.004.
The wording stated the new QSK dELAY feature gave you an adjustment
after characters, well, my miswording, it should have stated Elements.
My mistake.

This feature in the Eagle works similar to the same feature in the
OMNI-VII. Giving you a way to set up how long the receiver is quieted
after a dit or dah is released. From 15-18ms for the for a dELAY value
of 1, to around 2.5 seconds for a value of 100.

Regarding the USB virtual com port settings.
Yes, the values are meaningful, even in a virtual com port setup.
The Eagle uses standard settings 576, 8, N, 1, HW flow control:
baud rate = 57600 bits/second
8 data bits
No parity
1 Stop bit
Hardware Flow Control Enabled.

The protocol is a subset of the Orion 2, so in a lot of instances, the
Orion 2 can be chosen as the driver.

Some programs work now, some don't.
Some look for the radio to return 566 if you say it is an Orion 2,
well, the Eagle returns 599, so it won't work properly with those
programs yet until they change the PC software to recognize 599.

I am in the middle of working out some last minute details in the
interface with other PC developers, to ensure it works properly and
provides the functions they need. e.g. one such developer really
requested that the bw be changeable via the cat control as well. That
is available in 1.682.

Once all this is in order, I'll publish the programmers interface
specification so that other PC developers can get their programs
updated. Again, it is a subset of the Orion 2 protocol, so they could
actually start today, cloning an Eagle selection to operate as an
Orion 2 selection would have, looking for 599/Eagle returned instead
of 566/Orion2, and then when the protocol spec is published, they
could then remove the commands the Eagle doesn't support, and modify
the few commands/queries that are different. I've hesitated posting
the interface spec for now until ALL issues seem to be worked out from
either the beta cat developers or in the firmware.

1.682 is what is being shipped in customers rigs this week, and we are
supplying existing customers with 1.682 as we speak. Windows had an
update two weeks ago that changed how the update/bootloader process
worked, so we are addressing this next firmware update with existing
customers directly.
Once 1.682 is in place with customers with the proper bootloader 6 to
handle the Windows update, then, when I get a newer version than
1.682, I will have an update file created for it.

I'm trying to monitor this and other reflectors, ....

Thanks,
John Henry
TenTec Engineering.
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec

<Prev in Thread] Current Thread [Next in Thread>
  • [TenTec] Eagle Update, Henry, John <=