Dale,
To answer a rhetorical question it is not your radio. It is surely a result of
TRLog much more strictly analyzing the data coming back from Icom interfaced
radios. I do want you to make sure for me that 6.71 is also a problem for you.
I would not have expected that based on the changes I made. Can you confirm
for me please.
Great set of data collected. Thanks for taking the time to do that! It looks
just like I would expect with intermittent data transfer to/from the radio.
When debugging this version I went through that testing to make sure the
program would work and allow one to change bands if a radio became
disconnected. Everything worked as designed for the IC706 I was using to debug
the interface and my TS850 and FT1000D combo at the home station. If I lose
comms and then get it back (unplug for a bit and then replug) TRLog synchs
back up with no problem even after interim ALT-Vs or ALT-Bs.
I am curious if you ever see a "comm error" pop up with a warning beep?
Does it matter if the VI+ and VI are swapped (physically at the computer or
using LOGCFG.DAT) as radio one and two? Do the errors follow the VI? When
swapped with ALT-R does the frequency displayed on TRLog track with the radio
as you spin the dial? I am not trying to "blame" the radio, but to understand
any potential differences between them. I have to ask as I do not have one to
play with myself.
What I suspect is there is SOMETHING different about the 735 and the Omni VI
which I am unaware of or is undocumented. For now I have to suggest you use
version 6.70 or 6.71B if that is working for you. If I come upwith nothing
else I can surely vector 735 and TenTec over to the older...not so
discriminating...interface code.
--
73 es God Bless de KK1L...ron rossi(kk1l@arrl.net) <><
Support Programmer for TRLog http://www.qth.com/tr
QTH: Jericho, Vermont
My page: http://www.qsl.net/kk1l
>
>I'm not convinced. Either it's my radio, which up until 6.71/.72 has been
>working just fine, or it's TRLog.
>
>My Omni VI+ works fine since I used John's config example. I also set baud
>rates to 4800.
>
>However, my Omni VI is still squirrely as heck when using alt-v/b. Check
>the test I conducted below
>
>73,
>dale, kg5u
>
>
>>
>> PROBLEM SOLVED!
>>
>> The default baud rate in TR is 4800. Most OMNI-VIs are set to 1200
>> (the default); therefore, users set configuration file in TR to 1200.
>> Since John said he was using the default setting in TR (4800) and had
>> no problem, I set TR and my OMNI-VI to the 4800 baud rate and found
>> the Alt-V/B problem went away. Ocassionally get some error tones in
>> the speaker, but all seems to be working okay now.
>>
>> THANKS John!!
>>
>> Kevin
>> W3DAD
>>
>>
>> ----- Original Message -----
>> From: "John Unger" <w4au@contesting.com>
>> To: <trlog@contesting.com>
>> Sent: Monday, January 13, 2003 11:43 AM
>> Subject: [TRLog] NAQP Experiences - Omni VI+ & TRLog 6.72
>>
>>
>> > I'm not sure why some people are still having problems using TRLog
>> 6.72
>> > with the Omni VI+, so I thought I post my experiences and settings
>> and see
>> > if that can help anyone still not able to get their Omni VI working
>> > properly with the latest verion of TR.
>> >
>> > Version 6.72 worked virtually flawlessly for me in the NAQP this
>> past
>> > weekend. (I made 825 Q's, a personal best effort for me...) I had my
>> Omni
>> > VI+ setup as an IC-781. Here's the pertinent part of my logcfg.dat
>> file:
>> >
>> > RADIO TWO NAME = OMNI IV
>> > RADIO TWO TYPE = IC781
>> > RADIO TWO RECEIVER ADDRESS = 4
>> > RADIO TWO CONTROL PORT = SERIAL 2
>> > RADIO ONE NAME = TS850S
>> > RADIO ONE TYPE = TS850
>> > RADIO ONE CONTROL PORT = SERIAL 1
>> > TWO RADIO MODE = TRUE
>> >
>> > I was using defaults for all the other radio-related parameters
>> including
>> > ICOM RESPONSE TIME and RADIO TWO BAUD RATE. During the contest I
>> booted my
>> > computer with DOS 6.22 using a floppy disk and ran TR that way, but
>> my
>> > experiences in running TR and the Omni VI were identical when I was
>> > checking things out using a DOS window in Windows 98se. I will be
>> glad to
>> > share my config.sys and autoexec.bat files, if anyone thinks that
>> these may
>> > be part of the problem.
>> >
>> > Interesting note: Prior to the contest I discovered that TR 6.72
>> would not
>> > work properly with the Omni VI and IC-781 setting if the RADIO TWO
>> TYPE and
>> > RADIO TWO RECEIVER ADDRESS lines were swapped. Ron is aware of this
>> problem
>> > and is working on it.
>> >
>> > I did notice a "Radio Two Communication Warning" flashing for a few
>> seconds
>> > in the lower left-hand corner of the screen (accompanied by a bell
>> tone
>> > from the computer) occasionally when I switched bands with ALT-V or
>> ALT-B
>> > or changed frequency by typing a frequency in the call window. This
>> > occurred about 10% of the time I did these operations, but did not
>> prevent
>> > the action from taking place. Most of the time I change bands with
>> the
>> > rig(s); it's just how I do things...
>> >
>> > I was also using the AUTO S&P feature with it's default settings; it
>> worked
>> > fine. Also, I thought the frequency readout window displayed the
>> current
>> > frequency much more smoothly than with earlier versions.
>> >
>> > I hope this information is helpful.
>> >
>> > 73 - John, W4AU
>> >
>
>
>KG5U Test conducted tis morning...
>
>
>I setup 6.72 and the following cfg for my Omni VI's:
>
>
>Radio one baud rate = 4800
>Radio one name = Radio 1
>Radio one type = ic781
>Radio one receiver address = 4
>Radio one control port = serial 2
>
>
>Radio two baud rate = 4800
>Radio two name = Radio 2
>Radio two type = ic781
>Radio two receiver address = 4
>Radio two control port = serial 1
>
>Two radio mode = true
>
>Relay control port = 1
>Keyer output port = parallel 1
>Paddle port = 1
>
>
>I rebooted the PC to DOS.
>
>I set up the radios as follows:
>Radio 1 (Omni VI (upgraded to plus) - 28010, 21010, 14010, 7010, 3510, 1810
>Radio 2 (Omni VI) - 28020, 21020, 14020, 7020, 3520, 1820
>
>With Radio 2 on 28020, I did a series of Alt-V's:
>(columns below indicate alt-v sequence nr, band indicator on screen,
>frequency display on screen, radio frequency)
>
>1. 20m 14025 14025
>2 40 7025 7025
>3 80 3543 3543
>4 160 1820 1820
>5 15 21010 21010
>(skipped 10m because radio 2 was on 10m).
>
>Radio 2 (with radio one on 21010):
>1 10-20-10 28020 14025
>2 10-20-10 28020 14025
>3 20 14025 14025
>4 20-40-20 14025 14025
>5 20-40-20 14025 7025
>6 20-40-20 14025 7025
>7 40 7025 7025
>8 40-80-40 7025 7025
>9 40-80-40 7025 7025
>10 40-80-40 7025 3543
>11 80 3543 3543
>12 80-160-80 3543 1820
>13 80-160-80 3543 1820
>14 160 1820 1820
>15 160-10-160 1820 28010
>16 160-10-160 1820 28010
>17 160-10-160 1820 28010
>18 10 28010 28010
>19 10-20-10 28010 28101
>20 10-20-10 28010 14025
>21 20 14025 14025
>(Radio 2 skipped 15m because radio 1 was on 21010)
>
>Interestingly, during the 'hops' where TRLog jumped from 10 to 20 and back
>to 10 for example, the remaining mults changed accordingly, as did the band
>indicator at the left end of the band-mode-date-time-s/n-call entry field
>line...whether or not the radio changed.
>
>I changed the order of the config parameters, but it didn't seem to matter.
>
>I've never had a problem with band changing radio 2 using 6.69 or earlier
>versions of TRLog.
>
>
>_______________________________________________
>TRLog mailing list
>TRLog@contesting.com
>http://lists.contesting.com/mailman/listinfo/trlog
|