Date   

Re: v4.0.266 auto-update is on-line ...

Jim K2QB
 

OK so I also had a hard time finding this but once I did being the curious sort of fellow that I am...I checked both the Glass & Borderless form along with the Set Form on Top and now my digital indicator window is gone. How do I get it back??

Jim K2QB


JT-Alert / Grid Tracker launch with Logger32 and WSJT-X? #ft8

Spiros Xanthopoulos
 

Hello,

I am using logger32 for my logging purposes, and i use WSJT-X for FT8. Now here comes the tricky part. Running either JT-Alert or Grid Tracker, stops the auto log from WSJT-X to Logger32. What ports are you guys using to still log qso's and use either Grid-Tracker or JT-Alert ?

73 SV2EVS


Re: 7610 Spot selects correct frequency change but mode incorrect

Jim Cox
 

What mode does the 7610 use for CW operation, CW or CWl/CWU?  Make sure you have the correct mode in your bandplan.  Jim K4JAF
 

From: David KN2M
Sent: Saturday, June 12, 2021 11:01 PM
To: hamlogger@groups.io
Subject: [hamlogger] 7610 Spot selects correct frequency change but mode incorrect
 
Now that the Flex is working, I note that the 7610 responds to a CW cluster spot by a frequency change but does not keep the correct mode.  It changes to SSB.  I don't see an obvious menu setting in Logger32 that would account for this issue.  Is this a program or radio setting??  Thanks.


Re: v4.0.266 auto-update is on-line ...

Bob
 

On 06/13/2021 3:50 AM Rob <g4ujs@...> wrote:
 
 
> 4.0.266 has a new menu to set the digital rotator direction window to be on-top

Can't find this, where is it?

 73 Rob G4UJS


Re: v4.0.266 auto-update is on-line ...

Jan <hamlogger@...>
 

I have the same question

73
Jan
PA4JJ

Op 13-6-2021 om 09:50 schreef Rob:
>4.0.266 has a new menu to set the digital rotator direction window to be on-top

Can't find this, where is it?

 73 Rob G4UJS

-- 
____________________________________________________
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: v4.0.266 auto-update is on-line ...

G4RRM Pete
 

Hi Bob

Seems to have fixed the issue I was seeing of the QSL info going missing.

 

Many thanks

 

73

Pete

G4RRM


Re: v4.0.266 auto-update is on-line ...

Rob
 

>4.0.266 has a new menu to set the digital rotator direction window to be on-top

Can't find this, where is it?

 73 Rob G4UJS


Re: Problem on LoTW sync

Bob
 

I had you , and several others, in mind when I added that. Let me know in a few days it that has resolved your problem. SeventyThree(s).

On 06/12/2021 11:55 PM Steve Harbin KT5G <kt5g@...> wrote:
 
 
NEW BEHAVIOR IN v266

I downloaded .266 and in this version I get a popup notification to turn off the cherry picker to run the sync.  This may have been the culprit.


Re: 7610 Spot selects correct frequency change but mode incorrect

Bob
 

Is this something new, or has this behavior started since you figured out why your Flex radio didn't work?
 
When clicking on the CW DX Spot, did Logger32 send a command  to change the radio mode to CW? If you use one of your many other radios and you click on a CW DX Spot, does it switch to CW?
 
My apologies, but apparently my ESP is very low today. SeventyThree(s).

On 06/13/2021 12:01 AM David KN2M <rodman@...> wrote:
 
 
Now that the Flex is working, I note that the 7610 responds to a CW cluster spot by a frequency change but does not keep the correct mode.  It changes to SSB.  I don't see an obvious menu setting in Logger32 that would account for this issue.  Is this a program or radio setting??  Thanks.


Re: 7610 Spot selects correct frequency change but mode incorrect

John Munton - G7SSE
 

David, one possible reason could be the entries in your Band / Mode Table.

Look at what you have entered for "Radio Mode" for your CW entries for each band;

 
--
73, John - G7SSE


7610 Spot selects correct frequency change but mode incorrect

David KN2M
 

Now that the Flex is working, I note that the 7610 responds to a CW cluster spot by a frequency change but does not keep the correct mode.  It changes to SSB.  I don't see an obvious menu setting in Logger32 that would account for this issue.  Is this a program or radio setting??  Thanks.


Re: Problem on LoTW sync

Steve Harbin KT5G
 

NEW BEHAVIOR IN v266

I downloaded .266 and in this version I get a popup notification to turn off the cherry picker to run the sync.  This may have been the culprit.


Re: Problem on LoTW sync

Steve Harbin KT5G
 

The file is pretty small - maybe three to ten QSO's.

After a few QSO's that have been auto uploaded to LOTW:
(1) I manually click the "Download LOTW QSL Information and sync into Logger32" button on L32LogSync v2.0.18
(2) the status bar on L32LogSync displays "Processing Complete! 9 Records downloaded from the LOTW Server"
(3) L32LogSync presents a popup box stating: "The LOTW Download Report has been downloaded to: C:\L32LogSync\LOTW Reports\6122021 95550 PM_LotwDownloadQSOReport.adi  By clicking the OK button this will start the synchronize routines in Logger32 to import this file"
(4) I click the OK button on L32LogSync
(5) A file dialog box is presented requesting me to enter the file name of the report.  I select the file and press enter.
(6) Logger 32 presents a popup box with a greyed-out header: "LoTW Sync : c:\l32logsync\lotw reports\6122021 95550 pm_l..." . The rest of the popup box is blank.
(7) Clicking anywhere on the Logger32 application elicits no response whatsoever.
(8) After roughly a minute or so, Windows 10 pops up a box stating: "Logger32 has stopped working  A problem caused the program to stop working correctly.  Windows will close the program and notify you if a solution is available".  I click on the Debug button.
(9) Visual Studio Just-in-Time Debugger pops up: An unhandled win32 exception occurred in [14896] Logger32.exe".  It requests Admin permission to debug. I click on "Yes, debug Logger32.exe"
(10) This is the debugger message for the unhandled exception: "Unhandled exception at 0x765D14AC (oleaut32.dll) in Logger32.exe: 0xC0000005: Access violation writing location 0x000A0C4C."

Thanks for looking into this.  Please let me know if you need any additional info.

Steve KT5G


Re: A word of caution ...

Larry Fravel
 

They may have been warned but  - - - - will they listen?  Again thank you for all your hard work,

Larry K8YYY

--
I got expelled from school on Pajama Day. Not my fault - I sleep naked.


A word of caution ...

Bob
 

Today's auto-update of v4.0.266 has a new menu option to recalculate statistics and at the same time recalculate distance based on gridsquare of the QSO.
 
For those who have a logbook that contains QSOs for a single callsign, or multiple callsigns but from a single QTH, no problem.
 
For those who have a logbook that has QSOs from multiple locations, you probably shouldn't use this option. Distance is calculated based on the current Latitude/Longitude entered into Logger32. So, all QSOs with a gridsquare that were made from a different QTH to the current Logger32 Latitude/Longitude will have incorrect distances.
 
I will add code so that will only recalculate distance if the QSO OPERATOR field matches the current Logger32 operator. Also, if the logbook has QSOs with more than one operator, the user will received a warning message.
 
You have been warned! SeventyThree(s)
 


v4.0.266 auto-update is on-line ...

Bob
 

v4.0.266 has a new menu to set the digital rotator direction window to be on-top. There is an additional recalculate stats menu that will also recalculate distance (if the QSO has a gridsquare entered) at the same time. And, there are some bug fixes. SeventyThree(s).


Re: Flex6600M COM port

David KN2M
 

Thank you. 

I have read and re-read all notes from Bob, Ted and Jim.  I found a way and needed to add a virtual serial port for Logger32 in CAT after the software change (COM19) and the frequency now appears in the logging window.  That was just not obvious at first and not automatic.

Success!


Re: Flex6600M COM port

Jim Cox
 

As another suggestion, have you placed a trouble ticket into Flex support.  They can walk you through your problem and will reply to you very quickly during the week.  Do this, instead of struggling yourself if not at least somewhat computer savvy.  Flex radios do require some computer knowledge.
 

From: David KN2M
Sent: Saturday, June 12, 2021 6:16 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Flex6600M COM port
 
Surely, there must be someone out there who knows more about this than I do (which is virtually nothing).  What is the limit on COM port assignment in Logger32, especially the new 4.x version??  Does this matter??


Re: Flex6600M COM port

Jim Cox
 

There is outlined on the Flex Radio Community site a method to remove unused CAT ports created by the SmartSDR software.  This will free these ports for use again if not currently assigned.
This may be your problem if you cant create any more ports below 16. 
 
You can go into the CAT pane that creates your CAT ports, carefully note and write down which ports you have created.  Choose Remove at the bottom, this will remove any current ports that are assigned by SmartSDR CAT.  Then reboot computer.  Bring up SmartSDR again and recreate your CAT ports using freed CAT numbers.  As many have said before, you can use Device Manager to see what ports are created at any time..  SmartSDR CAT ports are shown there as well as other CAT ports create by other software and physical ports as well.  Jim K4JAF
 
If you need further help, I can assist you via phone sometime, just let me know..  
 

From: David KN2M
Sent: Saturday, June 12, 2021 6:16 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Flex6600M COM port
 
Surely, there must be someone out there who knows more about this than I do (which is virtually nothing).  What is the limit on COM port assignment in Logger32, especially the new 4.x version??  Does this matter??


Re: Flex6600M COM port

Ted Bryant W4NZ
 

David,

Are the Flex radio and SmartSDR both on version 3.2.39?

 

What com ports are defined in SmartSDR CAT? You should also see these ports in Device Manager.  SmartSDR CAT is where the virtual com ports are created by SmartSDR for third party apps, like logger32, N1MM, etc. to communicate with the Flex radio.  Consult your SmartCAT User Guide if you need more info on creating com ports.

 

Here’s my Flex 6600M configuration in Logger32 (v.4.0.265):

 

 

Ted W4NZ

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Saturday, June 12, 2021 7:45 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Flex6600M COM port

 

One of the two stated objectives of Logger32 v4.0 was to replace the legacy Microsoft serial port OCX (MSComm32.OCX) with something that, without modification, could see an an address of > 16, and was better suited to handle the current generation of serial port devices that can talk and listen at the same time (they support OverlappedIO). MSComm32 has been replaced, and in the current release looks for serial port devices up to (and including) 255.

 

Previously, I offered the though that if the Windows device manager couldn't see radios serial port then Logger32 probably wouldn't be able to see it either. Apparently that thought fell on deaf ears. So, let me ask you a direction ... Can the Windows device manager see the radio serial port? SeventyThree(s).

On 06/11/2021 11:21 PM David KN2M <rodman@...> wrote:

 

 

I found this note in my computer.  It has to do with Logger32 and COM ports.

C:\Windows\SysWOW64 now contains modified MSComm32.Ocx file and original is named 3d1000MSComm32.Ocx
MSComm32.Ocx was also found at C:\$WINDOWS.~BT\NewOS\Windows\Sys\WOW64 and same substitution was made
Done in order to allow Logger32 more COM port headroom.
The modification was 3D 10 00 to 3D FF 00.  The modified MSComm32.Ocx file is stored as 3df

AND this note:

SmartSDR CAT necessary for FLEX-6600M to appear in Logger32 COM16

I still can't use Logger32 with the FLEX even though I reloaded the SDR program and find no other obvious problem or cause for the failure to connect.

and YES, I DO have other radios with COM ports that still work with Logger32 and those did NOT disappear.  AND I would like MORE radios available because my station has three rigs.  Thank you.

So, the question MAY be when Flex updated the new software, the drivers were replaced.  Have I "hit" the upper limit of COM ports again and is it impossible to go back to a previously assigned port, ie 16??

Thank you.

4841 - 4860 of 89399