Date   

locked Re: 2.16.12 No Decodes Displayed

neil_zampella
 

First off, I see that you have WSJT-X using a non-default UDP port, which is 2237.      The port 2333 is the deprecated N1MM connection that should not be used as the main UDP port number.   

Have you tried changing that back to the normal port number.  

If that doesn't work,  the default port for JT-Alert to Log4OM (both v1 & v2) is 2236.  I don't use it Log4OM, but I would make sure that JT-Alert and Log4OM both have the same port and control port (2241 is default) being used.

 

Neil, KN3ILZ


On Wed, Aug 19, 2020 at 03:42 AM, Graham Chaloner wrote:

Al,  Similar issue here with 2.16.12  I believe there is a conflict with the UDP configuration but not sure what because nothing has
changed apart from JTAlert (I don't use Grdi Tracker)

Running W10 Home 64 bit.  WSJT = 2.2.2
If I run only WSJT & JTAlert then no issue, JTAlert decodes fine.
If I run my normal configuration of Log4OM, WSJT & JTAlert the result is no decodes.  I also receive this warning

Unable to communicate with the WSJT-X process.

UDP Port : 2333

IP Address : 127.0.0.1

Values read from WSJT-X config file...

Will investigate further today but hope someone can trough a bit of light onto the problem!

73


--
Graham Chaloner
M0GWC


locked Re: 2.16.12 No Decodes Displayed

Gerard de Veer <gerard@...>
 

call PD0GIP

Ihave the same problem.
Running Win 10 64bit Pro and JTDX Latest version
HRD (Latest version)

Back to 2.16.10.


Best 73



Gerard de Veer PD0GIP
Borodinstraat 166
5011 HE Tilburg
Tel. 0134555888 - 0640798489


-------- Oorspronkelijk bericht --------
Van: "Graham Chaloner via groups.io" <m0gwc@...>
Datum: 19-08-20 09:34 (GMT+01:00)
Aan: Support@HamApps.groups.io
Onderwerp: Re: [HamApps] 2.16.12 No Decodes Displayed

Al,  Similar issue here with 2.16.12  I believe there is a conflict with the UDP configuration but not sure what because nothing has
changed apart from JTAlert (I don't use Grdi Tracker)

Running W10 Home 64 bit.  WSJT = 2.2.2
If I run only WSJT & JTAlert then no issue, JTAlert decodes fine.
If I run my normal configuration of Log4OM, WSJT & JTAlert the result is no decodes.  I also receive this warning

Unable to communicate with the WSJT-X process.

UDP Port : 2333

IP Address : 127.0.0.1

Values read from WSJT-X config file...

Will investigate further today but hope someone can trough a bit of light onto the problem!

73


--
Graham Chaloner
M0GWC


locked Re: 2.16.12 No Decodes Displayed

Graham Chaloner
 

Al,  Similar issue here with 2.16.12  I believe there is a conflict with the UDP configuration but not sure what because nothing has
changed apart from JTAlert (I don't use Grdi Tracker)

Running W10 Home 64 bit.  WSJT = 2.2.2
If I run only WSJT & JTAlert then no issue, JTAlert decodes fine.
If I run my normal configuration of Log4OM, WSJT & JTAlert the result is no decodes.  I also receive this warning

Unable to communicate with the WSJT-X process.

UDP Port : 2333

IP Address : 127.0.0.1

Values read from WSJT-X config file...

Will investigate further today but hope someone can trough a bit of light onto the problem!

73


--
Graham Chaloner
M0GWC


locked 2.16.12 No Decodes Displayed

ag5pc@...
 

I backed down to 2.16.10 and everything works, no changes. WSJT-X version 2.2.2 The 2.16.12 JTAlert title bar did not show mode, band info. Also it showed there were updates.
Let me know if you want screen shots, I’ll re-install 2.16.12.

Al
 


locked UDP Socket Conflict

Bud Governale
 

Each time I open N1MM when JTAlert is open I get the following message at the start of N1MM:

"Receiving UDP Socket 2237 for WSJT/JTDX Messages is already in use".

What do I do to resolve this apparent conflict.

Please help.

73,

Bud W3LL
W3LL@...


locked Re: UR5EQF

John Cranfield <zd7jc@...>
 

Hi Carl and all

 

Sadly, Vladimir went silent key in 2017 and no one has carried on the coding.

 

73 and stay safe everyone

 

John C.

 

John Cranfield (ZD7JC)

Waterfall View

The Briars

St Helena Island

Post Code: STHL 1ZZ

South Atlantic Ocean

Tel: +(290) 22400

Mobile: +(290) 66827

Email: zd7jc@...

Skype: john.cranfield69

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Carl - WC4H via groups.io
Sent: 18 August 2020 18:29
To: Support@HamApps.groups.io
Subject: Re: [HamApps] UR5EQF

 

Hi Jorge.

I have looked at UR5EQF and cannot find a version after May 19, 2015.  It does not include many several new modes, notably FT8 or FT4.  There appears to be no support for it.  It also can only use Omnig rig as the radio interface, which is a limitting factor for radio control.

Do you have a more current version?  If so, please share location to download.

73.
Carl - WC4H


locked Re: UR5EQF

Willi Passmann
 

Carl,

this seems to be the website of UR5EQF
https://ur5eqf.ru/download/ur5eqf_log

Download not tested by me.

vy 73,
Willi, DJ6JZ

Am 18.08.2020 um 20:29 schrieb Carl - WC4H via groups.io:

[Edited Message Follows]

Hi Jorge.

I have looked at UR5EQF and cannot find a version after May 19, 2015.  It does not include several new modes, notably FT8 or FT4.  There appears to be no support for it.  It also can only use Omnig rig as the radio interface, which is a limitting factor for radio control.

Do you have a more current version?  If so, please share location to download.

73.
Carl - WC4H



locked Re: UR5EQF

Carl - WC4H
 
Edited

Hi Jorge.

I have looked at UR5EQF and cannot find a version after May 19, 2015.  It does not include several new modes, notably FT8 or FT4.  There appears to be no support for it.  It also can only use Omnig rig as the radio interface, which is a limitting factor for radio control.

Do you have a more current version?  If so, please share location to download.

73.
Carl - WC4H


locked UR5EQF

Jorge Manuel
 

It wolud be fine to have the opportunity to have the solution for UR5EQF in the logging of JTAlert!

J

Kind regards,

 

JORGE-EA2DDE


locked UR5EQF as log

Jorge Manuel
 

I'm ussing since years UR5EQF as log. It would be nice to have JTAlert for "conncecting" direclly to it.  Until today I'm not able to upload automatically
the QSO or the QRZ I'm calling with JTDX to UR5EQF (since JTAlert has been install).  it would be fine if someone has experience with this topic. 


locked JT ALERT 2.16.12

rrex lehman
 

I was using an older version of JT Alert for many months and recently had an Windows error message and it stopped working. So uninstalled the old version JT Alert and reinstalled latest JT ALERT 2.16.12 which worked for 30 minutes but then stopped displaying stations decoded in WSJT-X.  No Windows error message just does not show any stations that are in WSJT-X..
Thanks for reading and any assistance appreciated.
Rex
WB8TDG


locked Re: Reinitialize the logs

g4wjs
 

On 17/08/2020 14:26, Wayne Morris wrote:
I don't want to change my logging process from WSJT since it is working perfectly as it is.
Wayne,

clearly it is not for the very reasons you have stated. If you use JTAlert then you should be logging QSOs via JTAlert, that's the only way that JTAlert can keep track of the current position.



--
73
Bill
G4WJS.


locked Reinitialize the logs

Wayne Morris
 

I have been using JT Alert with WSJT-X. The needed lists and worked before are not correct. Short of deleting everything in JT Alert and reinstalling, is there a way to force the program to read my HRD logs and rebuild the list it uses? I don't let JT Alert send logbook entries to HRD Log. I have WSJT do it. I have tried enabling HRD Logging in JT Alert, rebuilding, and then disabling HRD Log in JT Alert. It appears to process the log but it is still providing alerts for calls that I know I don't need. For example, new continent. This is the only method that seems available but I suspect there is an easier way.

I don't want to change my logging process from WSJT since it is working perfectly as it is.

Thanks for any assistance.


locked Re: IC 7000 and Signal Link #FT8 - CAT Control fails #FT8

B. Smith
 

Wsjt-x is more sensitive to RFI. Get some ferrite beads and or a feedline choke. 

On Aug 17, 2020 06:58, m_scot_alex <amsctalx@...> wrote:
Name? Callsign?

JTAlert has nothing to do with rig control - that's entirely in WSJT-X. You might want to post this in the WSJT-X group:

https://wsjtx.groups.io/g/main/topics 

73,

Mike - N8MSA


locked Re: IC 7000 and Signal Link #FT8 - CAT Control fails #FT8

m_scot_alex
 

Name? Callsign?

JTAlert has nothing to do with rig control - that's entirely in WSJT-X. You might want to post this in the WSJT-X group:

https://wsjtx.groups.io/g/main/topics 

73,

Mike - N8MSA


locked Re: Log Confirmation Popup Audio

ve7gtc
 

Thanks Laurie (and others).
For some reasdon as I mentioned I somehow skipped v.9 and didn't see the release notes. All good now.

Gus  K2GT


locked Re: Log Confirmation Popup Audio

Chuck Adams
 

In the latest version, it is NOW under JTAlert > Settings > Miscellaneous Alerts > Windows Notifications.  It was right there in the Release Notes like Laurie said if I just bothered to read them.  I am a damn idiot.

Sent from my T-Mobile 5G Device


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Sunday, August 16, 2020 8:00:18 PM
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] Log Confirmation Popup Audio
 
On 17/08/2020 8:48 am, ve7gtc wrote:
I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT

Try reading the release notes.

For your convenience ...
2.16.9 (18-Jul-2020)

  Changes:

    - Windows notification sounds: Used by some JTAlert popup messages, like logging
       success/failure, have been replaced with a dedicated sound file/volume
       selection. See the "Alerts -> Miscellaneous Alerts -> Windows Notifications"
       section of the Settings window.

de Laurie VK3AMA


locked Re: Log Confirmation Popup Audio

HamApps Support (VK3AMA)
 

On 17/08/2020 8:48 am, ve7gtc wrote:
I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT

Try reading the release notes.

For your convenience ...
2.16.9 (18-Jul-2020)

  Changes:

    - Windows notification sounds: Used by some JTAlert popup messages, like logging
       success/failure, have been replaced with a dedicated sound file/volume
       selection. See the "Alerts -> Miscellaneous Alerts -> Windows Notifications"
       section of the Settings window.

de Laurie VK3AMA


locked Re: Log Confirmation Popup Audio

Chuck Adams
 

On JTAlert > Settings > Manage Settings > Window > Pop-up Windows 

My latest version of JTAlert does NOT show ANY area to select "sounds for successful log and sounds for failure log."  The top portion of that window is blank.

I have not been able to find where to restore this lost functionality. 

I must be losing my mind.

Any suggestions?

Thanks and 73,

Chuck Adams
KV4VT 


Sent from my T-Mobile 5G Device



-------- Original message --------
From: Joseph Baker <joebaker324@...>
Date: 8/16/20 6:51 PM (GMT-05:00)
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Log Confirmation Popup Audio

Go to settings, window, pop up and select sounds for successful log and sound for failure log. 

On Sun, 16 Aug 2020 at 23:49, ve7gtc <ve7gtc@...> wrote:
I have lost the log confirmation popup audio. It last worked for me in version.8. I do not have .9, but it does not work in .10, .11, or the current .12. Am I missing something?
Gus  K2GT







--
Sent from iPhone 8 Plus


locked IC 7000 and Signal Link #FT8 - CAT Control fails #FT8

Angryconservative
 

Good evening....

I have ran WSJT-X and JT Alert from what seems the beginning.... Love the software.....  I run an IC 7000 with a west mountain plug and play due to the features, being it is compact and mobile as I have set it up as a Mobile EMCOMM system in a 1510 Pelican.  it is my primary digital unit for mobility..  I recently changed the West Mountain to a Signal Link for a couple of reasons...  I wanted to remove the dedication of the radio using the PC sound card and wanted to switch to a standard that all of my digital software assets.

The Problem is...as I configured each software package.... First FLDIGI, then Winlink...Cat control was very easy... and adjustments to power output to the platform was equally easy....

But with WSJT....all of it started out rather easy... RX/TX and PPT control etc...initially setting the Radio control to VOX as was required.  Once the Audio settings was set, FT8 was rolling... clean and easy.  Net step was to setup the CAT control... ICOM radio...  COM port the USB cable to the CAT control port on the back of the radio....  WSJT saw the com port, 8,2, none.  basically the same settings as the plug an play.... worked great for about two days...   I was on 40, the radio would try and click over the 20 meter without my input... CAT control stopped working, trying to change frequencies completely rendered my station unusable... Somehow the condition led to the dreaded error...*INI file not being found, HAMLIB error etc....I ended up having to reinstall WSJT-X and set the radio without CAT controls...it is working but without any CAT control...

But, FLDIGI and Winlink continue to work without any issue.  

I am running the latest version of WSJT-X 2.2.2 and JTALERT all drivers updated on Windows 10....

If anyone has any idea's as to why one day it works, then next it stops, it would be appreciated 

4361 - 4380 of 35529