|
Re: Divergent headings
Jim Hargrave
Gary
I can confirm what you are seeing.I'll explain: Callsign lookup shows TX5T has a Germany address. There is an exception for Austral Isl. When the spot is received, it will show the proper heading for Austral Isl. This will show up on the Bandmap tooltip. After the call lookup, the Gridsquare shows the Germany locator. This updates the lower status bar heading, but does not update the Bandmap heading. From your QTH, these headings are basically the same direction. From my QTH they near 180 deg different. If you do not fill Gridsquare field following a call lookup, they will be the same. 73, Jim - w5ifp@... From: hamlogger@... [mailto:hamlogger@...] Sent: Monday, February 27, 2017 5:30 PM To: hamlogger@... Subject: [hamlogger] Divergent headings Friends, I've just 'discovered' that we can optionally display headings on spots on the band maps - handy for the bands on which we have beams. In the course of idly playing with the new toy, by chance I noticed a tiny difference between the headings for TX5T in the Australs on the band map (68 degrees I think it was) and on the info bar at the bottom of the main Logger32 screen (72 degrees). The pop up message on the band map identified it correctly as Australs, but I wonder if the heading was for somewhere else, nearby, perhaps something to do with the ambiguity of that prefix? I realise it's a tiny discrepancy. Wouldn't it be nice to have an HF beam where 4 degrees mattered! The point is that it has the merest whiff of being a bug. 73 Gary ZL2iFB
|
|
|
|
Re: Divergent headings
gboutin@...
Gary,
toggle quoted messageShow quoted text
I tried your test using TX5C and TX5Z which are stations I have worked in the past. The log window shows them as follows: TX5C FO/C Clipperton 246 degrees TX5Z FO/A Austral 251 degrees The bandmap shows them both as France at 63 degrees. So, it appears to me the heading isn't the issue so much as deciding which is the correct country as both of the logged calls were country exceptions. If they appear in the bandmap now, presumably they could well be France. Does this match what you are seeing? > Gerald, VE1DT ---In hamlogger@..., <Gary@...> wrote : Hi Aki.
All the spots I have checked so far have been fine: the only ‘problem’ one is TX5T … which is what made me wonder about the way the program handles ambiguous prefixes.
It would be interesting to check an E5 North Cooks spot for the same reason, except I don’t think anyone is QRV from there at present.
73 Gary ZL2iFB
From: hamlogger@... [mailto:hamlogger@...]
Sent: Tuesday, 28 February 2017 12:55 p.m. To: hamlogger@... Subject: [hamlogger] Re: Divergent headings
sorry...I should say TX5T (not TX5C)
Gary
Friends,
I’ve just ‘discovered’ that we can optionally display headings on spots on the band maps – handy for the bands on which we have beams.
In the course of idly playing with the new toy, by chance I noticed a tiny difference between the headings for TX5T in the Australs on the band map (68 degrees I think it was) and on the info bar at the bottom of the main Logger32 screen (72 degrees). The pop up message on the band map identified it correctly as Australs, but I wonder if the heading was for somewhere else, nearby, perhaps something to do with the ambiguity of that prefix?
I realise it’s a tiny discrepancy. Wouldn’t it be nice to have an HF beam where 4 degrees mattered! The point is that it has the merest whiff of being a bug.
73 Gary ZL2iFB
|
|
|
|
Re: Divergent headings
Hi Aki.
All the spots I have checked so far have been fine: the only ‘problem’ one is TX5T … which is what made me wonder about the way the program handles ambiguous prefixes.
It would be interesting to check an E5 North Cooks spot for the same reason, except I don’t think anyone is QRV from there at present.
73 Gary ZL2iFB
From: hamlogger@... [mailto:hamlogger@...]
Sent: Tuesday, 28 February 2017 12:55 p.m. To: hamlogger@... Subject: [hamlogger] Re: Divergent headings
sorry...I should say TX5T (not TX5C)
Gary
Friends,
I’ve just ‘discovered’ that we can optionally display headings on spots on the band maps – handy for the bands on which we have beams.
In the course of idly playing with the new toy, by chance I noticed a tiny difference between the headings for TX5T in the Australs on the band map (68 degrees I think it was) and on the info bar at the bottom of the main Logger32 screen (72 degrees). The pop up message on the band map identified it correctly as Australs, but I wonder if the heading was for somewhere else, nearby, perhaps something to do with the ambiguity of that prefix?
I realise it’s a tiny discrepancy. Wouldn’t it be nice to have an HF beam where 4 degrees mattered! The point is that it has the merest whiff of being a bug.
73 Gary ZL2iFB
|
|
|
|
Re: Divergent headings
Jim Hargrave
Gary
I can confirm what you are seeing.I'll explain: Callsign lookup shows TX5T has a Germany address. There is an exception for Austral Isl. When the spot is received, it will show the proper heading for Austral Isl. This will show up on the Bandmap tooltip. After the call lookup, the Gridsquare shows the Germany locator. This updates the lower status bar heading, but does not update the Bandmap heading. From your QTH, these headings are basically the same direction. From my QTH they near 180 deg different. If you do not fill Gridsquare field following a call lookup, they will be the same. 73, Jim - w5ifp@... From: hamlogger@... [mailto:hamlogger@...] Sent: Monday, February 27, 2017 5:30 PM To: hamlogger@... Subject: [hamlogger] Divergent headings Friends, I've just 'discovered' that we can optionally display headings on spots on the band maps - handy for the bands on which we have beams. In the course of idly playing with the new toy, by chance I noticed a tiny difference between the headings for TX5T in the Australs on the band map (68 degrees I think it was) and on the info bar at the bottom of the main Logger32 screen (72 degrees). The pop up message on the band map identified it correctly as Australs, but I wonder if the heading was for somewhere else, nearby, perhaps something to do with the ambiguity of that prefix? I realise it's a tiny discrepancy. Wouldn't it be nice to have an HF beam where 4 degrees mattered! The point is that it has the merest whiff of being a bug. 73 Gary ZL2iFB
|
|
|
|
Re: Divergent headings
ayoshida@...
sorry...I should say TX5T (not TX5C)
73 de aki ja1nlx ---In hamlogger@..., <ayoshida@...> wrote : Gary I do not see this while clicking some spots on DX spot window or BandMap. I always see same headings. Do you see this only when clicking TX5C ? or do you always see when clicking any DX spot ? 73 de aki ja1nlx ---In hamlogger@..., <Gary@...> wrote : Friends,
I’ve just ‘discovered’ that we can optionally display headings on spots on the band maps – handy for the bands on which we have beams.
In the course of idly playing with the new toy, by chance I noticed a tiny difference between the headings for TX5T in the Australs on the band map (68 degrees I think it was) and on the info bar at the bottom of the main Logger32 screen (72 degrees). The pop up message on the band map identified it correctly as Australs, but I wonder if the heading was for somewhere else, nearby, perhaps something to do with the ambiguity of that prefix?
I realise it’s a tiny discrepancy. Wouldn’t it be nice to have an HF beam where 4 degrees mattered! The point is that it has the merest whiff of being a bug.
73 Gary ZL2iFB
|
|
|
|
Re: Divergent headings
ayoshida@...
Gary
I do not see this while clicking some spots on DX spot window or BandMap. I always see same headings. Do you see this only when clicking TX5C ? or do you always see when clicking any DX spot ? 73 de aki ja1nlx ---In hamlogger@..., <Gary@...> wrote : Friends,
I’ve just ‘discovered’ that we can optionally display headings on spots on the band maps – handy for the bands on which we have beams.
In the course of idly playing with the new toy, by chance I noticed a tiny difference between the headings for TX5T in the Australs on the band map (68 degrees I think it was) and on the info bar at the bottom of the main Logger32 screen (72 degrees). The pop up message on the band map identified it correctly as Australs, but I wonder if the heading was for somewhere else, nearby, perhaps something to do with the ambiguity of that prefix?
I realise it’s a tiny discrepancy. Wouldn’t it be nice to have an HF beam where 4 degrees mattered! The point is that it has the merest whiff of being a bug.
73 Gary ZL2iFB
|
|
|
|
Divergent headings
Friends,
I’ve just ‘discovered’ that we can optionally display headings on spots on the band maps – handy for the bands on which we have beams.
In the course of idly playing with the new toy, by chance I noticed a tiny difference between the headings for TX5T in the Australs on the band map (68 degrees I think it was) and on the info bar at the bottom of the main Logger32 screen (72 degrees). The pop up message on the band map identified it correctly as Australs, but I wonder if the heading was for somewhere else, nearby, perhaps something to do with the ambiguity of that prefix?
I realise it’s a tiny discrepancy. Wouldn’t it be nice to have an HF beam where 4 degrees mattered! The point is that it has the merest whiff of being a bug.
73 Gary ZL2iFB
|
|
|
|
icom 7700 communications
Ronald Scalise
Updating firmware did the trick logger 32 is now happy to talk to the 7700. Yhanks for all the help . 73 's Ron
|
|
|
|
<QSLMSG: > ADIF field seemed not taken by auto-upload function to Logger32
Team-SIM SIM-Mode
Hello All, Please i need help, i try to auto-upload a QSO to Logger32 by a digitalmode program, all seems to be logged correctly except ADIF field that remain empty !!! Please if any possible solution. It would be appreciated . Thanks 73's TEAM_SIM31
|
|
|
|
Another request for help
Mike
In Feb 2016 (yes last year) in msg number 68856 I asked for set up help on getting the CW machine to work post v3.50.0. I have been chasing this for the last year and have not made any progress. with v3.50.0 installed every thing on the CW machine works fine but the Bandmap does not follow any change in VFO Band. After I install a L32 version above v3.50.0 when I select the CW machine I get a message saying "CW Port error: Could not set comm state, there may be one or more invalid communication parameters" the error message box is titled Port 4. However the bandmap now follows the VFO changes I am using an FTdx3000 and win 7 in a dell Vostro 32 bit machine. I am an electronics guy not a PC guy so I find the terminology in the error message is well past my PC skill level so any help will be gratefully received. Mike G3VAO
|
|
|
|
Re: LOtW file export problem
Jim Hargrave
Larry,
You need to setup Logger32 to Automatically flag Imported QSOs for LOTW file export. See the setup process outlined in the Help file: “Tips, Tricks and Troubleshooting” Par 1.13 Since you already added the QSOs, follow the above process as a onetime submittal, LOTW will kick out the dupes. Once you setup the process, any contest log will automatically be properly flagged on import, as well as any newly entered QSOs. 73, Jim – w5ifp@... From: hamlogger@... [mailto:hamlogger@...] Sent: Sunday, February 26, 2017 10:12 AM To: hamlogger@... Subject: Re: [hamlogger] LOtW file export problem I am running logger version 3.50.309 on a Win 10 64 bit machine. I just finished the 160 meter phone contest and imported 495 Q’s as an .adi file from my Win-Test contest program. They all came into logger fine and are white (the color I use to indicate they need to be exported as an LOtW file so I can upload them. So far so good. When I select the Export a file for LOtW I get a message box that has “Only QSO’s by all operators” with a box that is not checked highlighted and then the path to save the file once it is exported. If I check “start” with the box not checked I get “you have not selected any operators. There is nothing to export.” Fair enough. If I check the box “All Operators” I get the message “There are no QSO’s with all operators flagged to put in the LOtW file”. This has not happened before and I feel that it has something to do with the imported 495 Q’s. I might add that under the operator column in logger my call sign is showing as it should for all Q’s. I have done all I can to try and figure this out on my own but am having about as much luck as I am hearing the XX9D – which as you might imagine is none. I have shut down logger and restarted it. I have rebooted the computer, I even tried recalculating the statistics thinking that might help. They Q’s show they are in my log but for some reason logger will not flag them and export them. If I need to delete all those Q’s and do something else to import them is there any way to mass delete them all at one time? Any and all suggestions are greatly appreciated. I usually have no problems with logger – always update it when a new version comes out and keep Club Log up to date each day automatically. Larry K8YYY "The world is changed by your examples, not by your opinions" Paul Coelho No virus found in this message. Checked by AVG - www.avg.com <http://www.avg.com/email-signature> Version: 2016.0.7998 / Virus Database: 4756/14023 - Release Date: 02/25/17
|
|
|
|
Re: Preset RST Sent and Received not showing.
atm_ken_hunter@...
Aki,
I did that a few times during the re-configuring without a fix. I walked away from the rig (shut everything down) for about 6 hours, fired it all up this morning and now is working normally again. Thanks for the suggestion but I do not want to try fixing it while it's not broke. ;0) Ken - KB7H
|
|
|
|
Re: LOtW file export problem
Larry Fravel
I am running logger version 3.50.309 on a Win 10 64 bit machine. I
just finished the 160 meter phone contest and imported 495 Q’s as an .adi file
from my Win-Test contest program. They all came into logger fine and are
white (the color I use to indicate they need to be exported as an LOtW file so I
can upload them. So far so good.
When I select the Export a file for LOtW I get a message box that has “Only
QSO’s by all operators” with a box that is not checked highlighted and then the
path to save the file once it is exported. If I check “start” with the box
not checked I get “you have not selected any operators. There is nothing to
export.” Fair enough. If I check the box “All Operators” I get the
message “There are no QSO’s with all operators flagged to put in the LOtW
file”. This has not happened before and I feel that it has
something to do with the imported 495 Q’s. I might add that
under the operator column in logger my call sign is showing as it should for all
Q’s.
I have done all I can to try and figure this out on my own but am having
about as much luck as I am hearing the XX9D – which as you might imagine is
none. I have shut down logger and restarted it. I have rebooted the
computer, I even tried recalculating the statistics thinking that might
help. They Q’s show they are in my log but for some reason logger will not
flag them and export them. If I need to delete all those Q’s and do
something else to import them is there any way to mass delete them all at one
time?
Any and all suggestions are greatly appreciated. I usually have no
problems with logger – always update it when a new version comes out and keep
Club Log up to date each day automatically.
Larry K8YYY
"The world is changed by your examples, not by your opinions" Paul Coelho No virus found in this message.
|
|
|
|
Re: Preset RST Sent and Received not showing.
Jim Hargrave
When all else fails…re-boot.
73, Jim – w5ifp@... From: hamlogger@... [mailto:hamlogger@...] Sent: Sunday, February 26, 2017 4:12 AM To: hamlogger@... Subject: RE: [hamlogger] Preset RST Sent and Received not showing. Hmmm... Something fishy here. For some reason, earlier this week when I clicked in the bandmap (as I usually do) the callsign transferred to the Entry Window and the radio changed to the stn freq but the RST Sent and Received windows were blank. This occurred several times resulting in blank RST entries in the logbook for those contacts. The preset values from the bandplan was not being moved to the Entry window. I spent 2 days trying everything I could think of including using a saved, known good, .ini file, verifying that the bandplan was correctly configured, restarting the computer etc. Noting made any difference so I asked for help from the Group, turned everything off and watched some boob tube movies. Came back down and --- now it's working the way it was before, Go figure. Is STUXNET still going around? Ken - KB7H [Non-text portions of this message have been removed]
|
|
|
|
Re: Preset RST Sent and Received not showing.
ayoshida@...
Ken
Try this for TEST. 1) Rename Logger32.ini to Logger32.old 2) Run Logger32 Yes Logger32 run with default settings. How you see RST fields now ? Is it normal or not ? 73 de aki ja1nlx ---In hamlogger@..., <atm_ken_hunter@...> wrote : Hmmm... Something fishy here. For some reason, earlier this week when I clicked in the bandmap (as I usually do) the callsign transferred to the Entry Window and the radio changed to the stn freq but the RST Sent and Received windows were blank. This occurred several times resulting in blank RST entries in the logbook for those contacts. The preset values from the bandplan was not being moved to the Entry window. I spent 2 days trying everything I could think of including using a saved, known good, .ini file, verifying that the bandplan was correctly configured, restarting the computer etc. Noting made any difference so I asked for help from the Group, turned everything off and watched some boob tube movies. Came back down and --- now it's working the way it was before, Go figure. Is STUXNET still going around? Ken - KB7H
|
|
|
|
Re: Preset RST Sent and Received not showing.
atm_ken_hunter@...
Hmmm... Something fishy here.
For some reason, earlier this week when I clicked in the bandmap (as I usually do) the callsign transferred to the Entry Window and the radio changed to the stn freq but the RST Sent and Received windows were blank. This occurred several times resulting in blank RST entries in the logbook for those contacts. The preset values from the bandplan was not being moved to the Entry window. I spent 2 days trying everything I could think of including using a saved, known good, .ini file, verifying that the bandplan was correctly configured, restarting the computer etc. Noting made any difference so I asked for help from the Group, turned everything off and watched some boob tube movies. Came back down and --- now it's working the way it was before, Go figure. Is STUXNET still going around? Ken - KB7H
|
|
|
|
Re: Preset RST Sent and Received not showing.
atm_ken_hunter@...
Jim,
That's the problem. The default RST Sent and Received boxes are NOT being populated by the data in the band plan. Worked OK during the CW Worldwide contest last weekend and I've made no changes since then ? Ver .309, Win 10 etc... Ken - KB7H
|
|
|
|
Re: Export QSL file problem
Andy - VA3PL <va3pl@...>
Hi Guys It is magic. The QSL export is working again. I do not know what fixed it. Probably exiting and loading the program fixed it. Sorry Andy
From: "'Jim Hargrave' w5ifp@... [hamlogger]" To: hamlogger@... Sent: Saturday, February 25, 2017 7:20 PM Subject: RE: [hamlogger] Export QSL file problem Andy,
Make sure the Path/Folder exist where you want to store the file. 73, Jim – w5ifp@... From: hamlogger@... [mailto:hamlogger@...] Sent: Saturday, February 25, 2017 11:52 AM To: hamlogger@... Subject: [hamlogger] Export QSL file problem Hi there I have a problem exporting QSL file. Logger ver 309 When I export QSL file I got in response - Bad file name or number. Just wandering if something got corrupted on my side? When I try to do same thing using Ver. 295 on enother computer all works fine. Export went fine and program ask if I want to mark those QSL as send. Any help would be greately appreciated. Andy SP9KR [Non-text portions of this message have been removed]
|
|
|
|
Re: Export QSL file problem
Andy - VA3PL <va3pl@...>
Hi Jim Path / Folder exist. Must be my error but so far I am unable fo correct this. 73 de Andy SP9KR
From: "'Jim Hargrave' w5ifp@... [hamlogger]" To: hamlogger@... Sent: Saturday, February 25, 2017 7:20 PM Subject: RE: [hamlogger] Export QSL file problem Andy,
Make sure the Path/Folder exist where you want to store the file. 73, Jim – w5ifp@... From: hamlogger@... [mailto:hamlogger@...] Sent: Saturday, February 25, 2017 11:52 AM To: hamlogger@... Subject: [hamlogger] Export QSL file problem Hi there I have a problem exporting QSL file. Logger ver 309 When I export QSL file I got in response - Bad file name or number. Just wandering if something got corrupted on my side? When I try to do same thing using Ver. 295 on enother computer all works fine. Export went fine and program ask if I want to mark those QSL as send. Any help would be greately appreciated. Andy SP9KR [Non-text portions of this message have been removed]
|
|
|
|
Re: Export QSL file problem
Andy - VA3PL <va3pl@...>
Must be a cockpit error but seems to me I am unable so far to find it. Andy SP9KR
From: "'VE6LB' ve6lb@... [hamlogger]" To: hamlogger@... Sent: Saturday, February 25, 2017 7:04 PM Subject: Re: [hamlogger] Export QSL file problem .309 QSL File export works fine here.
73, Gerry VE6LB
Sent: Saturday, February 25, 2017 10:51 AM
To: hamlogger@...
Subject: [hamlogger] Export QSL file problem Hi there
I have a problem exporting QSL
file.
Logger ver 309
When I export QSL file I got in
response - Bad file name or number. Just wandering if something got corrupted on
my side?
When I try to do same thing using Ver.
295 on enother computer all works fine. Export went fine and program ask if I
want to mark those QSL as send.
Any help would be greately
appreciated.
Andy SP9KR No virus found in this
message. Checked by AVG - www.avg.com Version: 2016.0.7998 / Virus Database: 4756/14020 - Release Date: 02/25/17
|
|
|