Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
Re: DOK references
Hi Steve,
toggle quoted message
Show quoted text
For me it's OK also... But what if someone , like you did, update his logbook with old qsl cards. So then it's possible that he had a qsl card from 20 years old with that SDOK. Koen --- In dxlab@..., "Steve GW4BKG" <gw4bkg@...> wrote:
|
|
Re: stupid /1440
Yawn.
_____ From: dxlab@... [mailto:dxlab@...] On Behalf Of Paul M Dunphy Sent: Thursday, September 03, 2009 10:21 PM To: DXLabs Subject: RE: [dxlab] stupid /1440 At 01:05 AM 9/4/2009, you wrote: What are the CALLSIGN/140 anyway?? They are everywhere.Hiram Percy Maxim's 140th birthday: <> .org/wiki/Hiram_Percy_Maxim 73, Paul VE1DX |
|
Re: Pathfinder 457 one minor / one wish
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...]On Behalf Of Bernard Grijpstra Sent: Thursday, September 03, 2009 4:04 PM To: DX-Lab Yahoo Group Subject: [dxlab] Pathfinder 457 one minor / one wish Hello Dave , One minor for PF : When focus is transferred from another window to pf window the cursor indicator is visible in the 'enter call' field. However when focus was in pf window (while checking out a qrz entry for example) and you return the focus to the entry field of pf by clicking in it the cursor indicator is invisible making editing of a call already in it a little bit difficult. I'm investigating... My wish for pf : To transfer a call from fe SC to PF you will have to double click a SC row , at the same time the DXK capture window is filled. How about just sending the call to pf on selection in SC, i like to check a call for fun in qrz via PF but need to clear the capture window every time afterwards. database entry, and then later double-click a second spot database entry,Why must you clear the Capture window? If you double-click a spot the Capture window will be automatically updated without your having to clear it. 73, Dave, AA6YQ |
|
Re: DOK references
Hi Koen,
toggle quoted message
Show quoted text
Thanks for the information & URLs. I think Dave's idea to leave users to enter their own additional DOKs as they need them is the best idea. There is no point in having a very large list which includes temporary DOKs which are more than 25 years old which will never be activated again. I have already added IBO83 to my Award230.txt file so must remember that when you produce your next file. 73s Steve GW4BKG ----- Original Message -----
From: koro19672002 To: dxlab@... Sent: Friday, September 04, 2009 7:40 AM Subject: [dxlab] Re: DOK references Hi Steve, The list i follow is the list from DARC. IBO is the special DOK for Friedrichshaven. And IBO83 is not in that list nor in the CSV file wich i use to make Award230.txt I discovered some more faults in that list... but i thrust DARC... If i'm right you can enter your Own value in the DOK field as well. Koen ON7RK --- In dxlab@..., "Steve GW4BKG" <gw4bkg@...> wrote: > > Dave, > Thanks for the guidance on SQL expressions. > I had overlooked the need to use the "ADIF field name" option rather than just "DOK". > I can now see how to better construct such queries in the future. > Koen, > There are many different awards that involved the working of various DOKs & not just DARC ones. > One I looked at earlier is the Baden Diploma where there is a requirement to work multiple "A" DOKs hence the query. > Dave, > The drop down list in DXKeeper includes some "special event" DOKs as well as standard ones. > I find that I have worked DOK IBO 83 which does not feature in your list. > However includes what I believe is a definitive list of all special DOKs some of which are temporary. > IBO 83 is temporary but there are other IBO DOKs which are also temporary which do in fact feature in the dropdown. > I assume that some awards may involve working such temporary DOKs but within certain time constraints. > However there must be several hundred of these so I guess including them all is not feasible. > 73s > Steve > GW4BKG > > > > |
|
Re: LotW - unrecognized mode
I have a release of DXKeeper that when synchronizing QSOs or QSLs with LotW,
toggle quoted message
Show quoted text
considers a QSO reported by LotW whose Mode is DATA to match a logged QSO whose mode "counts" as RTTY for ARRL awards. Suppose, for example, that you logged the QSO 7O1DX, 160m, JT65A, 2009-09-01, 12:34:56 So that LotW would accept this QSO, you configured TQSL to map JT65A to DATA. However, when you direct DXKeeper to "Sync LotW QSOs" or "Sync LotW QSLs", LotW reports the QSO 7O1DX, 160m, DATA, 2009-09-01, 12:34:56 which DXKeeper declares as "no matching QSO in Log". This new release of DXKeeper considers the reported QSO to match the logged QSO because the callsign, band, date, and time all match, and because JT65A counts as RTTY towards ARRL awards and therefore matches DATA. If you have - logged QSOs with digital modes that LotW does not accept, and - uploaded these QSOs to LotW by configuring TQSL to map these modes to DATA, and - would like to test this new release of DXKeeper, then please send email to me at aa6yq@... from an email account that accepts attachments (e.g. not gmail). Thanks... 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Dave AA6YQ Sent: Friday, September 04, 2009 2:11 AM To: dxlab@... Subject: RE: [dxlab] LotW - unrecognized mode -----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...]On Behalf Of bchriste9149 Sent: Thursday, September 03, 2009 11:04 PM To: dxlab@... Subject: [dxlab] LotW - unrecognized mode I've just started using LotW and eQSL.cc. When I uploaded 1 qso to LotW, I got an error message that it didn't like the JT6M mode. Is there a list of acceptable modes for LotW Yes, in <> and is there a way of uploading my qso without changing the mode? later direct DXKeeper to synchronize, it will report that it cannot find theYou can configure TQSL to "map" a digital mode to DATA, but when you QSO in your log (because the uploaded QSO has a mode of DATA but the logged QSO will has a mode of JT65A). In the next release, I'm planning to modify DXKeeper to consider DATA a match for any mode that counts as RTTY towards ARRL awards. With eQSL.cc I got a similar error, trying to upload a JT65A mode. 73,I defer to Rich W3ZJ on eQSL.cc matters. Dave, AA6YQ ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/03/09 05:50:00 |
|
Re: DOK references
Hi Steve,
toggle quoted message
Show quoted text
The list i follow is the list from DARC. IBO is the special DOK for Friedrichshaven. And IBO83 is not in that list nor in the CSV file wich i use to make Award230.txt I discovered some more faults in that list... but i thrust DARC... If i'm right you can enter your Own value in the DOK field as well. Koen ON7RK --- In dxlab@..., "Steve GW4BKG" <gw4bkg@...> wrote:
|
|
Re: LotW - unrecognized mode
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...]On Behalf Of bchriste9149 Sent: Thursday, September 03, 2009 11:04 PM To: dxlab@... Subject: [dxlab] LotW - unrecognized mode I've just started using LotW and eQSL.cc. When I uploaded 1 qso to LotW, I got an error message that it didn't like the JT6M mode. Is there a list of acceptable modes for LotW Yes, in <> and is there a way of uploading my qso without changing the mode? later direct DXKeeper to synchronize, it will report that it cannot find theYou can configure TQSL to "map" a digital mode to DATA, but when you QSO in your log (because the uploaded QSO has a mode of DATA but the logged QSO will has a mode of JT65A). In the next release, I'm planning to modify DXKeeper to consider DATA a match for any mode that counts as RTTY towards ARRL awards. With eQSL.cc I got a similar error, trying to upload a JT65A mode. 73,I defer to Rich W3ZJ on eQSL.cc matters. Dave, AA6YQ |
|
Re: stupid /1440
What are the CALLSIGN/140 anyway?? They are everywhere.
-Dick- N3XRU _____ From: dxlab@... [mailto:dxlab@...] On Behalf Of DANNY DOUGLAS Sent: Thursday, September 03, 2009 7:47 PM To: dxlab@... Subject: [dxlab] stupid /1440 I knew this stupid /140 behind all these stateside calls was gonna screw up data bases. Every spot with the /140 results in the hams name being printed out in WinWarbler, but the QTHs are not there - including state . The Zones are also missing in Spot Collector, because the programs do not know what to do with that info, and it "might" be someone mobile, or some such. I guess, with my VE certifica, I am elgible, but WILL NOT ever use such an indicator. I hate them On DX, I hate them on local calls. I hate green eggs and ham. 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 use, but as a courtesy do upload to eQSL for those who do. Moderator DXandTALK . <> yahoo.com/group/DXandTalk DXandTALK@YAHOOGROU <mailto:DXandTALK%40YAHOOGROUPS.COM> PS.COM Moderator Digital_modes . <> yahoo.com/group/digital_modes/?yguid=341090159 |
|
LotW - unrecognized mode
bchriste9149
I've just started using LotW and eQSL.cc. When I uploaded 1 qso to LotW, I got an error message that it didn't like the JT6M mode. Is there a list of acceptable modes for LotW and is there a way of uploading my qso without changing the mode?
With eQSL.cc I got a similar error, trying to upload a JT65A mode. Thanks for the help. Bob C WU9Q |
|
stupid /1440
DANNY DOUGLAS
I knew this stupid /140 behind all these stateside calls was gonna screw up data bases. Every spot with the /140 results in the hams name being printed out in WinWarbler, but the QTHs are not there - including state . The Zones are also missing in Spot Collector, because the programs do not know what to do with that info, and it "might" be someone mobile, or some such. I guess, with my VE certifica, I am elgible, but WILL NOT ever use such an indicator. I hate them On DX, I hate them on local calls. I hate green eggs and ham.
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 use, but as a courtesy do upload to eQSL for those who do. Moderator DXandTALK DXandTALK@... Moderator Digital_modes |
|
Re: Capture gone
--- In dxlab@..., lratcliff lratcliff <lratcliff@...> wrote:AA6YQ comments below In DXKeeper, the Capture window has disappeared. It is showing in the <>Please try the procedure described in 73,If this doesn't recover the Capture window, please let me know. Dave, AA6YQ |
|
Capture gone
In DXKeeper, the Capture window has disappeared. It is showing in the
task bar, but when I restore it, the other windows gray out, but it doesn't show anywhere. It was doing in before I just upgraded the software, and is still doing it after. What am I doing wrong? Im sure its a setting here on the computer causeing it. Lee KC4ART |
|
Re: Diferent station callsigns
Anela Karacic
Thank you very much Dave,
Best wishes! Anela - e74ee ________________________________ From: Dave AA6YQ <aa6yq@...> To: dxlab@... Sent: Thursday, September 3, 2009 10:48:26 PM Subject: RE: [dxlab] Re: Diferent station callsigns Do all of your QSOs made as T95LKA have their "station callsign" item set to T95LKA? Each QSO's "station callsign" item is displayed in the Auxiliary panel on the Main window's "Log QSOs" tab. 73, Dave, AA6YQ -----Original Message----- From: dxlab@... [mailto:dxlab@...]On Behalf Of Anela Karacic Sent: Thursday, September 03, 2009 4:35 PM To: dxlab@... Subject: Re: [dxlab] Re: Diferent station callsigns My call sign Dave! Earlier i had a T95LKA callsign, now it is E74EE. Both logs are in a same file, now I wuold like to know if I can export them separately devided by call sign? Thank you! Anela - e74ee ________________________________ From: aa6yq <aa6yq@...> To: dxlab@... Sent: Thursday, September 3, 2009 10:01:43 PM Subject: [dxlab] Re: Diferent station callsigns --- In dxlab@yahoogroups. com, Anela Karacic <anelae74ee@ ...> wrote:AA6YQ comments below I ask you before about this topic and you gave me an answer... Before, I hade two question how to export one part of my log (by date)? You explain me and I make it. Second question was How to export a part of my log (By call signs)? YOU also gave ma an explanation, but I stil, can not make it? Simply I do not know how to do that, I tried to make a steps as it is explain in HELP option, but again without any succsses. 73,Which callsign, Anela? Your callsign, or your QSO partner's callsign? Dave, AA6YQ ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/03/09 05:50:00 ------------------------------------ Yahoo! Groups Links |
|
Re: Diferent station callsigns
Do all of your QSOs made as T95LKA have their "station callsign" item set to
toggle quoted message
Show quoted text
T95LKA? Each QSO's "station callsign" item is displayed in the Auxiliary panel on the Main window's "Log QSOs" tab. 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Anela Karacic Sent: Thursday, September 03, 2009 4:35 PM To: dxlab@... Subject: Re: [dxlab] Re: Diferent station callsigns My call sign Dave! Earlier i had a T95LKA callsign, now it is E74EE. Both logs are in a same file, now I wuold like to know if I can export them separately devided by call sign? Thank you! Anela - e74ee ________________________________ From: aa6yq <aa6yq@...> To: dxlab@... Sent: Thursday, September 3, 2009 10:01:43 PM Subject: [dxlab] Re: Diferent station callsigns --- In dxlab@yahoogroups. com, Anela Karacic <anelae74ee@ ...> wrote:AA6YQ comments below I ask you before about this topic and you gave me an answer... Before, I hade two question how to export one part of my log (by date)? You explain me and I make it. Second question was How to export a part of my log (By call signs)? YOU also gave ma an explanation, but I stil, can not make it? Simply I do not know how to do that, I tried to make a steps as it is explain in HELP option, but again without any succsses. 73,Which callsign, Anela? Your callsign, or your QSO partner's callsign? Dave, AA6YQ ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/03/09 05:50:00 |
|
Re: Diferent station callsigns
Anela Karacic
My call sign Dave!
Earlier i had a T95LKA callsign, now it is E74EE. Both logs are in a same file, now I wuold like to know if I can export them separately devided by call sign? Thank you! Anela - e74ee ________________________________ From: aa6yq <aa6yq@...> To: dxlab@... Sent: Thursday, September 3, 2009 10:01:43 PM Subject: [dxlab] Re: Diferent station callsigns --- In dxlab@yahoogroups. com, Anela Karacic <anelae74ee@ ...> wrote:AA6YQ comments below I ask you before about this topic and you gave me an answer... Before, I hade two question how to export one part of my log (by date)? You explain me and I make it. Second question was How to export a part of my log (By call signs)? YOU also gave ma an explanation, but I stil, can not make it? Simply I do not know how to do that, I tried to make a steps as it is explain in HELP option, but again without any succsses. 73,Which callsign, Anela? Your callsign, or your QSO partner's callsign? Dave, AA6YQ |
|
Pathfinder 457 one minor / one wish
Bernard Grijpstra
Hello Dave ,
One minor for PF : When focus is transferred from another window to pf window the cursor indicator is visible in the 'enter call' field. However when focus was in pf window (while checking out a qrz entry for example) and you return the focus to the entry field of pf by clicking in it the cursor indicator is invisible making editing of a call already in it a little bit difficult. My wish for pf : To transfer a call from fe SC to PF you will have to double click a SC row , at the same time the DXK capture window is filled. How about just sending the call to pf on selection in SC, i like to check a call for fun in qrz via PF but need to clear the capture window every time afterwards. Best regards, Bernard Grijpstra PA3FZV |
|
Re: Diferent station callsigns
--- In dxlab@..., Anela Karacic <anelae74ee@...> wrote:AA6YQ comments below I ask you before about this topic and you gave me an answer... Before, I hade two question how to export one part of my log (by date)? You explain me and I make it. Second question was How to export a part of my log (By call signs)? YOU also gave ma an explanation, but I stil, can not make it? Simply I do not know how to do that, I tried to make a steps as it is explain in HELP option, but again without any succsses. 73,Which callsign, Anela? Your callsign, or your QSO partner's callsign? Dave, AA6YQ |
|
Diferent station callsigns
Anela Karacic
Dear Dave and other,
I ask you before about this topic and you gave me an answer... Before, I hade two question how to export one part of my log (by date)? You explain me and I make it. Second question was How to export a part of my log (By call signs)? YOU also gave ma an explanation, but I stil, can not make it? Simply I do not know how to do that, I tried to make a steps as it is explain in HELP option, but again without any succsses. If it is not a problem for you, please try one more time to help me with this! Thank you! Anela - e74ee |
|
Commander defect or feature
In it's Main window's "Main VFO" and "Sub VFO" panels, Commander is designed
to display two digits to the right of the "decimal point" (more correctly described as the "decimal separator"). Several months ago, Howard K7JNX pointed out that in locales where a character other than the period is used as the decimal separator, Commander displays three digits to the right of the decimal separator. This is the result of a defect. If I correct this defect, those of you operating from locales that use a comma or another character as the decimal separator will see the number of decimal digits to the right of the decimal separator reduced from 3 to 2. Will anyone view this as a loss of important functionality? The alternative would be to add an option that controls whether 2 or 3 decimal digits are displayed. My preference is to just correct the defect, as adding an option will increase the complexity as perceived by new users. 73, Dave, AA6YQ |
to navigate to use esc to dismiss