David,
I'm using MixW set up to use Pegasus/Jupiter (emulation) interfaced thru a
Rascal sound card interface using Com2 and the ORION II AUX I/O and N4PY
control software using Com1 and the ORION II Serial/Data port. Both
comports are set up for 57600 bits per second, Data bits 8, Parity none,
Stop bits 1, Flow control none, FIFO buffers set to high.
The computer control with this setup works very well and never fails. The
only glitch I have is related to a recently installed, after market, LDG
internal auto tuner and this is a display refresh glitch on the O2. So I
don't set the N4PY software for using the internal tuner, but rather use the
Tune button on the O2 for this function.
This setup has worked on all versions of Software for the O2 including
version 2.037j. I'm curious to find out what combination of settings work
for your software on 2.034 that do not work on 2.037j.
73
Ron KA7U
-----Original Message-----
From: tentec-bounces@contesting.com
[mailto:tentec-bounces@contesting.com]On Behalf Of David E. Shelton
Sent: Sunday, October 08, 2006 5:47 PM
To: tentec@contesting.com
Subject: [TenTec] Orion II firmware problems
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
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
|