Date   

Re: Rig Control For WSJT-X #ft8

Gary Hinson <Gary@...>
 

RTUM is OK then?

 

Am I sacked yet?

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 17 May 2021 11:14
To: hamlogger@groups.io
Subject: Re: [hamlogger] Rig Control For WSJT-X #ft8

 

... oh, and I forgot ... 'Geek Squad' teaches their rule 101 - If you tell the customer/client to RTFM, their employment is terminated on the spot, and they get to walk home ... 

On 05/16/2021 7:07 PM Bob <k4cy@...> wrote:

 

 

Gary, here in the land of the Big PX, we sell electronics to the totally inept, with the support (with a fee) of the 'Geek Squad'. They'll come install it, set it up, make it sing, dance, and talk, and even fix user malfunctions, if you sign the contract.

 

Mmmm, think there's a buck to be made out there somewhere? SeventyThree(s)AndBackToNetOverOver ...

On 05/16/2021 6:58 PM Gary Hinson <gary@...> wrote:

 

 

Hi John.

 

Provided you started WSJT-X from Logger32’s UDP BandMap <Start> menu (not by clicking a WSJT-X icon), the arrangement works like this:

 

 

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of JOHN Albano
Sent: 17 May 2021 09:43
To: hamlogger@groups.io
Subject: Re: [hamlogger] Rig Control For WSJT-X #ft8

 

Hi Gary thanks for the reply.

WSJT-X needs to use the USB of the TS590 to work.

The Logger32  also wants the UBS of the TS590 to control the rig..when I offer the Comm port of the TS590 i says it's invalid..the cluster uses it and TCP and UDP are all working.

So for F8 contacts, I leave things as above...the F8 contacts get logged properly on Logger32...the rig is be controlled only by the WSJT-X and NOT by Logger32.

So, I am asking the SAME USB to control both the WSJT-X and Logger 32.

I don't fully understand the next to last sentence but was able to get it configured make F8 contacts from it.

 


Re: Rig Control For WSJT-X #ft8

Bob
 

... oh, and I forgot ... 'Geek Squad' teaches their rule 101 - If you tell the customer/client to RTFM, their employment is terminated on the spot, and they get to walk home ... 

On 05/16/2021 7:07 PM Bob <k4cy@...> wrote:
 
 
Gary, here in the land of the Big PX, we sell electronics to the totally inept, with the support (with a fee) of the 'Geek Squad'. They'll come install it, set it up, make it sing, dance, and talk, and even fix user malfunctions, if you sign the contract.
 
Mmmm, think there's a buck to be made out there somewhere? SeventyThree(s)AndBackToNetOverOver ...
On 05/16/2021 6:58 PM Gary Hinson <gary@...> wrote:
 
 

Hi John.

 

Provided you started WSJT-X from Logger32’s UDP BandMap <Start> menu (not by clicking a WSJT-X icon), the arrangement works like this:

 

 

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of JOHN Albano
Sent: 17 May 2021 09:43
To: hamlogger@groups.io
Subject: Re: [hamlogger] Rig Control For WSJT-X #ft8

 

Hi Gary thanks for the reply.

WSJT-X needs to use the USB of the TS590 to work.

The Logger32  also wants the UBS of the TS590 to control the rig..when I offer the Comm port of the TS590 i says it's invalid..the cluster uses it and TCP and UDP are all working.

So for F8 contacts, I leave things as above...the F8 contacts get logged properly on Logger32...the rig is be controlled only by the WSJT-X and NOT by Logger32.

So, I am asking the SAME USB to control both the WSJT-X and Logger 32.

I don't fully understand the next to last sentence but was able to get it configured make F8 contacts from it.

 


Re: Rig Control For WSJT-X #ft8

JOHN Albano
 

Hi Gary,  helpful chart...thanks


Re: Rig Control For WSJT-X #ft8

Bob
 

Gary, here in the land of the Big PX, we sell electronics to the totally inept, with the support (with a fee) of the 'Geek Squad'. They'll come install it, set it up, make it sing, dance, and talk, and even fix user malfunctions, if you sign the contract.
 
Mmmm, think there's a buck to be made out there somewhere? SeventyThree(s)AndBackToNetOverOver ...

On 05/16/2021 6:58 PM Gary Hinson <gary@...> wrote:
 
 

Hi John.

 

Provided you started WSJT-X from Logger32’s UDP BandMap <Start> menu (not by clicking a WSJT-X icon), the arrangement works like this:

 

 

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of JOHN Albano
Sent: 17 May 2021 09:43
To: hamlogger@groups.io
Subject: Re: [hamlogger] Rig Control For WSJT-X #ft8

 

Hi Gary thanks for the reply.

WSJT-X needs to use the USB of the TS590 to work.

The Logger32  also wants the UBS of the TS590 to control the rig..when I offer the Comm port of the TS590 i says it's invalid..the cluster uses it and TCP and UDP are all working.

So for F8 contacts, I leave things as above...the F8 contacts get logged properly on Logger32...the rig is be controlled only by the WSJT-X and NOT by Logger32.

So, I am asking the SAME USB to control both the WSJT-X and Logger 32.

I don't fully understand the next to last sentence but was able to get it configured make F8 contacts from it.

 


Re: Rig Control For WSJT-X #ft8

Gary Hinson <Gary@...>
 

Hi John.

 

Provided you started WSJT-X from Logger32’s UDP BandMap <Start> menu (not by clicking a WSJT-X icon), the arrangement works like this:

 

 

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of JOHN Albano
Sent: 17 May 2021 09:43
To: hamlogger@groups.io
Subject: Re: [hamlogger] Rig Control For WSJT-X #ft8

 

Hi Gary thanks for the reply.

WSJT-X needs to use the USB of the TS590 to work.

The Logger32  also wants the UBS of the TS590 to control the rig..when I offer the Comm port of the TS590 i says it's invalid..the cluster uses it and TCP and UDP are all working.

So for F8 contacts, I leave things as above...the F8 contacts get logged properly on Logger32...the rig is be controlled only by the WSJT-X and NOT by Logger32.

So, I am asking the SAME USB to control both the WSJT-X and Logger 32.

I don't fully understand the next to last sentence but was able to get it configured make F8 contacts from it.


Re: Rig Control For WSJT-X #ft8

Fabio IZ8MBW
 

You cannot use the same COM port (also if it's an USB serial port) from more then one software in the same time.

Gary gives to you an option to use the same COM port by both Logger32 and WSJT-X (also if in fact the same COM port is used by one software in the same time). 

In my case, with Icom 7300, I use two different serial ports that manage that (same) radio in the same time, so one COM is for Logger32 and the other one is for WSJT-X or JTDX.

If you are not able to use two serial ports on the same radio use the Gary suggestion. 

73.
Fabio, IZ8MBW

Il dom, 16 mag, 2021 alle 23:42, JOHN Albano
<albanojc@...> ha scritto:
Hi Gary thanks for the reply.

WSJT-X needs to use the USB of the TS590 to work.

The Logger32  also wants the UBS of the TS590 to control the rig..when I offer the Comm port of the TS590 i says it's invalid..the cluster uses it and TCP and UDP are all working.

So for F8 contacts, I leave things as above...the F8 contacts get logged properly on Logger32...the rig is be controlled only by the WSJT-X and NOT by Logger32.

So, I am asking the SAME USB to control both the WSJT-X and Logger 32.

I don't fully understand the next to last sentence but was able to get it configured make F8 contacts from it.


Re: Rig Control For WSJT-X #ft8

JOHN Albano
 

Hi Gary thanks for the reply.

WSJT-X needs to use the USB of the TS590 to work.

The Logger32  also wants the UBS of the TS590 to control the rig..when I offer the Comm port of the TS590 i says it's invalid..the cluster uses it and TCP and UDP are all working.

So for F8 contacts, I leave things as above...the F8 contacts get logged properly on Logger32...the rig is be controlled only by the WSJT-X and NOT by Logger32.

So, I am asking the SAME USB to control both the WSJT-X and Logger 32.

I don't fully understand the next to last sentence but was able to get it configured make F8 contacts from it.


Re: Rig Control For WSJT-X #ft8

Gary Hinson <Gary@...>
 

Hi John.

 

You say “It will not accept the USB port …”: what do you mean ‘will not accept’? 

 

If Logger32 has CAT control of your TS590, it is holding the USB com4 port open, so WSJT-X or other software can’t use the same port.  Is that what you’ve found? 

 

However, if you open WSJT-X from the UDP BandMap’s <Start> menu item, Logger32 closes the CAT port first, so that WSJT-X can then open and use it instead.  When you close WSJT-X using the <Stop> menu item, Logger32 waits until WSJT-X shuts then re-opens the CAT port for you.

 

More details in the CAT and UDP BandMap chapters of the User Manual.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of JOHN Albano
Sent: 17 May 2021 07:11
To: hamlogger@groups.io
Subject: [hamlogger] Rig Control For WSJT-X #ft8

 

I was able to to setup rig control for Logger32..works fine on the USB com3 port.

On the WSJT-X end it will not accept the USB port or the COM com4 port.

The rig is a kenwood TS-590SG....

Any suggestions on what other have done to get the WSJT--X rig interface working?

Thanks for any help or direction, 73 John N6TRC


Rig Control For WSJT-X #ft8

JOHN Albano
 

I was able to to setup rig control for Logger32..works fine on the USB com3 port.

On the WSJT-X end it will not accept the USB port or the COM com4 port.

The rig is a kenwood TS-590SG....

Any suggestions on what other have done to get the WSJT--X rig interface working?

Thanks for any help or direction, 73 John N6TRC


Re: MMVARI error ptt

Bob
 

Mauro, yes there is a bug. I setup like this
 
Radio 1 = Icom address &H74
Radio 2 = Icom 7300 address &h94
 
When using radio 1 the PTT ON command is FE FE 74 E0 1C 00 01 FD
When using radio 2 the PTT ON command is FE FE 00 E0 1C 00 01 FD
 
The address for radio 2 is missing. I have made a fix for the next auto-update. 73.
 

On 05/16/2021 8:42 AM IV3SCP Mauro <iv3scp@...> wrote:
 
 
Hello everybody,
i think it is a bug of the program.
I have two radios set up in logger32.
Radio 1 Icom ic-756pro
Radio 2 Icom IC-7300
When I use digital systems I use radio 2 with MMVARI and set both radios with the command ptt cat
If I use radio 1 everything works fine, if I use radio 2 the ptt does not work. Opening the radio debug window I see the ptt command but the command is wrong, it is always that of the radio one FE 5C E0 1C 00 01 FD while that of 7300 is FE FE 94 E0 .....

Sorry for the English but I use google translate

Mauro IV3SCP


MMVARI error ptt

IV3SCP Mauro
 

Hello everybody,
i think it is a bug of the program.
I have two radios set up in logger32.
Radio 1 Icom ic-756pro
Radio 2 Icom IC-7300
When I use digital systems I use radio 2 with MMVARI and set both radios with the command ptt cat
If I use radio 1 everything works fine, if I use radio 2 the ptt does not work. Opening the radio debug window I see the ptt command but the command is wrong, it is always that of the radio one FE 5C E0 1C 00 01 FD while that of 7300 is FE FE 94 E0 .....

Sorry for the English but I use google translate

Mauro IV3SCP


Re: Error 13 "dochangerotor"

Juanjo Gamero
 

Many thanks, uncheck "error trapping" in view menu helped me.
73
Juanjo EA2A


Re: Scrolling Log Window

Bob
 

Allow me to restate ... This is resolved in the next auto-update if the logbook page is indexed by date/time. It will continue to not work if the logbook page is indexed on a secondary key. SeventyThree(s).

On 05/15/2021 2:33 PM Gary Hinson <gary@...> wrote:
 
 

My log is normally sorted by date & time. 

 

I just re-sorted it by TX frequency and went through the same process with the same callsign.  On clicking the scroll bar, the log jumped to 2006, and again the previous QSO window cleared.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 16 May 2021 06:19
To: hamlogger@groups.io
Subject: Re: [hamlogger] Scrolling Log Window

 

For the next auto-update I have made a change to fix this. It only works if the logbook page is indexed by the Date/Time. SeventyThree(s).

On 05/15/2021 11:10 AM Gianfranco via groups.io <tog-franco@...> wrote:

 

 

The scroll function is very useful and allows you to move easily within each text window of the Logger32 ... and it works correctly.
But there is a case where it is impossible to navigate properly within the Log window.
Let me explain with an example:

- I enter a Call in the Input Window

- and the "Previous QSO" window shows the QSO (s) made with this station;
- clicking, selecting a QSO will go to the corresponding QSO in the Log Window

So far so good but if I now try to scroll through the Log using scrolling in any way,
the Log window jumps to a completely different position and that's not good for me

Am I doing something wrong?
73 de ik3ogn GFranco
This also happens on the Log of my friends ...

 


Re: Scrolling Log Window

Gary Hinson <Gary@...>
 

My log is normally sorted by date & time. 

 

I just re-sorted it by TX frequency and went through the same process with the same callsign.  On clicking the scroll bar, the log jumped to 2006, and again the previous QSO window cleared.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 16 May 2021 06:19
To: hamlogger@groups.io
Subject: Re: [hamlogger] Scrolling Log Window

 

For the next auto-update I have made a change to fix this. It only works if the logbook page is indexed by the Date/Time. SeventyThree(s).

On 05/15/2021 11:10 AM Gianfranco via groups.io <tog-franco@...> wrote:

 

 

The scroll function is very useful and allows you to move easily within each text window of the Logger32 ... and it works correctly.
But there is a case where it is impossible to navigate properly within the Log window.
Let me explain with an example:

- I enter a Call in the Input Window

- and the "Previous QSO" window shows the QSO (s) made with this station;
- clicking, selecting a QSO will go to the corresponding QSO in the Log Window

So far so good but if I now try to scroll through the Log using scrolling in any way,
the Log window jumps to a completely different position and that's not good for me

Am I doing something wrong?
73 de ik3ogn GFranco
This also happens on the Log of my friends ...


Re: Scrolling Log Window

Gary Hinson <Gary@...>
 

Same here.

 

Having located a recent QSO in my log from the Previous QSOs window, when I clicked the area above the scroll box in the log expecting to page-up, instead it jumped to 2015 or so.  I don’t know why.  Also, the previous QSOs window cleared.

 

You’re not doing it wrong, GFranko: it’s a bug.

 

73

Gary    ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of DL7VOG
Sent: 16 May 2021 06:01
To: hamlogger@groups.io
Subject: Re: [hamlogger] Scrolling Log Window

 

Ciao Gianfranco,
the same here. If I scroll the same way from one of todays calls the log window jumps to QSOs in 2012. Odd behaviour - I haven't found any solution yet. Boring situation.

73 - Gerd / DL7VOG

Am 15.05.2021 um 15:10 schrieb Gianfranco via groups.io:

The scroll function is very useful and allows you to move easily within each text window of the Logger32 ... and it works correctly.
But there is a case where it is impossible to navigate properly within the Log window.
Let me explain with an example:

- I enter a Call in the Input Window

- and the "Previous QSO" window shows the QSO (s) made with this station;
- clicking, selecting a QSO will go to the corresponding QSO in the Log Window

So far so good but if I now try to scroll through the Log using scrolling in any way,
the Log window jumps to a completely different position and that's not good for me

Am I doing something wrong?
73 de ik3ogn GFranco
This also happens on the Log of my friends ...

 


Re: Scrolling Log Window

Bob
 

For the next auto-update I have made a change to fix this. It only works if the logbook page is indexed by the Date/Time. SeventyThree(s).

On 05/15/2021 11:10 AM Gianfranco via groups.io <tog-franco@...> wrote:
 
 
The scroll function is very useful and allows you to move easily within each text window of the Logger32 ... and it works correctly.
But there is a case where it is impossible to navigate properly within the Log window.
Let me explain with an example:

- I enter a Call in the Input Window

- and the "Previous QSO" window shows the QSO (s) made with this station;
-
clicking, selecting a QSO will go to the corresponding QSO in the Log Window
So far so good but if I now try to scroll through the Log using scrolling in any way,
the Log window jumps to a completely different position
and that's not good for me

Am I doing something wrong?
73 de ik3ogn GFranco
This also happens on the Log of my friends ...


Re: Scrolling Log Window

DL7VOG
 

Ciao Gianfranco,
the same here. If I scroll the same way from one of todays calls the log window jumps to QSOs in 2012. Odd behaviour - I haven't found any solution yet. Boring situation.

73 - Gerd / DL7VOG

Am 15.05.2021 um 15:10 schrieb Gianfranco via groups.io:

The scroll function is very useful and allows you to move easily within each text window of the Logger32 ... and it works correctly.
But there is a case where it is impossible to navigate properly within the Log window.
Let me explain with an example:

- I enter a Call in the Input Window

- and the "Previous QSO" window shows the QSO (s) made with this station;
-
clicking, selecting a QSO will go to the corresponding QSO in the Log Window


So far so good but if I now try to scroll through the Log using scrolling in any way,
the Log window jumps to a completely different position
and that's not good for me

Am I doing something wrong?
73 de ik3ogn GFranco
This also happens on the Log of my friends ...


Scrolling Log Window

Gianfranco
 

The scroll function is very useful and allows you to move easily within each text window of the Logger32 ... and it works correctly.
But there is a case where it is impossible to navigate properly within the Log window.
Let me explain with an example:

- I enter a Call in the Input Window

- and the "Previous QSO" window shows the QSO (s) made with this station;
-
clicking, selecting a QSO will go to the corresponding QSO in the Log Window


So far so good but if I now try to scroll through the Log using scrolling in any way,
the Log window jumps to a completely different position
and that's not good for me

Am I doing something wrong?
73 de ik3ogn GFranco
This also happens on the Log of my friends ...


Re: New error in 4.0.259

Bob
 

Your Icom errors are because the data received from your radio is incomplete - Possibly because you have configured the polling too fast.
 
As yet I do not understand the rotor messages yet, but every time a change of radio frequency is detected, Logger32 checks to see if it needs to select a different rotator.
 
73.

On 05/15/2021 1:39 AM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
 
 
Hi Bob.
I have the same error messages (and also others) if "Enable error trapping" is enabled.
 
Today I:
Start PC
Start Logger32 4.0.259
Start JTDX (version 2.2.156 64-bit)
 
I manually selected a decoded callsign from the UDP BandMap to call.
 
so Logger32 sent command to JTDX to call that callsing and I received these various messages one after one:
 
Inline image

 
Inline image

 
Inline image

 
Inline image

 
 
 
 
 
 
other errors during the same condition:
 
Inline image

 
Inline image
Inline image

 
Inline image

(and I don't have any rotor configured).
 
 
 
 
If I disable  "Enable error trapping" Logger32 seems to work well.
 
Thank you.
 
 
 
73
Fabio, IZ8MBW
 
 
 
On Friday, May 14, 2021, 08:13:40 PM GMT+2, Bob <k4cy@...> wrote:
 
 
Is this a reproduceable error? I can't get it to fail here. 73.
On 05/14/2021 1:50 PM Steve G1XOW <steve@...> wrote:
 
 

Hi, just downloaded 4.0.259 patch and within a few mins wasy these errors for the first time.

 

 


Re: Updates

KE1F Lou
 

Yes, indeed. Thanks a lot.

73, Lou KE1F

On 5/15/2021 02:46, N3ST wrote:
You can un-select "Enable auto-updates"
Go to Setup > Updates > Logger32 version updates > Enable auto updates
Is that what you are looking for?

Thanks,
Bryan
N3ST
> -------- Original Message --------
> Subject: [hamlogger] Updates
> From: "KE1F Lou" <lmecseri@...>
> Date: Fri, May 14, 2021 10:17 pm
> To: Logger32 <hamlogger@groups.io>
>
>
> I am a long time user of this great and free logging program, Logger32
> v. 4.0.255
>
> Since moving to Florida, I recorded over 84,000 QSOs so I can say that I
> am a mature user.
>
> I don't mind manually upload my QSOs once a month to LOTW or Clublog.
> (keeps my old brain working)
>
> How can I freeze my perfect Logger32 v. x.x.x to protect it from
> unneeded improvements?
>
> Only way I know now is to click on "NO" when an update message shows up.
> (But I don't know what did I say no to.)
>
> Is there a better way to stop update messages other than each time click
> on "NO"? Or if that is not a possibility  to advise the user of the
> changes in the update.
>
> 73, Lou KE1F
>
> ps: I broke to many perfect items by trying to make it better. :)
>
>
>
>
>

5201 - 5220 of 89399