|
Re: Logger32 RadioInfo UDP Broadcasts
Terry Glagowski / W1TR / AFA1DI
I would like to suggest that you make the periodic transmission more like 5 seconds or 10…
73, Terry / W1TR : )
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Monday, January 06, 2020 18:08 To: hamlogger@groups.io Subject: Re: [hamlogger] Logger32 RadioInfo UDP Broadcasts
Too late for auto-update 3.50.404, it was released this morning. The next version (in a few weeks) will have this format
'<?xml version="1.0" encoding="utf-8"?> and will broadcast the current frequency at least every 4 minutes - that way you can safely put your out-to-lunch timer at 5 minutes ... I'll add that tomorrow. SeventyThree(s). SeventyThree(s).
|
|
|
|
Re: Logger32 RadioInfo UDP Broadcasts
Bob
Too late for auto-update 3.50.404, it was released this morning. The next version (in a few weeks) will have this format
'<?xml version="1.0" encoding="utf-8"?>
'<app>Logger32</app> '<RadioInfo> ' <Freq>2120000</Freq> ' Note format is like 1420000 '</RadioInfo>
and will broadcast the current frequency at least every 4 minutes - that way you can safely put your out-to-lunch timer at 5 minutes ... I'll add that tomorrow. SeventyThree(s).
SeventyThree(s).
On January 6, 2020 at 5:30 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:
|
|
|
|
Re: Logger32 RadioInfo UDP Broadcasts
Terry Glagowski / W1TR / AFA1DI
Bob, Thanks for creating a UDP broadcast in Logger32 so that other applications can piggyback off the Logger32 Rig Control… The HFAUTO APP uses these UDP broadcasts to preset the ATU L/C Element Tuning Solution to track the TX VFO so that an AutoTune cycle is unnecessary.
There are now 3 applications that I know of which broadcast a <RadioInfo> UDP Packet in XML Document Format, each one a little different. N1MM has the most comprehensive set of radio properties, including both a <Freq> and <TXFreq> element and <RadioNr>, <FocusRadioNr>,<ActiveRadioNr> elements, plus a few more. DXLAB has these as well, but not a <FocusRadioNr>,<ActiveRadioNr> If an APP works with multiple transceivers, it is important to indicate which one should be used as a TX VFO source to set the L/C Tuning Solution. It cannot be jumping around from radio to radio since the HF-AUTO has continuously tunable L/C components, not relay switched ones.
The HFAUTO app can receive any number of UDP packets in XML Document format on any number of UDP ports for IPAddr=0.0.0.0. It’s a good thing that all the APPs don’t send the exact same <RadioInfo> UDP packet because I could not then tell which APP is the source. My preference would be that each application use a different XML Document Name… The FLDIGI_UDP helper program uses XML Document <FLDIGI> OR… if there were an element in the <RadioInfo> packet that identified the APP, such as <APP>Logger32</APP>
Another thing that can be an issue is that Logger32 only broadcasts the <RadioInfo> UDP Packet when there is a change in frequency. The HFAUTO APP uses a timeout to determine when CAT control has been lost due to a terminated application… this is adjustable in HFAUTO and can be shut off (CAT TMO=0) It would be really great to have a UDP packet every few seconds (5, 10, 20 seconds) even if there is no change, to confirm that CAT control is still active. N1MM does this, also DXLAB… currently FLDIGI_UDP (my APP) does so every 200 ms whether there is a change or not, but maybe this is wasteful of bandwidth.
I’m not sure how Logger32 handles SPLIT operation, but the other APPs have both a <Freq> and <TXFreq> element in the UDP, the HFAUTO needs the <TXFreq>… If one is not received, HFAUTO assumes <TXFreq> = <Freq> and transceiver mode without split is being used. The HFAUTO APP does not make use of MODE information, but N1MM, DXLAB, and FLDIGI all have a <Mode> element. Other APPs might need this information.
Kudos on using a decimal point to get the Hz digit… I always wondered why N1MM didn’t use a number in Hz instead of 10 Hz count! Earlier radios did not use 1 Hz resolution, but good systems engineering would have predicted that they would someday!
73, and I appreciate your help!
Terry G. Glagowski, Ph.D. / W1TR TGG Systems . (EMail) TGGsystems@ GMail.com .
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Sunday, January 05, 2020 06:23 To: hamlogger@groups.io Subject: Re: [hamlogger] Logger32 RadioInfo UDP Broadcasts
... and I don't have a radio with CAT control, but I simulated a VFO frequency change to 14001.234 kHz. This is broadcast:
<?xml version="1.0"?>
Simulated a frequency change to 14123 kHz. This is broadcast:
<?xml version="1.0"?>
SeventyThree(s)/
|
|
|
|
Re: Previous QSO's Exclamation Mark - Cannot display
Bob
Can't stretch a child form height? Two options: 1) Push the mouse button harder, or 2) Click VIEW and UNcheck the LOCK CHILD WINDOWS option. SeventyThree(s).
On January 6, 2020 at 4:17 PM "Anthony Buscaglia via Groups.Io" <tonybb@...> wrote:
|
|
|
|
Re: LOTW Sent flag
Bob
There is more than one way to send your QSOs to LoTW for verification. One way is to use the N2AMG application L32LogSync, another is to export an ADIF file (click FILE | EXPORT FILES | EXPORT LOTW FILE. How are you attempting it? SeventyThree(s).
On January 6, 2020 at 3:45 PM Marvin Stern <marbern@...> wrote:
|
|
|
|
Previous QSO's Exclamation Mark - Cannot display
Anthony Buscaglia
I have a problem with displaying previous QSO’s.
Over 200k Q’s in the log. I tried re-installing but still a problem. Any advice appreciated. Thanks 73 Tony K2NV
|
|
|
|
LOTW Sent flag
Marvin Stern <marbern@...>
After uplogging LOTW sent file to LOTW, It does not change sent flag to Y. HELP
|
|
|
|
Re: LOTW ADIF Sync problem
Bob
I haven't made a QSO in well over 10 years, so synchronizing my logbook with anything other than a hand chiseled granite stone isn't a priority. Hopefully someone on here can come to your aid. SeventyThree(s).
On January 6, 2020 at 12:38 PM "Anthony Buscaglia via Groups.Io" <tonybb@...> wrote:
|
|
|
|
Re: LOTW ADIF Sync problem
Anthony Buscaglia
Bob,
toggle quoted messageShow quoted text
That works if on the DXCC if there are no Granted for that DXCC Entity. But if you try to make the DXCC window show the correct Granted band countries it doesn’t compare with the DXCC Awards on LOTW. At least not in my case….. Tony
|
|
|
|
Re: LOTW ADIF Sync problem
Bob
I made a dummy logbook with one QSO with K2NV on 20M. DXCC shows 1 worked. I click on the W cell under the 20M column. The generic QSOs window opens and shows all 20M QSOs. I click on the K2NV QSO. This QSO is now highlighted in the Logbook Page Window (don't you just love how easy it is to navigate with the mouse?). Right click on the QSO, select the SET/SHOW AWARD CREDITS option. Just for fun I check the LoTW GRANTED option and click APPLY. I can still see the DXCC Window on the screen. It shows USA/20M cell is still W. Click on this cell to show the generic QSOs USA/20M and the K2NV QSO is now GRANTED. So, it all worked as expected. SeventyThree(s).
On January 5, 2020 at 8:57 PM "Anthony Buscaglia via Groups.Io" <tonybb@...> wrote:
|
|
|
|
Re: LOTW ADIF Sync problem
Bob
Looking at the code, it is expecting to see
<PROGRAMID:4> somewhere in the ADIF file header. I don't know what the context is, but it needs to be there or the file is rejected. SeventyThree(s).
On January 5, 2020 at 8:57 PM "Anthony Buscaglia via Groups.Io" <tonybb@...> wrote:
|
|
|
|
Re: LOTW ADIF Sync problem
Anthony Buscaglia
Hi Bob,
toggle quoted messageShow quoted text
Thanks for your response. 1.) I’ll try to figure out the header problem with ADIF Master… 2.) So let me see if I understand… You are saying that once the DXCC is updated and the DXCC Mixed, CW, Phone & Data are correct overall the Band Entries will not change. If I click on a “C” (now a “G” in DXCC Challange Table ) there is no way to make the DXCC WIndow reflect the fact that the band QSO is really Credited 3.) Yes I understand that I can go back and click see the update, but I have over 2500 to check….. I am running out of time…. (78) I am very thankful for the software, just trying to understand what to expect. 73 Tony K2NV
|
|
|
|
Re: CQ RU Cherrypicking
Huh? I'm not sure how that is related at all. My issue is that the FT4 or FT8 station I wish to communicate has now sent CQ RU ( CQ Roundup) which effectively means the same thing as CQ in that any station should be able to answer it. Logger 32 appears to treat it as a call to the mythical continent of "RU" where I don't reside. So it terminates my previous request to talk to that station in the cherry-pick window or manual window instead of answering it. If they just sent CQ, like they would on 364 other days of the year, it would answer it. Contests are great opportunities to cherry pick DX in any mode.
|
|
|
|
Re: CQ RU Cherrypicking
Tom Wylie
I was looking for Delaware but it won't let me send CW DE........ Tom GM4FDM
On Sun, 5 Jan 2020 22:41 Gary Wilson, <k2gw@...> wrote:
|
|
|
|
CQ RU Cherrypicking
As an avid user of Logger 32 and it's predecessor for 16 years, I love the product and have been having a ball with the new interface for cherry-picking needed contacts out of WSJT-X via UDP. But I think I ran across and inadvertent (and uncommon) problem today during the ARRL RTTY Roundup which now includes the FT8 and FT4 modes. During this contest, people call "CQ RU" instead of the normal "CQ" Both cherry-picking and manual selection from the Logger32 UDP band map start out fine, but as soon as a station sends "CQ RU", both the cherry-picking and manual selection options terminate the request. They probably think the station is only trying to call a station in a mythical continent or in Russia, and since I'm in neither, terminates my transmit request to WSJT. If it's some setting I'm overlooking, please let me know, but if not, it would be nice to allow folks to configure which "CQ xx" strings they would like to be able to cherry-pick, manually respond to, or ignore. It's not time critical as it will only occur during a contest like this past weekend. Gary, K2GW
|
|
|
|
Re: HFAUTO Program To Logger
Bob
Thanks, 73.
On January 5, 2020 at 2:33 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:
|
|
|
|
Re: HFAUTO Program To Logger
Terry Glagowski / W1TR / AFA1DI
I just released HFAUTO version 3.9.3.0 that is interoperable with Logger32.
Terry / W1TR
|
|
|
|
FW: HFAUTO Version 3.9.3.0 Released - Support for N1MM, DXLAB, Logger32, FLDIGI + FLDIGI_UDP Tested
Terry Glagowski / W1TR / AFA1DI
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 . (EMail) TGGsystems@ GMail.com .
|
|
|
|
Re: LOTW ADIF Sync problem
Bob
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).
|
|
|
|
Re: Logger32 with DStar, DMR and Fusion
keith hotchkiss
As easy as that. Cheers for your support.
HNY - Keith
|
|
|
