Date   

Re: strange resut in v3.5 and in v4

Jim Hargrave
 

We can't reveal everything. J

Jim – w5ifp-

 

>> -----Original Message-----

>> From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf

>> Of Tom Wylie

>> Sent: Sunday, July 5, 2020 11:23 AM

>> To: hamlogger@groups.io

>> Subject: Re: [hamlogger] strange resut in v3.5 and in v4

>>

>> Which Christmas?  :o)

>>

>>

>>

>> Tom

>> GM4FDM

>>

>> On 05/07/2020 17:15, Jim Hargrave wrote:

>> > Mike,

>> >

>> > L32 ver 4.0 is in controlled Beta /Debug testing.

>> >

>> > Anticipate public release by Christmas.

>> >

>> > Jim – w5ifp-*//*

>> >

>> > *From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On

>> Behalf Of *Mike

>> > *Sent:* Sunday, July 5, 2020 10:37 AM

>> > *To:* hamlogger@groups.io

>> > *Subject:* Re: [hamlogger] strange resut in v3.5 and in v4

>> >

>> >  From where did you get L32 4.0?

>> > Mike

>> >

>> >

>>

>>


Re: strange resut in v3.5 and in v4

Jan
 

The white one Tom... :-D

73
Jan
PA4JJ
Op 5-7-2020 om 18:23 schreef Tom Wylie:
Which Christmas?  :o)



Tom
GM4FDM

On 05/07/2020 17:15, Jim Hargrave wrote:
Mike,

L32 ver 4.0 is in controlled Beta /Debug testing.

Anticipate public release by Christmas.

Jim – w5ifp-*//*

*From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On Behalf Of *Mike
*Sent:* Sunday, July 5, 2020 10:37 AM
*To:* hamlogger@groups.io
*Subject:* Re: [hamlogger] strange resut in v3.5 and in v4

 From where did you get L32 4.0?
Mike






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


Re: strange resut in v3.5 and in v4

Bob
 

A valid question Tom. That entirely depends on when new state-of-the-art documentation is available. SeventyThree(s).

On 07/05/2020 12:23 PM Tom Wylie <thomasgwylie@gmail.com> wrote:


Which Christmas? :o)



Tom
GM4FDM

On 05/07/2020 17:15, Jim Hargrave wrote:
Mike,

L32 ver 4.0 is in controlled Beta /Debug testing.

Anticipate public release by Christmas.

Jim – w5ifp-*//*

*From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On Behalf Of *Mike
*Sent:* Sunday, July 5, 2020 10:37 AM
*To:* hamlogger@groups.io
*Subject:* Re: [hamlogger] strange resut in v3.5 and in v4

From where did you get L32 4.0?
Mike


Re: Any Help appreciated

Michael Buckle
 

Bob, I have sorted the RTTY selection issue, I have no idea why Logger32 suddenly started selecting RTTY instead of CW, perhaps the Gremlins have attacked.

I rebuilt any Band Monitor which demonstrated the RTTY issue by deleting the original monitor and replacing it with a newly formatted replacement.

As you suggested, I have zoomed the monitor windows to show only the first 100Khz and reset the Graticule Scale to 10Khz as shown on the Photo Below. Once again Bob, thanks for your help, 73s Mike G4RMV

On 04/07/2020 16:26, Bob wrote:
If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).
On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:




Re: strange resut in v3.5 and in v4

Tom Wylie
 

Which Christmas? :o)



Tom
GM4FDM

On 05/07/2020 17:15, Jim Hargrave wrote:
Mike,
L32 ver 4.0 is in controlled Beta /Debug testing.
Anticipate public release by Christmas.
Jim – w5ifp-*//*
*From:*hamlogger@groups.io [mailto:hamlogger@groups.io] *On Behalf Of *Mike
*Sent:* Sunday, July 5, 2020 10:37 AM
*To:* hamlogger@groups.io
*Subject:* Re: [hamlogger] strange resut in v3.5 and in v4
From where did you get L32 4.0?
Mike


Re: strange resut in v3.5 and in v4

Jim Hargrave
 

Mike,

 

L32 ver 4.0 is in controlled Beta /Debug testing.

Anticipate public release by Christmas.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Mike
Sent: Sunday, July 5, 2020 10:37 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] strange resut in v3.5 and in v4

 

From where did you get L32 4.0?
Mike


Re: strange resut in v3.5 and in v4

Mike
 

From where did you get L32 4.0?
Mike


Re: new contacts not populating the logbook

Bob
 

First, make sure that the Logbook Page Window is sorted by DATE (Click on the QSO DATE column header - the text will turn red). If you are sorted by some other field, then new QSOs will not necessarily be added at the bottom of the Logbook Page. SeventyThree(s).

On 07/05/2020 10:36 AM John Caulfield <jcaulfield@...> wrote:


When I enter (try to) a new contact it will not populate the logbook.
I  started a new logbook and that worked and then I imported the old log files into the new logbook and the problem started again.  do I have some sort of corruption and how might I  fix it?
thanks
John KØFUZ


new contacts not populating the logbook

John Caulfield <jcaulfield@...>
 

When I enter (try to) a new contact it will not populate the logbook.
I  started a new logbook and that worked and then I imported the old log files into the new logbook and the problem started again.  do I have some sort of corruption and how might I  fix it?
thanks
John KØFUZ


Re: DXCC Award Grids

PETER DOUGHTY
 

Hello Bob


Many thanks for your reply.

I have done as you advised and have found a strange issue!  If I go into the setup area I see that I have my chosen colour for confirmed slots (red/solid as it happens) in place but despite re-choosing it no colour is seen on the grid. I looked further at this point and find that if I choose any other colour they all work OK across the whole spectrum of grids. OK, I don't have to use red!

Interestingly, if I leave the background setting as red then it is seen OK as red in log book page, IOTA, WAC, WAZ, CQWPX and VUU but does not come through for DXCC, DXCC Challenge or WAS. They stay white.

Not sure when I noticed this first but it was a few weeks ago. All days the same in lockdown... only the skip changes! Just a thought that it might be an issue from an earlier upgrade but funny it is only with red?!? Presently set up on ver 3.50.419.

The main thing is I have a colour in place and all is good. Thanks again for that.

73s

Peter  G3TKK

On 05/07/2020 11:19, Bob wrote:
If you are sure it's just the highlight color you have lost (and not the actual W, C, and G status), then click SETUP | HIGHLIGHT| CONFIRMED HIGHLIGHT. SeventyThree(s).

On 07/05/2020 2:05 AM PETER DOUGHTY via groups.io <g3tkk=btinternet.com@groups.io> wrote:

Hello

I have been using the various DXCC award grids to map my stats with the
contacts shown as W C G as appropriate for decades.

For each I have had the background of the slots being red, yellow and
green as appropriate. Out of the blue I have lost the red background for
'confirmed' contacts though this is still in places such as IOTA logging
and across all the other windows show no change. Even on the DXCC grids
the worked and granted slot backgrounds are still in place.

Can anyone tell me how I did this and how I can get this back again?

73s

Peter G3TKK



Re: DXCC Award Grids

Bob
 

If you are sure it's just the highlight color you have lost (and not the actual W, C, and G status), then click SETUP | HIGHLIGHT| CONFIRMED HIGHLIGHT. SeventyThree(s).

On 07/05/2020 2:05 AM PETER DOUGHTY via groups.io <g3tkk=btinternet.com@groups.io> wrote:


Hello

I have been using the various DXCC award grids to map my stats with the
contacts shown as W C G as appropriate for decades.

For each I have had the background of the slots being red, yellow and
green as appropriate. Out of the blue I have lost the red background for
'confirmed' contacts though this is still in places such as IOTA logging
and across all the other windows show no change. Even on the DXCC grids
the worked and granted slot backgrounds are still in place.

Can anyone tell me how I did this and how I can get this back again?

73s

Peter G3TKK



DXCC Award Grids

PETER DOUGHTY
 

Hello

I have been using the various DXCC award grids to map my stats with the contacts shown as W C G as appropriate for decades.

For each I have had the background of the slots being red, yellow and green as appropriate. Out of the blue I have lost the red background for 'confirmed' contacts though this is still in places such as IOTA logging and across all the other windows show no change. Even on the DXCC grids the worked and granted slot backgrounds are still in place.

Can anyone tell me how I did this and how I can get this back again?

73s

Peter G3TKK


Re: Any Help appreciated

Bob
 

... also, as you're a CW only operator, you can zoom all the BandMaps to show only the spectrum of interest, then filter out all the modes du jour so that only your preference is visible (sort of like sanitizing the bands). SeventyThree(s).

On 07/04/2020 2:24 PM Michael Buckle via groups.io <mikejohnb@...> wrote:


Thanks Bob, I really appreciate your efforts on this subject, I will look into the CW Machine. I shut down the PC and restarted again, Bingo, CW is selected but only for a short time, then it reverts back to RTTY. Most frustrating. I will now check your suggestions, Thanks again.

On 04/07/2020 16:26, Bob wrote:
If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).
On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: VSPE splitter ports not visible to logger32

Bob
 

Logger32 version 3.50.xx supports COM1 - COM16. It is in the Help File. SeventyThree(s).

On 07/04/2020 6:07 PM Ignacy Misztal <no9e@...> wrote:


I created a VSPE splitter for serial rotor ports to use them by multiple applications and remote. I tried port 16 and 32. Both work with rotor controls and n1mm but not logger32.
The message is:
Invalid port 32.
These ports do not show in device manager.
Ignacy NO9E


VSPE splitter ports not visible to logger32

Ignacy Misztal
 

I created a VSPE splitter for serial rotor ports to use them by multiple applications and remote. I tried port 16 and 32. Both work with rotor controls and n1mm but not logger32.
The message is:
Invalid port 32.
These ports do not show in device manager.
Ignacy NO9E


Re: Any Help appreciated

Michael Buckle
 

Thanks Bob, I really appreciate your efforts on this subject, I will look into the CW Machine. I shut down the PC and restarted again, Bingo, CW is selected but only for a short time, then it reverts back to RTTY. Most frustrating. I will now check your suggestions, Thanks again.

On 04/07/2020 16:26, Bob wrote:
If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).
On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: Any Help appreciated

Bob
 

If you operate CW only, then yes, remove all the other modes from the BandPlan (if nothing else it will make things go much faster without having to plough through all the garbage to get to CW at the bottom of the list. Also, if you use the Logger32 CW Machine, toy can click the "Mode from Sound Card/CW Machine" option. that way, when the CW Machine is open the radio mode defaults to CW. SeventyThree(s).

On 07/04/2020 11:16 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: Any Help appreciated

Michael Buckle
 

Bob

I have checked the Mode on the input window and have posted another screen shot below.

I only use CW, I don't any other settings relating to RTTY or any other mode.

The strange part here is, this is identical to the mode on the input screen when the main Monitor window is selected and, when clicked, does not set to RTTY and sets as CW. I will try and see if there is anything I can do on the Radio settings. What would happen if I deselect all other modes or at least the RTTY mode???


On 04/07/2020 15:49, Bob wrote:
Do you have the Sound Card Data Window open (running RTTY maybe)? What option(s) have you selected to determine what mode to put your radio on (Click on the word MODE at the top/center of the Logbok Entry Window)? Looking at the Radio Debug Window is the mode command being sent from Logger32 correct (is the radio doing as it is told, or does it have a RTTY fetish)? SeventyThree(s). 
On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: Any Help appreciated

Bob
 

... also, what is/was the comments associated with the HB9CHB DX Spot? If the comments indicated RTTY, that would put the radio on RTTY. SeventyThree(s).

On 07/04/2020 10:29 AM Michael Buckle via groups.io <mikejohnb@...> wrote:


All, I have a small problem on 20m setup for Logger32 which appears to have just started.

Usage

  • Logger32 V3.50.419 (Latest available update)
  • Radio ICOM 7610

Now, when I look at the Monitor 20M band window and see a station I wish to work, I will click on that station and my radio QSYs to the Stations QRG, If however, it is the band for 20m and I click on 20.012 for a DX station, everything moves to that station but it changes the Mode to RTTY even though the station is clearly in the CW Area of the band. Now if I do exactly the same in the General Band Plan window (Left most Window in my Photo 1 attached), the radio again moves to 20m 14.012 but correctly changes to CW mode. Similarly, if I click on the scale graticule on the monitor, window, the Mode changes correctly.

Photo 1

Photo 2

This problem is very frustrating and I cant seem to set the band and mode for the 20m monitor to get the monitor to change to the CW end without the radio changing to RTTY. Any assistance on this issue would be appreciated.

Regards Mike G4RMV


Re: what is bad in bad.adi?

Gerry VE6LB
 

First line of bad.adi


On July 4, 2020 7:36:01 a.m. MDT, "Ilya Zozin,4Z1UF" <4z1uf@...> wrote:

 After attempt to import LoTW report I've got many rejects. The note says that bad.adi created and it will be noted why these Q's are rejected.
 I don't see any note and cannot find anything wrong. 

What is wrong?

73,
Ilya, 4Z1UF



--
Sent from my Android device by VE6LB with K-9 Mail.

2321 - 2340 of 82931