Gary,

You might try adjusting the pacing and EOC values in radios.ini for the 
selection you are using.  Maybe make them just a tad larger.  Sounds like 
your radio is responding slowly and perhaps the data is getting truncated or 
otherwise garbled somehow.  Increasing these may help.

Jack

----- Original Message ----- 
From: "Gary Senesac AL9A" <[EMAIL PROTECTED]>
To: "Z DX Base" <[email protected]>
Sent: Saturday, May 28, 2005 12:25 AM
Subject: Re: [Dxbase] Frequency


> Just about to create a new message about a similar problem, though DX 
> Atlas
> (V2.2 here) is not involved.  Having just recently acquired DSL capability 
> I
> have finally been able to utilize DX spotting clusters with DXB.  I'm 
> using
> VE7CC's AR User software and the spotting action seems to be what I have
> expected.  However, I am seeing one action I did not expect.  The 
> frequency
> entered into the log from the rig is intermittently wrong.  On some QSO's
> the correct frequency is entered, on others it is all over the map.  I get
> long strings of what appears to be random numbers, sometimes with a 
> leading
> negative sign.  How do you get a negative frequency?  Some times the
> frequency numbers are correct, but the decimal point is way off; 14185.50
> comes out as 14185000.00 or some such number.
>
> I had a long run into EU this afternoon on 17M and the problem was 
> constant.
> After going QRT I had to scroll to the top of the run, copy the correct
> frequency into the clipboard and manually edit each bad frequency by 
> pasting
> the correct frequency into the bad log entry.  I couldn't use Find & 
> Replace
> as the bad frequencies were all over the map.  While a pain, this is 
> fixable
> while doing a run because I know what frequency is correct.  When 
> searching
> & pouncing it can be a problem if the bad frequency isn't caught and
> corrected right away.  If I QSY to a new band or mode, how do I remember
> which frequency, band or mode was used to make the contact?  I've also
> noticed that when attempting to send a spot, the spot frequency will
> sometimes be off the mark as well, even if I have verified that the 
> correct
> frequency has been populated into the log.
>
> Rig here is also an Icom 756Pro.  PC is Pentium III laptop running ME. 
> I'm
> sure there is some kind of communication conflict between the computer and
> the radio.  I've tried adjusting the baud rate down from 19200 to 9600 
> with
> no effect.  Has anyone else ever noticed this behavior when connected to a
> DX cluster?  Would a higher DSL speed help? - running 128K now.  I haven't
> tried it yet, but I'm fairly confident that if I disconnect from the 
> cluster
> the frequency problem will go away.  Not a viable solution!
> Gary AL9A
>
> ----- Original Message ----- 
> From: "JV" <[EMAIL PROTECTED]>
> To: "Z DX Base" <[email protected]>
> Sent: May 27, 2005 3:36 PM
> Subject: [Dxbase] Frequency
>
>
>>     Ran into a strange problem last night. I had monitor 1 set to DXBase
>> 2005 and Monitor 2 to DX Atlas 2.25. After I had logged serval QSOs, I
>> happen to look at the frequency that was logged. All QSOs were 363416.56
> and
>> the band was 75. I closed DX Atlas and the frequencies were logged OK.
> Open
>> DX Atlas back up and got the same problem. Anyone have this happen to 
>> them
>> and if so, what's the cure. Using 2.4 MHz and XP pro. Rig is an IC-756
> pro.
>> JV
>> ______________________________________________________________
>> Dxbase mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/dxbase
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:[email protected]
>>
>
> ______________________________________________________________
> Dxbase mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dxbase
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[email protected]
> 

Reply via email to