At 07:06 AM 8/16/01 -0700, Tree N6TR wrote:
...
>Kenwood made the right choice - using a command set that was very
>efficient, using ASCII characters that appear on your keyboard.
I totally agree. I didn't mean to imply that it was somehow TRLog's fault
- quite the opposite.
>
>However, I have added the ability to put hex values into the
>RTTY send/stop strings, and this will also work for function key
>memories that are in the .cfg file. This will be in the 6.59
>which I hope to have out in the next couple of weeks. I am way
>behind in my e-mail and need to plow through it before I can
>send out a release.
This sounds really excellent. In the meantime, though, I understood that
VE7FO was commanding the radio from TRLog using some rendition of the hex
codes that involved using Ctl-x (where x is a varable, not the letter) to
send hex values. Or did I get that wrong?
If I read the manual correctly, Yaesu has the documentation really screwed
up. I *think* they mean to say that the normal order for sending commands
to the radio is P2|P1|P3(or null)|P4(or null)|Opcode. Whaaaa???
73, Pete N4ZR
--
FAQ on WWW: http://www.contesting.com/FAQ/trlog
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|