|
Addition request for HamApps
#DXLAB
#HamSpots
#FT8
Jim, what makes you think memory is being exhausted? Have you eliminated any other processes or system services that might be consuming excessive memory?
Jim, what makes you think memory is being exhausted? Have you eliminated any other processes or system services that might be consuming excessive memory?
|
By
g4wjs
· #32972
·
|
|
Running two instances of JT Alert on one computer
Jim, you said several things in your OP that seem wrong to me, you have failed to clarify what you are doing and when ask to you reply with unrelated details. Let;s try again with some specific querie
Jim, you said several things in your OP that seem wrong to me, you have failed to clarify what you are doing and when ask to you reply with unrelated details. Let;s try again with some specific querie
|
By
g4wjs
· #32847
·
|
|
Running two instances of JT Alert on one computer
Hi Jim, the secondary ports are not relevant. The two different ports for each WSJT-X instance should be fine so long as no other application is using those ports. In you OP you talked about setting u
Hi Jim, the secondary ports are not relevant. The two different ports for each WSJT-X instance should be fine so long as no other application is using those ports. In you OP you talked about setting u
|
By
g4wjs
· #32845
·
|
|
Running two instances of JT Alert on one computer
Hi Jim, this is nothing to do with DXKeeper, JTAlert transfers logged QSOs to DXKeeper regardless of how many WSJT-X and corresponding JTAlert instances you have running. I am not sure you understand
Hi Jim, this is nothing to do with DXKeeper, JTAlert transfers logged QSOs to DXKeeper regardless of how many WSJT-X and corresponding JTAlert instances you have running. I am not sure you understand
|
By
g4wjs
· #32843
·
|
|
Running two instances of JT Alert on one computer
Hi Jim, the part above seems wrong. For WSJT-X you can copy the shortcut used to start it and add a --rig-name= option to its command line, for JTAlert all you need do is start JTAlert a second time.
Hi Jim, the part above seems wrong. For WSJT-X you can copy the shortcut used to start it and add a --rig-name= option to its command line, for JTAlert all you need do is start JTAlert a second time.
|
By
g4wjs
· #32841
·
|
|
locked
Click to respond
Hi Bill, make sure you have the WSJT-X option "Settings->Reporting->UDP Server->Accept UDP requests" checked. 73 Bill G4WJS.
Hi Bill, make sure you have the WSJT-X option "Settings->Reporting->UDP Server->Accept UDP requests" checked. 73 Bill G4WJS.
|
By
g4wjs
· #32771
·
|
|
locked
Multicast port
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 o
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 o
|
By
g4wjs
· #32751
·
|
|
locked
Multicast port
Hi Jesús, why have you changed to a unicast address? Your original setup is OK. 73 Bill G4WJS.
Hi Jesús, why have you changed to a unicast address? Your original setup is OK. 73 Bill G4WJS.
|
By
g4wjs
· #32740
·
|
|
locked
Need help with RC2 and WSPR-Band-Hopping
Hi Bob, do you have correctly functioning CAT control? 73 Bill G4WJS.
Hi Bob, do you have correctly functioning CAT control? 73 Bill G4WJS.
|
By
g4wjs
· #32550
·
|
|
locked
WSJT-X rc2
Hi Laurie, Users pick the address, they can use any appropriate one. What is appropriate may depend on their requirements, i.e. do other applications need to access WSJT-X multicast traffic on a diffe
Hi Laurie, Users pick the address, they can use any appropriate one. What is appropriate may depend on their requirements, i.e. do other applications need to access WSJT-X multicast traffic on a diffe
|
By
g4wjs
· #32369
·
|
|
locked
WSJT-X rc2
Laurie, as I explained off list, 224.0.0.1 is a special multicast address known as the "All Hosts" address. The 224.0.0.0/8 block of addresses is also special as they are never routed. 224.0.0.1 speci
Laurie, as I explained off list, 224.0.0.1 is a special multicast address known as the "All Hosts" address. The 224.0.0.0/8 block of addresses is also special as they are never routed. 224.0.0.1 speci
|
By
g4wjs
· #32294
·
|
|
locked
WSJT-X rc2
Laurie, the OP claimed to be using 239.0.0.1, that is most definitely *not* in the 239.255.0.0/16 block of multicast addresses!
Laurie, the OP claimed to be using 239.0.0.1, that is most definitely *not* in the 239.255.0.0/16 block of multicast addresses!
|
By
g4wjs
· #32291
·
|
|
locked
JTA/2.3.0-rc2 failing
Hi Gene, that's not necessary although it could tale up to 15 seconds after the change is saved before JTAlert sees the WSJT-X traffic.
Hi Gene, that's not necessary although it could tale up to 15 seconds after the change is saved before JTAlert sees the WSJT-X traffic.
|
By
g4wjs
· #32287
·
|
|
locked
WSJT-X rc2
Hi Tom, you appear to be one of the users using an inappropriate multicast address that has caused this change to be made. Until a version of JTAlert is available that will receive multicast traffic o
Hi Tom, you appear to be one of the users using an inappropriate multicast address that has caused this change to be made. Until a version of JTAlert is available that will receive multicast traffic o
|
By
g4wjs
· #32286
·
|
|
locked
JTA/2.3.0-rc2 failing
Hi Al, this is expected. WSJT-X no longer sends multicast UDP datagrams on the default network interface. There is a JTAlert update on the way to account for that, until that is available you can *cha
Hi Al, this is expected. WSJT-X no longer sends multicast UDP datagrams on the default network interface. There is a JTAlert update on the way to account for that, until that is available you can *cha
|
By
g4wjs
· #32275
·
|
|
locked
JT Alert start up sequence
Hi ian, if you use the option to dock the JTAlert window to the WSJT-X main window it will not matter which is which.
Hi ian, if you use the option to dock the JTAlert window to the WSJT-X main window it will not matter which is which.
|
By
g4wjs
· #32185
·
|
|
locked
DXKeeper to LoTW
Mike, if I understand the process correctly it is not wholly down to DXKeeper. JTAlert requests that DXKeeper do a single QSO upload to LoTW when it passes a QSO to DXKeeper. It is not controlled by D
Mike, if I understand the process correctly it is not wholly down to DXKeeper. JTAlert requests that DXKeeper do a single QSO upload to LoTW when it passes a QSO to DXKeeper. It is not controlled by D
|
By
g4wjs
· #32064
·
|
|
locked
Strange UI phenomenon
Hi Laurie, this may not be relevant and your comment above just be using incorrect terminology, but wide-strings in Windows are not utf-8, they are 16-bit characters encoded with utf-16 little-edian U
Hi Laurie, this may not be relevant and your comment above just be using incorrect terminology, but wide-strings in Windows are not utf-8, they are 16-bit characters encoded with utf-16 little-edian U
|
By
g4wjs
· #32040
·
Edited
|
|
locked
Brilliant New Feature - Distance Filter
Craig, check the release notes: https://hamapps.com/php/notes.php?file=jtalert
Craig, check the release notes: https://hamapps.com/php/notes.php?file=jtalert
|
By
g4wjs
· #31833
·
|
|
locked
JTAlert want connect
Hi Tom, do you have the same UDP server settings in each of your WSJT-X configurations ("Settings->Reporting->UDP Server")? 73 Bill G4WJS.
Hi Tom, do you have the same UDP server settings in each of your WSJT-X configurations ("Settings->Reporting->UDP Server")? 73 Bill G4WJS.
|
By
g4wjs
· #31801
·
|