Date   

Re: O.T. DM780 question

Tom Provost <ag2a@...>
 

The window in DM780. I didn't know the bridge had
a window. Sorry for the confusion.

At 04:15 PM 1/28/2011, you wrote:


AA6YQ commnets below
-----Original Message-----
From:
<mailto:dxlab%40yahoogroups.com>dxlab@yahoogroups.com
[mailto:dxlab@yahoogroups.com]On Behalf Of
Tom Provost
Sent: Friday, January 28, 2011 11:56 AM
To: <mailto:dxlab%40yahoogroups.com>dxlab@yahoogroups.com
Subject: [dxlab] O.T. DM780 question

I am using dm780 bridged to the dxlab suite (for everything except
digital). I needed to load a new copy of version 4.1 after a hard
drive problem. Everything is working okay but for one thing. I use to
hover the cursor over a call sign in the received window and a text
bubble would appear with log data on that station,if worked before
and if so what bands. If I have worked the station before,it shows
the check mark after the call but no text. If I haven't worked the
call before it should show DXCC entity and whether we worked before
and what bands. I can't find any option that will add this text
bubble. Any ideas out there?

When you say "I use to hover the cursor over a call sign in the received
window and a text
bubble would appear with log data on that station", are you referring to a
"received window" in DM780, or in the DM780-to-DXLab bridge?

73,

Dave, AA6YQ


SpotSpy 1.4.9 is available

supernova12de <dl9ho@...>
 

This release

- correctly handles alerts for JT6M (tnx to Aart, PA3C and Jose, N4BAA)

SpotSpy 1.4.9 is available via SpotSpy's update feature. For more
information about SpotSpy visit http://www.dl9ho.de/SpotSpy/SpotSpy.htm

Full release is available at http://www.dl9ho.de/adidl.html

SpotSpy's Bugtracking and Feature Request page:
http://www.dl9ho.personalabrechner.de/flyspray/

73,
Volker, DL9HO


Re: DxKeeper 9.2.7

it9fga <it9fga@...>
 

You are right Dave, sorry my mistake!

73's de

Giuseppe, IT9FGA

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

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
it9fga
Sent: Friday, January 28, 2011 6:37 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DxKeeper 9.2.7


Hi to all,

after log a qso, I can modify all fields except ADDRESS..sam on your side ?

A QSO's address item can be modified by enabling the QSL panel in the
"Log Panels" panel on the Configuration window's Log tab.

If yuo have "Require Edit to modify logged QSOs" enabled, you'll have to
click the Edit button before modifying the Address (or any other) item.

73,

Dave, AA6YQ


Re: DxKeeper and CTRL+C

it9fga <it9fga@...>
 

Hi Dave,

It seems CTRL+C works correctly only after hit EDIT button...'require EDIT to modify logged QSOs' box is enabled, but don't you think it's un-needed in order to simply copy a text ?

73's de

Giuseppe, IT9FGA

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

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
it9fga
Sent: Friday, January 28, 2011 6:39 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DxKeeper and CTRL+C


Hi to all,

CTRL+C not working into DXKeeper fields...wht not enabling this feature?

In which textboxes does using CTRL-C to copy the textbox contents to the
Windows Clipboard not work correctly?

73,

Dave, AA6YQ


Re: DXKeeper errorlog

Dave AA6YQ
 

AA6YQ coaments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Scott Stembaugh
Sent: Saturday, January 29, 2011 1:22 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXKeeper errorlog


I just noticed the title bar was asking me to look at the error log and here
is what I found:

28-Jan-2011 02:51:28 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 02:51:53 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:00:41 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:34:47 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:35:17 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:36:14 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null

That's a defect; it's corrected in the next release of DXKeeper, which
I've sent you via email. Please let me know how it goes.

Are the times local or UTC? I was doing some QSL chores last night.

Errorlog times are in UTC.

73,

Dave, AA6YQ


DXKeeper errorlog

Scott Stembaugh
 

I just noticed the title bar was asking me to look at the error log and here
is what I found:

28-Jan-2011 02:51:28 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 02:51:53 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:00:41 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:34:47 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:35:17 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null
28-Jan-2011 03:36:14 > program error 94 in module DXQSLModule.UpdateQSLInfo,
State = 5: Invalid use of Null


Are the times local or UTC? I was doing some QSL chores last night.

vy 73,
--scott N9LJX
------
N9LJX
radio.n9ljx@gmail.com


Re: Commander 8.9.5 Memory Save Bug (Data_U, Data_L)

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Laurie, VK3AMA
Sent: Saturday, January 29, 2011 12:46 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Commander 8.9.5 Memory Save Bug (Data_U, Data_L)


Hi Dave,

A small bug in Commander. If I am in Data_U or Data_L mode and save the
current freq/mode/filter settings to a memory slot, Data_U gets saved as
USB and Data_L as LSB. Other modes behave correctly.

Thanks, Laurie; I've emailed you a new version of Commander that corrects
this defect.

73,

Dave, AA6YQ


Commander 8.9.5 Memory Save Bug (Data_U, Data_L)

Laurie, VK3AMA <groups02@...>
 

Hi Dave,

A small bug in Commander. If I am in Data_U or Data_L mode and save the current freq/mode/filter settings to a memory slot, Data_U gets saved as USB and Data_L as LSB. Other modes behave correctly.

de Laurie, VK3AMA


Re: IC-7700 and Commander startup

ken_800
 

Thanks Dave. Makes me feel better knowing that its not operator error but Icom related.

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

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
ken_800
Sent: Friday, January 28, 2011 11:12 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] IC-7700 and Commander startup


I use the Commander with a couple of radios and I have so far noticed this
issue only with the IC-7700. If I am on VFO-A and whether I am transmitting
or receiving, if I happened to start Commander at that time, the radio
switches to VFO-B and then switches back to VFO-A. It switches back to VFO-A
after commander is fully started. This brief pause and switch to VFO-B
especially while transmitting is very dangerous. Am I missing any specific
setting in the commander config or the IC-7700 that makes this happen?

Icom transceivers to not provide a way for transceiver control
applications like Commander to read the frequency in VFO B. The only way to
do that is by directing the transceiver to "swap" VFOs, read the frequency
now in VFO A, and then "swap" the VFOs again to restore the two VFOs.
Commander does this on startup, which is what you're seeing above.

Don't start or reconfigure Commander while you are transmitting.
73,

Dave, AA6YQ


Re: IC-7700 and Commander startup

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
ken_800
Sent: Friday, January 28, 2011 11:12 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] IC-7700 and Commander startup


I use the Commander with a couple of radios and I have so far noticed this
issue only with the IC-7700. If I am on VFO-A and whether I am transmitting
or receiving, if I happened to start Commander at that time, the radio
switches to VFO-B and then switches back to VFO-A. It switches back to VFO-A
after commander is fully started. This brief pause and switch to VFO-B
especially while transmitting is very dangerous. Am I missing any specific
setting in the commander config or the IC-7700 that makes this happen?

Icom transceivers to not provide a way for transceiver control
applications like Commander to read the frequency in VFO B. The only way to
do that is by directing the transceiver to "swap" VFOs, read the frequency
now in VFO A, and then "swap" the VFOs again to restore the two VFOs.
Commander does this on startup, which is what you're seeing above.

Don't start or reconfigure Commander while you are transmitting.
73,

Dave, AA6YQ


IC-7700 and Commander startup

ken_800
 

I use the Commander with a couple of radios and I have so far noticed this issue only with the IC-7700. If I am on VFO-A and whether I am transmitting or receiving, if I happened to start Commander at that time, the radio switches to VFO-B and then switches back to VFO-A. It switches back to VFO-A after commander is fully started. This brief pause and switch to VFO-B especially while transmitting is very dangerous. Am I missing any specific setting in the commander config or the IC-7700 that makes this happen?

Regards,
Ken


need help testing new Commander feature for FT-1000D and FTDX-9000

Dave AA6YQ
 

The current public release of Commander provides "Dual Track" capability for
the Elecraft K3, Icom IC-7800, and Yeasu FTDX-9000. Each of these
transceivers provides a sub-receiver with a separate antenna input. "Dual
Track", when enabled, automatically forces the sub-receiver VFO to follow
changes in the Main VFO, facilitating diversity reception.

Since the Yaesu FT-1000D and FTDX-5000 also include a sub-receiver with a
separate antenna input, I have extended the next version of Commander to
support "Dual Track" for these transceivers. If you'd be willing to test
this capability with your FT-1000D or FTDX-5000, please let me know via
aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


DXLab support for the new IC-7600 and IC-7700 firmware releases

Dave AA6YQ
 

Late last year, Icom released new firmware for the IC-7800 that fulfills a
longstanding request from the DXing and contesting communities: the ability
for transceiver control applications to determine whether the transceiver is
in Split mode. This firmware update also enables a transceiver control
application to transmit CW from text without any external interface. I
extended DXLab's Commander (transceiver control) and WinWarbler (digital
modes, CW transmission, phone voice keyer) components to exploit these new
capabilities.

Recently, Icom has released new firmware updates for the IC-7600 and IC-7700
that include both the "read split" and "transmit CW from text" capabilities
described above. Jay W5JAY has confirmed that the current release of
Commander follows changes to Split made from his IC-7700's front panel. If
you have an IC-7600, have updated its firmware to the new version, and have
tested this capability with Commander, please let me know.

I'd also appreciate hearing from anyone who has used WinWarbler to transmit
CW using the the new firmware on an IC-7600 or IC-7700.

DXLab applications are completely free, and available via www.dxlabsuite.com

73,

Dave, AA6YQ


Re: DXView Ctrl-enterturns rotor on low bands

Dave AA6YQ
 

+++ AA6YQ comments below

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Chuck Chandler
Sent: Friday, January 28, 2011 5:51 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] DXView Ctrl-enterturns rotor on low bands


On Fri, Jan 28, 2011 at 3:55 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:



AA6YQ comments below
There are times when one is chasing DX on a band whose antenna is not
rotatable. If a needed station is announced on a band whose antenna is
rotatable, it's desireable to initiate the rotation without having to
first
QSY.
I agree. If I am tuning around on 160 and see a spot for a new one on 15,
then shift-entering that call will rotate. That is a good thing.


Referring to your priorities above, you can accomplish these by typing
a
callsign and either striking the Enter key (if you don't want rotation) or
striking CTRL-Enter if you do want rotation.
Is there a way to get no rotation but still get the capture window
pre-filled? I guess my objective is to not have to enter the call in
DXView, then if it is needed enter it again in Capture.

Of course, simply doing what I have been doing, entering it in Capture, does
the DXView thing to see if it is needed, and I can Control-enter or
alt-enter to rotate as needed. I guess the bottom line is that for my needs
I have been doing it the right way so far. I had this idea in the back of
my head that it was more 'proper' to use DXView for this purpose.

+++ You're right that by depressing the CTRL key after typing a callsing in
DXView, you can both rotate your antenna to its short-path heading and
populate DXKeeper's Capture window by strikign CTRL-Enter instead of Enter.
But rather than add more options to DXView to "disconnect" populating the
Capture window from antenna rotation, I suggest that you continue to use the
Capture window, as it provides all the functionality you seek.

73,

Dave, AA6YQ


Re: DXView Ctrl-enterturns rotor on low bands

Chuck, WS1L
 

On Fri, Jan 28, 2011 at 3:55 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:



AA6YQ comments below
There are times when one is chasing DX on a band whose antenna is not
rotatable. If a needed station is announced on a band whose antenna is
rotatable, it's desireable to initiate the rotation without having to first
QSY.
I agree. If I am tuning around on 160 and see a spot for a new one on 15,
then shift-entering that call will rotate. That is a good thing.


Referring to your priorities above, you can accomplish these by typing a
callsign and either striking the Enter key (if you don't want rotation) or
striking CTRL-Enter if you do want rotation.
Is there a way to get no rotation but still get the capture window
pre-filled? I guess my objective is to not have to enter the call in
DXView, then if it is needed enter it again in Capture.

Of course, simply doing what I have been doing, entering it in Capture, does
the DXView thing to see if it is needed, and I can Control-enter or
alt-enter to rotate as needed. I guess the bottom line is that for my needs
I have been doing it the right way so far. I had this idea in the back of
my head that it was more 'proper' to use DXView for this purpose.

73 de Chuck, WS1L




Reply to sender<aa6yq@ambersoft.com?subject=RE%3A%20%5Bdxlab%5D%20DXView%20Ctrl-enterturns%20rotor%20on%20low%20bands>| Reply
to group<dxlab@yahoogroups.com?subject=RE%3A%20%5Bdxlab%5D%20DXView%20Ctrl-enterturns%20rotor%20on%20low%20bands>| Reply
via web post<http://groups.yahoo.com/group/dxlab/post;_ylc=X3oDMTJxbnA0ajZqBF9TAzk3MzU5NzE0BGdycElkAzMwMDc4MzcEZ3Jwc3BJZAMxNzA1MDYzMTA4BG1zZ0lkAzg4OTI5BHNlYwNmdHIEc2xrA3JwbHkEc3RpbWUDMTI5NjI1MTcyOQ--?act=reply&messageNum=88929>| Start
a New Topic<http://groups.yahoo.com/group/dxlab/post;_ylc=X3oDMTJlbDdkYzExBF9TAzk3MzU5NzE0BGdycElkAzMwMDc4MzcEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwNmdHIEc2xrA250cGMEc3RpbWUDMTI5NjI1MTcyOQ-->
Messages in this topic<http://groups.yahoo.com/group/dxlab/message/88907;_ylc=X3oDMTM2M3M1aGthBF9TAzk3MzU5NzE0BGdycElkAzMwMDc4MzcEZ3Jwc3BJZAMxNzA1MDYzMTA4BG1zZ0lkAzg4OTI5BHNlYwNmdHIEc2xrA3Z0cGMEc3RpbWUDMTI5NjI1MTcyOQR0cGNJZAM4ODkwNw-->(
3)
Recent Activity:

- New Members<http://groups.yahoo.com/group/dxlab/members;_ylc=X3oDMTJmMjZuaTFkBF9TAzk3MzU5NzE0BGdycElkAzMwMDc4MzcEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwN2dGwEc2xrA3ZtYnJzBHN0aW1lAzEyOTYyNTE3Mjk-?o=6>
16
- New Polls<http://groups.yahoo.com/group/dxlab/polls;_ylc=X3oDMTJnc3ZnaWlmBF9TAzk3MzU5NzE0BGdycElkAzMwMDc4MzcEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwN2dGwEc2xrA3Zwb2xscwRzdGltZQMxMjk2MjUxNzI5>
1

Visit Your Group<http://groups.yahoo.com/group/dxlab;_ylc=X3oDMTJldm5yZTNjBF9TAzk3MzU5NzE0BGdycElkAzMwMDc4MzcEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTI5NjI1MTcyOQ-->
[image: Yahoo! Groups]<http://groups.yahoo.com/;_ylc=X3oDMTJkZmpodWoyBF9TAzk3MzU5NzE0BGdycElkAzMwMDc4MzcEZ3Jwc3BJZAMxNzA1MDYzMTA4BHNlYwNmdHIEc2xrA2dmcARzdGltZQMxMjk2MjUxNzI5>
Switch to: Text-Only<dxlab-traditional@yahoogroups.com?subject=Change+Delivery+Format:+Traditional>,
Daily Digest <dxlab-digest@yahoogroups.com?subject=Email+Delivery:+Digest>
Unsubscribe <dxlab-unsubscribe@yahoogroups.com?subject=Unsubscribe> Terms
of Use <http://docs.yahoo.com/info/terms/>
.




--


===================
Chuck Chandler
chandlerusm@gmail.com
===================


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


Re: DXView Ctrl-enterturns rotor on low bands

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Chuck Chandler
Sent: Friday, January 28, 2011 7:41 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXView Ctrl-enterturns rotor on low bands


My usualy method of checking calls for need has been to enter them in the
capture window and then see what DXView has to say. I recently decided to
try entering the call in DXView and control-entering. This should give me a
propagation lookup as well as a callbook lookup and populate the capture
window. It does all that, but it also turns my rotor to the proper heading.


All well and good, but the rig was on 160, and the beam is not that big!

So, I checked DXView config, made sure rotor control was set to only accept
directives for 20-10 meters. It was.

I guess DXView doesn't know what band I'm on, so it turns the rotor. I like
the ability to get everything ready for a station, but turning the rotor
this way and that might be a bit much. I see shift-enter does a qrz lookup.

Is there a way to get the benefits of qrz, propagation, and capture pre-fill
without the rotor needlessly hunting? Priority for me would be:

Capture pre-fill
rotor if 20-10 meters
Propagation
qrz lookup

Not a big deal, and others may use the features differently so may have
different needs.

After thinking about this a bit more, I don't think consulting the
"Directive Acceptance by Band" panel when the user strikes CTRL-Enter in the
Main window's Callsign box is appropriate.

There are times when one is chasing DX on a band whose antenna is not
rotatable. If a needed station is announced on a band whose antenna is
rotatable, it's desireable to initiate the rotation without having to first
QSY.

Referring to your priorities above, you can accomplish these by typing a
callsign and either striking the Enter key (if you don't want rotation) or
striking CTRL-Enter if you do want rotation.

73,

Dave, AA6YQ


Re: Spotcollector VE7CC connect

Art K6XT <k6xt@...>
 

I don't know where K6XT-10 comes from Iain. Something VE7CC is
assigning. However.......

Sure enough. I had K6XT-2 in VE7CC, K6XT in Spotcollector config.
Corrected and working now.

73 Art
Allison, Colorado
A glass is good, and a lass is good,
And a pipe to smoke in cold weather;
The world is good, and the people are good,
And we ’re all good fellows together.
John O’Keefe
Happy New Year!

On 2011-01-28 12:00, iain macdonnell - N6ML wrote:
Art,

It appears that for this to work properly, the callsign suffix used in
the SpotCollector source must be the same as the one used in CCUser. I
suspect the SpotCollector is looking at the prompt text for a matching
callsign. It appears that you have one configured as "K6XT-10" and the
other as "K6XT-2"

~iain / N6ML


On Fri, Jan 28, 2011 at 5:34 PM, Art K6XT<k6xt@arrl.net> wrote:
I'm (trying to) use VE7CC as a spot source using VE7CC program telnet
server so I have also the handy by-band view in VE7CC.

In this discussion I'm renaming Spotcollector's VE7CC window to xyl's
call W0MOE to avoid confusion. VE7CC means the actual VE7CC program.
W0MOE means Spotcollector's VE7CC window.

VE7CC telnet is ON, port 7300.

SC is set to 127.0.0.1 as instructed, also port 7300. I can see various
spots in W0MOE window. However they're not showing in SC's main display
window.

A secondary, perhaps connected, issue is SC's Spot Sources Hide button
is uniquely (other windows work 'right') partially inoperative. It will
expand SC's W0MOE window but not contract it as the others do. And its
LED is permanently yellow although the spots are showing up just as they
do in VE7CC program window.

Tertiarily, if thats a word, every few minutes W0MOE reconnects itself
to VE7CC, having suffered a "K6XT command error". Typical text shown below.

W0MOE outgoing spots are correctly routed to the VE7CC program and sent
out to the world.

Skimmer server is connected to port 7300 as well. Skimmer spots are
correctly displayed. I changed VE7CC and W0MOE to 7302, this made no
difference in the situation. And I think the number of connections is
unlimited.

Any hints what is happening to the invisible W0MOE spots?

[K6XT Command error. Note, these spots in W0MOE window do not appear in
Spotcollector's main window but they should.]
Hello>
DX de WA2AOG: 24892.0 VP8ORK wkd up 1 1723Z
DX de N3DG: 14013.0 FM/AI5P 1723Z
DX de K1CP: 24892.0 VP8ORK up 1 Tnx 1726Z
K6XT command error
K6XT-10 de VE7CC-1 28-Jan-2011 1725Z CCC>
*** Connected to: CC User
K6XT-10 de VE7CC-1 28-Jan-2011 1725Z CCC>
Welcome to CC User
Please enter your call:
login:
K6XT-2
K6XT-2 de VE7CC-1>
Hello>
DX de EA1EYG: 21024.0 VP8ORK 1st call 2 up low but clear TU 1728Z
--

73 Art
Allison, Colorado
A glass is good, and a lass is good,
And a pipe to smoke in cold weather;
The world is good, and the people are good,
And we ’re all good fellows together.
John O’Keefe
Happy New Year!




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

Yahoo! Groups Links



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

Yahoo! Groups Links




Re: Thought

Paul M Dunphy
 

At 05:13 PM 1/28/2011, you wrote:

You can do this now by running Pathfinder, and selecting one of its
searches to be "automatic" when a callsign is selected in SpotCollector,
DXKeeper, DXView, or WinWarbler. To make the QRZ.com search automatic, for
example,

1. CTRL-Click Pathfinder's QRZ search button

2. in the Pathfinder Search window that appears, check the Auto box, and
then click the OK button. Now double-click a Spot Database entry, or click
on a QSO in the Log Page Display; Pathfinder should perform a QRZ lookup for
the selected callsign.

73,

Dave, AA6YQ

Thanks Dave! Works as you describe and is what I was looking for.

73, Paul VE1DX


Re: Spotcollector VE7CC connect

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
iain macdonnell - N6ML
Sent: Friday, January 28, 2011 2:01 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] Spotcollector VE7CC connect


Art,

It appears that for this to work properly, the callsign suffix used in
the SpotCollector source must be the same as the one used in CCUser.
I suspect the SpotCollector is looking at the prompt text for a matching
callsign.

Lee VE7CC insisted on this.
73,

Dave, AA6YQ


Re: O.T. DM780 question

Dave AA6YQ
 

AA6YQ commnets below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]On Behalf Of
Tom Provost
Sent: Friday, January 28, 2011 11:56 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] O.T. DM780 question


I am using dm780 bridged to the dxlab suite (for everything except
digital). I needed to load a new copy of version 4.1 after a hard
drive problem. Everything is working okay but for one thing. I use to
hover the cursor over a call sign in the received window and a text
bubble would appear with log data on that station,if worked before
and if so what bands. If I have worked the station before,it shows
the check mark after the call but no text. If I haven't worked the
call before it should show DXCC entity and whether we worked before
and what bands. I can't find any option that will add this text
bubble. Any ideas out there?

When you say "I use to hover the cursor over a call sign in the received
window and a text
bubble would appear with log data on that station", are you referring to a
"received window" in DM780, or in the DM780-to-DXLab bridge?

73,

Dave, AA6YQ

119221 - 119240 of 207995