|
|
|
1
|
eHam Forums / Computers And Software / RE: Your thoughts on Ham Radio Deluxe 6.xx
|
on: Today at 05:07:52 PM
|
Used MixW for 4 years, then DX labs. Neither of them have direct support, which is not expected for a free product. Sure you have the Yahoo groups to ask your questions, but no comparison to calling someone who can solve your problem now. I have spent many hours trying to solve problems with these other packages and days of waisted time waiting for Yahoo group help.
A search of Yahoo membership records shows no evidence of your having been a member of the DXLab Yahoo group. I review and respond to DXLab Yahoo group posts several times every day, and have no recollection of any post from you, much less a request for help that went unresolved. Reported defects in DXLab applications are given highest priority, and usually result in a corrected release within 24 hours. 73, Dave, AA6YQ
|
|
|
|
|
2
|
eHam Forums / DXing / RE: ARRL LoTW URL changes
|
on: Yesterday at 07:09:07 PM
|
Hi all, It looks like the ARRL has indeed rolled back the changes. Using the original https://p1k.arrl.org URLs in HRD 5, I was able to upload my contacts moments ago that I did since May 12. (The world has not ended, woohoo!) I did notice one oddity not related to HRD 5. If you go to the web site itself using the p1k.arrl.org, you'll be able to log in, but if you try to click on Your QSOs, it kicks you out back to the login screen, but this time the login screen has the lotw.arrl.org URL and if you log in there, all works fine. Probably an SSL thing. My thanks to ARRL for rolling this back while everyone is probably involved in supporting Dayton and not taking a position that would have required those running old/unsupported logging programs to switch or upgrade. (I'm sure there will be a change in LOTW in the future that will require me to upgrade, but something this arbitrary doesn't seem like it should be it). The ARRL did not "roll back" the URL change. They reverse engineered the unusual scheme employed by HRD 5 to access LotW, and then made changes to enable that unusual scheme to work.
|
|
|
|
|
4
|
eHam Forums / DXing / RE: ARRL LoTW URL changes
|
on: May 15, 2013, 04:52:48 PM
|
|
My understanding is this:
Yesterday afternoon, LotW Management changed the LotW Server's URL address. They did this in a way that they expected would be transparent, and so issued no warning to developers of applications that interoperate with the LotW. However, the change was not transparent, causing many such applications to lose the ability to interact with the LotW Server.
To compensate for the URL change, I released a new version of DXKeeper (DXLab's logging component) last night.
This morning, LotW Management identified the error that prevented the Server's old URL from continuing to work. That error has been corrected, so all applications that could previously interoperate with the LotW Server should again be able to do so.
73,
Dave, AA6YQ
|
|
|
|
|
6
|
eHam Forums / DXing / RE: So who here's going to Dayton?
|
on: May 03, 2013, 06:44:09 PM
|
I will be attending Dayton for the first time. I'll mostly be in the DXLab booth (EH0539), except Sunday morning at 9 am when I'll be presenting "DXing with DXLab". Look forward to finally meeting you and seeing your presentation. I'm intrigued at the notion of using the spot database for researching long-term operating patterns rather than just as a means of coarse/fine filtering and would like to see it actually in operation. East hall is back-end of beyond, so I'll get there eventually on Friday <grin>. I'm doing exactly that now in my quest to work VU7 on 12m and 10m: http://www.dxlabsuite.com/spotcollector/VU7.jpg 73, Dave, AA6YQ
|
|
|
|
|
7
|
eHam Forums / DXing / RE: So who here's going to Dayton?
|
on: May 03, 2013, 02:50:28 PM
|
|
I will be attending Dayton for the first time. I'll mostly be in the DXLab booth (EH0539), except Sunday morning at 9 am when I'll be presenting "DXing with DXLab".
73,
Dave, AA6YQ
|
|
|
|
|
8
|
eHam Forums / DXing / RE: What the H***
|
on: May 02, 2013, 02:35:25 PM
|
The sunspot number is 151 The flux is 159
And the bands seem DEAD here !
>>>The A and K indices were rather high (indicating geomagnetic disruption), but are dropping. 73, Dave, AA6YQ
|
|
|
|
|
9
|
eHam Forums / DXing / RE: VU7KV
|
on: May 01, 2013, 03:42:04 PM
|
It would be a small miracle to work him with a beam from Colorado, especially if I have to compete with all those marathoners.
Familiarize yourself with both the short-path and long-path openings for the bands on which you're QRV, and the need for a miracle will be diminished. 73, Dave, AA6YQ
|
|
|
|
|
10
|
eHam Forums / DXing / RE: DX Cluster for Long Island
|
on: April 29, 2013, 05:00:17 PM
|
To my knowledge you could use any cluster and the results will be the same. I use HB9DRV-9 and I see everything.
The results will be the same if you ignore time. European clusters generally report European DX faster than clusters on other continents, Asian clusters generally report Asian DX faster than clusters on other continents, etc. I have seen some clusters provide as much as two minutes of "early access" compared to other clusters. If you didn't find the DX before they were spotted, there can be a big difference in outcome between being able to make a call within the first 30 seconds after the first spot and showing up later minutes later with the pileup already in high gear. Snooze, you lose. 73, Dave, AA6YQ
|
|
|
|
|
11
|
eHam Forums / DXing / RE: Anyone ever work Chechnya?
|
on: April 21, 2013, 04:14:40 PM
|
In light of recent events (and without getting into those events on here), I was wondering if any of you have worked it? I realize it counts for nothing as far as DXCC goes (other than Russia). Just curious. I would have to dig deep into my old cards from the USSR days to see if I came even remotely close.....the surrionding republics of Georgia, Armenia and Azerbaijan I am sure many of you have, as do I, but Chechnya has a spotlight on it once again....What say you?....any of you work this once unknown (to most of us) part of Russia prior to it being in the news?
Stations operating in the "Republic of Chechnya", Oblast 96, are assigned Russian callsigns ending in 6P or 7P. I have no QSOs with stations in Chechnya. 73, Dave, AA6YQ
|
|
|
|
|
12
|
eHam Forums / DXing / RE: 10 MTR LONGPATH QRP
|
on: April 15, 2013, 06:52:07 PM
|
Nice job! I've worked both in the same day on 10M LP but there is no way to predict that opening. You just have to spend a lot of time on 10 meters.
Not true, as this DXLab propagation forecast demonstrates. 73, Dave, AA6YQ We've had quite a few 10 meter long path discussions during the past few years and I think most following the topic realized I meant that one can't predict a long path opening to SE Asia for a given day with any high level of confidence, and not that a prediction can't be made. I have a feeling you understood that, too, Dave, but why waste an opportunity to plug your program? You posted "there is no way to predict that opening", but now you claim that I must have known you meant "there is no way to predict that opening with any high level of confidence"? And you're castigating me for promoting software that demonstrably does what you claimed can't be done, and is totally free? Is this not a forum for discussing effective DXing? Sure, the propagation programs can make predictions but how accurate are they?
Accurate enough to help me get from a novice ticket to the top of Honor Roll in two solar cycles. Propagation prediction, HF beacon monitoring, and the ability to rapidly analyze DX spot data combine to identify likely openings. Knowledge of likely openings combined with knowledge of the operating habits of needed DX stations yields faster award progress. 73, Dave, AA6YQ
|
|
|
|
|
14
|
eHam Forums / DXing / RE: How Many Active Ham Loggers?
|
on: April 13, 2013, 06:15:39 PM
|
I've been seeing a noticeable increase in Hams, particularly Internationals, that are using LOTW now. That's great! Only need to send a QSL if I want to. I'm seeing about 40%+ lately confirmed with LOTW. Had a guy in Venezuela yesterday that barely spoke english (I'm lucky I don't need to speak a foreign language) and had to work for a minute or more to get the contact. He was calling CQ and I just wanted to say HI - that I could hear him etc.. He posted that to eQSL and LOTW immediately. I was thinking he was using paper logs in the jungle or something  I'm seeing this more and more in the last few months. Don't know if it's just coincidence. I'm curious to see if the computer upgrade made a difference and what the next report of total users will be from LOTW. It's up nearly 4,000 users in the last 6 months, and I think those that join are the active ones we're likely to run across.. looking to complete awards, DX, Contests etc. LOTW is performing very well recently. The mail confirmation isn't a problem. Google and others use that mailed password for certain items. If they maintain their performance and highlight the process of getting approved a little clearer (like don't forget the last part about requesting the postcard), it should grow nicely (A few larger red highlighted areas.. Step #1, Step #2) Interesting note about 3rd party software having an issue. LotW's instability late last year was the result of its server running out of disk space, and of a long-latent defect that caused batches of uploaded QSOs in LotW's processing queue to be randomly dropped. When users discovered that QSOs were being dropped, they began re-uploading their QSOs, which increased the length of LotW's processing queue, which increased the time it took for LotW to acknowledge the acceptance of uploaded QSOs, which prompted more users to re-upload QSOs. There were no issues with 3rd party applications; it was the users of such applications who were able to detect that batches of uploaded QSOs were being dropped. 73, Dave, AA6YQ
|
|
|
|
|
15
|
eHam Forums / DXing / RE: How Many Active Ham Loggers?
|
on: April 12, 2013, 02:30:49 PM
|
I'm using HRD 6.0, and while it is not the be all and end all, I will stick with it as bugs are fixed and refinements integrated. It gives quite a few options of sorting data. One option that HRD gives you out of the box that a lot of people don't take advantage of is that it can directly interface MS SQL Server for your log. By default it uses something like an access database. Not sure if that storage is proprietary. Once you have installed MSSQL and configured HRD to use it, you can use SQL queries against your logs. Once you learn how to create SQL queries, there is no data combination that can't be extracted. SQL, of course, has it's own learning curve. Not for the timid, but it's an option often overlooked. DXLab has long provided the ability to filter (query) and sort log data via SQL. Since these operations cannot damage the data, there is no reason to be timid, and most users aren't. Buttons and checkboxes are provided for common filtering operations, e.g. by-callsign, by-entity, by-band, by-mode. 73, Dave, AA6YQ
|
|
|
|
|
Loading...
|