|
Re: UDP Auto flagging for upload to LOTW?
Chuck Kraly K0XM
I agree Villi, but here is what I get when I right click
|
|
|
|
Re: Bandmap missing FT8
Marty W0EET
Bob and Vince,
Thanks for your detailed yet inappropriate and unnecessarily condescending responses. The problem was I, as a first time Telnet user, assumed VE7CC was streaming spots based on my filter settings and didn't look carefully enough at the content detail. In reality, they filter out FT8 spots by default. If you're seeing FT8 spots you must have turned it on via command line as described at VE7CC. So when I wasn't seeing FT8 spots in L32 I assumed there was a problem with the filtering in the DX Spotting. My bad. And one final point if I may. I'm a casual FT8 user, almost exclusively on 6m. I agree it's "mindless" but with a compromise antenna during the sunspot minimum it's better than nothing. I've been licensed since the mid '60s, have 324 countries confirmed, have built numerous QRP transceivers and antenna systems, tens of thousands of CW contacts operating from 3 countries, been coding since Basic, a BSEE. SO BUGGER OFF. SeventyThree(s)
|
|
|
|
Re: UDP Auto flagging for upload to LOTW?
Vilhjalmur Sigurjonsson
The menu route is: Right click on the log entry window, then Setup | QSLing and QSO export | Flag new QSO for LOTW 73 Villi
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Chuck Kraly K0XM
Ok I KNOW I must be missing something simple, but I am using either JTALert/JTDX or MSHV with UDP to Logger32. The QSO is added fine, BUT like yesterday on 6mtrs, I had to manually flag 65 qsos for LOTW upload. Is there a way for UDP packets to automagically be flagged on import? I looked through the messages here and I cannot see any of the options listed. Running the latest 3.50.418
|
|
|
|
Re: UDP Auto flagging for upload to LOTW?
ja1nlx
Chuck When you import adi file you see this table and options. 73
On 2020/06/11 19:20, Chuck Kraly K0XM
wrote:
Ok I KNOW I must be missing something simple, but I am using either JTALert/JTDX or MSHV with UDP to Logger32. The QSO is added fine, BUT like yesterday on 6mtrs, I had to manually flag 65 qsos for LOTW upload. Is there a way for UDP packets to automagically be flagged on import? I looked through the messages here and I cannot see any of the options listed. Running the latest 3.50.418 --
73 de aki JA1NLX
|
|
|
|
UDP Auto flagging for upload to LOTW?
Chuck Kraly K0XM
Ok I KNOW I must be missing something simple, but I am using either JTALert/JTDX or MSHV with UDP to Logger32. The QSO is added fine, BUT like yesterday on 6mtrs, I had to manually flag 65 qsos for LOTW upload. Is there a way for UDP packets to automagically be flagged on import? I looked through the messages here and I cannot see any of the options listed. Running the latest 3.50.418
Chuck K0XM
|
|
|
|
Re: Logger32 error
Mario, IZ8DBJ
Hello to all, thanks for the reply and for the help. I have disabled the lookups and hope to receive good news. Thanks again. 73 de Mario, IZ8DBJ
Il giorno gio 11 giu 2020 alle 09:57 F4FQH Olivier <unit365@...> ha scritto:
|
|
|
|
Re: Logger32 error
F4FQH Olivier
Ciao Mario,
Issue still not found. Bob said to desactivate lockups for the moment, but
we need it, so here, i make with the issue for the moment.
73
Olivier
F4FQH
From: Mario,
IZ8DBJ
Sent: Thursday, June 11, 2020 9:11 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 error Hello to all, Does nobody have idea of as resolving it? I have followed the councils that
Bob has given to me, but unfortunately the continuous problem to return the use
of Logger32 difficult.
73 Mario, IZ8DBJ
Il giorno sab 6 giu 2020 alle 11:31 Mario, IZ8DBJ
via groups.io
<iz8dbj@...> ha scritto:
|
|
|
|
Re: Logger32 error
Mario, IZ8DBJ
Hello to all, Does nobody have idea of as resolving it? I have followed the councils that Bob has given to me, but unfortunately the continuous problem to return the use of Logger32 difficult. 73 Mario, IZ8DBJ
Il giorno sab 6 giu 2020 alle 11:31 Mario, IZ8DBJ via groups.io <iz8dbj=gmail.com@groups.io> ha scritto:
|
|
|
|
VSC and sda2000
F4FQH Olivier
Hi all and Bob, Is there a way to setup VSC with the steppir SDA 2000
? Tryed many things and VSC don’t recognize the
controler. Tried to keep SDA100 in the setup and uncheked it but
nothing. I think they doesn’t work together finaly. In Ver, serial interface version there is ?? Bob, maybe a new feature in the VSC antenna controler to implement,
if it’s sure it’s not working! I can test if you need. Why i use VSC and nothing else because i have 2 rigs, 2 MK and i can
use the antenna with everybody ! Thanks 73s Olivier F4FQH
|
|
|
|
Re: Microsoft.NET Framework
Johan ZS1A
Ok found the problem.
The new Win 10 update changed the date format. I changed it back and did a Sats recalculation from Logger32. Wholla !
|
|
|
|
Re: Bandmap missing FT8
Vince Shirley
Marty, Kerpow!!.... You asked for that. FT8 bores the pants off me, but even I managed to do that for myself. Vince G0ORC
On Tue, 9 Jun 2020 at 19:30, Bob <k4cy@...> wrote:
|
|
|
|
Re: Bandmap missing FT8
Bob
Marty, can you be a little more specific. I connected to VE7CC and I get an avalanche of of FT8 DX Spots. Like this:
and in the DX Spots Window, I see this:
And the tooltip for AE4CC on 10M shows this:
It even knew 28074 was an FT8 frequency. Let's see what's in the 10M BandPlan:
and there isn't even a 10M segment in there. Magic. If you go back to the first picture, You'll notice that the FT8 DX Spots are from and aggregator or skimmer. In that case, Logger32 does not need to go to the BandPlan to figure out what the mode is, it's right there as the first word of the comment field.
And, one final point if I may. If I can paraphrase your question "We FT8 users are too bone idle to edit our own BandPlans, can you do it for us?" Did I miss something? SeventyThree(s).
On June 9, 2020 at 1:56 PM Marty W0EET <mhtmr10@...> wrote:
|
|
|
|
Bandmap missing FT8
Marty W0EET
Greetings
Ft8 dx cluster spots don't appear in my VE7CC Cluster Telnet connection in L32 apparently because the Bandmap doesn't have mapping of Ft8 although other digital modes are there. Now I suppose I could edit the mapping to include all those Ft8 fqs but since so many of us use that mode, couldn't it be incorporated in an L32 update? 73, Marty W0EET
|
|
|
|
Re: InonoProbe W10 Help
Rick Williams - VE7TK
Alex announced a month or so ago that Ionprobe has been discontinued. I believe the reason was difficulty in getting the necessary data.
73, Rick VE7TK
|
|
|
|
Re: L32 CW KEYER AND IC-7300
Mike
On Mon, Jun 8, 2020 at 11:00 PM, Richard Zalewski wrote:
Looking for some help with the settings for cw keyer and ic-7300.https://radioaficion.com/cms/ic-7300-usb-port-settings/
|
|
|
|
InonoProbe W10 Help
Clark WU4B
Even since converting to W10, while Ionoprobe runs (in the task bar), I can't bring up the app on the screen.
I sent an email to Alex, some time ago but never heard back. Does anyone know how to fix this? It also doesn't seem to be working with Hamcap when initiated from Logger32. TIA, -- 73, Clark WU4B
|
|
|
|
L32 CW KEYER AND IC-7300
Richard Zalewski
Looking for some help with the settings for cw keyer and ic-7300. Getting strange results playing around with settings on both ends. Tnx Richard W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
|
|
|
|
Re: Logger 32 - Crystal ball ...
F4FQH Olivier
just forgot something.....not at the same time connected to sames com ports
!!! if logger control some radio toys !!
From: F4FQH
Olivier
Sent: Monday, June 8, 2020 10:10 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger 32 - Crystal ball
... Ciao Bob !
A nice job !
Will be slower here...hmm 8700K clocked at 5.1GHZ, 32GO DDR4 at 3333, 2x
samsung 960pro RAID0, pc is ready for v4 ! ahaha
To test v4 on the same PC, simple. We have just to copy the logger32 folder
to an other location. In the INI just changing folders path, and rename
logger32.exe in, for example, logger32v4.exe. Create a shortcut on
desktop.
And 2 logger32 can be launched at same time.
So, everybody could keep 3.50 in good standing, and test V4 without
destroying their logs.
Of course, it’s better to really continue loging QSO on 3.50 to be sure, or
manualy log QSO in the v4, if the user don’t make a lot of QSO.
I will try v4
73
Olivier
F4FQH
From: Bob
Sent: Monday, June 8, 2020 9:48 PM
To: hamlogger@groups.io
Subject: [hamlogger] Logger 32 - Crystal ball ... It
was a good night last night. The local rioters and looters vandalized and set
fire to a neighborhood liquor store. I guess they're really pissed off about
George. As I already have a new flat screen TV and more Nikes than I can ever
wear, one of them was kind enough to stop by with a bottle of Famous Grouse for
me. I promptly opened it and poured a large glass with a single ice cube. As I
held it up to the light of the burning strip mall, I watched the glow of flames
play tricks as they reflected off the ice cube ... I saw the future of Logger32
unfolding right there before my eyes (well maybe it was the second or third
glass, I don't remember exactly) ... Logger32 ver 4.0 has been in Beta testing for a week or so. What's the big deal? There were primarily two objectives - an updated database to support more QSOs, and a replacement of the Microsoft serial port OCX. The Logger32 skin (its look, touch and feel) remains the same. Initial tests of the database on some random logbooks indicate logbook size of >1M QSOs is achievable. To give you an idea of how things have changed, on my PCs, the LoTW users file from Club Log uses about 5% of file capacity. With ver 4.0 it drops to 1%. A sample logbook with 275K QSOs I have uses 60% of available space on ver 3.50. With ver 4.0 it uses 17%. In addition to this, the updated database does a better job of efficiently storing the data for faster retrieval. The price for these performance enhancements is slower import of ADIF files, and slower recalculation of statistics. Also, the new database can read databases from ver 3.50, but once opened in 4.0 the become unreadable to 3.50 -- There's no backward compatibility. The replacement serial port OCX has been implemented for the radios, the CW Machine, and rotor control. No problems so far. I am in absolutely no hurry to release 4.0, and guesstimate maybe Christmas. But we need more testers. Many more testers. For those with two PCs, it's easy, just copy some files to one of the PCs and you're good to go. For those with a single PC, it's a little tricky, and if you open your logbook with ver 4.0 in error, it becomes unreadable on 3.50. Once the volunteers gain a little confidence in 4.0, you can use as your main logging program - updates and bug fixes are done by auto-update. If you want to participate, eMail Jim at w5ifp@... he will subscribe you to a new reflector, get you destructions, and the files you need to get started. Thanks, SeventyThree(s).
|
|
|
|
Re: Logger 32 - Crystal ball ...
F4FQH Olivier
Ciao Bob !
A nice job !
Will be slower here...hmm 8700K clocked at 5.1GHZ, 32GO DDR4 at 3333, 2x
samsung 960pro RAID0, pc is ready for v4 ! ahaha
To test v4 on the same PC, simple. We have just to copy the logger32 folder
to an other location. In the INI just changing folders path, and rename
logger32.exe in, for example, logger32v4.exe. Create a shortcut on
desktop.
And 2 logger32 can be launched at same time.
So, everybody could keep 3.50 in good standing, and test V4 without
destroying their logs.
Of course, it’s better to really continue loging QSO on 3.50 to be sure, or
manualy log QSO in the v4, if the user don’t make a lot of QSO.
I will try v4
73
Olivier
F4FQH
From: Bob
Sent: Monday, June 8, 2020 9:48 PM
To: hamlogger@groups.io
Subject: [hamlogger] Logger 32 - Crystal ball ... It
was a good night last night. The local rioters and looters vandalized and set
fire to a neighborhood liquor store. I guess they're really pissed off about
George. As I already have a new flat screen TV and more Nikes than I can ever
wear, one of them was kind enough to stop by with a bottle of Famous Grouse for
me. I promptly opened it and poured a large glass with a single ice cube. As I
held it up to the light of the burning strip mall, I watched the glow of flames
play tricks as they reflected off the ice cube ... I saw the future of Logger32
unfolding right there before my eyes (well maybe it was the second or third
glass, I don't remember exactly) ...
Logger32 ver 4.0 has been in Beta testing for a week or so. What's the big deal? There were primarily two objectives - an updated database to support more QSOs, and a replacement of the Microsoft serial port OCX. The Logger32 skin (its look, touch and feel) remains the same. Initial tests of the database on some random logbooks indicate logbook size of >1M QSOs is achievable. To give you an idea of how things have changed, on my PCs, the LoTW users file from Club Log uses about 5% of file capacity. With ver 4.0 it drops to 1%. A sample logbook with 275K QSOs I have uses 60% of available space on ver 3.50. With ver 4.0 it uses 17%. In addition to this, the updated database does a better job of efficiently storing the data for faster retrieval. The price for these performance enhancements is slower import of ADIF files, and slower recalculation of statistics. Also, the new database can read databases from ver 3.50, but once opened in 4.0 the become unreadable to 3.50 -- There's no backward compatibility. The replacement serial port OCX has been implemented for the radios, the CW Machine, and rotor control. No problems so far. I am in absolutely no hurry to release 4.0, and guesstimate maybe Christmas. But we need more testers. Many more testers. For those with two PCs, it's easy, just copy some files to one of the PCs and you're good to go. For those with a single PC, it's a little tricky, and if you open your logbook with ver 4.0 in error, it becomes unreadable on 3.50. Once the volunteers gain a little confidence in 4.0, you can use as your main logging program - updates and bug fixes are done by auto-update. If you want to participate, eMail Jim at w5ifp@... he will subscribe you to a new reflector, get you destructions, and the files you need to get started. Thanks, SeventyThree(s).
|
|
|
|
Logger 32 - Crystal ball ...
Bob
It was a good night last night. The local rioters and looters vandalized and set fire to a neighborhood liquor store. I guess they're really pissed off about George. As I already have a new flat screen TV and more Nikes than I can ever wear, one of them was kind enough to stop by with a bottle of Famous Grouse for me. I promptly opened it and poured a large glass with a single ice cube. As I held it up to the light of the burning strip mall, I watched the glow of flames play tricks as they reflected off the ice cube ... I saw the future of Logger32 unfolding right there before my eyes (well maybe it was the second or third glass, I don't remember exactly) ...
Logger32 ver 4.0 has been in Beta testing for a week or so. What's the big deal? There were primarily two objectives - an updated database to support more QSOs, and a replacement of the Microsoft serial port OCX. The Logger32 skin (its look, touch and feel) remains the same. Initial tests of the database on some random logbooks indicate logbook size of >1M QSOs is achievable. To give you an idea of how things have changed, on my PCs, the LoTW users file from Club Log uses about 5% of file capacity. With ver 4.0 it drops to 1%. A sample logbook with 275K QSOs I have uses 60% of available space on ver 3.50. With ver 4.0 it uses 17%. In addition to this, the updated database does a better job of efficiently storing the data for faster retrieval. The price for these performance enhancements is slower import of ADIF files, and slower recalculation of statistics. Also, the new database can read databases from ver 3.50, but once opened in 4.0 the become unreadable to 3.50 -- There's no backward compatibility. The replacement serial port OCX has been implemented for the radios, the CW Machine, and rotor control. No problems so far. I am in absolutely no hurry to release 4.0, and guesstimate maybe Christmas. But we need more testers. Many more testers. For those with two PCs, it's easy, just copy some files to one of the PCs and you're good to go. For those with a single PC, it's a little tricky, and if you open your logbook with ver 4.0 in error, it becomes unreadable on 3.50. Once the volunteers gain a little confidence in 4.0, you can use as your main logging program - updates and bug fixes are done by auto-update. If you want to participate, eMail Jim at w5ifp@... he will subscribe you to a new reflector, get you destructions, and the files you need to get started. Thanks, SeventyThree(s).
|
|
|
