Date   

Re: off-topic: new search engine Wolfram Alpha comes online at 0 UTC

Peter Laws / N5UWY
 

On Fri, May 15, 2009 at 14:20, Danny Douglas <n7dc@comcast.net> wrote:


Of course Hal will be able to ask and tell himself.  Brrrrrr.
"Daisy, Daisy ..."


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: off-topic: new search engine Wolfram Alpha comes online at 0 UTC

Danny Douglas <n7dc@...>
 

Amazing. If we were just being born now, we wouldnt have to learn much of anything. Just ask the computer. Of course after that, with no one learning how to do things/compute , there would be no further input to the data base. Of course Hal will be able to ask and tell himself. Brrrrrr.

Danny Douglas
N7DC
ex WN5QMX ET2US WA5UKR ET3USA
SV0WPP VS6DD N7DC/YV5 G5CTB

All 2 years or more (except Novice)
Pls QSL direct, buro, or LOTW preferred,
I Do not us, but as a courtesy do upload to eQSL for
those who do.

Moderator
DXandTALK
http://groups.yahoo.com/group/DXandTalk
DXandTALK@YAHOOGROUPS.COM

Moderator
Digital_modes
http://groups.yahoo.com/group/digital_modes/?yguid=341090159

----- Original Message -----
From: Dave Bernstein
To: dxlab@yahoogroups.com
Sent: Friday, May 15, 2009 2:44 PM
Subject: [dxlab] off-topic: new search engine Wolfram Alpha comes online at 0 UTC





Check out the intro:

http://www.wolframalpha.com/screencast/introducingwolframalpha.html






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



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.12.31/2116 - Release Date: 05/15/09 06:16:00

----------


----------


No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.12.31/2116 - Release Date: 05/15/09 06:16:00


off-topic: new search engine Wolfram Alpha comes online at 0 UTC

Dave AA6YQ
 


Re: CAT Commands for the Yaesu FT-2000 and FT-2000D

Art Searle W2NRA <w2nra@...>
 

Hi John,

From: "John Bastin" <jbastin@sssnet.com>
What firmware revision is your FT2000? I noticed that there seemed to
be some changes after I did the Firmware Update to version 1.46 (and I
see there are a couple of new updates dated 5/8/2009 that I haven't
done).

73,
I'm using the latest update V0148-v11.53 and that is what I used in the CAT command files. There were 2 menu items added several updates ago and there were a couple of subtle menu changes as display features were added. IMO the latest update is the best so far.

73 Art W2NRA
"Keep to the Code!"
w2nra.com


Re: CAT Commands for the Yaesu FT-2000 and FT-2000D

John Bastin <jbastin@...>
 

On May 14, 2009, at 21:20 , Art Searle W2NRA wrote:

If anyone is interested I have prepared 5 CAT command sequence files for my
own use with the Yaesu FT-2000 and FT-2000D and the User-defined Control
feature of DXLab's Commander rig control software. These command sequence
files contain the commands to set the default Menu values for all 149 items
in the FT-2000's menu. Each file contains up to 32 commands that can be
directly loaded into a User-defined Control button. When loaded the note
next to each command is the same in appearance as the menu item on your rig.
You can use these commands as a starting point to customize your own menu
settings, in conjunction with the FT-2000 CAT Manual (bottom of page 6 thru
page 8, EX section). You can then store them in a Commander User- defined
Control button. You don't have to use all of the commands. Just the ones you
want to modify for your own Custom Menu Settings. Once customized and stored
it's reset your menu after a master reset on updating the rig's software.
If you need any help setting specific values please let me know.

The file is located at the top of the page at http://w2nra.com/
What firmware revision is your FT2000? I noticed that there seemed to be some changes after I did the Firmware Update to version 1.46 (and I see there are a couple of new updates dated 5/8/2009 that I haven't done).

73,

John K8AJS
jbastin@sssnet.com


CAT Commands for the Yaesu FT-2000 and FT-2000D

Art Searle W2NRA <w2nra@...>
 

If anyone is interested I have prepared 5 CAT command sequence files for my own use with the Yaesu FT-2000 and FT-2000D and the User-defined Control feature of DXLab's Commander rig control software. These command sequence files contain the commands to set the default Menu values for all 149 items in the FT-2000's menu. Each file contains up to 32 commands that can be directly loaded into a User-defined Control button. When loaded the note next to each command is the same in appearance as the menu item on your rig. You can use these commands as a starting point to customize your own menu settings, in conjunction with the FT-2000 CAT Manual (bottom of page 6 thru page 8, EX section). You can then store them in a Commander User-defined Control button. You don't have to use all of the commands. Just the ones you want to modify for your own Custom Menu Settings. Once customized and stored it's reset your menu after a master reset on updating the rig's software. If you need any help setting specific values please let me know.

The file is located at the top of the page at http://w2nra.com/

73 Art W2NRA
"Keep to the Code!"
w2nra.com


Re: DXKeeper Log Frequency Error

Dave AA6YQ
 

AA6yQ comments below
--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@...> wrote:

One more observation. I just changed the frequency precision to 2, and the frequency on the log page changed to 10.121. I changed back to 3, and there was no change.

That's correct. The valid range for the Precision setting is 3 to 6. If you specify a precision of less than 3, DXKeeper uses 3. This is described in the documentation.

I just opened a .txt file for VP5RZS, and find that in most cases, a band was recorded, but not an exact frequency.

By ".txt" file, are you referring to the ADIF file generated by N1MM that you imported into DXKeeper?
There are some cases of 21025, 28.0, 28, 14175, etc.

In an ADIF file, frequency tags that specify 21025 and 14175 are incorrect -- they mean 21025 mhz and 14175 mhz respectively.
I still don't know why the frequency is displaying incorrectly, but think that if we can just delete the frequency, and leave the band info, we should be OK. I'll give that a try, but would appreciate your comments on what seems to have gone wrong.

If the .txt file you refer to above is the ADIF file you imported, then what went wrong is that N1MM allowed you to log invalid band-frequency combinations.
The next release of DXKeeper flags an imported QSO as Broken if its band and frequency aren't consistent.
73,

Dave, AA6YQ

Bob WB2NVR

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@> wrote:

Dave -

I just noticed in my W2RZS log, in DXKeeper, the frequency is shown as 18.13497. In the configuration, the frequency precision is set to 3. I don't think that was always the case. Also noticed the frequency listed in SpotCollector is 14,071.0, which doesn't appear to be in the same format as DXKeeper.

Does this give you any clue?

Thanks!

Bob WB2NVR

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@> wrote:

Correct - all of the Q's have the incorrect frequency listed in the log. In some cases, the frequency is missing. As of the last time I opened this log, and made a backup, everything was OK. I use the same DXK program with 5 other logs, and all of the other's are OK. I don't know what I might have done to cause this, but all of the backups that I opened displayed the same problem. Other call signs open OK. Frequency is set to 3 decimal places.

Is there any way to correct the frequencies? The original log was imported from N1MM, and I still have that log.

Bob

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

What do you mean by "the frequency was not displayed correctly", Bob?

I did look in the ADIF file you sent me. The very first QSO -- YE8A -- has a band of 10m and a frequency of 28025 Mhz, which is incorrect; the frequency should be 28.025 Mhz. Perhaps other QSOs have this problem as well.

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "w2rzs" <wb2nvr@> wrote:

Hi Dave -

When I opened my log for VP5RZS to enter some QSL's, I noticed that the frequency was not displayed correctly for many (possibly all) Q's. I loaded a few backups, and they were all the same.

I'll email direct an ADIF export of the log, along with a number of backups and the Errorlog file. The backups don't have any additional Q's, just QSL information updates. DXKeeper version is 7.6.2.

If there is anything you can do to help resolve this, I'd really appreciate it. Other logs for other calls all seem to be OK.

Thanks for your help!

Bob WB2NVR


Re: DXKeeper Log Frequency Error

Dave AA6YQ
 

DXKeeper logs frequencies in megahertz because ADIF records frequencies in megahertz. Providing the option for DXKeeper to display frequencies in kilohertz is "on the list" -- but DXKeeper will continue to represent frequencies in the log file using megahertz.

The fact that DXKeeper can display frequencies with user-specified precision has nothing to do with your log containing QSOs whose frequencies are incorrect.

Please take a look in your N1MM-generated ADIF files at the QSOs in question to see what frequencies were imported into DXKeeper.

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@...> wrote:

Dave -

I just noticed in my W2RZS log, in DXKeeper, the frequency is shown as 18.13497. In the configuration, the frequency precision is set to 3. I don't think that was always the case. Also noticed the frequency listed in SpotCollector is 14,071.0, which doesn't appear to be in the same format as DXKeeper.

Does this give you any clue?

Thanks!

Bob WB2NVR

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@> wrote:

Correct - all of the Q's have the incorrect frequency listed in the log. In some cases, the frequency is missing. As of the last time I opened this log, and made a backup, everything was OK. I use the same DXK program with 5 other logs, and all of the other's are OK. I don't know what I might have done to cause this, but all of the backups that I opened displayed the same problem. Other call signs open OK. Frequency is set to 3 decimal places.

Is there any way to correct the frequencies? The original log was imported from N1MM, and I still have that log.

Bob

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

What do you mean by "the frequency was not displayed correctly", Bob?

I did look in the ADIF file you sent me. The very first QSO -- YE8A -- has a band of 10m and a frequency of 28025 Mhz, which is incorrect; the frequency should be 28.025 Mhz. Perhaps other QSOs have this problem as well.

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "w2rzs" <wb2nvr@> wrote:

Hi Dave -

When I opened my log for VP5RZS to enter some QSL's, I noticed that the frequency was not displayed correctly for many (possibly all) Q's. I loaded a few backups, and they were all the same.

I'll email direct an ADIF export of the log, along with a number of backups and the Errorlog file. The backups don't have any additional Q's, just QSL information updates. DXKeeper version is 7.6.2.

If there is anything you can do to help resolve this, I'd really appreciate it. Other logs for other calls all seem to be OK.

Thanks for your help!

Bob WB2NVR


Re: DXKeeper Log Frequency Error

Dave AA6YQ
 

AA6YQ comments below
--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@...> wrote:

Correct - all of the Q's have the incorrect frequency listed in the log. In some cases, the frequency is missing. As of the last time I opened this log, and made a backup, everything was OK.

Are you saying that your YE8A QSO's frequency was once correct in DXKeeper, but subsequently changed to 28025 MHZ?
I use the same DXK program with 5 other logs, and all of the other's are OK. I don't know what I might have done to cause this, but all of the backups that I opened displayed the same problem. Other call signs open OK. Frequency is set to 3 decimal places.

The "Frequency precision" setting governs how frequencies are displayed in the Log Page Display; it doesn't have any affect on how frequencies are stored in the log.
Is there any way to correct the frequencies? The original log was imported from N1MM, and I still have that log.

What frequency is recorded in the N1MM-generated ADIF record for your YE8A QSO?
Correcting frequency errors like that of your YE8A QSO require dividing the frequency by 1000; there is currently no way to apply such an action to all QSOs in the Log Page Display.
Are all of the incorrect frequencies similar -- off by a factor of 1000?
In those QSOs that are missing frequencies, are frequencies specified in the N1MM-generated ADIF file that you imported?
73,

Dave, AA6YQ


Re: DXKeeper Log Frequency Error

wb2nvr <wb2nvr@...>
 

One more observation. I just changed the frequency precision to 2, and the frequency on the log page changed to 10.121. I changed back to 3, and there was no change.

I just opened a .txt file for VP5RZS, and find that in most cases, a band was recorded, but not an exact frequency. There are some cases of 21025, 28.0, 28, 14175, etc. I still don't know why the frequency is displaying incorrectly, but think that if we can just delete the frequency, and leave the band info, we should be OK. I'll give that a try, but would appreciate your comments on what seems to have gone wrong.

Bob WB2NVR

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@...> wrote:

Dave -

I just noticed in my W2RZS log, in DXKeeper, the frequency is shown as 18.13497. In the configuration, the frequency precision is set to 3. I don't think that was always the case. Also noticed the frequency listed in SpotCollector is 14,071.0, which doesn't appear to be in the same format as DXKeeper.

Does this give you any clue?

Thanks!

Bob WB2NVR

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@> wrote:

Correct - all of the Q's have the incorrect frequency listed in the log. In some cases, the frequency is missing. As of the last time I opened this log, and made a backup, everything was OK. I use the same DXK program with 5 other logs, and all of the other's are OK. I don't know what I might have done to cause this, but all of the backups that I opened displayed the same problem. Other call signs open OK. Frequency is set to 3 decimal places.

Is there any way to correct the frequencies? The original log was imported from N1MM, and I still have that log.

Bob

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

What do you mean by "the frequency was not displayed correctly", Bob?

I did look in the ADIF file you sent me. The very first QSO -- YE8A -- has a band of 10m and a frequency of 28025 Mhz, which is incorrect; the frequency should be 28.025 Mhz. Perhaps other QSOs have this problem as well.

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "w2rzs" <wb2nvr@> wrote:

Hi Dave -

When I opened my log for VP5RZS to enter some QSL's, I noticed that the frequency was not displayed correctly for many (possibly all) Q's. I loaded a few backups, and they were all the same.

I'll email direct an ADIF export of the log, along with a number of backups and the Errorlog file. The backups don't have any additional Q's, just QSL information updates. DXKeeper version is 7.6.2.

If there is anything you can do to help resolve this, I'd really appreciate it. Other logs for other calls all seem to be OK.

Thanks for your help!

Bob WB2NVR


Re: DXKeeper Log Frequency Error

wb2nvr <wb2nvr@...>
 

Dave -

I just noticed in my W2RZS log, in DXKeeper, the frequency is shown as 18.13497. In the configuration, the frequency precision is set to 3. I don't think that was always the case. Also noticed the frequency listed in SpotCollector is 14,071.0, which doesn't appear to be in the same format as DXKeeper.

Does this give you any clue?

Thanks!

Bob WB2NVR

--- In dxlab@yahoogroups.com, "wb2nvr" <wb2nvr@...> wrote:

Correct - all of the Q's have the incorrect frequency listed in the log. In some cases, the frequency is missing. As of the last time I opened this log, and made a backup, everything was OK. I use the same DXK program with 5 other logs, and all of the other's are OK. I don't know what I might have done to cause this, but all of the backups that I opened displayed the same problem. Other call signs open OK. Frequency is set to 3 decimal places.

Is there any way to correct the frequencies? The original log was imported from N1MM, and I still have that log.

Bob

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

What do you mean by "the frequency was not displayed correctly", Bob?

I did look in the ADIF file you sent me. The very first QSO -- YE8A -- has a band of 10m and a frequency of 28025 Mhz, which is incorrect; the frequency should be 28.025 Mhz. Perhaps other QSOs have this problem as well.

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "w2rzs" <wb2nvr@> wrote:

Hi Dave -

When I opened my log for VP5RZS to enter some QSL's, I noticed that the frequency was not displayed correctly for many (possibly all) Q's. I loaded a few backups, and they were all the same.

I'll email direct an ADIF export of the log, along with a number of backups and the Errorlog file. The backups don't have any additional Q's, just QSL information updates. DXKeeper version is 7.6.2.

If there is anything you can do to help resolve this, I'd really appreciate it. Other logs for other calls all seem to be OK.

Thanks for your help!

Bob WB2NVR


Re: DXKeeper Log Frequency Error

wb2nvr <wb2nvr@...>
 

Correct - all of the Q's have the incorrect frequency listed in the log. In some cases, the frequency is missing. As of the last time I opened this log, and made a backup, everything was OK. I use the same DXK program with 5 other logs, and all of the other's are OK. I don't know what I might have done to cause this, but all of the backups that I opened displayed the same problem. Other call signs open OK. Frequency is set to 3 decimal places.

Is there any way to correct the frequencies? The original log was imported from N1MM, and I still have that log.

Bob

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

What do you mean by "the frequency was not displayed correctly", Bob?

I did look in the ADIF file you sent me. The very first QSO -- YE8A -- has a band of 10m and a frequency of 28025 Mhz, which is incorrect; the frequency should be 28.025 Mhz. Perhaps other QSOs have this problem as well.

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "w2rzs" <wb2nvr@> wrote:

Hi Dave -

When I opened my log for VP5RZS to enter some QSL's, I noticed that the frequency was not displayed correctly for many (possibly all) Q's. I loaded a few backups, and they were all the same.

I'll email direct an ADIF export of the log, along with a number of backups and the Errorlog file. The backups don't have any additional Q's, just QSL information updates. DXKeeper version is 7.6.2.

If there is anything you can do to help resolve this, I'd really appreciate it. Other logs for other calls all seem to be OK.

Thanks for your help!

Bob WB2NVR


SpotSpy 1.2.6 is available

supernova12de <dl9ho@...>
 

This release

- comes with redesign of SpotSpy's configuration window (request FS#3,
tnx to Jose, N1BAA).

- provides the new textbox "Duration time" (configuration window, Alarms
tab), (request FS#13, tnx to Jose, N1BAA)

- provides the new selection hh:mm (configuration window, General tab,
Spottime format), (request FS#15, tnx to Koen, ON7RK)

- provides the ability to enter the End time for needed call signs
(configuration window, Needed call signs tab). Default is 2099-01-31.

Existing entries in needed callsigns list will be converted to
2098-01-31

- removes old entries from needed callsigns list when application starts

- expands Import of needed callsigns (Daily DX calendar added)

- expands import feature (425DXN and Daily DX calendar). End date will
be saved and displayed. Old entries will be removed automatically

- supports e-mail-alerts to multiple recipients. Use CC and/or BCC
(E-mail configruation window). Syntax is <dl9ho@anywhere.com>,
<dl9ho2@athome.net> (Request FS#7, tnx to Cliff, K3LL)

- uses SpotCollector's settings for qsy tranceiver if double clicked a
RTTY spot in SpotSpy's alert window (request FS#17, tnx to Eddie, G4KHG)

- updates the Online help

SpotSpy 1.2.6 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: az--path

Dave AA6YQ
 

I should point out that you can log both the antenna path (short or long) and azimuth via DXKeeper's Capture window and via WinWarbler's "QSO Info" panel. If DXView is running, these items will be initialized to the path and heading last sent to your rotator.

73,

Dave, AA6YQ

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

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] On Behalf Of Vlad
UA6JD
Sent: Thursday, May 14, 2009 3:46 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] az--path

Why not indicate azimuth box in DXKeeper Capture and in WinWarbler? In
DXView all indicate OK.

Doing that would expand the size of DXKeeper's Capture window and
WinWarbler's Main window to display information already presented by DXView.


73,

Dave, AA6YQ


Re: az--path

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] On Behalf Of Vlad
UA6JD
Sent: Thursday, May 14, 2009 3:46 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] az--path

Why not indicate azimuth box in DXKeeper Capture and in WinWarbler? In
DXView all indicate OK.

Doing that would expand the size of DXKeeper's Capture window and
WinWarbler's Main window to display information already presented by DXView.


73,

Dave, AA6YQ


Sorry_DXKeeper_pwr box

Vlad UA6JD <ua6jw@...>
 

this request send as error - this problem was fix a time ago,sorry

power box was all time 100 watts.
where setup for default to change power?
--
73 Vlad UA6JD


DXKeeper_pwr box

Vlad UA6JD <ua6jw@...>
 

power box was all time 100 watts.
where setup for default to change power?



--
73 Vlad UA6JD


az--path

Vlad UA6JD <ua6jw@...>
 

Why not indicate azimuth box in DXKeeper Capture and in WinWabler?
In DXView all indicate OK.



--
73 Vlad UA6JD


Re: DXKeeper Log Frequency Error

Dave AA6YQ
 

What do you mean by "the frequency was not displayed correctly", Bob?

I did look in the ADIF file you sent me. The very first QSO -- YE8A -- has a band of 10m and a frequency of 28025 Mhz, which is incorrect; the frequency should be 28.025 Mhz. Perhaps other QSOs have this problem as well.

73,

Dave, AA6YQ

--- In dxlab@yahoogroups.com, "w2rzs" <wb2nvr@...> wrote:

Hi Dave -

When I opened my log for VP5RZS to enter some QSL's, I noticed that the frequency was not displayed correctly for many (possibly all) Q's. I loaded a few backups, and they were all the same.

I'll email direct an ADIF export of the log, along with a number of backups and the Errorlog file. The backups don't have any additional Q's, just QSL information updates. DXKeeper version is 7.6.2.

If there is anything you can do to help resolve this, I'd really appreciate it. Other logs for other calls all seem to be OK.

Thanks for your help!

Bob WB2NVR


DXKeeper Log Frequency Error

Bob WB2NVR
 

Hi Dave -

When I opened my log for VP5RZS to enter some QSL's, I noticed that the frequency was not displayed correctly for many (possibly all) Q's. I loaded a few backups, and they were all the same.

I'll email direct an ADIF export of the log, along with a number of backups and the Errorlog file. The backups don't have any additional Q's, just QSL information updates. DXKeeper version is 7.6.2.

If there is anything you can do to help resolve this, I'd really appreciate it. Other logs for other calls all seem to be OK.

Thanks for your help!

Bob WB2NVR

137201 - 137220 of 205932