开云体育

It seems that Logger32 tracks the "main" WAZ Awards 5BWAZ, and WAZ for Mixed, SSB, CW, RTTY, and Digital. (Yes, WAZ treats RTTY as a distinct mode.) I recently earned the WAZ award for 12m, all in digital mode. There does not seem to be a way to mark that award as "Granted" for any of the QSOs in that award submission using the panel for updating awards. I get a warning that it cannot be done because a Primary Administrative region is unspecified, but that seems to be a wayward notice. It seems that the WAZ award may not be activated for reporting individual bands. If that's the case, OK. (There are numerous WAZ award categories with unique awards available for almost all modes on all bands--perhaps more programming than anyone would like to undertake an retain one's sanity!)

My old laptop has seen better days. I need to upgrade, and would like to hear recommendations from the Logger32 Logging Program group and WWDXC club member group. I am naturally concerned about L32 compatibility. Your advice would be greatly appreciated. - John Owens - N7TK

Effective today, April 3, 2025, all Logger32 License and Annual Maintenance fees are subject to the US Department of Commerce 'Reciprocal Tariffs'. The additional revenue will be automatically deposited in my 'Famous Grouse' fund. Are we having fun yet? SeventyThree(s).

I wonder, is it possible to have Logger32 translate the CAT data received from a connected radio before it sends it to the Echo port? I have searched the user manual, but can't see anything. That's not to say it isn't there, of course... The use case I have in mind is: Radio (FTdx101) connected to Logger32 via USB Amplifier (Acom 2000) connected to radio via coax and PTT cable At present, the amplifier automatically tunes to whatever segment it detects when I send it some RF. It is possible, however, to connect the amplifier to a serial port and have it select the appropriate band segment as the data on the serial port changes. This means the amplifier is already tuned correctly prior to RF being applied, which is probably slightly better for the amplifier. In a perfect world, I could connect the amplifier CAT port to the serial connector on the rear panel of the radio, but, apparently, the Acom doesn't speak FTdx101 language. Yaesu changed the format of the CAT data for the FTdx101 & FTdx10 series of radios, as I understand it. Thus, I thought a work-around could be to send the data out from the logging software via the Echo port. It would need to be translated into something more vanilla, before being sent, though- Kenwood TS2000 or Yaesu FT1000, maybe. This would compensate for the amplifier firmware's inability to communicate with the FTdx101 or FTdx10. Is there already a way to do this? If not, is it something that would constitute a worthwhile enhancement? Or is it only me? Cheers, John G4DRS

Logger32 3.5.454 worked a week ago. Today It wold not connect to Flex via COM4. N1MM connects. I updated to 4.0. It asked my to recalculate statistics. While the program was doing it, an upgrade windows popped up and I foolishly agreed before the recalculation was complete. Now when starting, there is a message about ADIFCountriesWithSecondary_Subdivisions.txt missing, and the program stops. Any idea why the COM4 stopped working with logger 32 and still works with N1MM? How to fix the message? When 4.0 came up, it also did not read COM4. Ignacy NO9E .

GE Bob, I followed all the instructions in the manual, kept getting the same error message, turned off the Firewall and then tried to run autoinstaller.exe as an administrator and got a different error message, one that wasn't in the manual so went with Plan C, and updated manually. Easy Peasy, but it's strange that I never had this problem before In any case, the problem is resolved even if I can't figure out what caused it. Thanks for your help, 73, Dave WB2PJH

Hello, I contacted today 3B9FA on 6m FT8. The Qso is automatcaly uploaded in my Logger32 Logbook page and all is ok. On the other hand, this contact (new one for me) does not appear in the window DXCC Challenge Award. I do "recalculate the statistcs" in Tools window but nothing changes and the box W does not appear. Any idea ? Tks for help. 73's. Jean-Claude F6HDH

Found it, seems my L32 window had been re- sized somehow to what I showed, managed to re-size it OK now it behaves properly. 73 Ian G4GIR

Suddenly happened. When I open one of my configs it opens like this. When I click on the centre MAXIMISE symbol it opens up and fills the screen. If I try to drag it in order to resize it it just reverts back to the above. I guess this is a winowzzz thing. As other Config short cuts open OK. Anyone have a clue why this is happening? 73 Ian G4GIR

Hi Bob, Hi group! 1. Concerning the radio-status for my PA: Recently I needed to activate UDP-broadcast of radio-status to send the QRG of my radio to an RF2K-amp in the same network as my L32-computer. In the L32 manual and other groups I found information how to activate the broadcast. I struggled a bit because my PA ( IP 192.168.0.235, UDP-port 12060) wouldn?t hear the shouts of L32, which runs on a machine at 192.168.0.232. I think that L32 broadcasts the status just for the local machine on 127.0.0.1. Is that true? If yes, would it be possible to give an IP to L32 where the UDPs should be talked to? 2. Concerning UDP and rotators: I?d like to run two rotators using L32s capability to send rotator commands thru UDP. One rotator 1 is used for HF and rotator 2 is used by another trx and for VHF. I run two instances of pstRotatorAz in the background on the same machine as L32 runs. So these broadcasts could be local ones like 127.0.0.1. Am I able to do this? Do I have to setup two rotators with two different rotator-UDP-ports? Can I assign specified ports for the two rotators? Thanks for reading all this and being concerned like I am :-) 73 de Lenz, DL8RDL

I apologize if this has been discussed here before. We have a new toy called GOTA - Grids on the Air. You need to have the grid in the adif record. After manually inserting the grid into the existing QSO record (a QSO way back in time) the Logger thinks for a while, then uselessly opens the window to change the Administrative primary and secondary subdivision. Closing that window causes the jump to the end of the logbook. You have to search again for the original QSO. You see then that the grid was entered correctly , but you have lost few seconds of time. To process hundreds or thousands of logbook records this way drives you crazy. Could this bug be fixed please? 73, Ruda, OK2QA