Re: Jim (W5IFP)
And hope Jim for all the best!? I just want to tell that there are friends on another side of the earth caring about him. 73 de Joseph, BD4EPV
By
BD4EPV
·
#85105
·
|
Re: Jim (W5IFP)
Thanks you for sharing and your eloquence Bob.? My prayers for Jim and his family. Larry K8YYY Shinnston WV EM99uk -- I got expelled from school on Pajama Day. Not my fault - I sleep naked.
By
Larry Fravel
·
#85104
·
|
Re: Jim (W5IFP)
I really hope Jim is back again. 73 de aki JA1NLX
By
ja1nlx
·
#85103
·
|
Re: Jim (W5IFP)
Very nice said Bob Get well Jim de KB2SSE
By
Kenneth Hansen <khansen@...>
·
#85102
·
|
Re: Jim (W5IFP)
Randall, thanks so much for your message. We, the Logger32 community and Beta testers, have been very concerned for Jim's well being for a few weeks. Please tell Jim we are all rooting for him, and he
By
Bob
·
#85101
·
|
Re: LOTW showing ¡°cross¡± band contacts
When logging FT4/FT8 contacts that originated from UDP messages, a single frequency is part of the message. It is the radio VFO frequency plus the transmit audio. This is logged as the ADIF FREQ
By
Bob
·
#85100
·
|
Re: LOTW showing ¡°cross¡± band contacts
??? IF you start WSJT-X from the Start menu on the UDP BandMap, it takes control of the radio away from Logger32 (Logger32 drops its CAT connection, then WSJT-X opens its CAT connection). This happens
By
Gary Hinson <Gary@...>
·
#85099
·
|
Re: LOTW showing ¡°cross¡± band contacts
I also had the issue. But it was operator error. WSJT you never changed the frequency in the program. Mine was a 60m contact and I had 6m on wsjt. That¡¯s why it di the cross band. Sent from Mail for
By
Bruce B
·
#85098
·
|
Re: LOTW showing ¡°cross¡± band contacts
Hi Dale. Please check section 38.10 of the User Manual <https://www.logger32.net/files/Logger32_v4_User_Manual.pdf#page=625&zoom=100,76,710> for me. Does that help? I don¡¯t use SO2R so haven¡¯t had
By
Gary Hinson <Gary@...>
·
#85097
·
|
LOTW showing ¡°cross¡± band contacts
On a recent manual upload (from Logger 32 to LOTW) many Qs in LOTW showed the band as ¡°cross¡±¡which they were not. Everything in Logger looks fine and all the Qs were made with WSJT X. ?I¡¯m
By
Dale Peterson
·
#85096
·
Edited
|
Re: CW machine issue
Hi, open radio 1 (or 2), does your computer sees the radio? 73
By
Panos
·
#85095
·
|
Re: Cherry picking
What do you see in the cherry-picking event viewer? SeventyThree(s).
By
Bob
·
#85094
·
|
Cherry picking
Due to computer failure, I am setting up Logger32 and WSJT-x again. All seems to work now except that Cherry picking is not working. Seems to me that Logger32 is picking up callsigns and immediately
By
Andy VA3PL
·
#85093
·
|
Re: WAS
there are also several AK callsign stations that are in the 48 states so make sure it really is AK.
By
Joe N3XLS
·
#85092
·
|
Re: WAS
Thanks Bob It is now fixed, state field was the issue
By
Kenneth Hansen <khansen@...>
·
#85091
·
|
Re: CW machine issue
Blame Bill G. Look into windows logs, you might find something interesting about that issue there. Mike
By
Mike
·
#85090
·
|
CW machine issue
CW machine fails to load: Any help?
By
Antonis Parashis
·
#85089
·
|
Re: Error 6
Hello Bob When the error message appears, I have to press OK about 3-4 times until the window goes away. Whether after that the red VFO arrow appears in the bandmap window, I do not know now.
By
HB9DDS
·
#85088
·
|
Re: WAS
Also, check the QSO to make sure thew STATE field says AK, 73.
By
Bob
·
#85087
·
|
Re: WAS
I will check, Thanks for theinfo Kenneth Hansen Owner ScanAm Technical Services, LLC
By
Kenneth Hansen <khansen@...>
·
#85086
·
|