I'm using the microHAM MK with an Orion II. There was a note in the "What's
New" file for 2.037j saying that system timing changes had been made to
clock the serial interface more accurately at the specified 57,600bps. In
the past the actual rate being something closer to 60kbps. I use the
DX-Labs Commander app to control the OII. In the configuration dialog for
Commander the choices for baud rate are 56,000 or 57,600 bps. I had to
change to 56k to get things working normally after loading 2.037j. I also
use N1MM and the setting Tom recommends for the Orion is 56k. These
settings are actually applied to the "Virtual" serial interface used by the
MK.
Not sure if the mismatch is in the app or if the serial interface is now
actully running closed to 56k than 57.6k?
73,
Pat, W5VY
-----Original Message-----
From: tentec-bounces@contesting.com [mailto:tentec-bounces@contesting.com]
On Behalf Of David E. Shelton
Sent: Sunday, October 08, 2006 7:27 PM
To: 'Discussion of Ten-Tec Equipment'
Subject: Re: [TenTec] Orion II firmware problems
I am using microHAM MK to interface the rig but I have tried it both ways
via the direct COM port cable as well. Neither works well. I do enjoy the
rig but there are definite problems that are quite irritating to say the
least. In particular, what about the overall reliability of the rig say in a
contest situation or chasing that rare DX station. I am starting to think
that there are more important things than the specs of the rig.
73,
David, N4IN
-----Original Message-----
From: tentec-bounces@contesting.com [mailto:tentec-bounces@contesting.com]
On Behalf Of Michael W Elliott
Sent: Sunday, October 08, 2006 7:08 PM
To: Discussion of Ten-Tec Equipment
Subject: Re: [TenTec] Orion II firmware problems
Others are having this prob
what controller you using ???
"David E. Shelton" <des.n4in@gmail.com> wrote:
Is it just me or does the current version of FW 2.037j have some issues
with
computer interfacing the Orion II. I can't get DX4WIN, MixW, WriteLog, or
several others to interface smoothly with 2.037j. I reverted back to 2.034
and the problems are gone. When will this be fixed? I looks like the FW was
released September 7. This is a fairly significant problem that would affect
about everyone with these rigs. Is there a work around other than using
2.034? Thanks,
David, N4IN
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
Michael W. Elliott, CISSP
(Certified Information Security Specialist Professional)
THE INSIDE ADVANTAGE -
RETIREMENT - LEISURE, REST and ONLY ELECTRONIC MAIL PAYMENTS
Servant to Bridgett, Collin and all my Creditors
St. Louis County Missouri
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
|