Date   

Re: L32 LogSync

Jeff Wilson <jjw5257@...>
 

Thanks Rick.  I had done all as you suggested before. Saw the (L32).  I did a check for updates and did the repair install.  Then I checked LOTW setup in L32Synch and found all of my past callsigns but not my Current VE3CV!  How could this have been removed?  Not to worry, all good now.
73
Jeff


Re: Logger32 go down when telnet to the cluster is ON

Alex Del Chicca
 

Hi to all,

Bob I solved the problem .... after having done several tests I found that the WINDOWS 10 PRO operating system had problems

and I installed again on the same machine windows 10 PRO clean and after reinstalling the ver. 3.5 and later, ..... ver. 4.0.238 works perfectly.

 

For all settings .... radio rotor etc. to set it up again I don't think I will have any problems.

 

Thanks again for the work you are doing.

73 Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Alex Del Chicca via groups.io
Inviato: sabato 23 gennaio 2021 17:24
A: hamlogger@groups.io
Oggetto: [hamlogger] Logger32 go down when telnet to the cluster is ON

 

Hi to ALL,

I upgraded from the latest version 3.5 to version 4.0 without any errors.

After doing database maintenance and updating statistics, I updated to ver. 4.0.235 without problems.

 

The open windows are: Operator :, Dx Spots, Worked / Confirmed Logbook page, Previous QSOs and Telnet for IK5PWJ-6 cluster connection,

I also opened the CW Machine window.

Unfortunately after some time, sometimes 30 min. others after an hour the Logger32 program closes, leaving only the window outside

the Logger32 Window of the CW Machine open.

 

In practice the window of Logger32 disappears.

 

I then made several tests, reinstalling the logger32 vers. 4 from vers. 3.5 where I had previously deleted all the log

and then reinstalled the ik5pwj log from the previously saved adif file.

 

Unfortunately, the problem reoccurred by going the Logger32 program down and always remaining the CW Machine -Software window.

 

At this point I did a test and I disabled the connection via telnet to the cluster no longer receiving the spots both

in the Telnet window and in the DX Spot window.

 

Well .... the Logger32 program ran for hours without closing.

I am sure that the block depends on the right spots that the telnet receives and sends to the DX Spots window,

because if I reactivate the telnet connection and the spots start to arrive again, the program goes down again.

 

What's up ? and how can this problem be eliminated?

 

When I use the same configurations on the latest version of the program vers. 3.5 .... everything works,

including telnet and spot-free spots or whatever.

 

Thanks for any Help

73 Alex ik5pwj.


V4.0.238 - run time error

Filipe Lopes
 

Hello,
After updating to V4 I keep having this error bellow, it is not specific to one action but it happens a lot when starting the log or when logging a callsign.

In this example I was logging this qso using the CW macro TU$log$ and the error came up


Anyone else having this issue?

I did not have this before with V3

thanks
FIlipe CT1ILT


Re: Logger 32 V4 and WSJT-X

Philip (G4OBK) Catterall
 

Thanks to Bob K4CY for a personal email with a fix for my issue of the callsign not transferring from the UDP Band Map window to the Log entry call box. 

Bob suggested I open Cherry Picker Options from the Band Map Config and check Cherry pick decoded callsign on next CQ. Now the callsign and the locator transfer from the band map window to the log entry box in L32 every time. . 

73 Phil G4OBK


Re: Logger 32 V4 and WSJT-X

Bob
 

Chris, I still have no idea what the problem is, but we're making progress. Y ou're confusing two very different/separate features/functions -  The JTDX control panel and manual calling.
 
The JTDX control panel is simply to allow the user to change JTDX band and mode and turn off TX Enable remotely (from Logger32). You'll find (I hope) that the JTDX control panel allows the user to click on a FT4/8 DX Spot and JTDX dutifully does what Logger32 tells it to do. You'll even notice that if the DX Spot includes the stations audio frequency JTDX uses that frequency as the RX frequency.
 
Now to Manual calling, here's how it works (in your case, how it is supposed to work). Click on a callsign in the UDP BandMap. Logger32now starts an automatic sequence (no operator intervention) that starts by waiting for the stations next CQ, or 73, or RRR73. When received, Logger32 tells JTDX to reply. If no reply after two calls Logger32 tells JTDX to quit calling and wait for the next opportunity to call again. This sequence is tried 5 times. If no luck after 5 tries, or after 10 minutes of trying, or after 90 seconds on not decoding the station The manual calling sequence picks up it's marbles and goes home to mummy. If/when the station answers a call the manual calling sequence quits and allows JTDX (or WSJT) to complete the contact with no user input.
 
So, what you thought was the manual calling sequence is not.
 
So the actual problem is that when you click on a callsign in the UDP BandMap you are not actually starting the sequence. So back to drawing board. The thing for you to look for is the text appearing in the manual calling event viewer or the colored box being place around the callsign you clicked on in the UDP BandMap. Once that happens, we're in business. I don't want to bother the reflector users further on this problem, so I'll take if offline. And work directly with you.
 
SeventyThree(s).

On 01/28/2021 2:39 PM Philip (G4OBK) Catterall <cq@...> wrote:
 
 

Hi Bob

 

These tests and checks have got me liking JTDX! Extra L32 features over WSJT-X, I could be a late adopter…

 

Opened the manual calling event viewer and when I click a callsign in the JTDX Band Map the event viewer window remains blank – the locator transfers to the log entry window in L32 but the callsign does not. If I initiate a QSO using AUTOTX and enable TX by clicking a callsign in the Receive or Main Control Windows JTDX will call the station and the callsign and locator goes into the log entry window. Nothing goes into the manual calling event window - it remains blank.  I know that the manual event calling window is operating correctly as if I change mode or band in the (excellent new to V4) JTDX Control panel window, the time and change is shown.

 

Whether we can fix this minor issue or not I like using JTDX!

 

73 Phil G4OBK


succesfull update to version 4,0,238

Herman Römer - PA9HR
 

Hi folks,

i just updated to version 4 and everything seems to working smoothly. I am a logger32 user for over 16 years and I am impressed by all the hard work that the logger32-team is putting into it. Thank you very much!

73 Herman Römer - PA9HR


Re: Logger 32 V4 and WSJT-X

Philip (G4OBK) Catterall
 

Hi Bob

 

These tests and checks have got me liking JTDX! Extra L32 features over WSJT-X, I could be a late adopter…

 

Opened the manual calling event viewer and when I click a callsign in the JTDX Band Map the event viewer window remains blank – the locator transfers to the log entry window in L32 but the callsign does not. If I initiate a QSO using AUTOTX and enable TX by clicking a callsign in the Receive or Main Control Windows JTDX will call the station and the callsign and locator goes into the log entry window. Nothing goes into the manual calling event window - it remains blank.  I know that the manual event calling window is operating correctly as if I change mode or band in the (excellent new to V4) JTDX Control panel window, the time and change is shown.

 

Whether we can fix this minor issue or not I like using JTDX!

 

73 Phil G4OBK


Re: Cluster issue

Bob
 

Chris, if I understand you correctly, when you look at the Cluster/Localhost window there are many spots. But only 25% of those appear to be making it to the DX Spot window.
 
If I am correct, you have configured an option to block them. Off the top of my head I can think of three places where this is happening.
 
a) The blocking filters setup window. Right click on the DX SPOT window. Click SETUP | DX SPOT BLOCKING/PASS FILTERS. Countless options there.
 
b) If your VE7CC connection in on the Localhost socket, there is an option to filter RBN duplicate spots (and the vast majority of them are duplicates). Right click on the Localhost pane of the Cluster window. Click SETUP LOCALHOST & RBN CONNECTIONS. There are two filter options there. If you change either of them, click APPLY FILTERS.
 
c) On the DX Spot window there is an option where DX Spots that are already visible on the DX Spot window are not simple appended to the bottom of window, but simply overwrite the existing entry. Right click the DX Spot window. Click SETUP | APPEARANCE. Check or UNcheck the option as you like.
 
Editorial note: You might want to seriously consider to NOT have every single DX Spot received from VE7CC populate the DX Spot. It is a  waste of bandwidth, oxygen, and CPU cycles. 
 
SeventyThree(s).

On 01/28/2021 12:48 PM chrisgd6twf <gd6twf@...> wrote:
 
 
I am using the latest version of VE7CC and Logger32 v4.0.235. The issue I have is that only a percentage of the spots are feeding into Logger 32 when I compare the Logger 32 cluster window to the spots on Logger 32. There is no time delay between VE7CC and Logger 32. 

I am receiving spots across all bands but only about 1 in 4 of total spots. 

Thanks
Chris GD6TWF


Re: Cluster issue

John Owens
 

You need to set the DX Spot Blocking/Pass Filters to determine which spots migrate to you DX SPOTS Window. The filters will  determine a lot of things about which spots you want to come to the DX SPOTS Window. Right click in the DX SPOTS Window open area, Go down to SETUP, and then over the Blocking/Pass filters setting. You will have to decide what you want to see come  through. 
 
I recommend doing it locally in L32, rather than doing the settings via the VE7CC Website. Much easier to change if you want to once you have it set up. 
 
John Owens -  N7TK

On 01/28/2021 9:48 AM chrisgd6twf <gd6twf@...> wrote:
 
 
I am using the latest version of VE7CC and Logger32 v4.0.235. The issue I have is that only a percentage of the spots are feeding into Logger 32 when I compare the Logger 32 cluster window to the spots on Logger 32. There is no time delay between VE7CC and Logger 32. 

I am receiving spots across all bands but only about 1 in 4 of total spots. 

Thanks
Chris GD6TWF


Re: Enhancement

Rick EA4M
 

Ok, I have something similar bob but I thought on the enhancement for those who don't spend time trying to know how to confirm a qso, there are a lot of hams don't doing that...... Bit anyway thanks a lot


El jue., 28 ene. 2021 14:19, Bob <k4cy@...> escribió:
Rick, you are correct satellite QSOs and the requirements for electronic confirmation are a pain in the ass. I understand you request (no problems with your English).
 
It is not necessary to make any changes to Logger32 to meet your needs. You can already configure the logbook entry window to show BAND_RX, SAT_NAME, and SAT_MODE ADIF fields.
 
If you operate both HF and satellite, then can consider having two Logger32 configurations (with a common logbook). One setup for an HF logbook entry window, and one for satellite.
 
73.
On 01/28/2021 3:30 AM Rick EA4M via groups.io <ea4m=ure.es@groups.io> wrote:
 
 
Hello
 
I know that satellites world is a little complicated for adif and specially Lotw. I have noticed that some users do not fill correclty the fields necesary to confirm a qso via Lotw or Eqsl , resulting a lack of match for many qso's. That is why I ask for an enhancement for satellite qso's.
 
I don't know if it is possible or very complicated because I don't know anything about programming.... but here I go
 
It could consist on a menu or a new sub menu in qso window to choose logging qso in satellite mode prefilling some fields as  PROP_MODE , the field BAND_RX amd BAND_TX with a selectable menu from available bands, the field SAT_NAME with a selectable menu from a file containing the names of satellites ( this could contain also rx band for BAND_RX field and tx band for BAND_TX field such as any other information) and finally the field SAT_MODE that contains if the cross band was V/U or U/V or other with a selectable menu( the file containing sat names could contain this information too )
 
I don't kno wif I explained my self correctly 'cause english is not my mother tongue and I'm not good english speaker.....
 

Please let mekow if I could help, I will be able to build the needed file to do that if necessary.....
 
Thanks
 
Rick EA4M
 

Libre de virus. www.avast.com


Cluster issue

chrisgd6twf
 

I am using the latest version of VE7CC and Logger32 v4.0.235. The issue I have is that only a percentage of the spots are feeding into Logger 32 when I compare the Logger 32 cluster window to the spots on Logger 32. There is no time delay between VE7CC and Logger 32. 

I am receiving spots across all bands but only about 1 in 4 of total spots. 

Thanks
Chris GD6TWF


Re: Logger 32 V4 and WSJT-X

Bob
 

John, you said: I have to start L32, then check "allow WSJT-X to.....", then start WSJT-X, use it for a while, then stop WSJT-X, then uncheck "allow WSJT-X to.....".
 
I don't think you're quite there yet. The blue text I've highlighted should be unnecessary. If the radio comm port is open when you start WSJT/JTDX (from the UDP menus). You will notice the port closes before WSJT/JTDX starts. Then, when you stop WSJT/JTDX (from the UDP menus) the radio comm port automagically re-opens after WSJT/JTDX shuts down. SeventyThree(s).

On 01/28/2021 10:17 AM John Scott <scotts@...> wrote:
 
 
Ignore previous message.

I have it fingered out now.

I have to start L32, then check "allow WSJT-X to.....", then start WSJT-X, use it for a while, then stop WSJT-X, then uncheck "allow WSJT-X to.....".

All is now well.  

Sorry to ask stupid questions.  RTFM carefully!

73

John, VE1JS


Re: Logger 32 V4 and WSJT-X

John Scott, VE1JS
 

Ignore previous message.

I have it fingered out now.

I have to start L32, then check "allow WSJT-X to.....", then start WSJT-X, use it for a while, then stop WSJT-X, then uncheck "allow WSJT-X to.....".

All is now well.  

Sorry to ask stupid questions.  RTFM carefully!

73

John, VE1JS


Re: File /Secondary Admin data files/DVGE.csv uploaded #file-notice

Bob
 

Thanks Fonsi. 73.

On 01/28/2021 9:37 AM hamlogger@groups.io Notification <noreply@groups.io> wrote:
 
 

 

The following files have been uploaded to the Files area of the hamlogger@groups.io group.

By: ec7akv@...

Description:
Secondary Admin Subdivision Award for EA 28/01/2021 For Diploma Vertiges Geodesicos de España

 

 


File /Secondary Admin data files/DVGE.csv uploaded #file-notice

hamlogger@groups.io Notification <noreply@...>
 

The following files have been uploaded to the Files area of the hamlogger@groups.io group.

By: ec7akv@...

Description:
Secondary Admin Subdivision Award for EA 28/01/2021 For Diploma Vertiges Geodesicos de España


Re: Enhancement

Bob
 

Rick, you are correct satellite QSOs and the requirements for electronic confirmation are a pain in the ass. I understand you request (no problems with your English).
 
It is not necessary to make any changes to Logger32 to meet your needs. You can already configure the logbook entry window to show BAND_RX, SAT_NAME, and SAT_MODE ADIF fields.
 
If you operate both HF and satellite, then can consider having two Logger32 configurations (with a common logbook). One setup for an HF logbook entry window, and one for satellite.
 
73.

On 01/28/2021 3:30 AM Rick EA4M via groups.io <ea4m@...> wrote:
 
 
Hello
 
I know that satellites world is a little complicated for adif and specially Lotw. I have noticed that some users do not fill correclty the fields necesary to confirm a qso via Lotw or Eqsl , resulting a lack of match for many qso's. That is why I ask for an enhancement for satellite qso's.
 
I don't know if it is possible or very complicated because I don't know anything about programming.... but here I go
 
It could consist on a menu or a new sub menu in qso window to choose logging qso in satellite mode prefilling some fields as  PROP_MODE , the field BAND_RX amd BAND_TX with a selectable menu from available bands, the field SAT_NAME with a selectable menu from a file containing the names of satellites ( this could contain also rx band for BAND_RX field and tx band for BAND_TX field such as any other information) and finally the field SAT_MODE that contains if the cross band was V/U or U/V or other with a selectable menu( the file containing sat names could contain this information too )
 
I don't kno wif I explained my self correctly 'cause english is not my mother tongue and I'm not good english speaker.....
 

Please let mekow if I could help, I will be able to build the needed file to do that if necessary.....
 
Thanks
 
Rick EA4M
 

Libre de virus. www.avast.com


Enhancement

Rick EA4M
 

Hello

I know that satellites world is a little complicated for adif and specially Lotw. I have noticed that some users do not fill correclty the fields necesary to confirm a qso via Lotw or Eqsl , resulting a lack of match for many qso's. That is why I ask for an enhancement for satellite qso's.

I don't know if it is possible or very complicated because I don't know anything about programming.... but here I go

It could consist on a menu or a new sub menu in qso window to choose logging qso in satellite mode prefilling some fields as  PROP_MODE , the field BAND_RX amd BAND_TX with a selectable menu from available bands, the field SAT_NAME with a selectable menu from a file containing the names of satellites ( this could contain also rx band for BAND_RX field and tx band for BAND_TX field such as any other information) and finally the field SAT_MODE that contains if the cross band was V/U or U/V or other with a selectable menu( the file containing sat names could contain this information too )

I don't kno wif I explained my self correctly 'cause english is not my mother tongue and I'm not good english speaker.....


Please let mekow if I could help, I will be able to build the needed file to do that if necessary.....

Thanks

Rick EA4M


Libre de virus. www.avast.com


Re: Enhancement question

Bob
 

Just post your ideas here (everyone else does). SeventyThree(s).

On 01/27/2021 4:01 PM Ricardo Navarrete via groups.io <ea4m@...> wrote:
 
 
Hello All
 
I don't know if it is the right way to ask for an improvement or enhancement.
Do I post here or is there any oter way ???

Thnaks in adv.
 
73 de Rick EA4M

Libre de virus. www.avast.com


Enhancement question

Rick EA4M
 

Hello All

I don't know if it is the right way to ask for an improvement or enhancement.
Do I post here or is there any oter way ???

Thnaks in adv.

73 de Rick EA4M

Libre de virus. www.avast.com


Re: Small enhancement

Malcolm Bosher
 

Bob

Thank you for implementing that small enhancement for me it will save a lot of coping and pasting.

73  Malcolm  GU0UVH

2941 - 2960 of 85242