Date   

locked Click to respond

bill@...
 

JTAlert is great.  But it would be even better if you could click on an alerted call sign to initiate a WSJT-X response.  I find i am usually too slow to enter the information into WSJT-X manually.  Is an automatic response feasible?


locked Re: ADIF File ADDRESS count error

Michael Black
 

Doesn't appear so...I just tested that.

I'll have to work with him and reduce the file and fields down until it works.

TQSL was just flashing "0 recs" as though it was stuck in a loop...and never quit.  Only had 12 QSOs in the file.

Mike




On Tuesday, December 15, 2020, 05:48:45 PM CST, Laurie, VK3AMA <hamapps.support@...> wrote:




On 16/12/2020 9:52 am, Michael Black via groups.io wrote:
> <MY_CQ_ZONE:1>0<MY_ITU_ZONE:1>0<


Perhaps TQSL is choking on the zeros for the ITU & CQZones?

de Laurie VK3AMA










locked Re: ADIF File ADDRESS count error

Laurie, VK3AMA
 

On 16/12/2020 9:52 am, Michael Black via groups.io wrote:
<MY_CQ_ZONE:1>0<MY_ITU_ZONE:1>0<
Perhaps TQSL is choking on the zeros for the ITU & CQZones?

de Laurie VK3AMA


locked Re: ADIF File ADDRESS count error

Laurie, VK3AMA
 



On 16/12/2020 9:52 am, Michael Black via groups.io wrote:
Laurie -- seems the <ADDRESS> tag in the ADIF file is maybe stripping CR's and giving the wrong field length.  The file won't upload to LOTW with TQSL 2.7

e.g. this has 76 chars in instead of 80
<CALL:6>WB2DHY<QSO_DATE:8>20201106<TIME_ON:6>135800<TIME_OFF:6>135900<FREQ:9>10.136704<FREQ_RX:9>10.136704<BAND:3>30m<BAND_RX:3>30m<MODE:3>FT8<DXCC:3>291<COUNTRY:13>United States<CQZ:1>5<ITUZ:1>8<CONT:2>NA<RST_SENT:3>+10<RST_RCVD:3>-15<LOTW_QSL_SENT:1>R<LOTW_QSL_RCVD:1>R<QSLMSG:25>FT8  Sent: +10  Rcvd: -15<GRIDSQUARE:6>FM17bj<DISTANCE:4>1104<TX_PWR:2>40<A_INDEX:1>4<K_INDEX:1>2<SFI:2>91<COMMENT:25>FT8  Sent: +10  Rcvd: -15<NAME:6>Philip<QTH:18>AMELIA COURT HOUSE<STATE:2>VA<PFX:3>WB2<CNTY:9>VA,Amelia<ADDRESS:80>Philip P Lorito
12371 DEATON LANE
AMELIA COURT HOUSE
VA, 23002
United States<IOTA:6>NA-083<MY_GRIDSQUARE:4>EN52<MY_CQ_ZONE:1>0<MY_ITU_ZONE:1>0<STATION_CALLSIGN:6>WA9JBQ<QSO_COMPLETE:1>Y<EOR>


Mike W9MDB


The 80 character count is correct. There are 72 characters in your sample plus 4 line endings, which on PC are 2 characters (CRLF). 72 + 4*2 = 80.

If that ADIF record is not uploading, it wont be because of the address field. Unless TQSL is broken which is unlikely as there have been no reports that I am aware of. Does TQSL provide any sort of error report? I suggest you raise this with the LoTW/TQSL people.

FWIW, there is only one place in the JTAlert code where CRLFs are deliberately stripped from an ADIF address field and that is in the data sent to HRD logs. The HRD TCP API is fundamentally broken where it stops processing incoming TCP data when a CRLF is encountered in the TCP stream despite CRLFs being supported by the ADIF spec and the HRD API requiring ADIF data!

de Laurie VK3AMA


locked Re: Win 7 to 10

Michael Black
 

You copy the whole HamApps folder in there.

Mike W9MDB




On Tuesday, December 15, 2020, 04:58:42 PM CST, Joseph Hurd <jhboards@...> wrote:


Hi Mike,

Closest file I can find for HamApps is: C:\users\New Owner\AppData\Local

That folder has several other folders and .ini files in it.

Do I just copy my exported file into that folder - C:\users\New Owner\AppData\Local  - or into a folder within it?


locked Re: Win 7 to 10

Joseph Hurd
 

Hi Mike,

Closest file I can find for HamApps is: C:\users\New Owner\AppData\Local

That folder has several other folders and .ini files in it.

Do I just copy my exported file into that folder - C:\users\New Owner\AppData\Local  - or into a folder within it?


locked ADIF File ADDRESS count error

Michael Black
 

Laurie -- seems the <ADDRESS> tag in the ADIF file is maybe stripping CR's and giving the wrong field length.  The file won't upload to LOTW with TQSL 2.7

e.g. this has 76 chars in instead of 80
<CALL:6>WB2DHY<QSO_DATE:8>20201106<TIME_ON:6>135800<TIME_OFF:6>135900<FREQ:9>10.136704<FREQ_RX:9>10.136704<BAND:3>30m<BAND_RX:3>30m<MODE:3>FT8<DXCC:3>291<COUNTRY:13>United States<CQZ:1>5<ITUZ:1>8<CONT:2>NA<RST_SENT:3>+10<RST_RCVD:3>-15<LOTW_QSL_SENT:1>R<LOTW_QSL_RCVD:1>R<QSLMSG:25>FT8  Sent: +10  Rcvd: -15<GRIDSQUARE:6>FM17bj<DISTANCE:4>1104<TX_PWR:2>40<A_INDEX:1>4<K_INDEX:1>2<SFI:2>91<COMMENT:25>FT8  Sent: +10  Rcvd: -15<NAME:6>Philip<QTH:18>AMELIA COURT HOUSE<STATE:2>VA<PFX:3>WB2<CNTY:9>VA,Amelia<ADDRESS:80>Philip P Lorito
12371 DEATON LANE
AMELIA COURT HOUSE
VA, 23002
United States<IOTA:6>NA-083<MY_GRIDSQUARE:4>EN52<MY_CQ_ZONE:1>0<MY_ITU_ZONE:1>0<STATION_CALLSIGN:6>WA9JBQ<QSO_COMPLETE:1>Y<EOR>


Mike W9MDB


locked Re: Win 7 to 10

Michael Black
 


%LOCALAPPDATA%\HamApps

Mike W9MDB


On Tuesday, December 15, 2020, 04:22:05 PM CST, Joseph Hurd <jhboards@...> wrote:


[Edited Message Follows]

Trying to import my JT Alert files from a Win 7 PC to a Win 10 PC.
Successfully copied my JT Alert file off the old Win 7 PC [C:\users\user name\appdata\local\hamapps] per the FAQs.
The FAQ lists the same file path to copy the file to for the new PC, but for Win 7 & 8 only, nothing about where to copy to in Win 10. I cannot find the same file path or folder in Win 10. Where do I copy/import the exported JTAlert files to on Win 10?


locked Win 7 to 10

Joseph Hurd
 
Edited

Trying to import my JT Alert files from a Win 7 PC to a Win 10 PC.
Successfully copied my JT Alert file off the old Win 7 PC [C:\users\user name\appdata\local\hamapps] per the FAQs.
The FAQ lists the same file path to copy the file to for the new PC, but for Win 7 & 8 only, nothing about where to copy to in Win 10. I cannot find the same file path or folder in Win 10. Where do I copy/import the exported JTAlert files to on Win 10?


locked Re: Lately I see a small square indicator in the upper right corner of decoded callsigns.

Bob, KA2TQV
 

On Tue, Dec 15, 2020 at 01:30 PM, Ron W3RJW wrote:
https://hamapps.groups.io/g/Support/topic/text_msg_indicator/78826772?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,78826772
Ron,

Thanks

Bob, KA2TQV


locked Re: Multicast port

Jesus
 

Michael, thank you very much for your contribution, the UDP multicast port working perfectly.
A picture is worth a thousand words.
If it has been useful for a radio broadcast that had this problem, solve it, effectiveness of the Group
Very grateful Michael ..
Cordially,
Jesus, EA1YR


El mar, 15 dic 2020 a las 18:13, Michael Black via groups.io (<mdblack98=yahoo.com@groups.io>) escribió:
What does WSJT-X look like?
Here's mine...

Inline image





On Tuesday, December 15, 2020, 10:57:07 AM CST, Jesus <jesusluanco@...> wrote:


Good afternoon Michael, I follow your instructions, I activated WSJT-X UDP Multicast on Loopback in JTAlert; change in WSJT the UDP server to 239.255.0.0 and port to 2334, but it does not decode and the error that I indicate in the image appears, in case it can help you in the solution.
With the previous version of wsjt-x 2.2.2, everything worked perfect.
I have returned to the server 127.0.0.1 with port 2237 and everything is ok.

Cordially,
Jesus, EA1YR

El mar, 15 dic 2020 a las 16:53, Michael Black via groups.io (<mdblack98=yahoo.com@groups.io>) escribió:
Inline image


Mike W9MDB




On Tuesday, December 15, 2020, 09:46:21 AM CST, Jesus <jesusluanco@...> wrote:


Good afternoon Bill, I'm using version 2.3.0-r3 of WSJT-X and the truth is, I can't find in JTAlert, the option to mark JTAlert "Menu-> Settings-> WSJT-X UDP Multicast on Loopback"
I thank you for telling me how to activate it by means of an image.
I appreciate your understanding.

Cordially,
Jesus, EA1YR

El lun, 14 dic 2020 a las 22:33, g4wjs (<bill.8@...>) escribió:
Hi Jesús,

nothing should have changed unless you are using the latest WSJT-X v2.3.0 RC2 release candidate. In that case you must either check the JTAlert option "Menu->Settings->WSJT-X UDP Multicast on Loopback" or check the main network interface in the WSJT-X "Settings->Reporting->Outgoing interfaces" drop down list.

73
Bill
G4WJS.

On 14/12/2020 20:23, Jesus wrote:
Good afternoon Bill, following your indication, I have reconfigured the UDP port in WSJT-X, to the values indicated in the previous email, that is, 239.255.0.0, port 2334.
JTAlert 2.16.17, does not decode or recognize the working band.
Active in JTAlert configuration, / Applications / WSJT-X / JTDX, have the checkbox marked: Forward UDP packets from WSJT-X (received only), but still not decoded; I uncheck it, to no avail.
I choose to change the port in WSJT-X, to its origin, that is, 127.0.0.1, port 2237, everything works again, JTAlert recognizes the band and decodes normally.
Am I missing any configuration for the multifunction port to work?
I appreciate the help you can give me

Cordially,
Jesus, EA1YR

El dom, 13 dic 2020 a las 20:52, g4wjs (<bill.8@...>) escribió:
On 13/12/2020 19:44, Jesus wrote:
Buenos días Laurie, con las últimas versiones de WSJT-X, recibí información sobre los puertos UDP multicast a través del Grupo, pero honestamente no veo cuál puede ser la configuración más práctica.
Tenía el servidor UDP configurado en wsjt-x, 239.255.00 y el puerto 2334, lo que hizo que JTAlert y GridTracker funcionaran simultáneamente.
Con la última versión, lo tengo de nuevo al estándar, 127.0.0.1 / 2237
En vista de las diferentes opciones, agradezco a Laurie que indiques tus criterios al respecto con respecto a la configuración adecuada.
Asimismo, es necesario en la configuración de JTAlert, / Aplicaciones / WSJT-X / JTDX, tener marcada la casilla de verificación: ¿Reenviar paquetes UDP de WSJT-X (solo recibidos)?

Cordialmente,
Jesús, EA1YR

Hi Jesús,

why have you changed to a unicast address? Your original setup is OK.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Lately I see a small square indicator in the upper right corner of decoded callsigns.

Ron W3RJW
 

On Tue, Dec 15, 2020 at 08:33 AM, Bob K wrote:
I had read the release notes, but was still confused. I thought the underscore beneath the call indicated texting was possible. If true, how does that differ from the little square?
It doesn't !!...  See Message above/below: https://hamapps.groups.io/g/Support/topic/text_msg_indicator/78826772?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,78826772
 
--
73
Ron, W3RJW


locked Re: Multicast port

Michael Black
 

What does WSJT-X look like?
Here's mine...

Inline image





On Tuesday, December 15, 2020, 10:57:07 AM CST, Jesus <jesusluanco@...> wrote:


Good afternoon Michael, I follow your instructions, I activated WSJT-X UDP Multicast on Loopback in JTAlert; change in WSJT the UDP server to 239.255.0.0 and port to 2334, but it does not decode and the error that I indicate in the image appears, in case it can help you in the solution.
With the previous version of wsjt-x 2.2.2, everything worked perfect.
I have returned to the server 127.0.0.1 with port 2237 and everything is ok.

Cordially,
Jesus, EA1YR

El mar, 15 dic 2020 a las 16:53, Michael Black via groups.io (<mdblack98=yahoo.com@groups.io>) escribió:
Inline image


Mike W9MDB




On Tuesday, December 15, 2020, 09:46:21 AM CST, Jesus <jesusluanco@...> wrote:


Good afternoon Bill, I'm using version 2.3.0-r3 of WSJT-X and the truth is, I can't find in JTAlert, the option to mark JTAlert "Menu-> Settings-> WSJT-X UDP Multicast on Loopback"
I thank you for telling me how to activate it by means of an image.
I appreciate your understanding.

Cordially,
Jesus, EA1YR

El lun, 14 dic 2020 a las 22:33, g4wjs (<bill.8@...>) escribió:
Hi Jesús,

nothing should have changed unless you are using the latest WSJT-X v2.3.0 RC2 release candidate. In that case you must either check the JTAlert option "Menu->Settings->WSJT-X UDP Multicast on Loopback" or check the main network interface in the WSJT-X "Settings->Reporting->Outgoing interfaces" drop down list.

73
Bill
G4WJS.

On 14/12/2020 20:23, Jesus wrote:
Good afternoon Bill, following your indication, I have reconfigured the UDP port in WSJT-X, to the values indicated in the previous email, that is, 239.255.0.0, port 2334.
JTAlert 2.16.17, does not decode or recognize the working band.
Active in JTAlert configuration, / Applications / WSJT-X / JTDX, have the checkbox marked: Forward UDP packets from WSJT-X (received only), but still not decoded; I uncheck it, to no avail.
I choose to change the port in WSJT-X, to its origin, that is, 127.0.0.1, port 2237, everything works again, JTAlert recognizes the band and decodes normally.
Am I missing any configuration for the multifunction port to work?
I appreciate the help you can give me

Cordially,
Jesus, EA1YR

El dom, 13 dic 2020 a las 20:52, g4wjs (<bill.8@...>) escribió:
On 13/12/2020 19:44, Jesus wrote:
Buenos días Laurie, con las últimas versiones de WSJT-X, recibí información sobre los puertos UDP multicast a través del Grupo, pero honestamente no veo cuál puede ser la configuración más práctica.
Tenía el servidor UDP configurado en wsjt-x, 239.255.00 y el puerto 2334, lo que hizo que JTAlert y GridTracker funcionaran simultáneamente.
Con la última versión, lo tengo de nuevo al estándar, 127.0.0.1 / 2237
En vista de las diferentes opciones, agradezco a Laurie que indiques tus criterios al respecto con respecto a la configuración adecuada.
Asimismo, es necesario en la configuración de JTAlert, / Aplicaciones / WSJT-X / JTDX, tener marcada la casilla de verificación: ¿Reenviar paquetes UDP de WSJT-X (solo recibidos)?

Cordialmente,
Jesús, EA1YR

Hi Jesús,

why have you changed to a unicast address? Your original setup is OK.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Multicast port

Jesus
 

Good afternoon Michael, I follow your instructions, I activated WSJT-X UDP Multicast on Loopback in JTAlert; change in WSJT the UDP server to 239.255.0.0 and port to 2334, but it does not decode and the error that I indicate in the image appears, in case it can help you in the solution.
With the previous version of wsjt-x 2.2.2, everything worked perfect.
I have returned to the server 127.0.0.1 with port 2237 and everything is ok.

Cordially,
Jesus, EA1YR


El mar, 15 dic 2020 a las 16:53, Michael Black via groups.io (<mdblack98=yahoo.com@groups.io>) escribió:
Inline image


Mike W9MDB




On Tuesday, December 15, 2020, 09:46:21 AM CST, Jesus <jesusluanco@...> wrote:


Good afternoon Bill, I'm using version 2.3.0-r3 of WSJT-X and the truth is, I can't find in JTAlert, the option to mark JTAlert "Menu-> Settings-> WSJT-X UDP Multicast on Loopback"
I thank you for telling me how to activate it by means of an image.
I appreciate your understanding.

Cordially,
Jesus, EA1YR

El lun, 14 dic 2020 a las 22:33, g4wjs (<bill.8@...>) escribió:
Hi Jesús,

nothing should have changed unless you are using the latest WSJT-X v2.3.0 RC2 release candidate. In that case you must either check the JTAlert option "Menu->Settings->WSJT-X UDP Multicast on Loopback" or check the main network interface in the WSJT-X "Settings->Reporting->Outgoing interfaces" drop down list.

73
Bill
G4WJS.

On 14/12/2020 20:23, Jesus wrote:
Good afternoon Bill, following your indication, I have reconfigured the UDP port in WSJT-X, to the values indicated in the previous email, that is, 239.255.0.0, port 2334.
JTAlert 2.16.17, does not decode or recognize the working band.
Active in JTAlert configuration, / Applications / WSJT-X / JTDX, have the checkbox marked: Forward UDP packets from WSJT-X (received only), but still not decoded; I uncheck it, to no avail.
I choose to change the port in WSJT-X, to its origin, that is, 127.0.0.1, port 2237, everything works again, JTAlert recognizes the band and decodes normally.
Am I missing any configuration for the multifunction port to work?
I appreciate the help you can give me

Cordially,
Jesus, EA1YR

El dom, 13 dic 2020 a las 20:52, g4wjs (<bill.8@...>) escribió:
On 13/12/2020 19:44, Jesus wrote:
Buenos días Laurie, con las últimas versiones de WSJT-X, recibí información sobre los puertos UDP multicast a través del Grupo, pero honestamente no veo cuál puede ser la configuración más práctica.
Tenía el servidor UDP configurado en wsjt-x, 239.255.00 y el puerto 2334, lo que hizo que JTAlert y GridTracker funcionaran simultáneamente.
Con la última versión, lo tengo de nuevo al estándar, 127.0.0.1 / 2237
En vista de las diferentes opciones, agradezco a Laurie que indiques tus criterios al respecto con respecto a la configuración adecuada.
Asimismo, es necesario en la configuración de JTAlert, / Aplicaciones / WSJT-X / JTDX, tener marcada la casilla de verificación: ¿Reenviar paquetes UDP de WSJT-X (solo recibidos)?

Cordialmente,
Jesús, EA1YR

Hi Jesús,

why have you changed to a unicast address? Your original setup is OK.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Multicast port

Michael Black
 

Inline image


Mike W9MDB




On Tuesday, December 15, 2020, 09:46:21 AM CST, Jesus <jesusluanco@...> wrote:


Good afternoon Bill, I'm using version 2.3.0-r3 of WSJT-X and the truth is, I can't find in JTAlert, the option to mark JTAlert "Menu-> Settings-> WSJT-X UDP Multicast on Loopback"
I thank you for telling me how to activate it by means of an image.
I appreciate your understanding.

Cordially,
Jesus, EA1YR

El lun, 14 dic 2020 a las 22:33, g4wjs (<bill.8@...>) escribió:
Hi Jesús,

nothing should have changed unless you are using the latest WSJT-X v2.3.0 RC2 release candidate. In that case you must either check the JTAlert option "Menu->Settings->WSJT-X UDP Multicast on Loopback" or check the main network interface in the WSJT-X "Settings->Reporting->Outgoing interfaces" drop down list.

73
Bill
G4WJS.

On 14/12/2020 20:23, Jesus wrote:
Good afternoon Bill, following your indication, I have reconfigured the UDP port in WSJT-X, to the values indicated in the previous email, that is, 239.255.0.0, port 2334.
JTAlert 2.16.17, does not decode or recognize the working band.
Active in JTAlert configuration, / Applications / WSJT-X / JTDX, have the checkbox marked: Forward UDP packets from WSJT-X (received only), but still not decoded; I uncheck it, to no avail.
I choose to change the port in WSJT-X, to its origin, that is, 127.0.0.1, port 2237, everything works again, JTAlert recognizes the band and decodes normally.
Am I missing any configuration for the multifunction port to work?
I appreciate the help you can give me

Cordially,
Jesus, EA1YR

El dom, 13 dic 2020 a las 20:52, g4wjs (<bill.8@...>) escribió:
On 13/12/2020 19:44, Jesus wrote:
Buenos días Laurie, con las últimas versiones de WSJT-X, recibí información sobre los puertos UDP multicast a través del Grupo, pero honestamente no veo cuál puede ser la configuración más práctica.
Tenía el servidor UDP configurado en wsjt-x, 239.255.00 y el puerto 2334, lo que hizo que JTAlert y GridTracker funcionaran simultáneamente.
Con la última versión, lo tengo de nuevo al estándar, 127.0.0.1 / 2237
En vista de las diferentes opciones, agradezco a Laurie que indiques tus criterios al respecto con respecto a la configuración adecuada.
Asimismo, es necesario en la configuración de JTAlert, / Aplicaciones / WSJT-X / JTDX, tener marcada la casilla de verificación: ¿Reenviar paquetes UDP de WSJT-X (solo recibidos)?

Cordialmente,
Jesús, EA1YR

Hi Jesús,

why have you changed to a unicast address? Your original setup is OK.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Multicast port

Jesus
 

Good afternoon Bill, I'm using version 2.3.0-r3 of WSJT-X and the truth is, I can't find in JTAlert, the option to mark JTAlert "Menu-> Settings-> WSJT-X UDP Multicast on Loopback"
I thank you for telling me how to activate it by means of an image.
I appreciate your understanding.

Cordially,
Jesus, EA1YR


El lun, 14 dic 2020 a las 22:33, g4wjs (<bill.8@...>) escribió:
Hi Jesús,

nothing should have changed unless you are using the latest WSJT-X v2.3.0 RC2 release candidate. In that case you must either check the JTAlert option "Menu->Settings->WSJT-X UDP Multicast on Loopback" or check the main network interface in the WSJT-X "Settings->Reporting->Outgoing interfaces" drop down list.

73
Bill
G4WJS.

On 14/12/2020 20:23, Jesus wrote:
Good afternoon Bill, following your indication, I have reconfigured the UDP port in WSJT-X, to the values indicated in the previous email, that is, 239.255.0.0, port 2334.
JTAlert 2.16.17, does not decode or recognize the working band.
Active in JTAlert configuration, / Applications / WSJT-X / JTDX, have the checkbox marked: Forward UDP packets from WSJT-X (received only), but still not decoded; I uncheck it, to no avail.
I choose to change the port in WSJT-X, to its origin, that is, 127.0.0.1, port 2237, everything works again, JTAlert recognizes the band and decodes normally.
Am I missing any configuration for the multifunction port to work?
I appreciate the help you can give me

Cordially,
Jesus, EA1YR

El dom, 13 dic 2020 a las 20:52, g4wjs (<bill.8@...>) escribió:
On 13/12/2020 19:44, Jesus wrote:
Buenos días Laurie, con las últimas versiones de WSJT-X, recibí información sobre los puertos UDP multicast a través del Grupo, pero honestamente no veo cuál puede ser la configuración más práctica.
Tenía el servidor UDP configurado en wsjt-x, 239.255.00 y el puerto 2334, lo que hizo que JTAlert y GridTracker funcionaran simultáneamente.
Con la última versión, lo tengo de nuevo al estándar, 127.0.0.1 / 2237
En vista de las diferentes opciones, agradezco a Laurie que indiques tus criterios al respecto con respecto a la configuración adecuada.
Asimismo, es necesario en la configuración de JTAlert, / Aplicaciones / WSJT-X / JTDX, tener marcada la casilla de verificación: ¿Reenviar paquetes UDP de WSJT-X (solo recibidos)?

Cordialmente,
Jesús, EA1YR

Hi Jesús,

why have you changed to a unicast address? Your original setup is OK.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Lately I see a small square indicator in the upper right corner of decoded callsigns.

Bob, KA2TQV
 

I know I’m going to get into trouble here, but...

I had read the release notes, but was still confused. I thought the underscore beneath the call indicated texting was possible. If true, how does that differ from the little square?

Bob, KA2TQV


locked Re: Multicast port

g4wjs
 

Hi Jesús,

nothing should have changed unless you are using the latest WSJT-X v2.3.0 RC2 release candidate. In that case you must either check the JTAlert option "Menu->Settings->WSJT-X UDP Multicast on Loopback" or check the main network interface in the WSJT-X "Settings->Reporting->Outgoing interfaces" drop down list.

73
Bill
G4WJS.

On 14/12/2020 20:23, Jesus wrote:
Good afternoon Bill, following your indication, I have reconfigured the UDP port in WSJT-X, to the values indicated in the previous email, that is, 239.255.0.0, port 2334.
JTAlert 2.16.17, does not decode or recognize the working band.
Active in JTAlert configuration, / Applications / WSJT-X / JTDX, have the checkbox marked: Forward UDP packets from WSJT-X (received only), but still not decoded; I uncheck it, to no avail.
I choose to change the port in WSJT-X, to its origin, that is, 127.0.0.1, port 2237, everything works again, JTAlert recognizes the band and decodes normally.
Am I missing any configuration for the multifunction port to work?
I appreciate the help you can give me

Cordially,
Jesus, EA1YR

El dom, 13 dic 2020 a las 20:52, g4wjs (<bill.8@...>) escribió:
On 13/12/2020 19:44, Jesus wrote:
Buenos días Laurie, con las últimas versiones de WSJT-X, recibí información sobre los puertos UDP multicast a través del Grupo, pero honestamente no veo cuál puede ser la configuración más práctica.
Tenía el servidor UDP configurado en wsjt-x, 239.255.00 y el puerto 2334, lo que hizo que JTAlert y GridTracker funcionaran simultáneamente.
Con la última versión, lo tengo de nuevo al estándar, 127.0.0.1 / 2237
En vista de las diferentes opciones, agradezco a Laurie que indiques tus criterios al respecto con respecto a la configuración adecuada.
Asimismo, es necesario en la configuración de JTAlert, / Aplicaciones / WSJT-X / JTDX, tener marcada la casilla de verificación: ¿Reenviar paquetes UDP de WSJT-X (solo recibidos)?

Cordialmente,
Jesús, EA1YR

Hi Jesús,

why have you changed to a unicast address? Your original setup is OK.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: Multicast port

Jesus
 

Good afternoon Bill, following your indication, I have reconfigured the UDP port in WSJT-X, to the values indicated in the previous email, that is, 239.255.0.0, port 2334.
JTAlert 2.16.17, does not decode or recognize the working band.
Active in JTAlert configuration, / Applications / WSJT-X / JTDX, have the checkbox marked: Forward UDP packets from WSJT-X (received only), but still not decoded; I uncheck it, to no avail.
I choose to change the port in WSJT-X, to its origin, that is, 127.0.0.1, port 2237, everything works again, JTAlert recognizes the band and decodes normally.
Am I missing any configuration for the multifunction port to work?
I appreciate the help you can give me

Cordially,
Jesus, EA1YR


El dom, 13 dic 2020 a las 20:52, g4wjs (<bill.8@...>) escribió:
On 13/12/2020 19:44, Jesus wrote:
Buenos días Laurie, con las últimas versiones de WSJT-X, recibí información sobre los puertos UDP multicast a través del Grupo, pero honestamente no veo cuál puede ser la configuración más práctica.
Tenía el servidor UDP configurado en wsjt-x, 239.255.00 y el puerto 2334, lo que hizo que JTAlert y GridTracker funcionaran simultáneamente.
Con la última versión, lo tengo de nuevo al estándar, 127.0.0.1 / 2237
En vista de las diferentes opciones, agradezco a Laurie que indiques tus criterios al respecto con respecto a la configuración adecuada.
Asimismo, es necesario en la configuración de JTAlert, / Aplicaciones / WSJT-X / JTDX, tener marcada la casilla de verificación: ¿Reenviar paquetes UDP de WSJT-X (solo recibidos)?

Cordialmente,
Jesús, EA1YR

Hi Jesús,

why have you changed to a unicast address? Your original setup is OK.

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: 2.16.16 crashes

f8nhf
 

Good evening Stuart

glad to see that it works for you
here I reinstalled everything by deleting all the HamApps folders from the PC
it still doesn't work here
can you please make me copies of your config's please
config: hrd..... QSO forwarding
             : JTDX ....... reporting tab
             : JTAlert loging V5/V6
 thank you in advance

Denis F8NHF
                             

5141 - 5160 of 37686