Date   

locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

Joe Subich, W4TV
 

On 2021-02-19 9:49 AM, OM Marlon via groups.io wrote:

Log4OM sees this as Albania here,I supposed it will be logged that way
once we have a QSO
DXKeeper (DXLab Suite) also sees ZA/IN3PPH as Albania if I enter it
directly. However, it logged as Italy when worked in WSJTX 3.4.0
and logged by JTAlert 2.16.17.

73,

... Joe, W4TV


On 2021-02-19 9:49 AM, OM Marlon via groups.io wrote:
Hi Joe,
Log4OM sees this as Albania here,I supposed it will be logged that way once we have a QSO
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
*From: *Joe Subich, W4TV <mailto:lists@subich.com>
*Sent: *Friday, 19 February 2021 10:03 pm
*To: *Support@HamApps.groups.io <mailto:Support@HamApps.groups.io>
*Subject: *Re: [HamApps] Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om
In my case ZA/IN3PPH logged as ITALY.  There were no previous
QSOs with either ZA/IN3PPH, IN3PPH or */IN3PPH.
73,
    ... Joe, W4TV
On 2021-02-19 8:55 AM, Michael Black via groups.io wrote:

> Check your log for a previous QSO where it's logged as U.S.

>

> Mike W9MDB

>

>

>

>

> On Friday, February 19, 2021, 07:42:48 AM CST, Joe Subich, W4TV

> <lists@subich.com> wrote:

>

>

> On 2021-02-19 6:52 AM, Dave wrote:

>  > When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx

>  > that I just worked. Log4om logs it as United States instead of US

>  > Virgin Islands.

> I think I can remove Log4OM and JTDX from the issue.  I saw the same

> incorrect entity when logging ZA/IN3PPH from WSJTX 2.4.0-rc1 to

> DXKeeper (DXLab Suite) via JT-Alert.

>

> 73,

>

>      ... Joe, W4TV

>

>

> On 2021-02-19 6:52 AM, Dave wrote:

>  > I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1
month ago

>  > and have Log4om configured to receive logging info from JTAlert. When

>  > Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I

>  > just worked. Log4om logs it as United States instead of US Virgin

>  > Islands. It does this on all compound calls worked. It only
started this

>  > after I configured JTDX & JTAlert. I had no issue with WSJT-X &
JTAlert,

>  > Log4om.

>  > So I'm not sure where the issue might be. I looked over all 3 apps and

>  > saw nothing that I could change.

>  >

>  > Thanks,

>  > Dave

>  > k4em


locked Re: WSJT-X Audio Output Reduces

Michael Black
 

If it's ALC it would more likely be that audio level is too high and the ALC starts reducing it slowly.

Mike W9MDB




On Friday, February 19, 2021, 10:56:52 AM CST, Roger M via groups.io <ac6bw@...> wrote:


Maybe your rig's ALC is set right on the hairy edge, where it starts to drop power. Try increasing the audio level just a little, to increase ALC a bit.
--
73,
Roger
AC6BW


locked Re: WSJT-X Audio Output Reduces

Roger- AC6BW
 

Maybe your rig's ALC is set right on the hairy edge, where it starts to drop power. Try increasing the audio level just a little, to increase ALC a bit.
--
73,
Roger
AC6BW


locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

Jim N6VH
 


On 2/19/2021 3:52 AM, Dave wrote:
I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago and have Log4om configured to receive logging info from JTAlert. When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I just worked. Log4om logs it as United States instead of US Virgin Islands. It does this on all compound calls worked. It only started this after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert, Log4om.
So I'm not sure where the issue might be. I looked over all 3 apps and saw nothing that I could change.

Thanks,
Dave
k4em
_._,_._,_


Dave,

I did a test log to Log4OM using WSJT-X 2.3.0  and JTAlert 2,16.17, and kp2/nk4dx logged correctly as US Virgin Islands. I then deleted that QSO from Log4OM and did the same test, except I used JTDX 2.2.0-rc153, with the same results. Both times the QSO loged correctly.

73,

Jim N6VH


locked Re: FT450D & SCU-17: unable to issue a frequency command to rig from other programs.

KD7YZ Bob
 

My Bad .. I "thought" I'd selected the FT-450 group ... very sorry


locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

Michael Black
 

JTAlert gets it correct too.  This would be a successful QRZ lookup.

Mike W9MDB


Inline image





On Friday, February 19, 2021, 08:49:37 AM CST, OM Marlon via groups.io <du3cwm@...> wrote:


Hi Joe,

 

Log4OM sees this as Albania here,I supposed it will be logged that way once we have a QSO

 

 

Sent from Mail for Windows 10

 

From: Joe Subich, W4TV
Sent: Friday, 19 February 2021 10:03 pm
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

 

 

In my case ZA/IN3PPH logged as ITALY.  There were no previous

QSOs with either ZA/IN3PPH, IN3PPH or */IN3PPH.

 

73,

 

    ... Joe, W4TV

 

 

On 2021-02-19 8:55 AM, Michael Black via groups.io wrote:

> Check your log for a previous QSO where it's logged as U.S.

>

> Mike W9MDB

>

>

>

>

> On Friday, February 19, 2021, 07:42:48 AM CST, Joe Subich, W4TV

> <lists@...> wrote:

>

>

> On 2021-02-19 6:52 AM, Dave wrote:

>  > When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx

>  > that I just worked. Log4om logs it as United States instead of US

>  > Virgin Islands.

> I think I can remove Log4OM and JTDX from the issue.  I saw the same

> incorrect entity when logging ZA/IN3PPH from WSJTX 2.4.0-rc1 to

> DXKeeper (DXLab Suite) via JT-Alert.

>

> 73,

>

>      ... Joe, W4TV

>

>

> On 2021-02-19 6:52 AM, Dave wrote:

>  > I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago

>  > and have Log4om configured to receive logging info from JTAlert. When

>  > Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I

>  > just worked. Log4om logs it as United States instead of US Virgin

>  > Islands. It does this on all compound calls worked. It only started this

>  > after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert,

>  > Log4om.

>  > So I'm not sure where the issue might be. I looked over all 3 apps and

>  > saw nothing that I could change.

>  >

>  > Thanks,

>  > Dave

>  > k4em

 

 

 

 

 

 

 


locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

OM Marlon, DW3CWM
 

Hi Joe,

 

Log4OM sees this as Albania here,I supposed it will be logged that way once we have a QSO

 

 

Sent from Mail for Windows 10

 

From: Joe Subich, W4TV
Sent: Friday, 19 February 2021 10:03 pm
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

 

 

In my case ZA/IN3PPH logged as ITALY.  There were no previous

QSOs with either ZA/IN3PPH, IN3PPH or */IN3PPH.

 

73,

 

    ... Joe, W4TV

 

 

On 2021-02-19 8:55 AM, Michael Black via groups.io wrote:

> Check your log for a previous QSO where it's logged as U.S.

>

> Mike W9MDB

>

>

>

>

> On Friday, February 19, 2021, 07:42:48 AM CST, Joe Subich, W4TV

> <lists@...> wrote:

>

>

> On 2021-02-19 6:52 AM, Dave wrote:

>  > When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx

>  > that I just worked. Log4om logs it as United States instead of US

>  > Virgin Islands.

> I think I can remove Log4OM and JTDX from the issue.  I saw the same

> incorrect entity when logging ZA/IN3PPH from WSJTX 2.4.0-rc1 to

> DXKeeper (DXLab Suite) via JT-Alert.

>

> 73,

>

>      ... Joe, W4TV

>

>

> On 2021-02-19 6:52 AM, Dave wrote:

>  > I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago

>  > and have Log4om configured to receive logging info from JTAlert. When

>  > Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I

>  > just worked. Log4om logs it as United States instead of US Virgin

>  > Islands. It does this on all compound calls worked. It only started this

>  > after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert,

>  > Log4om.

>  > So I'm not sure where the issue might be. I looked over all 3 apps and

>  > saw nothing that I could change.

>  >

>  > Thanks,

>  > Dave

>  > k4em

 

 

 

 

 

 

 


locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

Joe Subich, W4TV
 

In my case ZA/IN3PPH logged as ITALY. There were no previous
QSOs with either ZA/IN3PPH, IN3PPH or */IN3PPH.

73,

... Joe, W4TV

On 2021-02-19 8:55 AM, Michael Black via groups.io wrote:
Check your log for a previous QSO where it's logged as U.S.
Mike W9MDB
On Friday, February 19, 2021, 07:42:48 AM CST, Joe Subich, W4TV <lists@subich.com> wrote:
On 2021-02-19 6:52 AM, Dave wrote:
> When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx
> that I just worked. Log4om logs it as United States instead of US
> Virgin Islands.
I think I can remove Log4OM and JTDX from the issue.  I saw the same
incorrect entity when logging ZA/IN3PPH from WSJTX 2.4.0-rc1 to
DXKeeper (DXLab Suite) via JT-Alert.
73,
    ... Joe, W4TV
On 2021-02-19 6:52 AM, Dave wrote:
> I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago
> and have Log4om configured to receive logging info from JTAlert. When
> Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I
> just worked. Log4om logs it as United States instead of US Virgin
> Islands. It does this on all compound calls worked. It only started this
> after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert,
> Log4om.
> So I'm not sure where the issue might be. I looked over all 3 apps and
> saw nothing that I could change.
>
> Thanks,
> Dave
> k4em


locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

Michael Black
 

Check your log for a previous QSO where it's logged as U.S.

Mike W9MDB




On Friday, February 19, 2021, 07:42:48 AM CST, Joe Subich, W4TV <lists@...> wrote:


On 2021-02-19 6:52 AM, Dave wrote:
> When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx
> that I just worked. Log4om logs it as United States instead of US
> Virgin Islands.
I think I can remove Log4OM and JTDX from the issue.  I saw the same
incorrect entity when logging ZA/IN3PPH from WSJTX 2.4.0-rc1 to
DXKeeper (DXLab Suite) via JT-Alert.

73,

    ... Joe, W4TV


On 2021-02-19 6:52 AM, Dave wrote:
> I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago
> and have Log4om configured to receive logging info from JTAlert. When
> Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I
> just worked. Log4om logs it as United States instead of US Virgin
> Islands. It does this on all compound calls worked. It only started this
> after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert,
> Log4om.
> So I'm not sure where the issue might be. I looked over all 3 apps and
> saw nothing that I could change.
>
> Thanks,
> Dave
> k4em







locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

Joe Subich, W4TV
 

On 2021-02-19 6:52 AM, Dave wrote:
When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx
that I just worked. Log4om logs it as United States instead of US
Virgin Islands.
I think I can remove Log4OM and JTDX from the issue. I saw the same
incorrect entity when logging ZA/IN3PPH from WSJTX 2.4.0-rc1 to
DXKeeper (DXLab Suite) via JT-Alert.

73,

... Joe, W4TV


On 2021-02-19 6:52 AM, Dave wrote:
I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago and have Log4om configured to receive logging info from JTAlert. When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I just worked. Log4om logs it as United States instead of US Virgin Islands. It does this on all compound calls worked. It only started this after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert, Log4om.
So I'm not sure where the issue might be. I looked over all 3 apps and saw nothing that I could change.
Thanks,
Dave
k4em


locked Re: Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

OM Marlon, DW3CWM
 

Hi Dave,

 

I run LOG4OM2 V. 22.11.0.0, JTAlert 2.16.17,  JTDX 2.2.rc 152, all at the same time with no apparent problems,  and was interested to see so I copied the call to LOG4OMN2 and it recognized the call as US Virgin Is., I have not worker Virgin islands yet, but most likely it will be logged that way.

 

You may want to check settings and update resources menu, that may help .

 

Marlon DW3CWM

 

Sent from Mail for Windows 10

 

From: Dave
Sent: Friday, 19 February 2021 8:39 pm
To: Support@HamApps.groups.io
Subject: [HamApps] Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

 

I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago and have Log4om configured to receive logging info from JTAlert. When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I just worked. Log4om logs it as United States instead of US Virgin Islands. It does this on all compound calls worked. It only started this after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert, Log4om.
So I'm not sure where the issue might be. I looked over all 3 apps and saw nothing that I could change.

Thanks,
Dave
k4em

 


locked FT450D & SCU-17: unable to issue a frequency command to rig from other programs.

KD7YZ Bob
 

Last month I had WSJTx; FLRig , DxLab's Commander, all changing the FT450 frequency from the software.
I haven't used the rig in a week or two ... suddenly I can control all aspects of the rig except changing the frequency. Other programs READ the freq, just can't alter the freq.

Except: the Yaesu program PCC_450, seen in screenshot ... I can spin the interface's "Dial Knob" and the Rig, FT450D, mimics the PCC450 display everytime.

Today I went onto https://www.silabs.com site and got the latest win-10 drivers from this year ... re-installed with the SCU-17 unplugged from USB , and so forth.

Please advise.

Tnx es 73

KD7YZ Bob


locked Not logging compound call signs in Log4om. using JTDX, JTalert, Log4om

Dave
 

I am using JTDX, JTAlert & Log4OM. I switched to JTDX about 1 month ago and have Log4om configured to receive logging info from JTAlert. When Log4om receives QSO info from a compound callsign ex: kp2/nk4dx that I just worked. Log4om logs it as United States instead of US Virgin Islands. It does this on all compound calls worked. It only started this after I configured JTDX & JTAlert. I had no issue with WSJT-X & JTAlert, Log4om.
So I'm not sure where the issue might be. I looked over all 3 apps and saw nothing that I could change.

Thanks,
Dave
k4em


locked Re: WSJT-X Audio Output Reduces

Michael Black
 

Also...wrong email group...that's a wsjt-x question.

Mike W9MDB





On Thursday, February 18, 2021, 11:34:44 PM CST, Mark via groups.io <m.weiss@...> wrote:


My WSJT-X audio level starts out at the desired level, but it declines substantially during the 15 second cycle.  That, of course, reduces the RF power out of the transceiver.

 

Does anyone also have that experience?  If so, what is the fix?

 

Tnx & 73,

 

Mark, K6FG


locked Re: WSJT-X Audio Output Reduces

Michael Black
 

What rig?
What power level?

Could be thermal control?

Mike W9MDB




On Thursday, February 18, 2021, 11:34:44 PM CST, Mark via groups.io <m.weiss@...> wrote:


My WSJT-X audio level starts out at the desired level, but it declines substantially during the 15 second cycle.  That, of course, reduces the RF power out of the transceiver.

 

Does anyone also have that experience?  If so, what is the fix?

 

Tnx & 73,

 

Mark, K6FG


locked WSJT-X Audio Output Reduces

Mark
 

My WSJT-X audio level starts out at the desired level, but it declines substantially during the 15 second cycle.  That, of course, reduces the RF power out of the transceiver.

 

Does anyone also have that experience?  If so, what is the fix?

 

Tnx & 73,

 

Mark, K6FG


locked Re: New Computer Hookup Problem

W7JHR@...
 

Thanks Laurie that did the trick. I knew it was a matter of pressing the right button, but I just couldn’t find it. 

Thanks,
Jim W7JHR


locked Re: Slow path to logging

Radio K0HB
 

 

From: Laurie, VK3AMA
Sent: Thursday, February 18, 2021 06:40
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Slow path to logging

 



Your problem is that your JTAlert settings do not match the Log4OM settings.

  • You have the JTAlert inbound connection set to port 2235 in Log4OM.
  • You have the ADIF_Message port set to port 2335 in JTAlert.

The ports need to match. Set Log4OM to use port 2335 and turn off the port 1240 inbound connection.

How does that work now?

de Laurie VK3AMA

 

That was it Laurie!  A bloody typo!

I can’t count how many times I examined those port numbers and didn’t catch it.

I sincerely apologize for wasting hours of your time, chasing a TYPO!

Again, I apologize, but appreciate your persistence.

 

73, de Hans, K0HB

 

 

 


locked Re: JTAlert error alert

w4lde
 

Mike,

The folder I was referring to is:  C:/users/"name"/AppData/Local/HamApps/W4LDE/logs/JTAlert

Normally there's 3 files, however, after using the ADIF Master or some other program deposit, I had five additional files, two from ADIF master and three with no name with the typical ahdcxz-----, used I guess by temps.

I did review the error file left there by ADIF Master and found that every mode "FT4" was I.D. as a bad mode.  So now I'm thinking that the Master program I was using was old, very old.

Anyway the issue is behind me and all is working OK.

Good to see your call and offer of help once again, thank you..

Stay Safe
73 de Ron W4LDE


locked Re: Help setting up B4

Mark
 

Thank you Laurie.  That did the trick.

73,

Mark, K6FG

3341 - 3360 of 36467