Date   

Re: Printing QSL Cards

Tom Brouard <stagehand@...>
 

Well that makes perfect sence to me. Thank you

73

Tom KB2VNB

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Monday, April 30, 2001 4:57 PM
To: dxlab@...
Subject: [dxlab] Re: Printing QSL Cards


Think of the four "quadrants" of an 8.5x11 sheet as being labeled A,
B, C, and D. The printing algorithm is set up so that after you slice
the printed sheets into four "decks", placing the A deck atop the B
deck atop the C deck atop the D deck will yield a correctly prefix-
sorted deck, ready to send to the outgoing QSL buro.

This algorithm produces the behaviour you noticed.

73,

Dave, AA6YQ

--- In dxlab@y..., "Tom Brouard" <stagehand@h...> wrote:
Hi Dave,

I printed 5 QSL cards in DXKeeper on the Epson 740 at work and
oddly enough
it printed three on one page and two on the second. They came out
fine but I
was curious about why it didn't print 4 on one page and 1 on the
second. I
expect to be printing more in the next few weeks I'll try printing
them in
different groups and let you know what happens.

This may already be on your list but I think it would be fun to be
able to
customize The QSL cards with graphics, fonts, colors etc.

73 Tom KB2VNB

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Re: CI-V Commander

Dave, AA6YQ <dhb@...>
 

I have a copy of the Omni VI Plus Computer Interface documentation, but see
no reference to these capabilities. If your documentation has this
information, please email or send me a copy and we'll give it a try.

My understanding is that there's a lot of variation between the PC
interfaces supported by different Yaesu radios. I was planning to start with
an FT1000D -- since that's what I'll likely buy next month.

I use a 706 for DX-peditions. Its amazing how rig control and logging
applications can make such a small radio almost indistinguishable
operationally from much larger boxes.

Eventually, I'd like to built a QRP CW/RTTY/PSK transceiver on a PCMCIA
card; that will make for a truly portable setup.

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Monday, April 30, 2001 5:42 PM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


Dave,

The Omni VI and VI Plus (models 563 and 564) can provide this
information. You have to poll for it, but it's there. If you are
interested in adding this as an enhancement when you start adding
more rigs to the list I can provide you with the command strings
and as always, testing.

BTW: I'm seriously considering getting the new Yaesu FT-817 for
QRP and portable operating. I just have to decide if I really want
it bad enough to part with the green stamps :-) If you add that
rig to the list you'll really be twisting my arm to buy it and a
laptop for my boat (a 30 foot cabin cruiser) and next years trip
to St. Maarten. Come on, I just need a couple of bruises, not too
many :-)

----
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave Bernstein [mailto:dhb@...]
> Sent: Monday, April 30, 2001 4:48 PM
> To: dxlab@...
> Subject: [dxlab] Re: CI-V Commander
>
>
> Unfortunately, the CI-V command set does not include a
> way for the
> radio to inform the application that
>
> - split mode is enabled or disabled
> - VFO A or B is enabled or disabled
> - dual watch is enabled or disabled (if supported)
>
> So keeping things "in sync" means not using the radio
> buttons for
> these functions.
>
> The next version of CI-V Commander will include additional
> diagnostics for this runtime error, which I've so far
> been unable to
> replicate.
>
> I'm currently in "get SpotCollector released to beta
> test" mode,
> meaning I'm putting off improvements and non-critical
> defect repairs
> to released applications. I do regard the DXKeeper
> "3037" runtime
> error as critical, and am working with Microsoft to
> track it down; I
> don't think its their defect, I just need a clue or two.
>
> 73,
>
> Dave, AA6YQ
>
>
> --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
> > Dave,
> >
> > I notice that when I click split in CI-V commander,
> it properly
> > puts the rig into split mode and onto VFO B. BTW, the split
> > functionality is very nice, I use it regularly. However, if I
> > later turn split off by pushing the button on my Omni
> 6+ instead
> > of clicking the checkbox in CI-V Commander, it does
> not deactivate
> > the split checkbox. I'm not sure if this is unique to
> the Omni 6+,
> > but you might want to check it out. FYI: I use it in
> polling mode
> > to avoid the occasional run time errors that still
> occur when it's
> > free running.
> >
> > -----
> > 73, Rich - W3ZJ
> > www.w3zj.com
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/




Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


Re: CI-V Commander

Richard B Drake
 

Dave,

It's on page 5-11 section 5.7, "Expanded Commands for Models 563
and 564 Only" (Mine is a 564). The other expanded commands include
"0Ch: Read Offset Frequency", "0Dh: Write Offset Frequency", "13h:
Announce Frequency of Current VFO (Optional Voice Board Required -
I don't have it)", and "16h: Set/Clear Transmit Mode". I would
take the pages out and scan them for you if I could figure out how
to take them out of the binder without damaging it.

"Command 17h: Return Transceiver Status"
Transceiver Response:

FE FE RA SA DATA FD

DATA is one byte with the following format:

Bit Position
0 Split status (0=OFF, 1=ON)
1 VFO Selected (0=A, 1=B)
2 TX Status (0=RX, 1=TX)
3 RIT Status (0=OFF, 1=ON)
4 XIT Status (0=OFF, 1=ON)
5 VOX Status (0=OFF, 1=ON)
6 LOCK Status (0=OFF, 1=ON)
7 NOT USED

Note: The command code is not echoed.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Monday, April 30, 2001 8:46 PM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


I have a copy of the Omni VI Plus Computer Interface
documentation, but see
no reference to these capabilities. If your
documentation has this
information, please email or send me a copy and we'll
give it a try.

My understanding is that there's a lot of variation
between the PC
interfaces supported by different Yaesu radios. I was
planning to start with
an FT1000D -- since that's what I'll likely buy next month.

I use a 706 for DX-peditions. Its amazing how rig
control and logging
applications can make such a small radio almost
indistinguishable
operationally from much larger boxes.

Eventually, I'd like to built a QRP CW/RTTY/PSK
transceiver on a PCMCIA
card; that will make for a truly portable setup.

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Monday, April 30, 2001 5:42 PM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


Dave,

The Omni VI and VI Plus (models 563 and 564) can provide this
information. You have to poll for it, but it's there.
If you are
interested in adding this as an enhancement when you
start adding
more rigs to the list I can provide you with the
command strings
and as always, testing.

BTW: I'm seriously considering getting the new Yaesu
FT-817 for
QRP and portable operating. I just have to decide if
I really want
it bad enough to part with the green stamps :-) If
you add that
rig to the list you'll really be twisting my arm to
buy it and a
laptop for my boat (a 30 foot cabin cruiser) and next
years trip
to St. Maarten. Come on, I just need a couple of
bruises, not too
many :-)

----
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave Bernstein [mailto:dhb@...]
> Sent: Monday, April 30, 2001 4:48 PM
> To: dxlab@...
> Subject: [dxlab] Re: CI-V Commander
>
>
> Unfortunately, the CI-V command set does not include a
> way for the
> radio to inform the application that
>
> - split mode is enabled or disabled
> - VFO A or B is enabled or disabled
> - dual watch is enabled or disabled (if supported)
>
> So keeping things "in sync" means not using the radio
> buttons for
> these functions.
>
> The next version of CI-V Commander will include additional
> diagnostics for this runtime error, which I've so far
> been unable to
> replicate.
>
> I'm currently in "get SpotCollector released to beta
> test" mode,
> meaning I'm putting off improvements and non-critical
> defect repairs
> to released applications. I do regard the DXKeeper
> "3037" runtime
> error as critical, and am working with Microsoft to
> track it down; I
> don't think its their defect, I just need a clue or two.
>
> 73,
>
> Dave, AA6YQ
>
>
> --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
> > Dave,
> >
> > I notice that when I click split in CI-V commander,
> it properly
> > puts the rig into split mode and onto VFO B. BTW,
the split
> > functionality is very nice, I use it regularly.
However, if I
> > later turn split off by pushing the button on my Omni
> 6+ instead
> > of clicking the checkbox in CI-V Commander, it does
> not deactivate
> > the split checkbox. I'm not sure if this is unique to
> the Omni 6+,
> > but you might want to check it out. FYI: I use it in
> polling mode
> > to avoid the occasional run time errors that still
> occur when it's
> > free running.
> >
> > -----
> > 73, Rich - W3ZJ
> > www.w3zj.com
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/




Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: CI-V Commander

Pagel, Mike <mpagel@...>
 

Hi Richard:

I'm following the Omni VI+ issue with interest, as I was the person who
supplied Dave with the copy of the portion of the 564's manual on software
issues.

The software link with my Omni VI+ is far better with Dave's software than
it is with LOGic.

73, de Mike, K9UW

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Tuesday, May 01, 2001 7:44 AM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


Dave,

It's on page 5-11 section 5.7, "Expanded Commands for Models 563
and 564 Only" (Mine is a 564). The other expanded commands include
"0Ch: Read Offset Frequency", "0Dh: Write Offset Frequency", "13h:
Announce Frequency of Current VFO (Optional Voice Board Required -
I don't have it)", and "16h: Set/Clear Transmit Mode". I would
take the pages out and scan them for you if I could figure out how
to take them out of the binder without damaging it.

"Command 17h: Return Transceiver Status"
Transceiver Response:

FE FE RA SA DATA FD

DATA is one byte with the following format:

Bit Position
0 Split status (0=OFF, 1=ON)
1 VFO Selected (0=A, 1=B)
2 TX Status (0=RX, 1=TX)
3 RIT Status (0=OFF, 1=ON)
4 XIT Status (0=OFF, 1=ON)
5 VOX Status (0=OFF, 1=ON)
6 LOCK Status (0=OFF, 1=ON)
7 NOT USED

Note: The command code is not echoed.

----
73, Rich - W3ZJ


-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Monday, April 30, 2001 8:46 PM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


I have a copy of the Omni VI Plus Computer Interface
documentation, but see
no reference to these capabilities. If your
documentation has this
information, please email or send me a copy and we'll
give it a try.

My understanding is that there's a lot of variation
between the PC
interfaces supported by different Yaesu radios. I was
planning to start with
an FT1000D -- since that's what I'll likely buy next month.

I use a 706 for DX-peditions. Its amazing how rig
control and logging
applications can make such a small radio almost
indistinguishable
operationally from much larger boxes.

Eventually, I'd like to built a QRP CW/RTTY/PSK
transceiver on a PCMCIA
card; that will make for a truly portable setup.

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Monday, April 30, 2001 5:42 PM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


Dave,

The Omni VI and VI Plus (models 563 and 564) can provide this
information. You have to poll for it, but it's there.
If you are
interested in adding this as an enhancement when you
start adding
more rigs to the list I can provide you with the
command strings
and as always, testing.

BTW: I'm seriously considering getting the new Yaesu
FT-817 for
QRP and portable operating. I just have to decide if
I really want
it bad enough to part with the green stamps :-) If
you add that
rig to the list you'll really be twisting my arm to
buy it and a
laptop for my boat (a 30 foot cabin cruiser) and next
years trip
to St. Maarten. Come on, I just need a couple of
bruises, not too
many :-)

----
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave Bernstein [mailto:dhb@...]
> Sent: Monday, April 30, 2001 4:48 PM
> To: dxlab@...
> Subject: [dxlab] Re: CI-V Commander
>
>
> Unfortunately, the CI-V command set does not include a
> way for the
> radio to inform the application that
>
> - split mode is enabled or disabled
> - VFO A or B is enabled or disabled
> - dual watch is enabled or disabled (if supported)
>
> So keeping things "in sync" means not using the radio
> buttons for
> these functions.
>
> The next version of CI-V Commander will include additional
> diagnostics for this runtime error, which I've so far
> been unable to
> replicate.
>
> I'm currently in "get SpotCollector released to beta
> test" mode,
> meaning I'm putting off improvements and non-critical
> defect repairs
> to released applications. I do regard the DXKeeper
> "3037" runtime
> error as critical, and am working with Microsoft to
> track it down; I
> don't think its their defect, I just need a clue or two.
>
> 73,
>
> Dave, AA6YQ
>
>
> --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
> > Dave,
> >
> > I notice that when I click split in CI-V commander,
> it properly
> > puts the rig into split mode and onto VFO B. BTW,
the split
> > functionality is very nice, I use it regularly.
However, if I
> > later turn split off by pushing the button on my Omni
> 6+ instead
> > of clicking the checkbox in CI-V Commander, it does
> not deactivate
> > the split checkbox. I'm not sure if this is unique to
> the Omni 6+,
> > but you might want to check it out. FYI: I use it in
> polling mode
> > to avoid the occasional run time errors that still
> occur when it's
> > free running.
> >
> > -----
> > 73, Rich - W3ZJ
> > www.w3zj.com
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/ <http://docs.yahoo.com/info/terms/>




Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/ <http://docs.yahoo.com/info/terms/>




Yahoo! Groups Sponsor

<http://rd.yahoo.com/M=190481.1393724.2979175.2/D=egroupmail/S=1700063108:N/
A=613970/?http://www.newaydirect.com> www.newaydirect.com

<http://us.adserver.yahoo.com/l?M=190481.1393724.2979175.2/D=egroupmail/S=17
00063108:N/A=613970/rand=664302776>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .


Re: CI-V Commander

Richard B Drake
 

Mike,

Thanks for doing that, it does indeed work well. One of the things
that makes it great is that Dave is so responsive to bug reports
and enhancement requests from his growing user community. Thus,
with all the input, the suite is quickly evolving into a super
package! We really make him work hard, don't we, for nothing more
in return than an occasional, "Thanks", for the great stuff!

----
73, Rich - W3ZJ

-----Original Message-----
From: Pagel, Mike [mailto:mpagel@...]
Sent: Tuesday, May 01, 2001 9:53 AM
To: 'dxlab@...'
Subject: RE: [dxlab] Re: CI-V Commander


Hi Richard:

I'm following the Omni VI+ issue with interest, as I
was the person who
supplied Dave with the copy of the portion of the 564's
manual on software
issues.

The software link with my Omni VI+ is far better with
Dave's software than
it is with LOGic.

73, de Mike, K9UW

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Tuesday, May 01, 2001 7:44 AM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


Dave,

It's on page 5-11 section 5.7, "Expanded Commands for Models 563
and 564 Only" (Mine is a 564). The other expanded
commands include
"0Ch: Read Offset Frequency", "0Dh: Write Offset
Frequency", "13h:
Announce Frequency of Current VFO (Optional Voice Board
Required -
I don't have it)", and "16h: Set/Clear Transmit Mode". I would
take the pages out and scan them for you if I could
figure out how
to take them out of the binder without damaging it.

"Command 17h: Return Transceiver Status"
Transceiver Response:

FE FE RA SA DATA FD

DATA is one byte with the following format:

Bit Position
0 Split status (0=OFF, 1=ON)
1 VFO Selected (0=A, 1=B)
2 TX Status (0=RX, 1=TX)
3 RIT Status (0=OFF, 1=ON)
4 XIT Status (0=OFF, 1=ON)
5 VOX Status (0=OFF, 1=ON)
6 LOCK Status (0=OFF, 1=ON)
7 NOT USED

Note: The command code is not echoed.

----
73, Rich - W3ZJ


-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Monday, April 30, 2001 8:46 PM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


I have a copy of the Omni VI Plus Computer Interface
documentation, but see
no reference to these capabilities. If your
documentation has this
information, please email or send me a copy and we'll
give it a try.

My understanding is that there's a lot of variation
between the PC
interfaces supported by different Yaesu radios. I was
planning to start with
an FT1000D -- since that's what I'll likely buy next month.

I use a 706 for DX-peditions. Its amazing how rig
control and logging
applications can make such a small radio almost
indistinguishable
operationally from much larger boxes.

Eventually, I'd like to built a QRP CW/RTTY/PSK
transceiver on a PCMCIA
card; that will make for a truly portable setup.

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Monday, April 30, 2001 5:42 PM
To: dxlab@...
Subject: RE: [dxlab] Re: CI-V Commander


Dave,

The Omni VI and VI Plus (models 563 and 564) can
provide this
information. You have to poll for it, but it's there.
If you are
interested in adding this as an enhancement when you
start adding
more rigs to the list I can provide you with the
command strings
and as always, testing.

BTW: I'm seriously considering getting the new Yaesu
FT-817 for
QRP and portable operating. I just have to decide if
I really want
it bad enough to part with the green stamps :-) If
you add that
rig to the list you'll really be twisting my arm to
buy it and a
laptop for my boat (a 30 foot cabin cruiser) and next
years trip
to St. Maarten. Come on, I just need a couple of
bruises, not too
many :-)

----
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave Bernstein [mailto:dhb@...]
> Sent: Monday, April 30, 2001 4:48 PM
> To: dxlab@...
> Subject: [dxlab] Re: CI-V Commander
>
>
> Unfortunately, the CI-V command set does not include a
> way for the
> radio to inform the application that
>
> - split mode is enabled or disabled
> - VFO A or B is enabled or disabled
> - dual watch is enabled or disabled (if supported)
>
> So keeping things "in sync" means not using the radio
> buttons for
> these functions.
>
> The next version of CI-V Commander will include additional
> diagnostics for this runtime error, which I've so far
> been unable to
> replicate.
>
> I'm currently in "get SpotCollector released to beta
> test" mode,
> meaning I'm putting off improvements and non-critical
> defect repairs
> to released applications. I do regard the DXKeeper
> "3037" runtime
> error as critical, and am working with Microsoft to
> track it down; I
> don't think its their defect, I just need a clue or two.
>
> 73,
>
> Dave, AA6YQ
>
>
> --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
> > Dave,
> >
> > I notice that when I click split in CI-V commander,
> it properly
> > puts the rig into split mode and onto VFO B. BTW,
the split
> > functionality is very nice, I use it regularly.
However, if I
> > later turn split off by pushing the button on my Omni
> 6+ instead
> > of clicking the checkbox in CI-V Commander, it does
> not deactivate
> > the split checkbox. I'm not sure if this is unique to
> the Omni 6+,
> > but you might want to check it out. FYI: I use it in
> polling mode
> > to avoid the occasional run time errors that still
> occur when it's
> > free running.
> >
> > -----
> > 73, Rich - W3ZJ
> > www.w3zj.com
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
<http://docs.yahoo.com/info/terms/>




Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
<http://docs.yahoo.com/info/terms/>




Yahoo! Groups Sponsor

<http://rd.yahoo.com/M=190481.1393724.2979175.2/D=egroupmail/S=170
0063108:N/
A=613970/?http://www.newaydirect.com> www.newaydirect.com

<http://us.adserver.yahoo.com/l?M=190481.1393724.2979175.2/D=egrou
pmail/S=17
00063108:N/A=613970/rand=664302776>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service
<http://docs.yahoo.com/info/terms/> .







To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/


CI-V Commander

Tom Brouard <stagehand@...>
 

Hi Dave,

The interface is great!!!!!.

I am experiencing a "run-time error '6' overflow" whenever I adjust anything
at the radio. I thought that you had covered this in a past email but I
could not find it.
(I somehow lost a chunk of old emails.)


73

Tom KB2VNB


Re: CI-V Commander

Dave, AA6YQ <dhb@...>
 

I'm glad the interface works.

As for the run-time error, you and Rich are the lucky two. Rich worked
around it by setting his radio's CI-V Transceive option to "off" and
configuring CI-V Commander to poll by checking the "Continuous Frequency and
Mode Interrogation" checkbox in the Radio panel of the General tab in the
Config window. Let me know if that doesn't work, and I'll immediately create
an instrumented version to track down this defect.

Out of curiousity, what baud rate are you running? If its 19200 or 9600, you
might try reducing it and see if that helps. If it works, this isn't a
solution -- just a workaround and a clue for me.

73,

Dave, AA6YQ

-----Original Message-----
From: Tom Brouard [mailto:stagehand@...]
Sent: Tuesday, May 01, 2001 6:06 PM
To: Dxlab
Subject: [dxlab] CI-V Commander


Hi Dave,

The interface is great!!!!!.

I am experiencing a "run-time error '6' overflow" whenever I adjust
anything
at the radio. I thought that you had covered this in a past email but I
could not find it.
(I somehow lost a chunk of old emails.)


73

Tom KB2VNB


Yahoo! Groups Sponsor

Click Here for Travel Deals!


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


Pathfinder Users: new EA and LU searches

Dave, AA6YQ <dhb@...>
 

Thanks to Fred K3ZO, Pathfinder can now search the online Spanish callbook
for EA, EA6, EA8, and EA9 callsigns. That's two new online callbook
discoveries in a row for Fred.

Tony, LU2DKN, recently reported the URL for an Argentine online callbook.
Thanks Tony!

To update your search library, terminate Pathfinder (if its running), and
then link to http://www.qsl.net/pathfinder/UpdateSearchLibrary.htm ; aftter
you restart Pathfinder, it will display the EA or LU callbook search buttons
if you enter EA/EA6/EA8/EA9 or LU callsigns respectively. The Pathfinder Web
Client ( http://www.qsl.net/pathfinder/WebClient/ ) has been updated with
the above addition; the only action required of its users is to click their
Browser's "refresh" button.

As always, reports of new online QSL sources or changes to existing sources
are greatly appreciated.

73,

Dave, AA6YQ

Pathfinder is a free program that makes it easy to find QSL information from
more than 100 web-accessible sources. See http://www.qsl.net/pathfinder/ for
additional information and download instructions. Or use the Pathfinder Web
Client -- its a little less flexible, but requires no downloading or
installation and runs in any Javascript-supporting browser on Windows,
MacOS, Linux, or Unix; just visit http://www.qsl.net/pathfinder/WebClient/ .


Re: CI-V Commander

Tom Brouard <stagehand@...>
 

At first try the workaround is working. I will have more time tomorrow to
run the radio longer to see what happens.

FYI. I had the com set at 9600 and the radio on Auto. Then I changed the
com to 19200 no change, set the radio to 19200, no change and then restored
to 9600 at the com and Auto at the radio. I have a Gateway 600 mhz pentium
3. I have 384 meg ram at 42% used. I run a cable modem and leave the
computer on 24/7. I also have an Intel anypoint network for the two kids
computer. I'm not sure any of this info helps but just in case it does here
it is.

73

Tom KB2VNB

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Wednesday, May 02, 2001 12:14 AM
To: dxlab@...
Subject: RE: [dxlab] CI-V Commander


I'm glad the interface works.

As for the run-time error, you and Rich are the lucky two. Rich worked
around it by setting his radio's CI-V Transceive option to "off" and
configuring CI-V Commander to poll by checking the "Continuous Frequency and
Mode Interrogation" checkbox in the Radio panel of the General tab in the
Config window. Let me know if that doesn't work, and I'll immediately create
an instrumented version to track down this defect.

Out of curiousity, what baud rate are you running? If its 19200 or 9600, you
might try reducing it and see if that helps. If it works, this isn't a
solution -- just a workaround and a clue for me.

73,

Dave, AA6YQ

-----Original Message-----
From: Tom Brouard [mailto:stagehand@...]
Sent: Tuesday, May 01, 2001 6:06 PM
To: Dxlab
Subject: [dxlab] CI-V Commander


Hi Dave,

The interface is great!!!!!.

I am experiencing a "run-time error '6' overflow" whenever I adjust
anything
at the radio. I thought that you had covered this in a past email but I
could not find it.
(I somehow lost a chunk of old emails.)


73

Tom KB2VNB


Yahoo! Groups Sponsor

Click Here for Travel Deals!


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Pathfinder Users: new DX-Central search, warning re EA search

Dave, AA6YQ <dhb@...>
 

As Ted W8TTS reported, there's been a change in DX-Central's search
database. Kelly KE9KD, who maintains the DX-Central site, confirms that it
was re-designed in early January. At that time
the individual "managers", "routes" and "bulletins" databases and were
combined, allowing a single search to query all three databases and produce
more user-friendly results.

A new search file named DX-Central.txt is now available; the DX-Central
Managers and DX-Centrol Routes are obsolete, and can be deleted from your
search folder.

To update your search library, follow the instructions in
http://www.qsl.net/pathfinder/UpdateSearchLibrary.htm , paying particular
attention to the text in red font, which directs you to the instructions for
assigning a search file to a key; these instructions are available via
http://www.qsl.net/pathfinder/AssignSearchButton.htm.

Warning: an EA ham examined the online EA callbook made accessible by
yesterday's search library update, and found many missing or incorrect
addresses. Caveat Emptor.


73,

Dave, AA6YQ

Pathfinder is a free program that makes it easy to find QSL information from
more than 100 web-accessible sources. See http://www.qsl.net/pathfinder/ for
additional information and download instructions. Or use the Pathfinder Web
Client -- its a little less flexible, but requires no downloading or
installation and runs in any Javascript-supporting browser on Windows,
MacOS, Linux, or Unix; just visit http://www.qsl.net/pathfinder/WebClient/ .


Work around for runtime error. CI-V Commander

Tom Brouard <stagehand@...>
 

So far the workaround for the runtime error is working well. I have not yet
received the error again.

I have had an odd thing happen with the curser. When I clicked on the up
arrow to change the band the bands kept changing even after I let go of the
mouse or moved the curser away from the arrow. This happened twice and each
time exiting and restarting the program seem to fix it.

I also thought of a few potential enhancements for you to consider. I always
have a copy of the band plan next to me. I have to check the frequencies to
be sure I have privileges on the band I am about to use. I thought that some
of us (with a failing memory like me) might want the option the customize
the frequencies that the CI-V commander will allow access and mode use. One
thought is when the ham band option is checked then the option to check a
particular license class (which will allow access only to those particular
privileges )pops up. And/or it can be completely user definable. Allowing
the user to program only the frequencies and modes that he or she wants to
work.


73
Tom KB2VNB


Re: Work around for runtime error. CI-V Commander

Richard B Drake
 

Yes, Logger has a user definable table called, "Band Plans". Here
you can define the frequency band limits and also specify mode,
which is quite useful. For example if you are operating in a band
segment normally used for PSK31 it knows to log PSK as the mode
even though the rig is in USB or LSB mode. This would indeed be a
useful addition to DXKeeper, even beyond defining the limits of a
license class.

----
73, Rich - W3ZJ

-----Original Message-----
From: Tom Brouard [mailto:stagehand@...]
Sent: Tuesday, May 08, 2001 9:14 AM
To: Dxlab
Subject: [dxlab] Work around for runtime error. CI-V Commander



So far the workaround for the runtime error is working
well. I have not yet
received the error again.

I have had an odd thing happen with the curser. When I
clicked on the up
arrow to change the band the bands kept changing even
after I let go of the
mouse or moved the curser away from the arrow. This
happened twice and each
time exiting and restarting the program seem to fix it.

I also thought of a few potential enhancements for you
to consider. I always
have a copy of the band plan next to me. I have to
check the frequencies to
be sure I have privileges on the band I am about to
use. I thought that some
of us (with a failing memory like me) might want the
option the customize
the frequencies that the CI-V commander will allow
access and mode use. One
thought is when the ham band option is checked then the
option to check a
particular license class (which will allow access only
to those particular
privileges )pops up. And/or it can be completely user
definable. Allowing
the user to program only the frequencies and modes that
he or she wants to
work.


73
Tom KB2VNB




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: Work around for runtime error. CI-V Commander

Dave Bernstein <dhb@...>
 

The first generation (monolithic) DXLab has these capabilities -- one
can define bands and band segments and establish frequency-based
modes; operating outside the band turns the VFO red. Some of this
functionality belongs in CI-V Commander, and some of it belongs in
DXKeeper; I'll add it to the list...

73,

Dave, AA6YQ

--- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Yes, Logger has a user definable table called, "Band Plans". Here
you can define the frequency band limits and also specify mode,
which is quite useful. For example if you are operating in a band
segment normally used for PSK31 it knows to log PSK as the mode
even though the rig is in USB or LSB mode. This would indeed be a
useful addition to DXKeeper, even beyond defining the limits of a
license class.

----
73, Rich - W3ZJ

-----Original Message-----
From: Tom Brouard [mailto:stagehand@h...]
Sent: Tuesday, May 08, 2001 9:14 AM
To: Dxlab
Subject: [dxlab] Work around for runtime error. CI-V Commander



So far the workaround for the runtime error is working
well. I have not yet
received the error again.

I have had an odd thing happen with the curser. When I
clicked on the up
arrow to change the band the bands kept changing even
after I let go of the
mouse or moved the curser away from the arrow. This
happened twice and each
time exiting and restarting the program seem to fix it.

I also thought of a few potential enhancements for you
to consider. I always
have a copy of the band plan next to me. I have to
check the frequencies to
be sure I have privileges on the band I am about to
use. I thought that some
of us (with a failing memory like me) might want the
option the customize
the frequencies that the CI-V commander will allow
access and mode use. One
thought is when the ham band option is checked then the
option to check a
particular license class (which will allow access only
to those particular
privileges )pops up. And/or it can be completely user
definable. Allowing
the user to program only the frequencies and modes that
he or she wants to
work.


73
Tom KB2VNB




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@y...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



Re: Work around for runtime error. CI-V Commander

Dave Bernstein <dhb@...>
 

I have seen the "out of control arrow" problem many times over the
years, but have never been able to track it down. Its not made an
appearance since I upgraded to Win2000. I'll ask Microsoft about it
the next time I touch base with them on the 3037 problem.

73,

Dave, AA6YQ

--- In dxlab@y..., "Tom Brouard" <stagehand@h...> wrote:

So far the workaround for the runtime error is working well. I have
not yet
received the error again.

I have had an odd thing happen with the curser. When I clicked on
the up
arrow to change the band the bands kept changing even after I let
go of the
mouse or moved the curser away from the arrow. This happened twice
and each
time exiting and restarting the program seem to fix it.

I also thought of a few potential enhancements for you to consider.
I always
have a copy of the band plan next to me. I have to check the
frequencies to
be sure I have privileges on the band I am about to use. I thought
that some
of us (with a failing memory like me) might want the option the
customize
the frequencies that the CI-V commander will allow access and mode
use. One
thought is when the ham band option is checked then the option to
check a
particular license class (which will allow access only to those
particular
privileges )pops up. And/or it can be completely user definable.
Allowing
the user to program only the frequencies and modes that he or she
wants to
work.


73
Tom KB2VNB


Re: Work around for runtime error. CI-V Commander

Richard B Drake
 

I too have seen the "out of control arrow" many times with many
different programs and it sure is annoying. However, about a month
ago I replaced my ailing old mechanical mouse with a new Microsoft
Optical mouse (which is the best thing since sliced bread), and
installed the new Intellipoint 3.2 software that came with it. I
have not seen the problem since then!

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Wednesday, May 09, 2001 12:34 AM
To: dxlab@...
Subject: [dxlab] Re: Work around for runtime error.
CI-V Commander


I have seen the "out of control arrow" problem many
times over the
years, but have never been able to track it down. Its
not made an
appearance since I upgraded to Win2000. I'll ask
Microsoft about it
the next time I touch base with them on the 3037 problem.

73,

Dave, AA6YQ

--- In dxlab@y..., "Tom Brouard" <stagehand@h...> wrote:

So far the workaround for the runtime error is
working well. I have
not yet
received the error again.

I have had an odd thing happen with the curser. When
I clicked on
the up
arrow to change the band the bands kept changing even
after I let
go of the
mouse or moved the curser away from the arrow. This
happened twice
and each
time exiting and restarting the program seem to fix it.

I also thought of a few potential enhancements for
you to consider.
I always
have a copy of the band plan next to me. I have to check the
frequencies to
be sure I have privileges on the band I am about to
use. I thought
that some
of us (with a failing memory like me) might want the
option the
customize
the frequencies that the CI-V commander will allow
access and mode
use. One
thought is when the ham band option is checked then
the option to
check a
particular license class (which will allow access
only to those
particular
privileges )pops up. And/or it can be completely user
definable.
Allowing
the user to program only the frequencies and modes
that he or she
wants to
work.


73
Tom KB2VNB

------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/



DXView 1.3.1 is available

Dave, AA6YQ <dhb@...>
 

I could not replicate this failure, Mark, but I did find a Control Array
without a 0'th element -- the rotator selection control. In DXView 1.3.1, I
added a 0'th element (which won't be visible) corresponding to "no rotator
selected". Please let me know if this eliminates the problem.

DXLab users: in this release, the "Plot Control" tab in the configuration
window has been relabed "Plot Filters" to better describe its function, and
a new "Mode Filter" has been added to the tab (joining the already-present
band and origin filters). Plot filters aren't of much use at present, but
will be quite helpful once SpotCollector (which I'm working furiously to
release) is sending DXCluster spots to DXView.

You can upgrade to DXView 1.3.1 by downloading
http://www.qsl.net/dxview/DXView131Update.exe - store it in your DXView
folder and execute it; you can then run the extracted DXView131.exe . Your
online help will be updated by this process.

73,

Dave, AA6YQ

-----Original Message-----
From: K7HPH [mailto:k7hph@...]
Sent: Tuesday, May 08, 2001 2:25 PM
To: dhb@...
Subject: Error Message on DXView


Hello:

When I try to bring up DXView I get the error message, "Runtime Error
Control Array Element "0" Dosen't Exist"
Can you tell me what I am doing wrong?

Thanks, Mark, K7HPH


DXKeeper 1.2.7 is available

Dave, AA6YQ <dhb@...>
 

In this version, striking CTRL-Enter in any QSO Capture Window textbox logs
the current information and clears all fields for the next QSO. I did not
add this functionality to fields in the main logging window; lets see how
this first change works.

DXKeeper 1.2.7 will be a pre-requisite for the forthcoming SpotCollector
release -- the Configuration screen's Awards tab is considered in
determining whether a spotted station is "needed", just as it determines
what QSOs you need confirmed. SpotCollector references these settings even
if DXKeeper is not running.

If you've already installed DXKeeper 1.1.1 or later, you can upgrade to
version 1.2.7 by downloading and then running
http://www.qsl.net/dxkeeper/DXKeeper127Update.exe .

73,

Dave, AA6YQ

-----Original Message-----
From: Dave Bernstein [mailto:dhb@...]
Sent: Friday, April 20, 2001 1:15 PM
To: dxlab@...
Subject: [dxlab] Re: So far so good


I understand Rich's suggestion to be "striking CTRL-Enter in any QSO
Capture Window textbox logs the current information and clears all
fields for the next QSO".

Should the same behavior apply in the main logging window?

Ron, I'm not sure what you mean by "a special button". Please
elaborate.

By the way, Ron, is DXView 1.2.9 controlling your rotator properly
through ARSWIN?

73,

Dave, AA6YQ

--- In dxlab@y..., "Ron Eberson" <zx@c...> wrote:
> You meen a special button for this Richard that likes great not
mistakes to
> the put two buttons good idea.
>
> Ron
>
>
> -----Oorspronkelijk bericht-----
> Van: Richard B Drake [mailto:rich@w...]
> Verzonden: vrijdag 20 april 2001 17:49
> Aan: Dxlab
> Onderwerp: [dxlab] So far so good
>
>
> Dave,
>
> So far the new versions of DXKeeper and DXView are running
> smoothly but we'll run them a little longer before giving a clean
> bill of health :-) I like the new functionality. One thing, I
> would like to see the Ctl+Enter logging function in the capture
> window work with the cursor in any field instead of just the
> callsign field. I often find my cursor in the Name or QTH fields
> and my hands on the keyboard when I'm ready to log a contact.
>
> -----
> 73, Rich - W3ZJ
> www.w3zj.com
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@y...
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


SpotCollector update

Dave Bernstein <dhb@...>
 

SpotCollector is now operational to the point where I am using it
with the other DXLab applications in daily service. I need to remove
some rough edges before releasing it to beta testing, but the end is
in sight. Check out the screen shot at
http://www.qsl.net/spotcollector/spotdatabase.jpg .

SpotCollector captures spots from the DX Summit spotting network (by
way of the #CQDX IRC channel) and up to four additional telnet-
accessible spotting networks. Spots are merged and stored in a
database on your PC, enabling you to monitor, sort, and filter them
in real time. A PC running Windows 95, 98, 2000, or NT with an SVGA
or better display is required. SpotCollector is free, and contains
no advertising. Commercial use is expressly forbidden.

Interoperation with DXLab applications:

- If you're using DXView, incoming spots will be plotted on its
world map

- If you're using DXKeeper, SpotCollector will color spot database
entries for stations with whom you need a QSO to achieve specified
DXing objectives

- If you're using CI-V Commander, clicking on a spot database entry
will QSY your Icom transceiver to the appropriate frequency and mode


73,

Dave, AA6YQ


Re: SpotCollector update

Ron Eberson <zx@...>
 

Looks great i look out to use it.

Ron

-----Oorspronkelijk bericht-----
Van: Dave Bernstein [mailto:dhb@...]
Verzonden: donderdag 17 mei 2001 6:19
Aan: dxlab@...
Onderwerp: [dxlab] SpotCollector update


SpotCollector is now operational to the point where I am using it
with the other DXLab applications in daily service. I need to remove
some rough edges before releasing it to beta testing, but the end is
in sight. Check out the screen shot at
http://www.qsl.net/spotcollector/spotdatabase.jpg .

SpotCollector captures spots from the DX Summit spotting network (by
way of the #CQDX IRC channel) and up to four additional telnet-
accessible spotting networks. Spots are merged and stored in a
database on your PC, enabling you to monitor, sort, and filter them
in real time. A PC running Windows 95, 98, 2000, or NT with an SVGA
or better display is required. SpotCollector is free, and contains
no advertising. Commercial use is expressly forbidden.

Interoperation with DXLab applications:

- If you're using DXView, incoming spots will be plotted on its
world map

- If you're using DXKeeper, SpotCollector will color spot database
entries for stations with whom you need a QSO to achieve specified
DXing objectives

- If you're using CI-V Commander, clicking on a spot database entry
will QSY your Icom transceiver to the appropriate frequency and mode


73,

Dave, AA6YQ


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Pathfinder Users: RW1QM is down for repairs

Dave, AA6YQ <dhb@...>
 

As you can see from http://www.ampr.spb.ru, RW1QM is recovering from
problems with his hosting server. Lets wish Alex a speedy recovery; until
then, the Octavia database is another excellent source of CIS QSO info. If
you haven't assigned Octavia to a search button, follow the instructions at
http://www.qsl.net/pathfinder/AssignSearchButton.htm; in step 4, select the
file Octavia.txt from your search folder.

73,

Dave, AA6YQ


Pathfinder is a free program that makes it easy to find QSL information from
more than 100 web-accessible sources. See http://www.qsl.net/pathfinder/ for
additional information and download instructions. Or use the Pathfinder Web
Client -- its a little less flexible, but requires no downloading or
installation and runs in any Javascript-supporting browser on Windows,
MacOS, Linux, or Unix; just visit http://www.qsl.net/pathfinder/WebClient/ .