Date   

locked Re: How are JTAlert messages sent?

g4wjs
 

On 06/07/2020 19:05, Larry Floyd wrote:
This is not a question of how to use the messaging feature, it's a question about how the actual information in each text message is sent?  There's a misconception that the information is sent via FT8, but I suspect it's sent via the Internet from JTAlert app to JTAlert app.  Correct?

Thanks.

- Larry - W5EIT
Larry,

they are sent via the Internet using the HamSpots server for routing. I have noticed a couple of JA stations recently sending test messsages that they have sent RR73, if you have not received a confirmation of your sent report over the air then the QSO is *not* valid. If someone attempts to complete a QSO like this using JTAlert text messages then you should ignore the message and continue sending an R+report message and only log the QSO once you have received RRR or RR73 over the air, otherwise it is a busted QSO.



--
73
Bill
G4WJS.


locked Re: transmitter keying

g4wjs
 

On 06/07/2020 20:01, richard clare wrote:
When JT Alerts logs qso to DX Labs, my Yaesu mk V transmits at low power for about 3 seconds, The first time it has ever done this. Does anybody have a clue for me?
Hi Richard,

some sort of VOX keying being used combined with the sound card connected to you rig being the system default sound card.



--
73
Bill
G4WJS.


locked How are JTAlert messages sent?

Larry W5EIT
 

This is not a question of how to use the messaging feature, it's a question about how the actual information in each text message is sent?  There's a misconception that the information is sent via FT8, but I suspect it's sent via the Internet from JTAlert app to JTAlert app.  Correct?

Thanks.

- Larry - W5EIT


locked transmitter keying

richard clare
 

When JT Alerts logs qso to DX Labs, my Yaesu mk V transmits at low power for about 3 seconds, The first time it has ever done this. Does anybody have a clue for me?


locked Re: Not logging some QSOs to DXKeeper. #DXLAB

HamApps Support (VK3AMA)
 

On 5/07/2020 9:25 am, g4wjs wrote:

Hi Laurie,

a socket close call is not the same as doing a socket shutdown call first. Is this code AutoIT or .Net?


--
73
Bill
G4WJS.

AutoIT. The TCP logging component in JTAlert is not part of the new .NET based JTAlertV2.Manager code. What AutoIT does under the hood is unknown, it only offers a TCPCloseSocket command, but that is likely their friendly description of the function executing the low-level TCP instructions.

I just stopped the auto logging to DXKeeper, 20 hours continuous, logging every 30 seconds. Not a single QSO was lost, 2410 records sent and logged.

Before I shutdown the Test, I went into DXKeeper and deliberately changed the Base Port of the Network Service (from 52000 to 62000) which as expected stopped DXK from receiving the logging instructions. JTAlert correctly identified an inability to connect (recorded a standard 10060 error) after 10 retries. Resetting the DXK port back to 52000 and logging resumed.

Perhaps a Network Service restart is all that is needed, rather than a DXKeeper restart if the failed logging occurs again.

At this time, I don't know where else to look.

de Laurie VK3AMA


locked Re: JTalert integration with EQSL - Help

HamApps Support (VK3AMA)
 

On 5/07/2020 3:29 pm, Barry Bettman wrote:
Tonight I spend a couple of hours trying to configure the latest JTalert for eqsl integration but not successful yet.

I enabled the EQSL option and got a message when trying to log from WSJT-X 2.2.2 that the udp 2337 was not talking to wsjt-x.  Then I changed the udp in jtalert to 2337 and when I logged a contact in WSJT-x this time did not get an error; however the call logged into wsjt-x never showed up in eqsl.

I have also searched online for help and istructions on integration jtalert with eqsl, but to no avail.

Can anyone help, please

73,

Barry K6ST

Eqsl integration is easy. set the enable checkbox and make sure you have the "Callsign, Password & QTH Nickname" fields filled in.

   

Uploading to Eqsl (and the other online services) depends on JTAlert being set to log QSOs, so you need to enable your logger in JTAlert. If JTAlert shows "NO Log" in the titlebar than you don't have a logger enabled and there will be no online log uploads.

Uploading to Eqsl is then automatic each time JTAlert receives a QSO logged message from WSJT-X.

You cannot change the UDP port that JTAlert is listening to for WSJT-X messages. That is automatic and is determined by reading the WSJT-X config file.

If your getting UDP error messages from JTAlert, than UDP traffic from WSJT-X will not be received and no QSOs logged (or uploaded) or decoded callsigns shown.

Make sure you have the WSJT-X UDP Server settings correct. eg.

   

If you make any UDP changes, restart both WSJT-X and JTAlert.

If you still have problems, Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: JTAlertV2.Manager will not start

HamApps Support (VK3AMA)
 

On 6/07/2020 3:19 am, Jan Eliasson wrote:
I am using JTAlert 2.16.8 on a Windows 7 Professional 64 bits computer.

JTAlertV2.Manager will not start. I can see atempts in processes in the taskmanager. i have tried to disable the firewall (Windows) and Avast Anti virus,

I can not exactly say when it stopped working, but my last uploaded QSO in Clublog was from the beginning of april. So it started with version 2.16.3 or 2.16.4. 

73 de SM7NDX, Jan

Jan,

Are you seeing repeated attempts (like every second or so) to start JTAlertV2.Manager? You should as JTAlert will try and start the process when it detects it is not running.

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: wsjt 2.2.2 #FT8

Dave Garber
 

Is the callsign in the wsjtx window showing up in jtalert?

If yes then recheck user name and password for eqsl.  If not then it is not hearing on 2237.  Did you restart both software after making changes
sent by my LG phone

On Sun, Jul 5, 2020, 10:11 AM Barry Bettman, <k6st@...> wrote:
Just using the native log in wsjt-x and enabled eqsl in jtalert with udp 2337

73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio




On Sun, Jul 5, 2020 at 7:06 AM Dave Garber <ve3wej@...> wrote:
What logging program are you using

sent by my LG phone

On Sun, Jul 5, 2020, 9:56 AM Barry Bettman, <k6st@...> wrote:
Attached was the jtalert error screenshot.  When I changed the udp in jtlaert to 2337, and logged a qso,in wsjt-x then no error message came up.

But the qso logged in wsjt-x never showed up,in eqsl.

73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio






locked Re: JTAlertV2.Manager will not start

Dave Garber
 

Have you both tried to add an exemption to the hamapps folders then reinstall jtalert

sent by my LG phone

On Sun, Jul 5, 2020, 5:06 PM John, <k4ag@...> wrote:
Hi Jan,

If you find a solution please let me know. I'm having the same problem. Messages to and from Laurie haven't come up with a solution. I asked if there was a way to force it to start. Laurie said it's hard wired in the program.
After many attempts I occasionally get it started, then after using it I minimize it rather than closing it, that works great until a computer restart is needed.
73, John

On 7/5/2020 1:19 PM, Jan Eliasson wrote:
Hello!

I am using JTAlert 2.16.8 on a Windows 7 Professional 64 bits computer.

JTAlertV2.Manager will not start. I can see atempts in processes in the taskmanager. i have tried to disable the firewall (Windows) and Avast Anti virus,

I can not exactly say when it stopped working, but my last uploaded QSO in Clublog was from the beginning of april. So it started with version 2.16.3 or 2.16.4. 

73 de SM7NDX, Jan


Virus-free. www.avg.com


locked Re: JTAlertV2.Manager will not start

John
 

Hi Jan,

If you find a solution please let me know. I'm having the same problem. Messages to and from Laurie haven't come up with a solution. I asked if there was a way to force it to start. Laurie said it's hard wired in the program.
After many attempts I occasionally get it started, then after using it I minimize it rather than closing it, that works great until a computer restart is needed.
73, John

On 7/5/2020 1:19 PM, Jan Eliasson wrote:
Hello!

I am using JTAlert 2.16.8 on a Windows 7 Professional 64 bits computer.

JTAlertV2.Manager will not start. I can see atempts in processes in the taskmanager. i have tried to disable the firewall (Windows) and Avast Anti virus,

I can not exactly say when it stopped working, but my last uploaded QSO in Clublog was from the beginning of april. So it started with version 2.16.3 or 2.16.4. 

73 de SM7NDX, Jan


Virus-free. www.avg.com


locked Re: Click on JTAlert and get PathFinder to see "Call sign" ?

KD7YZ Bob
 

Dunno what the 'Scales' Icon means next to the Message Subject.
Here are my supporting evidence jpegs.
Firstly: AFTER a QSO is logged, then the call-sign is transported by something to Pathfinder.

No Context Menu path to DXKeeper, DXView or Pathfinder works despite them being in the Context-Menu .

I would love to use the "Test Button" seen in the screenshot of the help file .. but wait ... there isn't one, that I can find.

Is there a a user out there who actually Does use Pathfinder to see a decoded callsign from JTAlert? A month ago I could.

Have a look and please tell me the corrections to make.


locked JTAlertV2.Manager will not start

Jan Eliasson
 

Hello!

I am using JTAlert 2.16.8 on a Windows 7 Professional 64 bits computer.

JTAlertV2.Manager will not start. I can see atempts in processes in the taskmanager. i have tried to disable the firewall (Windows) and Avast Anti virus,

I can not exactly say when it stopped working, but my last uploaded QSO in Clublog was from the beginning of april. So it started with version 2.16.3 or 2.16.4. 

73 de SM7NDX, Jan


locked Re: wsjt 2.2.2 #FT8

Barry Bettman
 

Just using the native log in wsjt-x and enabled eqsl in jtalert with udp 2337

73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio




On Sun, Jul 5, 2020 at 7:06 AM Dave Garber <ve3wej@...> wrote:
What logging program are you using

sent by my LG phone

On Sun, Jul 5, 2020, 9:56 AM Barry Bettman, <k6st@...> wrote:
Attached was the jtalert error screenshot.  When I changed the udp in jtlaert to 2337, and logged a qso,in wsjt-x then no error message came up.

But the qso logged in wsjt-x never showed up,in eqsl.

73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio






locked Re: wsjt 2.2.2 #FT8

Dave Garber
 

What logging program are you using

sent by my LG phone

On Sun, Jul 5, 2020, 9:56 AM Barry Bettman, <k6st@...> wrote:
Attached was the jtalert error screenshot.  When I changed the udp in jtlaert to 2337, and logged a qso,in wsjt-x then no error message came up.

But the qso logged in wsjt-x never showed up,in eqsl.

73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio






locked Re: wsjt 2.2.2 #FT8

Barry Bettman
 

Attached was the jtalert error screenshot.  When I changed the udp in jtlaert to 2337, and logged a qso,in wsjt-x then no error message came up.

But the qso logged in wsjt-x never showed up,in eqsl.

73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio






locked Re: JTalert integration with EQSL - Help

Barry Bettman
 

To be clear, what I am looking for is instructions to integrate jtalert with aeqsl so when a qso is logged in wsjtx, it is automatically uploaded to Eqsl also,
73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio




On Sun, Jul 5, 2020 at 12:30 AM Barry Bettman <k6st@...> wrote:
Tonight I spend a couple of hours trying to configure the latest JTalert for eqsl integration but not successful yet.

I enabled the EQSL option and got a message when trying to log from WSJT-X 2.2.2 that the udp 2337 was not talking to wsjt-x.  Then I changed the udp in jtalert to 2337 and when I logged a contact in WSJT-x this time did not get an error; however the call logged into wsjt-x never showed up in eqsl.

I have also searched online for help and istructions on integration jtalert with eqsl, but to no avail.

Can anyone help, please

73,

Barry K6ST


locked Re: wsjt 2.2.2 #FT8

Barry Bettman
 

To be clear, what I am looking for is instructions to integrate jtalert with qso so when a qso is logged in wsjtx, it is automatically uploaded to Eqsl also,
Thanks,

73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio




On Sun, Jul 5, 2020 at 6:29 AM Barry Bettman <k6st@...> wrote:
Thanks,

I start wsjt x first. The error message was from jtalert I believe.


73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio




On Sun, Jul 5, 2020 at 6:23 AM neil_zampella <neilz@...> wrote:

Roert,

Is this a JT-Alert message?    Which program are you starting first, WSJT-X or JT-Alert??

 

Neil, KN3ILZ


locked Re: wsjt 2.2.2 #FT8

Barry Bettman
 

Thanks,

I start wsjt x first. The error message was from jtalert I believe.


73,

Barry K6ST
Nevada Section Youth Coordinator

ARRL (American Radio Relay League) arrl.org

The national association for amateur radio




On Sun, Jul 5, 2020 at 6:23 AM neil_zampella <neilz@...> wrote:

Roert,

Is this a JT-Alert message?    Which program are you starting first, WSJT-X or JT-Alert??

 

Neil, KN3ILZ


locked Re: wsjt 2.2.2 #FT8

neil_zampella
 

Roert,

Is this a JT-Alert message?    Which program are you starting first, WSJT-X or JT-Alert??

 

Neil, KN3ILZ


locked JTalert integration with EQSL - Help

Barry Bettman
 

Tonight I spend a couple of hours trying to configure the latest JTalert for eqsl integration but not successful yet.

I enabled the EQSL option and got a message when trying to log from WSJT-X 2.2.2 that the udp 2337 was not talking to wsjt-x.  Then I changed the udp in jtalert to 2337 and when I logged a contact in WSJT-x this time did not get an error; however the call logged into wsjt-x never showed up in eqsl.

I have also searched online for help and istructions on integration jtalert with eqsl, but to no avail.

Can anyone help, please

73,

Barry K6ST

5561 - 5580 of 36205