开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
Date

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

Dave Bernstein
 

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




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

 

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




Work around for runtime error. CI-V Commander

Tom Brouard
 

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


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

Dave, AA6YQ
 

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
, 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
.

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 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 .


Re: CI-V Commander

Tom Brouard
 

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


Pathfinder Users: new EA and LU searches

Dave, AA6YQ
 

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 ; 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 ( ) 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 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 .


Re: CI-V Commander

Dave, AA6YQ
 

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.


CI-V Commander

Tom Brouard
 

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

 

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
<>




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
<>




Yahoo! Groups Sponsor

<
0063108:N/
A=613970/?> www.newaydirect.com

<
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
<> .







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



Your use of Yahoo! Groups is subject to


Re: CI-V Commander

Pagel, Mike
 

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
<>




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
<>




Yahoo! Groups Sponsor

<
A=613970/?> www.newaydirect.com

<
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
<> .


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





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




Re: CI-V Commander

Dave, AA6YQ
 

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





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: Printing QSL Cards

Tom Brouard
 

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


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


Re: Printing QSL Cards

Dave Bernstein
 

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


Re: CI-V Commander

Dave Bernstein
 

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


Printing QSL Cards

Tom Brouard
 

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


CI-V Commander

 

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


Re: ID Timer

Dave Bernstein
 

Principle: one gesture per state change.

In this case, the state change is "the beginning of a QSO". It should
not be necessary go convey this to a logging function with one
gesture (clicking the Start button), and to an ID timing function
with another gesture.

A separate ID timer is also one more window to manage, though DXLab
is not exactly stingy with windows...

73,

Dave, AA6YQ


--- In dxlab@y..., cherry@n... wrote:
Tom, I use this ID timer.

It is not connected to dxlab but is there any reason
for the timer to be connected to dxlab.
Regards, Jim FitzSimons W7ANF
Mailto:w7anf@q...

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

I was ragchewing this afternoon and thought that an ID timer
might
be a
feature worth discussing. I noticed while gabbing away that I
lost
track of
how long it had been since I said my callsign. Here is my
thought:

An option in the config screen to turn this feature on or off.

When the Start button is pressed in the capture screen of
DXKeeper
clock or
digital countdown image appears on the screen. (or can pop up say
after 9
minutes) and flashes or makes a sound to warn you to ID.

Press a restart button to countdown again, or press the log
button
to stop
counter and log QSO.

I imagine that all sorts of options can be thought of but is the
basic idea.

Does this sound like a feature that is worthwhile?

73

Tom KB2VNB


Re: DXCC Prefix

Dave Bernstein
 

Thanks, Robin. At the moment, anything that's not RA0, UA0, RA9, or
UA9 is classified as European Russia. I have several sources of more
recent prefix info to review, but haven't had time to peruse them and
update DXView's database.

I'll get to this eventually, but would be happy to guide anyone
interested in accelerating the process.

73,

Dave, AA6YQ

--- In dxlab@y..., RTrebil640@a... wrote:
A very small problem Dave. When I entered RU0B into DXView it
registered as European Russia. In fact it is a small island 77.5N,
82.5E (IOTA AS 057)and should register as UA0, Asiatic Russia
Robin gw3zcf