hamlogger@groups.io

Home Messages Hashtags

Between

and

Re: HFAUTO Program To Logger Terry Glagowski / W1TR / AFA1DI #78464 I just released HFAUTO version 3.9.3.0 that is interoperable with Logger32. Terry / W1TR
More All Messages By This Member
FW: HFAUTO Version 3.9.3.0 Released - Support for N1MM, DXLAB, Logger32, FLDIGI + FLDIGI_UDP Tested Terry Glagowski / W1TR / AFA1DI #78463 Dear HFAUTO and Logger32 Users: HFAUTO Version 3.9.3.0 Released - Support for N1MM, DXLAB, Logger32, FLDIGI + FLDIGI_UDP Tested Logger32 broadcasts a UDP packet in a similar format to N1MM+ and DXLAB containing RadioInfo – Frequency information, on port 12061, just one number above the default N1MM+ port. As far as I know, this port number is NOT configurable in the INI file. The HFAUTO software now decodes this properly. To enable this from the Logger32 Side… Use the Setup Menu, Frequency Item… Check the Enable Frequency Change UDP Broadcast CheckBox To enable this from the HFAUTO Side… Edit the [Network] section of the configuration file. Add a receive port for 12061: [Network] ;................................................... ; The Following are Manually Edited ;................................................... ; Broadcast UDP Addresses and Ports UDP_Broadcast.0=127.0.0.1:13080 ; To ALS-1306 ;UDP_Broadcast.1=127.0.0.1:14080 ; To RCS-8/10 (This Computer Only) UDP_Broadcast.1=127.0.0.255:14080 ; To RCS-8/10 (All Computers on LAN) ; UDP Receive Ports for IP=0.0.0.0 UDP_Receive.0=12020 ; From FLDIGI UDP_Receive.1=12050 ; From RCS-8/10 UDP_Receive.2=12060 ; From N1MM UDP_Receive.3=12061 ; From LOGGER32 UDP_Receive.4=12070 ; From DXLAB UDP_Receive.5=8000 ; From W1TR Rig Control ; User Defined CAT Control Properties USER.CAT_Source=UserCAT ; Source Name: User Defined CAT USER.XML_DocName=USERDOC ; XML Document: Name User Defined CAT USER.XML_FreqField=FREQ ; XML Freq Field: User Defined CAT ;=============================================================================== Since Logger32 only broadcasts a UDP packet when the frequency changes… I recommend you set the CAT TIMEOUT to ZERO, thereby disabling the timeout and notification that CAT CTRL has been lost (default is 20 since N1MM broadcasts every 10 or so seconds). I also recommend to the developer of Logger32 that this UDP packet be broadcast at least every few seconds even if there are no changes, say every 5, 10, or even 20 seconds. Terry G. Glagowski, Ph.D. / W1TR *TGG Systems .* 25 Hnath Road, Ashford, CT 06278 . (860) 429-9444 (Home) . (860) 617-1969 (Cell) . (EMail) TGGsystems@ GMail.com . (Web) http://www.glagowski.org/TGG_Systems .
More All Messages By This Member
Re: LOTW ADIF Sync problem Bob #78462 1) The error is explicit. The file you are attempting to use to synchronize your logbook to LoTW does not appear to have the correct header information (It's an 'I'm covering your ass message). 2 & 3) Once the DXCC/Challenge Awards windows are opened and populated, changing the underlying data does not re-populate the award window. After changing the underlying data, changes can be seen by clicking on one of the comboboxes to requery the award. SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 12:27 PM "Anthony Buscaglia via Groups.Io" < tonybb@...> wrote: Hi All I am a newbie to L32. I transferred 200k+ Qs from my old logging program (home brew FileMaker 6) I am working on reconciling my DXCC and Challenge data. Two problems: 1. When I try to sync with LOTW ADI file I get this error: 2. When I manually update my DXCC challenge by band, the Challenge table is right but when I view the DXCC table it does not reflect the entries updated in the Challenge table. I also noticed incidents when updating the credits by clicking on the table entries and going to the log and updating that in some cases the updates did not apply. I realize I am at the bottom of the learning curve, so I appreciate any help! Best 73 Tony K2NV
More All Messages By This Member
Re: Logger32 with DStar, DMR and Fusion keith hotchkiss #78461 As easy as that. Cheers for your support. HNY - Keith
More All Messages By This Member
Re: HFAUTO Program To Logger Bob #78460 The picture of the menu showing how to enable frequency UDP broadcasting is from the Logger32 Help file. For the latest, Google GITHUB Logger32. SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 11:56 AM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote: Bob, Can you give me some more details about this UDP broadcast. I am the author / developer of the HFAUTO software, and would like to make the HFAUTO interoperable with Logger32. The HFAUTO software gets CAT information from UDP broadcasts... Currently N1MM, DXLAB, and FLDIGI+ FLDIGI_UDP (an extension to FLDIGI that I developed) are supported. Others have figured out how to use DDUTIL to accomplish this. Since the logic for N1MM is different than DXLAB and FLDIGI, the UDP needs to have at least some difference from the N1MM UDP for me to process it. Please give me details or reference to LOGGER32 DOCs. Terry / W1TR
More All Messages By This Member
Re: Logger32 with DStar, DMR and Fusion Bob #78459 ADIF defined modes/submodes d'jour are laid out in the file ADIFMODES.TXT in the \Logger32 directory. I don't see Fusion (Nuclear or otherwise) or DMR listed, but apparently DSTAR is indeed a mode. So, if you add DSTAR to your BandPlan, and assuming it's digital mode, add it to your digital modes, then it should be relatively painless to log a DSTAR QSO. SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 1:42 PM keith hotchkiss <g0fea@...> wrote: Does anyone use logger32 for logging their DStar, DMR and Fusion contacts? If so how are you logging the correct modes? Cheers Keith - G0FEA
More All Messages By This Member
Logger32 with DStar, DMR and Fusion keith hotchkiss #78458 Does anyone use logger32 for logging their DStar, DMR and Fusion contacts? If so how are you logging the correct modes? Cheers Keith - G0FEA
More All Messages By This Member
LOTW ADIF Sync problem Anthony Buscaglia #78457 Hi All I am a newbie to L32. I transferred 200k+ Qs from my old logging program (home brew FileMaker 6) I am working on reconciling my DXCC and Challenge data. Two problems: 1. When I try to sync with LOTW ADI file I get this error: 2. When I manually update my DXCC challenge by band, the Challenge table is right but when I view the DXCC table it does not reflect the entries updated in the Challenge table. I also noticed incidents when updating the credits by clicking on the table entries and going to the log and updating that in some cases the updates did not apply. I realize I am at the bottom of the learning curve, so I appreciate any help! Best 73 Tony K2NV
More All Messages By This Member
Re: HFAUTO Program To Logger Terry Glagowski / W1TR / AFA1DI #78456 Bob, Can you give me some more details about this UDP broadcast. I am the author / developer of the HFAUTO software, and would like to make the HFAUTO interoperable with Logger32. The HFAUTO software gets CAT information from UDP broadcasts... Currently N1MM, DXLAB, and FLDIGI+ FLDIGI_UDP (an extension to FLDIGI that I developed) are supported. Others have figured out how to use DDUTIL to accomplish this. Since the logic for N1MM is different than DXLAB and FLDIGI, the UDP needs to have at least some difference from the N1MM UDP for me to process it. Please give me details or reference to LOGGER32 DOCs. Terry / W1TR
More All Messages By This Member
Re: QSO TIME Vilhjalmur Sigurjonsson #78455 DR Paul, According to your question I do assume that you key in the call sign and then hit ENTER. If you want to log anything other than the call and 599 this is not the proper way to go. You can decide number of fields to be filled automatially in the proper manner, e.g. the band, frequency and mode and you can have several other fields automatically filled in, either with fixed text, from the callbook (CD or Telnet) or/and from previous entries in the log. It is all up to you and you will have to set up the entry form for your preferences. Some fields require your keying in and will not be automatically populated. What you must do is to hit the TAB key to jump from one field to another. You can even decide the Tab jump order as you like. When you have filled in all you need, then and only then you should hit the ENTER key to log the QSO. 73 Villi TF3VS toggle quoted messageShow quoted text -----Original Message----- From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Paul F6EXV Sent: sunnudagur, 5. janúar 2020 11:34 To: hamlogger@groups.io Subject: Re: [hamlogger] QSO TIME Hi In other words, I need to log a QSO, then edit it and modify whatever I need/want to change ? Can I edit all the fields BEFORE logging ? Thanks + 73 Paul F6EXV Le 05/01/2020 à 11:30, Bob a écrit : Like this? When you type <ENTER> this is what is entered into the Logbook. /ti change/set the QSO Start time type CTRL+S. The help file is more than 400 pages, I recommend you read it. SeventyThree(s). PS. To download the current Help File, Google GITHUB LOGGER32. On January 5, 2020 at 5:17 AM Paul F6EXV < f6exv@hotmail.com <mailto:f6exv@hotmail.com>> wrote: Hi all I am trying to see if it is possible to modify any field of the logging windows BEFORE the QSO is actually logged ? For example, how to I add an IOTA reference, how do I modify the time, how do I add/modify a QSL manager, again, BEFORE the QSO is actually logged. If I have to log it first, and then edit the QSO to modify field(s), it will have already be uploaded to ClubLog and/or LoTW. This is what I do not want to happen. Thanks for help 73 Paul F6EXV
More All Messages By This Member
Re: Poblem on Clublog Bob #78454 If you had imported 2000 QSOs with "Invalid Country", you would click SETUP \| UPDATES \| VALIDATE YOUR LOGBOOK DXCC COUNTRY CODES FROMCLUB LOG. And Club Log will make the necessary corrections for you. This feature is described in the Help File. SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 7:19 AM Paul F6EXV <f6exv@hotmail.com> wrote: France I have manuall corrected the 13 calls that showed "inavlid country" after import. I would noyt want to do that if I imported 2000 QSOs.... What did I do wrong ? 73 Paul F6EXV Le 05/01/2020 à 13:14, Bob a écrit : If you type F6EXV into Logbook Entry Window, What Country is Logger32 telling you? Does the ADIF file from DXLog include The DXCC number somewhere? Importing ADIF files into Logger32 gives you a number of options. One option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you set this option? SeventyThree(s). On January 5, 2020 at 6:45 AM Paul F6EXV < f6exv@hotmail.com <mailto:f6exv@hotmail.com>> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV
More All Messages By This Member
Re: Poblem on Clublog Bob #78453 It's all in the Help File. SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 7:34 AM Paul F6EXV <f6exv@hotmail.com> wrote: The ADIF file created by DXLog does not contain a DXCC field. Yes, I had that option ticked. I imagine the solution it to NOT tick that option, and L32 will automatically fill in the DXCC field, so the upload to ClubLog will be correct. If this is correct, sorry for the bandwidth 73 Paul F6EXV Le 05/01/2020 à 13:26, Bob a écrit : You did no answer two more questions ... a) Does the ADIF file from DX Log include a DXCC field for each QSO? b) When you imported the ADIF file into Logger32 did you have the option to mark QSOs with no DXCC as "Invalid for DXCC"? SeventyThree(s). On January 5, 2020 at 7:19 AM Paul F6EXV <f6exv@hotmail.com> wrote: France I have manuall corrected the 13 calls that showed "inavlid country" after import. I would noyt want to do that if I imported 2000 QSOs.... What did I do wrong ? 73 Paul F6EXV Le 05/01/2020 à 13:14, Bob a écrit : If you type F6EXV into Logbook Entry Window, What Country is Logger32 telling you? Does the ADIF file from DXLog include The DXCC number somewhere? Importing ADIF files into Logger32 gives you a number of options. One option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you set this option? SeventyThree(s). On January 5, 2020 at 6:45 AM Paul F6EXV < f6exv@hotmail.com <mailto:f6exv@hotmail.com>> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV .
More All Messages By This Member
Re: Poblem on Clublog Paul F6EXV #78452 The ADIF file created by DXLog does not contain a DXCC field. Yes, I had that option ticked. I imagine the solution it to NOT tick that option, and L32 will automatically fill in the DXCC field, so the upload to ClubLog will be correct. If this is correct, sorry for the bandwidth 73 Paul F6EXV toggle quoted messageShow quoted text Le 05/01/2020 à 13:26, Bob a écrit : You did no answer two more questions ... a) Does the ADIF file from DX Log include a DXCC field for each QSO? b) When you imported the ADIF file into Logger32 did you have the option to mark QSOs with no DXCC as "Invalid for DXCC"? SeventyThree(s). On January 5, 2020 at 7:19 AM Paul F6EXV <f6exv@hotmail.com> wrote: France I have manuall corrected the 13 calls that showed "inavlid country" after import. I would noyt want to do that if I imported 2000 QSOs.... What did I do wrong ? 73 Paul F6EXV Le 05/01/2020 à 13:14, Bob a écrit : If you type F6EXV into Logbook Entry Window, What Country is Logger32 telling you? Does the ADIF file from DXLog include The DXCC number somewhere? Importing ADIF files into Logger32 gives you a number of options. One option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you set this option? SeventyThree(s). On January 5, 2020 at 6:45 AM Paul F6EXV < f6exv@hotmail.com <mailto:f6exv@hotmail.com>> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV .
More All Messages By This Member
Re: Poblem on Clublog Bob #78451 You did no answer two more questions ... a) Does the ADIF file from DX Log include a DXCC field for each QSO? b) When you imported the ADIF file into Logger32 did you have the option to mark QSOs with no DXCC as "Invalid for DXCC"? SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 7:19 AM Paul F6EXV <f6exv@hotmail.com> wrote: France I have manuall corrected the 13 calls that showed "inavlid country" after import. I would noyt want to do that if I imported 2000 QSOs.... What did I do wrong ? 73 Paul F6EXV Le 05/01/2020 à 13:14, Bob a écrit : If you type F6EXV into Logbook Entry Window, What Country is Logger32 telling you? Does the ADIF file from DXLog include The DXCC number somewhere? Importing ADIF files into Logger32 gives you a number of options. One option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you set this option? SeventyThree(s). On January 5, 2020 at 6:45 AM Paul F6EXV < f6exv@hotmail.com <mailto:f6exv@hotmail.com>> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV
More All Messages By This Member
Re: Poblem on Clublog Paul F6EXV #78450 France I have manuall corrected the 13 calls that showed "inavlid country" after import. I would noyt want to do that if I imported 2000 QSOs.... What did I do wrong ? 73 Paul F6EXV toggle quoted messageShow quoted text Le 05/01/2020 à 13:14, Bob a écrit : If you type F6EXV into Logbook Entry Window, What Country is Logger32 telling you? Does the ADIF file from DXLog include The DXCC number somewhere? Importing ADIF files into Logger32 gives you a number of options. One option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you set this option? SeventyThree(s). On January 5, 2020 at 6:45 AM Paul F6EXV < f6exv@hotmail.com <mailto:f6exv@hotmail.com>> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV
More All Messages By This Member
Re: Poblem on Clublog Bob #78449 If you type F6EXV into Logbook Entry Window, What Country is Logger32 telling you? Does the ADIF file from DXLog include The DXCC number somewhere? Importing ADIF files into Logger32 gives you a number of options. One option is to Flag QSOs with no DXCC as "Invalid for DXCC". How did you set this option? SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 6:45 AM Paul F6EXV < f6exv@...> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV
More All Messages By This Member
Re: Poblem on Clublog Paul F6EXV #78448 It says "Not accepted for DXCC". This happened to all the QSO I imported (mostly JAs, but not only) toggle quoted messageShow quoted text Le 05/01/2020 à 13:01, Bob a écrit : Merde! If you look at the QSO in the Logbook Entry, What is the DXCC for the QSO? I suspect the problem is none of the three programs. It is probably the operator. SeventyThree(s). On January 5, 2020 at 6:45 AM Paul F6EXV <f6exv@hotmail.com> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV .
More All Messages By This Member
Re: Poblem on Clublog Bob #78447 Merde! If you look at the QSO in the Logbook Entry, What is the DXCC for the QSO? I suspect the problem is none of the three programs. It is probably the operator. SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 6:45 AM Paul F6EXV <f6exv@hotmail.com> wrote: Hi all I am sending this email to the 3 forums, as I am very unsure which program is "responsible" of the following. I logged a few QSO in CW on DXLog (CW, DXpedition mode). I exported that log to an adif file, and imported that file into Logger32. Logger32 then automatically uploaded these QSO onto Clublog. The upload went fine, BUT the country is indicated as "invalid". Any idea which program is responsible, and how to solve that ? Thanks + 73 Paul F6EXV
More All Messages By This Member
Re: QSO TIME Charles #78446 Paul, You can also set up the other user fields in the Log Entry Window and edit those during the Qso (or before the Qso has ended) which is very useful too. 73 Charles Charles Wilmott (MØOXO) 60 Church Hill, Royston, Barnsley, South Yorkshire, S71 4NG England, United Kingdom Tel ; (+44) 7900 500775 The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised. toggle quoted messageShow quoted text On Sun, 5 Jan 2020, 11:56 Bob, <k4cy@...> wrote: No, you can edit the Logbook Entry Window as much as you like BEFORE you add the QSO to the logbook. If your QTH is Marseilles, then I can change your name to AbdulRahman, or AbuBooBoo, or whatever they call themselves down there under the palm trees. I can even change the name to Paul before I log the QSO. SeventyThree(s). > On January 5, 2020 at 6:34 AM Paul F6EXV <f6exv@...> wrote: > > > Hi > In other words, I need to log a QSO, then edit it and modify whatever I > need/want to change ? > Can I edit all the fields BEFORE logging ? > Thanks + 73 > Paul F6EXV > > Le 05/01/2020 à 11:30, Bob a écrit : > > Like this? > > > > > > > > When you type <ENTER> this is what is entered into the Logbook. /ti > > change/set the QSO Start time type CTRL+S. The help file is more than > > 400 pages, I recommend you read it. SeventyThree(s). > > > > PS. To download the current Help File, Google GITHUB LOGGER32. > > > >> On January 5, 2020 at 5:17 AM Paul F6EXV < f6exv@... > >> <mailto:f6exv@...>> wrote: > >> > >> > >> Hi all > >> I am trying to see if it is possible to modify any field of the logging > >> windows BEFORE the QSO is actually logged ? > >> For example, how to I add an IOTA reference, how do I modify the time, > >> how do I add/modify a QSL manager, again, BEFORE the QSO is actually > >> logged. > >> If I have to log it first, and then edit the QSO to modify field(s), it > >> will have already be uploaded to ClubLog and/or LoTW. This is what I do > >> not want to happen. > >> > >> Thanks for help > >> 73 > >> Paul F6EXV > >> > > > > > >
More All Messages By This Member
Re: QSO TIME Bob #78445 No, you can edit the Logbook Entry Window as much as you like BEFORE you add the QSO to the logbook. If your QTH is Marseilles, then I can change your name to AbdulRahman, or AbuBooBoo, or whatever they call themselves down there under the palm trees. I can even change the name to Paul before I log the QSO. SeventyThree(s). toggle quoted messageShow quoted text On January 5, 2020 at 6:34 AM Paul F6EXV <f6exv@hotmail.com> wrote: Hi In other words, I need to log a QSO, then edit it and modify whatever I need/want to change ? Can I edit all the fields BEFORE logging ? Thanks + 73 Paul F6EXV Le 05/01/2020 à 11:30, Bob a écrit : Like this? When you type <ENTER> this is what is entered into the Logbook. /ti change/set the QSO Start time type CTRL+S. The help file is more than 400 pages, I recommend you read it. SeventyThree(s). PS. To download the current Help File, Google GITHUB LOGGER32. On January 5, 2020 at 5:17 AM Paul F6EXV < f6exv@hotmail.com <mailto:f6exv@hotmail.com>> wrote: Hi all I am trying to see if it is possible to modify any field of the logging windows BEFORE the QSO is actually logged ? For example, how to I add an IOTA reference, how do I modify the time, how do I add/modify a QSL manager, again, BEFORE the QSO is actually logged. If I have to log it first, and then edit the QSO to modify field(s), it will have already be uploaded to ClubLog and/or LoTW. This is what I do not want to happen. Thanks for help 73 Paul F6EXV
More All Messages By This Member

4481 - 4500 of 82924

Home Messages Hashtags About Features Pricing Updates Terms Help Twitter