Jim,
I made up an adapter cable to convert my DB-25 to DB-25 control cable =
(which does work beautifully, I might add) to a DB-25 to DB-9. I used =
the pinouts in Omni VI Operator's Manual (pp 5-1). It did not work.
I then read the NA Operator's Manual. I included a jumper from pin 7 to =
pin 8 on the DB-9. No difference. It still doesn't work. I tried =
different com port settings. Nil. In fact while I was identifying =
XCVR1 in any of the com ports, the band change function (ALT-F1, ALT-F2) =
was inoperative. Even removing XCVR1 from
the com port setup did not restore the keyboard band change function. I =
had to reboot.=20
I was going to use the adapter at Field Day, but it looks like that's =
out. Unless I haul my full-size 286 up there and go with that instead of =
the lap top.=20
I hope you had success with your cable and your Omni and 486 not =
conversing.
73,
Dale Martin, KG5U
kg5u@hal-pc.org
see my homepage: http://www.hal-pc.org/~kg5u
----------
From: BK1ZX70SFL@aol.com[SMTP:BK1ZX70SFL@aol.com]
Sent: Saturday, June 15, 1996 17:26 PM
To: na-user@ve7tcp.ampr.org
Cc: cq-contest@tgv.com; kg5u@HAL-PC.ORG; wc4e@mcimail.com
Subject: My Omni VI and My '486 Aren't Speaking
This msg x-posted contest refl & na-user refl
HALP!
Appliance operator seeks your savy CONTESTOR expertise in resolving the
following:
I am stepping into the 90's and asking my digital xcvr to talk and share
frequency info with my computer.
Hdwe/Sftwe: Omni VI/'486/NA v10.0 Software
Step 1) Purchased NA10.0 and W1GEE interface cable from K3LR at LTA =
Booth
last month.
Step 2) Ran W1GEE program that came with the interface cable.
Step 3) W1GEE program says that the port I thought was Comm 2 is Comm 1. =
By
shorting the far end of the interface plug and running W1GEE's program
telling it I was hooked up to Comm 2 nothing happened, on a whim I tell =
the
program its comm 1 and voila it acknowledges me. So, I guess that socket =
is
Comm 1. Already I am toasted.
Step 4) I assume that it is actually Comm 1 on the '486 that will be
interfacing with the Omni VI, and I tell "Config" I have an ICOM 735 =
(even
tho its an Omni VI - that's what the manual sez to tell it) and I tell =
it
that it is Comm 1 @ 9600 baud. I tell "Equipment" that I have a radio =
"1",
and I turn the Omni VI "CDE" to ON and tell it to run @ 9600 =
baud....here's
what happens:
Nothin (positive anyways)
The Omni VFO locks - it won't budge, the NA software won't change bands. =
The
software will call CQ and log callsigns, but when you Alt/F1 or Alt/F2 =
it
don't go up or down a band.
Obviously the two are NOT in agreement as to what's going on.=20
If I shut off the "Equipment" Radio 1 on NA the software will manually =
change
bands again, but the Omni VI is still locked up (I think its pissed off =
there
is another microprocessor in my life). If I do a Master Reset of the =
Omni VI
and turn the "CDE" to "off" it is manually tunable again.
I have tried re-booting the computer, changing just about any of the =
software
switches, but I get the feeling there is something I am forgetting to =
do.=20
I tried telling the software it was actually Comm 2 (like I really =
thought in
the first place) and the behaviour is the same with the vfo locking on =
the
rig and the software not wanting to change bands.=20
Using Alt-F to show what frequency things are on displays 14.000 so it
definately appears no info is being exchanged between the two boxes.
I am truly an appliance operator and when you get two digital beasts
confronting me the only thing I know to do is:
Scream For Help On The Reflectors!
Sound like a familiar problem? I knew I should have gone to W3LPL's =
party.
Pse es tnx
Jim zx k1zx@contesting.com
--
Submissions: na-user@ve7tcp.ampr.org
Administrative requests: na-user-REQUEST@ve7tcp.ampr.org
Questions: owner-na-user@ve7tcp.ampr.org
|