Date   

Re: Cherry-picking and tail-ending for "RRR"

Damian M0BKV
 

It works for me, perfectly. RR73 or RRR after R-18 or whatever the RST/dB is sent IS a good contact so 73 following is polite and also confirms completion which we all like to know BUT isn't compulsory so moving to the next call after RRR or RR73 should be no problem.


On Wed, Mar 31, 2021, 07:32 Fabio IZ8MBW via groups.io <iz8mbw=yahoo.it@groups.io> wrote:
Hi Gary.
I agree with you and I partially don't agree with you  :-)
I agree to not call call a station "premature" but generally DX Station will go on to make QSOs with other station also without "wait" for the “73”.
The theory is different from practice, in a big pile up condition no one DX Station wait for “73” before to make others QSOs. About always, after a QSO is just finished, I send “73” but the DX Station is already "busy" to answers to all the others station without consider my "73".

Anyway, since some stations send "RRR" instead of "RR73" and Logger32 consider "RR73" as a good condition for "Cherry-picking" to start to call the station, I don't understand why "RR73" is OK and "RRR" is not OK.
Since "RRR" is a synonymous of "RR73" Logger32 should behave the same way.

In conclusion, in my opinion, make more sense that Logger32 will consider "RRR" as good condition for "Cherry-picking" to start to call like it do for "RR73".

Thank you and 73s.



Fabio, IZ8MBW



On Tuesday, March 30, 2021, 10:46:56 PM GMT+2, Gary Hinson <gary@...> wrote:


Hi Fabio.

 

“RRR” normally precedes the final over when the station sends a “73”.  So, arguably, calling someone who has just sent an RRR message is not tail-ending and is a little premature.

 

Personally, I’m usually happy to wait until the QSO is over before calling, spending my time looking for a suitable frequency to transmit on rather than transmitting at every opportunity.

 

The exception is when the DX station is going rapidly from QSO to QSO without a break or CQing.  After maybe 5 to 10 minutes trying politely but unsuccessfully to tail-end, I may turn on Hound mode in JTDX to call him after every over for a while (just a few mins), provided I am transmitting on a clear frequency.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Fabio IZ8MBW via groups.io
Sent: 31 March 2021 08:01
To: Logger32 Groups Io <hamlogger@groups.io>
Subject: [hamlogger] Cherry-picking and tail-ending for "RRR"

 

Hello.

Based on my experience of use, the "Cherry-picking" works after decode of "CQ", "73" and "RR73" but it does not work after decode of "RRR".

Some station likes to use to send "RRR" instead of "RR73".

 

This is an example, the station "CP6UA" sent the "RRR" and the "Cherry-picking" did not start to call him:

 

 

 

 

I hope that a future upgrade of Logger32 will cover also "RRR" for Cherry-picking and tail-ending.

 

Thanks.

 

 

 

73s

Fabio, IZ8MBW

 


ODP: [hamlogger] ODP: Future request - Spot locally to Band Map

Andy VA3PL
 

Hi Gary
That was my senior moment and when you pointed it to right direction all came back to me.
Thank a lot

Andy



Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Gary Hinson <Gary@...>
Wysłane: sobota, 3 kwietnia 2021 20:09
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] ODP: Future request - Spot locally to Band Map
 

Section 14.5 is closer to the mark, Andy, describing 4 ways to spot stations privately on your bandmaps

 

 

If you really want to get to know all the ins and outs of the program, try writing/revising the User Manual!  A year ago, I didn’t know how bookmarks or the scratchpad worked, and there are other Logger32 functions I am still learning about.  It’s a voyage of discovery.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jose EA7BJ
Sent: 03 April 2021 22:34
To: hamlogger@groups.io
Subject: Re: [hamlogger] ODP: Future request - Spot locally to Band Map

 

Hi Andy and all.

I don't know if it's what you're looking for, see section 14.3 of the manual, "dx spot history"

73 Jose EA7BJ


Re: ODP: Future request - Spot locally to Band Map

Gary Hinson
 

Section 14.5 is closer to the mark, Andy, describing 4 ways to spot stations privately on your bandmaps

 

 

If you really want to get to know all the ins and outs of the program, try writing/revising the User Manual!  A year ago, I didn’t know how bookmarks or the scratchpad worked, and there are other Logger32 functions I am still learning about.  It’s a voyage of discovery.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jose EA7BJ
Sent: 03 April 2021 22:34
To: hamlogger@groups.io
Subject: Re: [hamlogger] ODP: Future request - Spot locally to Band Map

 

Hi Andy and all.

I don't know if it's what you're looking for, see section 14.3 of the manual, "dx spot history"

73 Jose EA7BJ


Re: BandMap

thott2001
 

I got it.....
Trial & Error and study the manual in detail. 
For me it’s solved ......

73! Thomas, DG8FBV and nice Easter holidays 


Am 03.04.2021 um 11:33 schrieb thott2001 via groups.io <thott2001@...>:

I am to stupid :-) 

I need your help how can I configure that within 
 the BandMap instead of Monitor, the Bands are 
 shown to select the separate Band? 

I read the manual but I can not configure it :-(
<image0.jpeg>


Thank you for your help!

73! Thomas, DG8FBV 


Re: ODP: Future request - Spot locally to Band Map

Jose EA7BJ
 

Hi Andy and all.

I don't know if it's what you're looking for, see section 14.3 of the manual, "dx spot history"

73 Jose EA7BJ


BandMap

thott2001
 

I am to stupid :-) 

I need your help how can I configure that within 
 the BandMap instead of Monitor, the Bands are 
 shown to select the separate Band? 

I read the manual but I can not configure it :-(


Thank you for your help!

73! Thomas, DG8FBV 


ODP: [hamlogger] Future rwquwst - Spot locally to Band Map

Andy VA3PL
 

I am getting old Pavel...hi hi . I am a long time user of Logger32 and some how I missed this option.
Thanks a lot Pavel.
I owed to you.
Take care

Andy


Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Pavel Benka YT7TA <pbenka@...>
Wysłane: sobota, 3 kwietnia 2021 11:19
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] Future rwquwst - Spot locally to Band Map
 
It is already in Logger. Bookmark callsign (Ctrl+B) or write call sign in call fiel starting with ! (!SP9KR)

73!

On Sat, Apr 3, 2021 at 9:07 AM Andy VA3PL <va3pl@...> wrote:
Hi there Bob
Can we have option to spot callsign locally to Band map for later recall? Please.
Can I have this as a Easter gift?

Andy SP9KR
Retirement is the best job I've ever had



--
Pavel, YT7TA
member of YU7AJM - http://www.yu7ajm.org


Re: Future rwquwst - Spot locally to Band Map

Pavel Benka YT7TA
 

It is already in Logger. Bookmark callsign (Ctrl+B) or write call sign in call fiel starting with ! (!SP9KR)

73!


On Sat, Apr 3, 2021 at 9:07 AM Andy VA3PL <va3pl@...> wrote:
Hi there Bob
Can we have option to spot callsign locally to Band map for later recall? Please.
Can I have this as a Easter gift?

Andy SP9KR
Retirement is the best job I've ever had



--
Pavel, YT7TA
member of YU7AJM - http://www.yu7ajm.org


Re: JTDX Cherry picker stops after Rx RR73

DamianM0BKV
 

after installing update 250 all is back to normal. Thank you.


ODP: Future request - Spot locally to Band Map

Andy VA3PL
 

I meant Future Request...sorry

Andy


Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Andy VA3PL <va3pl@...>
Wysłane: sobota, 3 kwietnia 2021 09:07
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: [hamlogger] Future rwquwst - Spot locally to Band Map
 
Hi there Bob
Can we have option to spot callsign locally to Band map for later recall? Please.
Can I have this as a Easter gift?

Andy SP9KR
Retirement is the best job I've ever had


Future rwquwst - Spot locally to Band Map

Andy VA3PL
 

Hi there Bob
Can we have option to spot callsign locally to Band map for later recall? Please.
Can I have this as a Easter gift?

Andy SP9KR
Retirement is the best job I've ever had


Re: Importing ADIF files from N1MM

Fabio IZ8MBW
 

I don't think so because how can Loggre32 know all the STATE values for all USA QSOs?


73s
Fabio, IZ8MBW



On Friday, April 2, 2021, 06:08:44 PM GMT+2, <infosys4u@...> wrote:


When importing ADIF files from N1MM, will logger import the state field for each contact, from the USA, without the state data included in the original log? 
Tnx Bob


Re: Bug in V4 ? Problem solved!

Bernd DL9YAJ
 

Hi All,

yes, problems solved now here also!

After a new installation of operating system and also Logger 32 V4.0248 my problem wasn`t solved!

Now, i installed also the new 4.0249 and nice to see....
All problems solved, yippie !!

I haven´t configured all in L32 at the moment, it take some time, but at the moment i am very happy.

Time to say,

thank you very much for in the hole fantastic Logger32 team. You are doing a really, really nice work. Support is matchless good !

Thank you again.......

best 73s Bernd, DL9YAJ


Am 31.03.2021 um 21:46 schrieb Bernd DL9YAJ:

Hello All,

i am frustrated!!!
I am working nearly the hole day to get L32 V4 running, but with no success!!!
I am not able to add qsos manually!
After some problems with ActiveX error codes, i tried all to register some .ocx files, but with no success!

After hours, i decided to install a new clean windows 10 on the pc. So i download the newest version from Microsoft, cleaned the SSD and installed win10 pro 64bit from a bootable usb-stick.
After installing the win10 some updates were found and i also install them!

After the operating system is installed, first i install firefox browser and than download Logger32 V 4.028 from website.
Installed it and start the new version.

But what a surprise, the problem is still there!!!

Typing Ctrl-M oder clicking on "Manually ADD QSOs", the program closed immediately! No error -message, only closing!

For now, i have no idea und no more fun to try again!

Will go to bed now and hope for some help to get it running tomorrow or next days!

best 73s Bernd, DL9YAJ


Am 31.03.2021 um 11:40 schrieb Bernd DL9YAJ:
My problem persists! Cannot add a qso manually. The program closed after clicking on the button!
Cleaned the pc, also the registry to avoid that old entries distrub.

Any idea to test or solve the problem?

best 73s Bernd, DL9YAJ

Am 29.03.2021 um 14:34 schrieb Dave Colliau:
Mine is fine
Dave n8dc
On 03/29/2021 8:32 AM Bernd DL9YAJ <dl9yaj@darc.de> wrote:

  Hi all,

when i click on "Manually ADD QSOs" the program will close instantly.

The short-Cut "Ctrl-M" does the same?

A known bug? Using V 4.0.248 under Win10 Pro 64 Bit

73s Bernd, DL9YAJ













Importing ADIF files from N1MM

infosys4u@...
 

When importing ADIF files from N1MM, will logger import the state field for each contact, from the USA, without the state data included in the original log? 
Tnx Bob


JTDX Cherry picker stops after Rx RR73

DamianM0BKV
 

since the last Logger32 update when I use the Cherry Picker with JTDX it auto sequences OK until I receive RR73 then it halts and the Cherry Picker finds another call or does nothing. It use to auto send 73 and the 'Click to confirm the following QSO' Popup window appeared. It works when I Receive RRR but not RR73.
I thought there might be a new setting but can't find one.


Re: crash

Fabio IZ8MBW
 

Hi David.
I use Logger32 since 2008 and I also never have had crashes with older versions (3.x).
With version 4.x I'm also victim of "random" crash but now with latest version 4.0.249 the situation is better, personally I have had only one crash during the Logger32 closure and not anymore.
Now it's working well.


But I agree with Gary, if you complains issues/crash but do not give info/details probably none can solve a potential bug.

Try to understand what happens or what Logger32 "is doing" when it crash.
FT8 operation? If yes, JTDX or WSJT-X?
UDP open?
Landowning Club Lug exception?

What Logger32 is doing when it crash?



73s
Fabio, IZ8MBW



On Friday, April 2, 2021, 08:30:56 AM GMT+2, David Bonnet <f8crs63@...> wrote:


Gary,

I use L32 for more than 10 year and since 2-3 weeks I see almost averydays a pop-up window which says "the programme shut down" and have to restart L32.
never had this trouble before.

I use W10.



Garanti sans virus. www.avast.com

Le jeu. 1 avr. 2021 à 23:56, Gary Hinson <Gary@...> a écrit :

David,

 

I understand there are some problems with the HamLib rig-control function, which probably explains our problems with mode settings when using WSJT-X or JTDX.  Changes are being coded and tested.

 

As to “crash everyday !!!!”, we’ll need just a bit more info than those two words and 4 exclamations to even start diagnosing that issue – like for instance which version of Logger32 crashes for you, and on what version of Windows?   What are you doing at the time it crashes? 

 

There have been a few reports of sporadic crashes, but Logger32 is stable for most users (including me) so we’d like to narrow down the differences between systems.  Something, somewhere, is creating a problem for some users, sometimes. 

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of David Bonnet
Sent: 02 April 2021 06:19
To: hamlogger@groups.io
Subject: [hamlogger] crash

 

hi all

 

crash everyday !!!! I'm with W10 and with the last version the FT8/FT4 is no more recognised utomatically !!!!!!!

I use to run WSJT and the TX goes to USB-D and L32 in FT4 and FT_ but doesn' work anymore, have to do it manually.

 

 

 

Garanti sans virus. www.avast.com


Re: crash

Jan
 

David

What version are you using?

73
Jan
PA4JJ

Op 2-4-2021 om 08:30 schreef David Bonnet:
Gary,

I use L32 for more than 10 year and since 2-3 weeks I see almost averydays a pop-up window which says "the programme shut down" and have to restart L32.
never had this trouble before.

I use W10.



Garanti sans virus. www.avast.com

Le jeu. 1 avr. 2021 à 23:56, Gary Hinson <Gary@...> a écrit :

David,

 

I understand there are some problems with the HamLib rig-control function, which probably explains our problems with mode settings when using WSJT-X or JTDX.  Changes are being coded and tested.

 

As to “crash everyday !!!!”, we’ll need just a bit more info than those two words and 4 exclamations to even start diagnosing that issue – like for instance which version of Logger32 crashes for you, and on what version of Windows?   What are you doing at the time it crashes? 

 

There have been a few reports of sporadic crashes, but Logger32 is stable for most users (including me) so we’d like to narrow down the differences between systems.  Something, somewhere, is creating a problem for some users, sometimes. 

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of David Bonnet
Sent: 02 April 2021 06:19
To: hamlogger@groups.io
Subject: [hamlogger] crash

 

hi all

 

crash everyday !!!! I'm with W10 and with the last version the FT8/FT4 is no more recognised utomatically !!!!!!!

I use to run WSJT and the TX goes to USB-D and L32 in FT4 and FT_ but doesn' work anymore, have to do it manually.

 

 

 

Garanti sans virus. www.avast.com


-- 
____________________________________________________
my dxspider clusters running on a raspberry pi zero:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: crash

David Bonnet
 

Gary,

I use L32 for more than 10 year and since 2-3 weeks I see almost averydays a pop-up window which says "the programme shut down" and have to restart L32.
never had this trouble before.

I use W10.



Garanti sans virus. www.avast.com


Le jeu. 1 avr. 2021 à 23:56, Gary Hinson <Gary@...> a écrit :

David,

 

I understand there are some problems with the HamLib rig-control function, which probably explains our problems with mode settings when using WSJT-X or JTDX.  Changes are being coded and tested.

 

As to “crash everyday !!!!”, we’ll need just a bit more info than those two words and 4 exclamations to even start diagnosing that issue – like for instance which version of Logger32 crashes for you, and on what version of Windows?   What are you doing at the time it crashes? 

 

There have been a few reports of sporadic crashes, but Logger32 is stable for most users (including me) so we’d like to narrow down the differences between systems.  Something, somewhere, is creating a problem for some users, sometimes. 

 

73

Gary  ZL2iFB

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of David Bonnet
Sent: 02 April 2021 06:19
To: hamlogger@groups.io
Subject: [hamlogger] crash

 

hi all

 

crash everyday !!!! I'm with W10 and with the last version the FT8/FT4 is no more recognised utomatically !!!!!!!

I use to run WSJT and the TX goes to USB-D and L32 in FT4 and FT_ but doesn' work anymore, have to do it manually.

 

 

 

Garanti sans virus. www.avast.com


Re: N8VB vCOM

Prasad
 

Sorry Thomas, I have never used HRD. 

73 de Prasad VU2PTT



On Thu, Apr 1, 2021 at 9:44 PM thott2001 via groups.io <thott2001=yahoo.de@groups.io> wrote:
Hello Prasad,

thank you for the fast reply!
I try the VSPE but it didn’t work with both 
programs. I tried different vCOM settings 
but I can not change frequency of the Transcv. 
by clicking on the call within Logger32 
DX Cluster. 
I will still try to configure it out. 

Nevertheless thank your for the help.  

73! Thomas, DG8FBV 


Am 01.04.2021 um 13:45 schrieb Prasad <vu2ptt@...>:


Thomas,

I use this:  http://www.eterlogic.com/Products.VSPE.html - it is quite reliable and is free for 32-bit operating systems. Something like this will be required if you need to split a port.

Another option I have used in the past is K5FR's VSPmgr: http://k5fr.com/DDUtilV3wiki/index.php?title=VSP_Manager

73 de Prasad VU2PTT



On Thu, Apr 1, 2021 at 4:28 PM thott2001 via groups.io <thott2001=yahoo.de@groups.io> wrote:

Hello,

Anybody has a link or a tip were I can find 
the virtual COM driver N8VB vCOM?
It’s for connecting the last free HamRadio
Deluxe with the Logger32 to use the CAT 
system of the HRD. 

I found some in the net but either they didn’t 
work or the source seems not trustable. 

Thank you very much for the help

73! Thomas, DG8FBV, stay safe!


v4.0.249 released

Gary Hinson
 

After extensive beta testing and bug fixing through March, Logger32 version 4.0.429 has been released as an autoupdate, resolving a bunch of issues.  The Logger32 v4 User Manual has been updated as well.

 

As a reminder, the v4 manual is online and (due to being 22 Mb!) is not included in Logger32 autoupdates.   

 

The Help menu’s User Manual line should take you to https://www.logger32.net/files/Logger32_v4_User_Manual.pdf    If it doesn’t, you can edit the line using Help → Setup Help menu options

 

You can read the manual through your browser as well, using the same URL.  You may need to refresh your browser/clear the cache to grab the current version (check the version number and date on the front cover).

 

Further issue/bug reports are always welcome, including corrections and improvement suggestions for the User Manual. 

 

73

Gary  ZL2iFB

(plus Bob K4CY and the Logger32 beta test crew)

1841 - 1860 of 85226