[TenTec] computer control/logging

John Crux [email protected]
Thu, 18 Apr 2002 10:24:32 +0100


The Omni-V has the same unusual interface. I modified it when I 
changed the firmware, but there is something else to watch out for. 
Some logging programs simply do not handle oddball (but not uncommon) 
port settings such as COM3 IRQ 5. I found that because my OMNI is on 
COM 3 I can neither use nor test a number of programs.  Use a 
different port ??? Yes, if you have one free, but I set my system up 
thinking COM 5 IRQ 5 would be OK. I now have four ports and custom 
cables which I cannot easily swap over without hardware changes and 
upsetting the DXCluster and data TNCs. I also have a very cramped 
under-stairs shack full of junk.

My logging/shack PC runs WIN 98  24/7 at 200 mHz. I occasionally stop 
it and reboot, but Win 98 has given me little trouble.  I have found 
that the logging software gets very unhappy if I turn the Omni off 
before I press the key to disable frequency readout. It does not 
crash, but it hangs before it goes in to "you do not have a rig 
connected" mode, until I stop and restart the log software, with the 
Omni turned on again. 
. 
Keyboard errors (operator fumbles) can result in the Omni changing 
bands, modes etc  unexpectedly. But there are over 14000 entries in 
the log and so far I lost no data.  The only problem has been the 
(separate) software used to connect to the DXCluster. For some reason 
that locks up unpredictably. No-one else has reported this. But the 
logbook carries on running, so it is probably not in the software and 
not a Win 98 glitch. It could be in the 4 port card hardware ... ??
 
The joys of computer control ....  I am about to try to add my 
Elecraft K2 to the system. In theory it can go onto COM 1, the empty 
mouse port (I used a PS2 mouse to free up 4 ports) because the K2 
serial port comes with 9 pin plugs. I might be able to reach the COM 
1 socket .... it would help if I was double jointed and had a very 
long arm. With my talent for computer disaster it will not be so easy.
See y'all at Dayton
73  John G3JAG

On Wednesday 17 April 2002 8:44 am, Talbot, George A. wrote:
> Mark,
>
> > -----Original Message-----
> > From: Charles Mark Cring [mailto:[email protected]]
> > Sent: Tuesday, April 16, 2002 2:07 PM
> > To: [email protected]
> > Cc: [email protected]
> > Subject: Re: [TenTec] computer control/logging
>
> <snip>
>
> > My Paragon also has the RS-232 port on it, but I have not had any
> > luck with getting it to work.  I haven't tried very hard yet,
> > though.   I downloaded the original "basic" program from the web
> > (I think I found it on the "unofficial" Ten Tec web site) and ran
> > it in QBASIC. The time I tried it, the program didn't seem to do
> > anything at all, but it wouldn't even "exit" (by hitting the
> > letter x, according to the menu). But I'm not sure yet if the
> > problem was in the program, the
>
> communications,
>
> > etc...or whether the program will even run correctly in win 98
> > dos window...or for that matter, whether my RS-232 is even good.
>
> Well, the delay required to allow for the Paragon's processing
> overhead required timing loops in the software which had to be
> increased as the speed of the Host Computer increased. To get the
> program to work with my "slow" 75 MHz Pentium I had to nest the
> timing loops to make the program not to crash the Paragon firmware.
> As I recall I had to increase the time delay something like 200
> times from the "stock" program which was deigned to run on a 4.77
> MHz machine. I will have to look up the line numbers in the Basic
> Program that need to be changed and get back to you.
>
> Also you can use "HyperTerminal" to troubleshoot the RS-232
> interface with the Paragon to see if that portion of the set up is
> working. From the Accessories Menu select HyperTerminal and name
> the new connection "Paragon" or something else that will let you
> know it is being used with your radio. Then in the set-up make sure
> it is set for 1200 Baud, 8 Data Bits, 1 Stop Bit, No Parity and no
> flow control. Also make sure the Com Port is the same one that is
> being used to connect to your Paragon. If all is working you should
> be able to "connect" to the Paragon and issue commands from the
> keyboard (see the Basic Program / RS 232 Documentation with the
> Paragon).
>
> > So if you find out anything, let me know.   Likewise if I
> > ever get mine
> > going I will let you know.  I'm probably not going to spend a
> > whole lot
> > of time on it, but if I get a chance to mess around with it
> > again, I'll
> > probably try the basic program from a command prompt and go
> > from there.
> >
> > Good luck!
> >
> > 73 de Mark N8COO
>
> Hope this helps some,
>
> Regards,
>
> George V73GT
>
> PS. Feel free to contact me if you need more assistance.
> _______________________________________________
> Tentec mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/tentec