DXLab@groups.io | Messages

Re: No Last QSO Information on WW

Mario Aviles

Dave:

I checked in DX Keeper and it is not registering most of the information you pointed out. The only fields being registered are CALL DXCC, Starting UTC BAND MODE, SENT, REceived. It is not registering all the other information, not even the exchanged reports. THis is a contest which is not in the drop down box, so I entered it manualy. WW shows the fields and the counter does increment by one each time I looged a station but this info is not on DXK

Thanks for your help

Mario

Show quoted text

----- Original Message -----
  From: aa6yq
  To: dxlab@...
  Sent: Tuesday, September 15, 2009 5:31 PM
  Subject: [dxlab] Re: No Last QSO Information on WW


    In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date?

  73,

  Dave, AA6YQ

  --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote:
  >
  > Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded he said that we had already worked and indeed, I checked DXKeeper and he was logged. When I unselected the contest mode, then it gave the adecuate indication
  >
  > 73?s
  >
  > Mario
  > ----- Original Message -----
  > From: aa6yq
  > To: dxlab@...
  > Sent: Tuesday, September 15, 2009 5:16 PM
  > Subject: [dxlab] Re: No Last QSO Information on WW
  >
  >
  > With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID.
  >
  > 73,
  >
  > Dave, AA6YQ
  >
  > --- In dxlab@..., "Mario Aviles" <mario.aviles@> wrote:
  > >
  > > Hi Group:
  > >
  > > Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case. Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus.
  > >
  > > Any ideas?
  > >
  > > 73?s
  > >
  > > Mario/YS1MAE
  > >
  > > [Non-text portions of this message have been removed]
  > >
  >
  >
  >
  >
  >
  > [Non-text portions of this message have been removed]
  >





[Non-text portions of this message have been removed]

Re: No Last QSO Information on WW

#72195

In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date?

   73,

       Dave, AA6YQ

Show quoted text

--- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote:

Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded he said that we had already worked and indeed, I checked DXKeeper and he was logged. When I unselected the contest mode, then it gave the adecuate indication

73?s

Mario
  ----- Original Message -----
  From: aa6yq
  To: dxlab@...
  Sent: Tuesday, September 15, 2009 5:16 PM
  Subject: [dxlab] Re: No Last QSO Information on WW


    With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID.

  73,

  Dave, AA6YQ

  --- In dxlab@..., "Mario Aviles" <mario.aviles@> wrote:
  >
  > Hi Group:
  >
  > Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case. Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus.
  >
  > Any ideas?
  >
  > 73?s
  >
  > Mario/YS1MAE
  >
  >
  >

Re: No Last QSO Information on WW

Mario Aviles

#72194

Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded he said that we had already worked and indeed, I checked DXKeeper and he was logged. When I unselected the contest mode, then it gave the adecuate indication

73?s

Mario

Show quoted text

----- Original Message -----
  From: aa6yq
  To: dxlab@...
  Sent: Tuesday, September 15, 2009 5:16 PM
  Subject: [dxlab] Re: No Last QSO Information on WW


    With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID.

  73,

  Dave, AA6YQ

  --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote:
  >
  > Hi Group:
  >
  > Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case. Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus.
  >
  > Any ideas?
  >
  > 73?s
  >
  > Mario/YS1MAE
  >
  > [Non-text portions of this message have been removed]
  >





[Non-text portions of this message have been removed]

Re: No Last QSO Information on WW

#72193

With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID.

   73,

       Dave, AA6YQ

Show quoted text

--- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote:

Hi Group:

Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case.  Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus.

Any ideas?

73?s

Mario/YS1MAE

No Last QSO Information on WW

Mario Aviles

#72192

Hi Group:

Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case.  Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus.

Any ideas?

73?s

Mario/YS1MAE

Re: PropView & Vista 64

#72191

Tnx Rich & Dave - I was under the impression that VOACAP would not run with NTFS, but I returned to Greg's site and read a bit more carefully - it is NTFS compressed that is the problem. I was not aware that ICEPAC was also installed along with VOACAP. I just tried PropView agn and it works fine with both.

Don W5FKX

Show quoted text

--- In dxlab@..., "aa6yq" <aa6yq@...> wrote:

I doubt anyone is going to release a 64-bit version of IONCAP. Its in all respects inferior to VOACAP and ICEPAC. Like Rich, I use ICEPAC.

   73,

       Dave, AA6YQ

--- In dxlab@..., Rich - W3ZJ <rich@> wrote:

Yes, Ioncap is an old  16 bit application that won't run on on 64 bit
Windows 7 either. However, both ICEPAC and VOCAP work ok. Try going to
the "Prediction Tab" click "Config" and select either ICEPAC or VOCAP. I
like ICEPAC.

73, Rich - W3ZJ

Don B wrote:
I just got around to installing PropView on my Vista64 pc and, upon attempting a path prediction, got the following error message:

"The program or feature: "&#92;??&#92;C:&#92;Progra~2&#92; ...&#92;Ioncap&#92;IONCAP.EXE" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the vendor ..."

Re: PropView & Vista 64

#72190

I doubt anyone is going to release a 64-bit version of IONCAP. Its in all respects inferior to VOACAP and ICEPAC. Like Rich, I use ICEPAC.

   73,

       Dave, AA6YQ

Show quoted text

--- In dxlab@..., Rich - W3ZJ <rich@...> wrote:

Yes, Ioncap is an old  16 bit application that won't run on on 64 bit
Windows 7 either. However, both ICEPAC and VOCAP work ok. Try going to
the "Prediction Tab" click "Config" and select either ICEPAC or VOCAP. I
like ICEPAC.

73, Rich - W3ZJ

Don B wrote:
I just got around to installing PropView on my Vista64 pc and, upon attempting a path prediction, got the following error message:

"The program or feature: "&#92;??&#92;C:&#92;Progra~2&#92; ...&#92;Ioncap&#92;IONCAP.EXE" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the vendor ..."

Re: PropView & Vista 64

#72189

Yes, Ioncap is an old  16 bit application that won't run on on 64 bit Windows 7 either. However, both ICEPAC and VOCAP work ok. Try going to the "Prediction Tab" click "Config" and select either ICEPAC or VOCAP. I like ICEPAC.

73, Rich - W3ZJ

Don B wrote:

Show quoted text

I just got around to installing PropView on my Vista64 pc and, upon attempting a path prediction, got the following error message:

"The program or feature: "&#92;??&#92;C:&#92;Progra~2&#92; ...&#92;Ioncap&#92;IONCAP.EXE" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the vendor ..."

PropView & Vista 64

#72188

I just got around to installing PropView on my Vista64 pc and, upon attempting a path prediction, got the following error message:

"The program or feature: "&#92;??&#92;C:&#92;Progra~2&#92; ...&#92;Ioncap&#92;IONCAP.EXE" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the vendor ..."

I installed PropView in the same directory as all of my DXLab apps. I?searched the group's archive but could only find a series of posts dating back to Nov 2008 that?seems to have ended with a note from Dave (Message #62332) about?a " ...lost ... association for Windows Batch Files" that?was apparently a pc-specific problem, as PV was running fine on his (Dave's)?machine. I could not find anything else, and the above reference does not seem to be applicable(?) to my case. BTW, I am logged-in as Admin. Would switching to VoaCap be a viable option or is there some other issue I should be looking into?

73,
Don W5FKX

[Non-text portions of this message have been removed]

Re: FW: Re: Windows 7 Resend with Spell Check auto on now :-)

#72187

As I said Gil the Keyspan 19HS serial port converter is working OK with a VIsta driver. However, when I initially set it up I was using the USB converter for commander and Win 7 did blue screen once with an event log entry showing that the problem was the 19HS driver. So, I switched the ports around so that Commander is driven by a on board serial port and the 19HS is being used for rotor control which is a much lighter duty. I.E.: Just an occasional heading click, instead of a constant every 200 MS pounding. Since then it has been OK but I have to say that I do have some doubts about the integrity of that driver.

73, Rich - W3ZJ

rojomn wrote:

Show quoted text

I tried the hardware on my lap[top today. It did not work there either so it
is not the particular computer. It seems it is certain to be a driver
problem or perhaps the USB-Serial hardware itself. It makes me afraid to
even think of buying one of the USB devices until they have been well tested
and guaranteed to work with W7. I am going to search for PCI cards for the
desktop but would rather have the USB-Serial so I could use it on either
system. Anyhow it is not DXLABS code although I never thought it was.

FW: Re: Windows 7 Resend with Spell Check auto on now :-)

rojomn

#72186

I tried the hardware on my lap[top today. It did not work there either so it
is not the particular computer. It seems it is certain to be a driver
problem or perhaps the USB-Serial hardware itself. It makes me afraid to
even think of buying one of the USB devices until they have been well tested
and guaranteed to work with W7. I am going to search for PCI cards for the
desktop but would rather have the USB-Serial so I could use it on either
system. Anyhow it is not DXLABS code although I never thought it was.



Gil, W0MN 
N 44.082147  W 92.513085 1050' EN34rb
Hierro Candente, Batir de repente

Show quoted text

-----Original Message-----
From: rojomn [mailto:rojomn@...]
Sent: Monday, September 14, 2009 8:20 AM
To: 'dxlab@...'
Subject: RE: [dxlab] Re: Windows 7 Resend with Spell Check auto on now :-)

I have tried several different drivers. Some were recommended on Windows
Live and also the latest form the factory and none work on Windows 7 so it
seems I will need new hardware. I tried the device on my Laptop running
Vista and it works perfectly. Obviously there is a driver problem and I have
my doubts that a solution is coming any time soon. I even got a BSOD when
disconnected cable while program was running.



Gil, W0MN 
N 44.082147  W 92.513085 1050' EN34rb
Hierro Candente, Batir de repente

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of
rojomn
Sent: Sunday, September 13, 2009 9:34 PM
To: dxlab@...
Subject: RE: [dxlab] Re: Windows 7 Resend with Spell Check auto on now
:-)

Here is the driver usage document. It seems to indicate that it should
work
o W7. I will keep trying. I don't know if I will get anywhere but
according
to this it passes all of Microsoft testing.

I am on build 7600 of W7. If anyone has been able to make Commander
work on
W7 with USB-Serial what one did you use and did you have to upgrade the
drivers?


PL-2303 Driver Setup Installer, Prolific Edition
Setup Installer Revision Note History
=================================================

System Requirement:
  . Supports the following Windows OSes:
	- Windows 98SE
	- Windows ME
	- Windows 2000 SP4
	- Windows XP SP2 and above (32 & 64 bit)
	- Windows Server 2003 (32 & 64 bit)
	- Windows Server 2008 (32 & 64 bit)
	- Windows Vista (32 & 64 bit)
	- Windows 7 (32 & 64 bit)
    	  NOTE: For Windows 7, please use RC build 7100 or above.
  . USB host controller
  . Device using PL-2303H/HX/X version chip


Supported device ID and product strings:
  . VID_067B&PID_2303 for "Prolific USB-to-Serial Comm Port"


Release Notes:
---------------
PL2303 Driver Installer v1.0.5.18
  Changes from Installer v1.0.3.11:
    . XP/2K/2003 (WDM Driver) v2.0.9.122:
	- supports both 32 and 64 bit OS
	- pass Microsoft XP Windows Logo Test (WLK 1.4)
    . Vista/7/2008 (WDF Driver) v3.3.5.122:
	- pass Microsoft Vista/Win7 Logo Test (WLK 1.4)

   Installer & Build date: 1.0.5.18_20090723

   Language Support:
	- English (default)
	- Chinese (Traditional)
	- Chinese (Simplified)
	- Japanese



========================================
Prolific Technology Inc.






Gil, W0MN 
N 44.082147  W 92.513085 1050' EN34rb
Hierro Candente, Batir de repente
-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On BehalfOf
Gil rojomn
Sent: Sunday, September 13, 2009 7:25 PM
To: dxlab@...
Subject: RE: [dxlab] Re: Windows 7 Resend with Spell Check auto onnow
:-)

I did download the latest driver. Perhaps the driver is not correctbut
it
is digitally signed which is usually a good sign. Strange thatWindows
says
it is working correctly and that it can send but not receive. I amsure
people are going to have a lot of problems with hardware just as they
did
switching to Vista. This device is the only one I have that I havehad
trouble with other than the PCI Serial card which I have been using
since XP
but not drive seems to be available for W7. The XP driver worked for
Vista.
Sort of give the lie to the statement that if it worked in Vista it
will
work in W&. Where have I heard such things before. :-)

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On BehalfOf
aa6yq
Sent: Sunday, September 13, 2009 7:14 PM
To: dxlab@...
Subject: [dxlab] Re: Windows 7

My recollection is that "program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device" is the result of a serial port driver
defect. Try
downloading the manufacturers latest driver.

    73,

         Dave, AA6YQ

--- In dxlab@..., "Gil Charter" <rojomn@...> wrote:

I installed Windows 7 and am testing the programs. I am using ProLogic
USB-Serial converter with the automatically found by windowsdriver.



It partially works. I can change the radio frequency and switchTX/RX
but
it
fails to read the frequency form the radio.



I am using 4800 with 2 stop bits and hardware flow control buttrying
RTS
always on made no change.





The error log is attached.




  ----------


13-Sep-2009 19:49:58 > CI-V Commander version 7.9.2
13-Sep-2009 19:49:58 > App.Path        : C:&#92;Program Files(x86)&#92;DXLab
Suite&#92;Commander
13-Sep-2009 19:49:58 > App.exe         : CI-V Commander
13-Sep-2009 19:49:58 > Operating System: Vista build 7600
13-Sep-2009 19:49:58 > Country         : United States
13-Sep-2009 19:49:58 > Language        : English (United States)
13-Sep-2009 19:49:58 > DXLab Apps      :
13-Sep-2009 19:49:58 > LocaleInfo.Initialize: decimal symbol:
,
[ascii 44]
13-Sep-2009 19:49:58 > LocaleInfo.Initialize: digit groupingsymbol:
.
[ascii 46]
13-Sep-2009 19:49:58 > LocaleInfo.Initialize: date separator:
/
[ascii 47]
13-Sep-2009 19:49:58 > LocaleInfo.Initialize: time separator:
:
[ascii 58]
13-Sep-2009 19:49:58 > CIVMessages.Form_Load
13-Sep-2009 19:49:58 > Common.RestoreWindowPosition: CIVMessages,DualMonitor = True
13-Sep-2009 19:49:58 >    from registry = (9690, 5100, 9015, 5595)
13-Sep-2009 19:49:58 >    restored to   = (9690, 5100, 9015, 5595)
13-Sep-2009 19:49:58 >    WindowState   = 0
13-Sep-2009 19:49:58 > CIVMessages.Form_Load complete
13-Sep-2009 19:49:58 > CIVComm.Form_Load
13-Sep-2009 19:49:58 > CIVComm.Form_Load complete
13-Sep-2009 19:49:58 > UserCommandSequenceDefinition.Form_Load
13-Sep-2009 19:49:58 > Common.RestoreWindowPosition:UserCommandSequenceDefinition, DualMonitor = True
13-Sep-2009 19:49:58 >    from registry = (125, 125, 11265, 8670)
13-Sep-2009 19:49:58 >    restored to   = (125, 125, 11265, 8670)
13-Sep-2009 19:49:58 >    WindowState   = 0
13-Sep-2009 19:49:58 > UserCommandSequenceDefinition.Form_Loadcomplete
13-Sep-2009 19:49:58 > CIVMain.Form_load: forms loaded
13-Sep-2009 19:49:58 > CIVModule.Initialize: start
13-Sep-2009 19:49:58 > CIVModule.Initialize, CI-V Preamble =?(254),
CI-V
Postamble = ?(253), CI-V Success = ?(251), CI-V Failure = ú(250),
ControllerID = à(224)
13-Sep-2009 19:49:58 > CIVModule.Initialize, CI-V code lengths = 1,1, 1,
1, 1
13-Sep-2009 19:49:58 >    InterrogateKey = T
13-Sep-2009 19:49:58 > CIVConfig.Interrogation_Click,Interrogation.Value
= 1
13-Sep-2009 19:49:58 > CIVConfig.Interrogation_Click: interrogationenabled, interval =
13-Sep-2009 19:49:58 > CIVConfig.PollInterval_Change: poll interval=
10
13-Sep-2009 19:49:58 > CIVModule.LoadRadioInfo:Common.InitializeTooltips
is true
13-Sep-2009 19:49:58 > CIVModule.LoadRadioInfo: Tooltips Checkboxalready
checked; restoring tooltips
13-Sep-2009 19:49:58 > CIVModule.Initialize: radio info loaded
13-Sep-2009 19:49:58 > CIVModule.Initialize: commport initialized
13-Sep-2009 19:49:58 > CIVModule.Initialize: radix selectioncomplete
13-Sep-2009 19:49:58 > CIVModule.Initialize: radio setting =KENWOOD
13-Sep-2009 19:49:58 > CIVModule.Initialize: bands initialized
13-Sep-2009 19:49:58 > CIVModule.Initialize: User Sequences loaded
13-Sep-2009 19:49:58 > CIVModule.Initialize: CurrentXcvr = -1
13-Sep-2009 19:49:58 > ParallelPortModule.Setup
13-Sep-2009 19:49:58 > ParallelPortModule.SelectRadio, Transmitting=
False
13-Sep-2009 19:49:58 > ParallelPortModule.SelectRadio, Transmitting=
False
13-Sep-2009 19:49:58 > CIVModule.UpdateRadio: Start
13-Sep-2009 19:49:58 > CIVMain.AltFreqDisplay_Change,AltFreqDisplay
=
13-Sep-2009 19:49:58 > CIVMain.AltFreqDisplay_Change complete
13-Sep-2009 19:49:58 > CIVModule.LoadMemories
13-Sep-2009 19:49:58 >    memories
13-Sep-2009 19:49:58 >       mem = 1, freq = 3,584.50, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 2, freq = 7,070.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 3, freq = 10,140.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 4, freq = 14,070.50, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 5, freq = 18,106.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 6, freq = 21,070.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 7, freq = 24,919.50, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 8, freq = 28,120.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 9, freq = .00, mode = 2, filter=
,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 10, freq = .00, mode = 2, filter=
,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 11, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 12, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 13, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 14, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 15, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 16, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 17, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 18, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 19, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 20, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 21, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 22, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 23, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 24, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 25, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 26, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 27, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 28, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 29, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 30, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 31, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 32, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 33, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 34, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 35, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 36, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 37, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 38, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 39, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 40, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 41, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 42, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 43, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 44, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 45, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 46, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 47, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 48, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 49, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 50, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 51, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 52, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 53, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 54, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 55, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 56, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 57, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 58, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 59, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 60, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 61, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 62, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 63, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 64, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 65, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 66, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 67, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 68, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 69, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 70, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 71, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 72, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 73, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 74, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 75, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 76, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 77, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 78, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 79, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 80, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 81, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 82, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 83, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 84, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 85, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 86, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 87, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 88, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 89, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 90, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 91, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 92, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 93, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 94, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 95, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 96, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 97, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 98, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 99, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >       mem = 100, freq = , mode = 11, filter=
Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:58 >    mode selectors
13-Sep-2009 19:49:58 >       LSB
13-Sep-2009 19:49:58 >       USB
13-Sep-2009 19:49:58 >       AM
13-Sep-2009 19:49:58 >       CW
13-Sep-2009 19:49:58 >       RTTY
13-Sep-2009 19:49:58 >       FM
13-Sep-2009 19:49:58 >       WBFM
13-Sep-2009 19:49:58 >       CW-R
13-Sep-2009 19:49:58 >       RTTY-R
13-Sep-2009 19:49:58 >       PKT
13-Sep-2009 19:49:58 >       PKT-R
13-Sep-2009 19:49:59 > CIVModule.SetCurrentMemoryBank, theBank = 0
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: Memories loaded
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: Filter Settingsinitialized
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: found radio modelKENWOOD
13-Sep-2009 19:49:59 > CIVModule.ConfigureCommPort
13-Sep-2009 19:49:59 >    Model = KENWOOD
13-Sep-2009 19:49:59 >    RadioSerialPort(CurrentRadioIndex) = True
13-Sep-2009 19:49:59 > CIVComm.OpenPort, Port = 3
13-Sep-2009 19:49:59 > CIVModule.Initialize: commport configured
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: model-independentinitialization complete
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: supplier: K
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: sending Kenwood modelID
command
13-Sep-2009 19:49:59 > CIVModule.SendCommand: Asc = I D ;
13-Sep-2009 19:49:59 > CIVModule.SendCommand: Asc = I D ;
13-Sep-2009 19:49:59 > CIVModule.SetCurrentMemoryBank, theBank = 0
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: model-dependentinitialization complete
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: CmdBuffer initialized
13-Sep-2009 19:49:59 > CIVModule.RequestVFOB
13-Sep-2009 19:49:59 > CIVModule.EnqueueXcvrCmd: Command = Wait
13-Sep-2009 19:49:59 > CIVModule.EnqueueXcvrCmd: Command = RequestFrequency
13-Sep-2009 19:49:59 > CIVModule.EnqueueXcvrCmd: Command = Wait
13-Sep-2009 19:49:59 > CIVModule.EnqueueXcvrCmd: Command = RequestMode
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: Interrogationcomplete
13-Sep-2009 19:49:59 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:49:59 > CIVModule.ExecuteNextXcvrCmd: 18 [Wait] F =0,
M =
0, A = 0, A2 = 0
13-Sep-2009 19:49:59 > CIVModule.ExecuteNextXcvrCmd: 10 [RequestFrequency] F = 0, M = 0, A = 0, A2 = 0
13-Sep-2009 19:49:59 >    CIVFreqSync = true
13-Sep-2009 19:49:59 > CIVModule.SendCommand: Asc = F A ;
13-Sep-2009 19:49:59 > CIVModule.ExecuteNextXcvrCmd: 18 [Wait] F =0,
M =
0, A = 0, A2 = 0
13-Sep-2009 19:49:59 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:49:59 > CIVModule.ExecuteNextXcvrCmd: 11 [RequestMode] F =
0, M = 0, A = 0, A2 = 0
13-Sep-2009 19:49:59 > CIVModule.SendCommand: Asc = M D ;
13-Sep-2009 19:49:59 > CIVModule.InitializeMultiXcvr: CurrentXcvr =-
1
13-Sep-2009 19:49:59 > ParallelPortModule.SelectRadio, Transmitting=
False
13-Sep-2009 19:49:59 > CIVModule.Initialize: multiple transceiverstructures initialize
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: Start
13-Sep-2009 19:49:59 > CIVModule.LoadMemories
13-Sep-2009 19:49:59 >    memories
13-Sep-2009 19:49:59 >       mem = 1, freq = 3,584.50, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 2, freq = 7,070.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 3, freq = 10,140.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 4, freq = 14,070.50, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 5, freq = 18,106.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 6, freq = 21,070.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 7, freq = 24,919.50, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 8, freq = 28,120.00, mode = 1,filter =
, split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 9, freq = .00, mode = 2, filter=
,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 10, freq = .00, mode = 2, filter=
,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 11, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 12, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 13, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 14, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 15, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 16, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 17, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 18, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 19, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 20, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 21, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 22, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 23, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 24, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 25, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 26, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 27, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 28, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 29, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 30, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 31, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 32, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 33, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 34, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 35, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 36, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 37, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 38, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 39, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 40, freq = , mode = -1, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 41, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 42, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 43, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 44, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 45, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 46, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 47, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 48, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 49, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 50, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 51, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 52, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 53, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 54, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 55, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 56, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 57, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 58, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 59, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 60, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 61, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 62, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 63, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 64, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 65, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 66, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 67, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 68, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 69, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 70, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 71, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 72, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 73, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 74, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 75, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 76, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 77, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 78, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 79, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 80, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 81, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 82, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 83, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 84, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 85, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 86, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 87, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 88, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 89, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 90, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 91, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 92, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 93, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 94, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 95, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 96, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 97, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 98, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 99, freq = , mode = 11, filter =Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >       mem = 100, freq = , mode = 11, filter=
Wide,
split = 0, ham = 0, dual = 0
13-Sep-2009 19:49:59 >    mode selectors
13-Sep-2009 19:49:59 >       LSB
13-Sep-2009 19:49:59 >       USB
13-Sep-2009 19:49:59 >       AM
13-Sep-2009 19:49:59 >       CW
13-Sep-2009 19:49:59 >       RTTY
13-Sep-2009 19:49:59 >       FM
13-Sep-2009 19:49:59 >       WBFM
13-Sep-2009 19:49:59 >       CW-R
13-Sep-2009 19:49:59 >       RTTY-R
13-Sep-2009 19:49:59 >       PKT
13-Sep-2009 19:49:59 >       PKT-R
13-Sep-2009 19:49:59 > CIVModule.SetCurrentMemoryBank, theBank = 0
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: Memories loaded
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: Filter Settingsinitialized
13-Sep-2009 19:49:59 > CIVModule.UpdateRadio: found radio modelKENWOOD
13-Sep-2009 19:49:59 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:49:59 > CIVModule.ConfigureCommPort
13-Sep-2009 19:49:59 >    Model = KENWOOD
13-Sep-2009 19:49:59 >    RadioSerialPort(CurrentRadioIndex) = True
13-Sep-2009 19:49:59 > CIVComm.OpenPort, Port = 3
13-Sep-2009 19:50:00 > CIVModule.Initialize: commport configured
13-Sep-2009 19:50:00 > CIVModule.UpdateRadio: model-independentinitialization complete
13-Sep-2009 19:50:00 > CIVModule.UpdateRadio: supplier: K
13-Sep-2009 19:50:00 > CIVModule.UpdateRadio: sending Kenwood modelID
command
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I D ;
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I D ;
13-Sep-2009 19:50:00 > CIVModule.SetCurrentMemoryBank, theBank = 0
13-Sep-2009 19:50:00 > CIVModule.UpdateRadio: model-dependentinitialization complete
13-Sep-2009 19:50:00 > CIVModule.UpdateRadio: CmdBuffer initialized
13-Sep-2009 19:50:00 > CIVModule.RequestVFOB
13-Sep-2009 19:50:00 > CIVModule.Initialize: UpdateRadio complete
13-Sep-2009 19:50:00 > CIVModule.Initialize: devices loaded
13-Sep-2009 19:50:00 > CIVModule.EnqueueXcvrCmd: Command = Wait
13-Sep-2009 19:50:00 > CIVModule.EnqueueXcvrCmd: Command = RequestFrequency
13-Sep-2009 19:50:00 > CIVModule.EnqueueXcvrCmd: Command = Wait
13-Sep-2009 19:50:00 > CIVModule.EnqueueXcvrCmd: Command = RequestMode
13-Sep-2009 19:50:00 > CIVModule.Initialize: Caption updated
13-Sep-2009 19:50:00 > Common.RestoreWindowPosition: CIVMain,DualMonitor
= True
13-Sep-2009 19:50:00 >    from registry = (-20700, 5295, 8400,5576)
13-Sep-2009 19:50:00 >    restored to   = (-20700, 5295, 8400,5576)
13-Sep-2009 19:50:00 >    WindowState   = 0
13-Sep-2009 19:50:00 > CIVModule.Initialize: complete
13-Sep-2009 19:50:00 > ParallelPortModule.Initialize
13-Sep-2009 19:50:00 > CIVMain.Form_load: CIVModule intialized
13-Sep-2009 19:50:00 > CIVMain.Form_load: DDEServerModuleinitialized
13-Sep-2009 19:50:00 > DDEServer.LinkExecute: 000test
13-Sep-2009 19:50:00 > CIVMain.SetMainXmitFreq split disabled,XmitFreq =
000,000.00
13-Sep-2009 19:50:00 > CIVMain.SetMainRcvFreq, RcvFreq = 000,000.00
13-Sep-2009 19:50:00 > CIVMain.SetMainXmitFreq complete
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd: 18 [Wait] F =0,
M =
0, A = 0, A2 = 0
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd: 10 [RequestFrequency] F = 0, M = 0, A = 0, A2 = 0
13-Sep-2009 19:50:00 >    CIVFreqSync = true
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = F A ;
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd: 18 [Wait] F =0,
M =
0, A = 0, A2 = 0
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd: 11 [RequestMode] F =
0, M = 0, A = 0, A2 = 0
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = M D ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd, Idle Mode = 0
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I D ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd, Idle Mode = 1
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I F ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd, Idle Mode = 2
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I F ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd, Idle Mode = 3
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I F ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd, Idle Mode = 4
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = F B ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd, Idle Mode = 0
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I D ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > CIVModule.ExecuteNextXcvrCmd, Idle Mode = 1
13-Sep-2009 19:50:00 > CIVModule.SendCommand: Asc = I F ;
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020 in moduleCIVComm.ReadPort:
Error reading comm device
13-Sep-2009 19:50:00 > program error 8020

Re: broke freq

#72185

AA6YQ comments below-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
k9ct
Sent: Tuesday, September 15, 2009 11:46 AM
To: dxlab@...
Subject: [dxlab] Re: broke freq

Dave:

I have lots of them...> 1000 q's that were manual entries from the 70's. Is
there a way to do a field replace for delete?

Yes:

1. backup your log (Config window, Log tab, Backup button)

2. filter your Log Page Display to contain only those QSOs whose TX
frequency is to be cleared (perhaps by using a date range, or if your only
broken QSOs are one's with an invalid TX frequency, you can use the Broke
button in the Filter panel at the bottom of the Main window's "Log QSOs"
tab)

3. on the Main window's "Log QSOs" tab, click the Adv button to display the
"Advanced Sorts, Filters, and Modifers" window; in this window's "Modify
QSOs in Log Page Display" panel at the bottom of the Window,

3a. set the "Item ADIF field name" selector to Freq

3b. leave the "Item new value" box empty

3c. click the Mod button

    73,

       Dave, AA6YQ

Thanks, Craig K9CT

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

On the Main window's "Log QSOs" tab, click in the QSO panel's "tx freq"box,
strike CTRL-A to select all digits in the frequency, and strike the Delete
key. Then click the Save button.

   73,

        Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
k9ct
Sent: Monday, September 14, 2009 9:33 PM
To: dxlab@...
Subject: [dxlab] broke freq

I looked through the past posts but can't find. How do I change the txfreq
to null and the tx band stays put? The band is right but the freq does not
match the band. I can select the broken ones. I tested on a single record
but the band changed and then it started to recompute for the dx prefix!

Thanks, Craig K9CT

------------------------------------

Yahoo! Groups Links

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/14/09
11:36:00

------------------------------------

Yahoo! Groups Links

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/15/09
05:59:00

Re: Error with N1MM to DXKeeper Bridge

pa3c_aart

#72184

V9.9.0 works OK (except a small glitch).
I have written a few times to Matthias but no response.
I think the interface is not updated anymore.

Also N1MM have to update their UDP-broadcast to be ADIF-compliant.
Have sent a bug report but not solved yet.

Ah well can't have them all


73, Aart PA3C

Show quoted text

--- In dxlab@..., "unmoyex" <unmoyex@...> wrote:

Hi Dave,
Can you point me in the right direction with this problem?
73
Stan N1ZX




Stan,

I don't think the bridge program you mentioned is distributed with N1MM
Logger. A new N1MM database field was added for rovers. I suspect that you
need to contact the DXKeeper author.

This is the second time this was answered on this reflector.

John, K3CT

----- Original Message -----
From: "n1jon" <n1zx@...>
To: <N1MMLogger@...>
Sent: Sunday, September 13, 2009 1:39 PM
Subject: [N1MM] Bridge error occured


I am using N1MM Logger V 993 and the n1mm-dxk-gw-wu bridge to log from
N1MM to DXKeeper.
I get the following error.

Error occured:
Object variable or with block vriable not set.

Is there a fix for this?

73
Stan N1ZX



------------------------------------

To unsubscribe, send an email to:
N1MMLogger-unsubscribe@...

Yahoo! Groups Links

Re: broke freq

k9ct

#72183

Dave:

I have lots of them...> 1000 q's that were manual entries from the 70's. Is there a way to do a field replace for delete?

Thanks, Craig K9CT

Show quoted text

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

On the Main window's "Log QSOs" tab, click in the QSO panel's "tx freq" box,
strike CTRL-A to select all digits in the frequency, and strike the Delete
key. Then click the Save button.

   73,

        Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
k9ct
Sent: Monday, September 14, 2009 9:33 PM
To: dxlab@...
Subject: [dxlab] broke freq


I looked through the past posts but can't find. How do I change the tx freq
to null and the tx band stays put? The band is right but the freq does not
match the band. I can select the broken ones. I tested on a single record
but the band changed and then it started to recompute for the dx prefix!

Thanks, Craig K9CT



------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/14/09
11:36:00

Re: broke freq

#72182

On the Main window's "Log QSOs" tab, click in the QSO panel's "tx freq" box,
strike CTRL-A to select all digits in the frequency, and strike the Delete
key. Then click the Save button.

   73,

        Dave, AA6YQ

Show quoted text

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
k9ct
Sent: Monday, September 14, 2009 9:33 PM
To: dxlab@...
Subject: [dxlab] broke freq

I looked through the past posts but can't find. How do I change the tx freq
to null and the tx band stays put? The band is right but the freq does not
match the band. I can select the broken ones. I tested on a single record
but the band changed and then it started to recompute for the dx prefix!

Thanks, Craig K9CT

------------------------------------

Yahoo! Groups Links

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/14/09
11:36:00

Re: Updates Problem

Michael Morgan

#72181

Try selecting a different mirror in the top of the DXLablauncher config
window.

Michael, AA5SH

From: dxlab@... [mailto:dxlab@...] On Behalf Of
npalex@...
Sent: Monday, September 14, 2009 9:13 PM
To: dxlab@...
Subject: [dxlab] Updates Problem

I have just downloaded DXLAB Suite to a new Laptop. All went well, and all
modules work. However DX Launcher shows updates available. Exercising that
choice brings up menu showing DXKeeper and Pathfinder updates (red) clicking
Upgrade button results in an error message with final statement that the
"upgrade file could not be downloaded and abort"

The operating system is windows XP pro.

Need a suggestion on how to resolve.

Norm W4QN

Re: Solar Flux data

#72179

Please do the following, George

1. on the Config window's General tab, check the "Log debugging info" box

2. open one of your spot source windows, and issue the command

SH/WWV

(verify that the cluster responds by displaying the last few WWV spots)

3. on the Config window's General tab, uncheck the "Log debugging info" box

4. attach the errorlog.txt file from you SpotCollector folder to an email
message, and send it to me at aa6yq@...

Thanks...

   73,

       Dave, AA6YQ

Show quoted text

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
George Steube
Sent: Monday, September 14, 2009 8:59 PM
To: dxlab@...
Subject: RE: [dxlab]Solar Flux data


Hi Dave,
I noticed for about the last month that the solar flux data has not been
updating.  The last update I have is 8/31.  I have gone to the spot sources
and downloaded solar data, but the solar flux data in SC doesn't  add it.  I
checked the help files and there doesn't seem to be a way of turning it off
so what else could be set wrong?  Thanks.
George
W2GS
  -----Original Message-----
  From: dxlab@... [mailto:dxlab@...]On Behalf Of
Dave AA6YQ
  Sent: Sunday, September 13, 2009 12:45 PM
  To: dxlab@...
  Subject: RE: [dxlab] VISTA


    When you say that the Solar Flux window is not operating, do you mean
that
  this window does not appear, or that the window appears but contains no
  data?

  What happens if you type a

  SH/WWV/100

  command to one of your spot sources?

  73,

  Dave, AA6YQ

  -----Original Message-----
  From: dxlab@... [mailto:dxlab@...]On Behalf Of
  leuven0
  Sent: Sunday, September 13, 2009 7:33 AM
  To: dxlab@...
  Subject: [dxlab] VISTA

  Long time DxLab user. Just downloaded DxLab to a new computer with Vista
OS
  and everything seems to be operating except the Solar Flux window in
  Spotcollector and consequently Propview. Any suggestions?

  Fred WA3JJM

  ------------------------------------

  Yahoo! Groups Links

  No virus found in this incoming message.
  Checked by AVG - www.avg.com
  Version: 8.5.339 / Virus Database: 270.13.83/2353 - Release Date: 09/12/09
  06:37:00










------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/14/09
11:36:00

Re: Updates Problem

#72180

On the Launcher's Config window, try selecting a different distribution
site.

   73,

      Dave, AA6YQ

Show quoted text

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
npalex@...
Sent: Monday, September 14, 2009 10:13 PM
To: dxlab@...
Subject: [dxlab] Updates Problem

I have just downloaded DXLAB Suite to a new Laptop.  All went well, and all
modules work.  However DX Launcher shows updates available.  Exercising that
choice brings up menu showing DXKeeper and Pathfinder updates (red) clicking
Upgrade button results in an error message with final statement that the
"upgrade file could not be downloaded and abort"

The operating system is windows XP pro.

Need a suggestion on how to resolve.

Norm W4QN

------------------------------------

Yahoo! Groups Links

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/14/09
11:36:00

Updates Problem

[email protected]

#72178

I have just downloaded DXLAB Suite to a new Laptop.  All went well, and all modules work.  However DX Launcher shows updates available.  Exercising that choice brings up menu showing DXKeeper and Pathfinder updates (red) clicking Upgrade button results in an error message with final statement that the "upgrade file could not be downloaded and abort"

The operating system is windows XP pro.

Need a suggestion on how to resolve.

Norm W4QN

broke freq

k9ct

#72177

I looked through the past posts but can't find. How do I change the tx freq to null and the tx band stays put? The band is right but the freq does not match the band. I can select the broken ones. I tested on a single record but the band changed and then it started to recompute for the dx prefix!

Thanks, Craig K9CT

开云体育