Date   

'<' and '>' not displaying correctly in DXC window

Sean - G4UCJ
 

I have noticed this strange phenomenon for some time, certainly over many versions (I can't remember when, or even if, the text has displayed correctly in the DX Cluster window).

Here's what happens: If I want to send a spot to the DX cluster that includes grid locators the '<' and '>' part of the spot get exchanged for other characters (i.e. IO92ma<ES>KP02xx, for example, end up like IO92ma&lt;ES&gt;KO02xx).
It doesn't seem to matter what I change, or whether the text comes from me entering a spot manually in the DX cluster window or if it comes from an external source (such as Live MUF which is connected to a different DX cluster node).
I have included a screengrab of the offending text. It does this on all spots that have the 'greater than'/'less than' symbols, whether entered by me or from another station on the cluster. I wondered if it might be a font issue, but I've tried changing the font wherever it has been possible (unless I have missed one that affects the cluster window) and I only use pretty standard fonts like Arial, Comic Sans or Calibri.
Any ideas on how to solve this as it makes spots tricky to read. BTW, the spots appear as they should when viewing the cluster from different software. I have also tried using different nodes just in case - but to no avail.
I'm thinking it is likely to be user error rather than a software issue.

Thanks in advance & 73,
Sean G4UCJ - IO92ma    


Microsoft.NET Framework

Johan ZS1A
 

Hi to all.
After the new Windows 10 update I get this when booting up Logger32 and when doing a QRZ lookup from Logger32
Any ideas ?


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.InvalidCastException: Conversion from string "26/05/2020 16:39:49" to type 'Date' is not valid.
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToDate(String Value)
   at L32Lookups.Common.AutoCheckforUpdate()
   at L32Lookups.wndQRZLookup.UpdateTimer_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
L32Lookups
    Assembly Version: 1.0.0.11
    Win32 Version: 1.0.0.11
    CodeBase: file:///C:/L32Lookups/L32Lookups.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
Microsoft.mshtml
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.0.3300.0
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



Re: L32 - WJST-X - JTAlert - Rig Control

Bob
 

Not exactly sure what eQSL is (see NOTE below the picture), but if you're interested in mainstream QSLing, see this. SeventyThree(s).



NOTE: Many years ago someone sent me a picture of the eQSL user/subscriber demographics. The pie chart was convienently rotated to such an angle as to make the overwhelming Logger32 majority of users look as small as possible. C'est la vie.

On May 31, 2020 at 7:51 PM "Larry Van Horn - Radio (N5FPW)" <n5fpw@...> wrote:

I agree re: UDP additional display items. Damian. I use JTAlert to show me who is using eqsl so I can work them for possible county hunting. That said, thank you to Bob and Aki for your comments. I will certainly give JTDX a whirl and will use the UDP BandMap. I saw that in the help.pdf and will give it a spin. Always willing to try a new configuration.

Thank you all for your thoughtful comments.

73 de Larry, N5FPW
Brasstown, NC

 


Re: L32 - WJST-X - JTAlert - Rig Control

Larry Van Horn - Radio (N5FPW)
 

I agree re: UDP additional display items. Damian. I use JTAlert to show me who is using eqsl so I can work them for possible county hunting. That said, thank you to Bob and Aki for your comments. I will certainly give JTDX a whirl and will use the UDP BandMap. I saw that in the help.pdf and will give it a spin. Always willing to try a new configuration.

Thank you all for your thoughtful comments.

73 de Larry, N5FPW
Brasstown, NC


Re: L32 - WJST-X - JTAlert - Rig Control

Damian M0BKV
 

I tried JTAlert and got it to work with WJST.x AND Logger32 BUT you have to stop Logged32 having any rig control and also manually log the QSO in L32. NOT recommended AND anyway Logger32 does everything needed for most of us. It would be good if the UDP band plan could also show States needed or other Primary Award items as well as Gridsquares. Not greatly important though as I think Logger32  does virtually all else JDAlert does.


Re: L32 - WJST-X - JTAlert - Rig Control

ja1nlx
 

Larry

Basically one com port can not be shared at same time.
If you start wsjtx from UDP BandMap "Start" menu then Logger32 close radio port first then
run wsjtx.
If you close wsjtx from "Stop" menu in UDP BandMap then Logger32 open radio port again.

UDP BandMap has an option "Allow wsjt/jtdx to set Logger32 frequency/mode" However you
use JTAleart and I do not know if this works or not.

My suggestion is to use JTDX without JTAleart instead of wsjtx. Logger32 provide everything
without JTAleart and feature I explain above.

73

On 2020/06/01 6:43, Larry Van Horn - Radio (N5FPW) wrote:
I absolutely love the L32/WSJT-X/JTAlert combo. I have everything set up to log out of JTAlert to L32. My Icom IC-7200 feeds rig control etc to WSJT-X via my one com port 6.
The one thing I would like to see is L32 getting freq/band changes automatically from WSJT-X instead of me manually changing it. 

My question does anyone know of a way or a setup that I can use with the combo above that will accept freq/band changes to L32 from either the rig or WSJT-X..I have a couple of ideas, but before I start digging in, I wondered if any of you may have some thoughts on this? No need to reinvent the wheel if there is a proven way to handle that function.

Thanks and 73 de Larry, N5FPW
Brasstown, NC
--
73 de aki
JA1NLX


Re: L32 - WJST-X - JTAlert - Rig Control

Bob
 

I have absolutely no idea what JTAlert is, or how/why you have it connected, but from a purely Logger32 perspective ... if WSJT and Logger32 are connected by UDP, then on the UDP BandMap click CONFIG and check the ALLOW WSJT/JTDX TO SET LOGGER32 FREQUENCY/MODE. And, FWIW, my piddling around shows JTDX is way better than WSJT and much more user friendly. SeventyThree(s).

On May 31, 2020 at 5:43 PM "Larry Van Horn - Radio (N5FPW)" <n5fpw@...> wrote:

I absolutely love the L32/WSJT-X/JTAlert combo. I have everything set up to log out of JTAlert to L32. My Icom IC-7200 feeds rig control etc to WSJT-X via my one com port 6.
The one thing I would like to see is L32 getting freq/band changes automatically from WSJT-X instead of me manually changing it. 

My question does anyone know of a way or a setup that I can use with the combo above that will accept freq/band changes to L32 from either the rig or WSJT-X..I have a couple of ideas, but before I start digging in, I wondered if any of you may have some thoughts on this? No need to reinvent the wheel if there is a proven way to handle that function.

Thanks and 73 de Larry, N5FPW
Brasstown, NC

 


L32 - WJST-X - JTAlert - Rig Control

Larry Van Horn - Radio (N5FPW)
 

I absolutely love the L32/WSJT-X/JTAlert combo. I have everything set up to log out of JTAlert to L32. My Icom IC-7200 feeds rig control etc to WSJT-X via my one com port 6.
The one thing I would like to see is L32 getting freq/band changes automatically from WSJT-X instead of me manually changing it. 

My question does anyone know of a way or a setup that I can use with the combo above that will accept freq/band changes to L32 from either the rig or WSJT-X..I have a couple of ideas, but before I start digging in, I wondered if any of you may have some thoughts on this? No need to reinvent the wheel if there is a proven way to handle that function.

Thanks and 73 de Larry, N5FPW
Brasstown, NC


Re: VUCC data missing

Larry Van Horn - Radio (N5FPW)
 

Thank you Jim. I missed that  Will await the fix.

Larry Van Horn, N5FPW
Brasstown NC


Re: VUCC data missing

Jim Altman
 

Bob acknowledged it was broken.  You’ll just have to wait for the next version.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of k2sha@...
Sent: Sunday, May 31, 2020 11:18 AM
To: hamlogger@groups.io
Subject: [hamlogger] VUCC data missing

 

HI Larry, I reported this same issue on May 25. The only reply was from another ham with the same problem. Rolled back to version 414 but no other fix was offered. 73, John K2SHA


VUCC data missing

k2sha@...
 

HI Larry, I reported this same issue on May 25. The only reply was from another ham with the same problem. Rolled back to version 414 but no other fix was offered. 73, John K2SHA


Re: VUCC award is empty now

Larry Van Horn - Radio (N5FPW)
 

Ditto here. it is broken. Rolled back to 415 and normal.


Re: IOTA colours gone!

Larry Van Horn - Radio (N5FPW)
 

Yes. When I first open the award window for IOTA, no colors.
Click on Mixed mode again and the colors are then displayed.

Did the V3.50.416 update this morning and now have other issues as well. 

VUCC award window is totally messed up, not displaying what it should statistics wise.

No problem previous version. Recalc statistics and issues remain.

Larry


Re: 2 issues: Stop autolog FT8 Qsos and Comm port

HI3B Radhames
 

BINGO Damian.
Solved the WSJT-X issue.
I glad about your help.and very valuable suggestion.
Hope turn OFF and OFF a few times when the comm port issue
comeback again.
73,
Radhames, HI3B

--
Change to Full Features Digest (Rich formatting)
Tnx.

HI3B


Comm port issue?

HI3B Radhames
 

Why frequently my comm 3 port does not appear in SET UP RADIO 1,  and when it appears I try to open Radio 1 and L32 display a window saying the port is in use, without  having  any other  app open  using that port.  I have Icom IC7300. I will appreciate confirmtion how all boxes has been marked in SET UP RADIO 1 window.
Any graphic information or  short explanation, step by step in plain English, for help me fix this repetitive issue, will be welcome.
 
Thanks in advance.
 
Radhames, HI3B-- 
Change to Full Features Digest (Rich formatting)
Tnx.

HI3B--
Change to Full Features Digest (Rich formatting)
Tnx.

HI3B


Logger32 stop to save FT8 esos

HI3B Radhames
 

What may be the reason why L32 stops auto log Qsos made using WSTJ-X?

Think issue does not in WSJT-X,

Can someone explain to me in simple English,  step  by step, how set settings?

I have Icom IC7300.

Any help  will be welcome.
 
Thanks in advance.
 
Radhames, HI3B--
 


Re: Run Time error 53 File not found vbis5032.dll

Bob
 

To CYA, make sure you put the \Logger32 folder in the exclusions list. SeventyThree(s).

On May 29, 2020 at 8:53 AM Bruce B <dxman340@...> wrote:

Thanks Bob. I read down below on virus threats. All better.  You made my weekend Bob. 73 and again Thanks

 


Re: Run Time error 53 File not found vbis5032.dll

Bruce B
 

Thanks Bob. I read down below on virus threats. All better.  You made my weekend Bob. 73 and again Thanks


Re: Run Time error 53 File not found vbis5032.dll

Bob
 

Sounds/looks to me like your security software decided Logger32 was malware, and quarantined it (and its shortcut icon). Ain't this fun. SeventyThree(s).

On May 29, 2020 at 8:29 AM Bruce B <dxman340@...> wrote:

Been running logger for along time. 18-20 if that sounds right. Great program.Only had a few minor issues in that time that I corrected.

Sorry if this sounds basic. But when running good you dont tinker with it. Now I have to open the hood and look again whats wrong. Its been about 8 years since I had to open the hood. LOL

My problem now is.

I booted up yesterday and all went well. After about 5 minutes the program closed. Ok click on Icon and nothing there. Second click and Icon is gone.
So after looking at the files. I do not see the little Icon in the folder with the antenna. But I finally get it to open 4 screens and the the dreaded error shows up.

Run Time error 53  File not found vbis5032.dll.  Looked at the files and its there. Spent about 3 hours searching and reading. Can someone point me in the direction to correct or do I need to reload program. Thanks Bruce

 


Run Time error 53 File not found vbis5032.dll

Bruce B
 

Been running logger for along time. 18-20 if that sounds right. Great program.Only had a few minor issues in that time that I corrected.

Sorry if this sounds basic. But when running good you dont tinker with it. Now I have to open the hood and look again whats wrong. Its been about 8 years since I had to open the hood. LOL

My problem now is.

I booted up yesterday and all went well. After about 5 minutes the program closed. Ok click on Icon and nothing there. Second click and Icon is gone.
So after looking at the files. I do not see the little Icon in the folder with the antenna. But I finally get it to open 4 screens and the the dreaded error shows up.

Run Time error 53  File not found vbis5032.dll.  Looked at the files and its there. Spent about 3 hours searching and reading. Can someone point me in the direction to correct or do I need to reload program. Thanks Bruce