开云体育

Hi, I don't know since when, but when I enter a callsign, the Azimuth indicated by logger is the right one, but if I precede the callsign with a prefix, followed by slash and the station callsign,

Lorenzo What do you expect CheckSpot ? It only displays your interested DX spot. Yes, clicking does nothing. This is by design. 73 de aki JA1NLX

hi Aki i click every where but nothing... of course i make a wrong setup....but i put in a new forder the application ...i see Connected to logger32, i see the spot into? down bar (pse see the screen

Rick the reason I said it didn't upload is because one, I received an error message telling me to check the error log which I cannot find, two, normally after it says successful I see the QSO's in the

Dear all ... the uploaded file if it is uploaded on LoTW will no longer be on your computer you just have to give the time for the server to manage and at the same time there is actually the crossing

Hi all New utility CheckSpot ver4.0 released. See details on my utility page. https://ja1nlx.web.fc2.com/UtilityProgram/index.html [https://ja1nlx.web.fc2.com/UtilityProgram/index.html] 73 de aki

"The utility removes all the Flag to Upload to LOTW before it actually uploads the file. " This is not the case. This question is being asked by Logger32 and has not passed any Data off to the utility

First thanks to Rick for the QSL utility and his other add-ins that work great. One issue with the QSL utility that I wish could be addressed is the following. The utility removes all the Flag to

I have no idea what a AGHIv font is, but if it works for you on the Logbook Entry Window, use it. SeventyThree(s).

*Okay, then explain to me why it is possible to enter information in Cyrillic when using the AGHIv Cyrillic Normal font?* **

In your example, Logger32 uses the ADIF fields NAME and QTH, not NAME_INTL and QTH_INTL The ADIF fields NAME and QTH use ASCII characters 32 to 126. The NAME_INTL and QTH_INTL use UTF-8 encoded

*Hello Bob* *in the QSO input window, not a single font supports Cyrillic. Can this be fixed? In other windows and tables everything is fine. Thank you**,* *Valery 73* [image:

If, as you say, there are no decoded callsigns appearing the UDP BandMap, then it is possible/probable that Logger32 and JTDX (or whatever) are not talking to each other by UDP messages. One of the

Sorry about little information , the call signs don’t show up in the band map panel and I also checked the tcp/adif is and it was unchecked Bob, every thing working on the 26th of Feb and nothing

Precious little information ....I'll assume you're using UDP logging. I'll further assume the Logger32 UDP BandMap is alive as well, and showing decoded stations callsigns. If my assumptions are

Anyone had any problems today as regard to logging FT8 and FT4 qso’s direct into to logger32 none of qso’s were logged into my logbook using JTDX WSJTX luck has if the went info there respective

GE Bob, I have learned another possibility : SPLIT how did I live without it till today ... hehe Incidentally I had an old L32 manual so I did not find your references, now is ok. TNX x help 73 Phil

AHHH! So you are the ONE !!!! ? 73 de Larry K8YYY [email protected]> wrote:

If I needed to do that, I would use macros I already have ... a) Split up 5 b) Tune c) Split off. SeventyThree(s). PS. I always tune on the TX frequency. It gives the other station warning to turn

HI Gary, John et All. Thank you for the advices, after 20 et more years of L32 use I have learned more options I never used HI. Both options the Scratchpad and the DX-Spot_History relate to the SPOTs