|
All,
I’m looking at section 32.3 in the manual. Does the UDP band map work together with JTAlert? I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating. What am I missing?
de KB2SSE Ken -- ScanAm Technical Services, LLC
|
|
|
Sorry, should be 2333 of course
All,
I’m looking at section 32.3 in the manual. Does the UDP band map work together with JTAlert? I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating. What am I missing?
de KB2SSE Ken --
ScanAm Technical Services, LLC
-- ScanAm Technical Services, LLC
|
|
|
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something).
So, I'd guess in Logger32 you'd configure like this:
a) Open the UDP BandMap.
Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open
one of the receive only UDP sockets on port 2223 (or whatever).
c) Kick back and make a not to yourself - Damn This DXing is fun.
SeventyThree(s).
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen <khansen@...> wrote:
Sorry, should be 2333 of course
All,
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
de KB2SSE
Ken
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
|
|
|
Good morning, Found an undocumented feature (I believe) When I set the band/mode to JTAlert, the band map (not UDP band map) reports “I’m lost”, guess it not seeing the frequency
On Thu, Feb 25, 2021 at 3:04 PM Bob < k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something).
So, I'd guess in Logger32 you'd configure like this:
a) Open the UDP BandMap.
Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open
one of the receive only UDP sockets on port 2223 (or whatever).
c) Kick back and make a not to yourself - Damn This DXing is fun.
SeventyThree(s).
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen < khansen@...> wrote:
Sorry, should be 2333 of course
All,
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
de KB2SSE
Ken
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
-- ScanAm Technical Services, LLC
|
|
|
There's supposed to be some kinda JTAlert window that Logger32 can detect, and once found, read the band/mode from the windows caption. That's the theory anyway. SeventyThree(s).
On 02/26/2021 8:47 AM Kenneth Hansen <khansen@...> wrote:
Good morning,
Found an undocumented feature (I believe)
When I set the band/mode to JTAlert, the band map (not UDP band map) reports
“I’m lost”, guess it not seeing the frequency
On Thu, Feb 25, 2021 at 3:04 PM Bob <
k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something).
So, I'd guess in Logger32 you'd configure like this:
a) Open the UDP BandMap.
Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open
one of the receive only UDP sockets on port 2223 (or whatever).
c) Kick back and make a not to yourself - Damn This DXing is fun.
SeventyThree(s).
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen <
khansen@...> wrote:
Sorry, should be 2333 of course
All,
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
de KB2SSE
Ken
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
|
|
|
It does, but not frequency, so I believe that is why the band map says “I’m lost”
On Fri, Feb 26, 2021 at 8:52 AM Bob < k4cy@...> wrote:
There's supposed to be some kinda JTAlert window that Logger32 can detect, and once found, read the band/mode from the windows caption. That's the theory anyway. SeventyThree(s).
On 02/26/2021 8:47 AM Kenneth Hansen < khansen@...> wrote:
Good morning,
Found an undocumented feature (I believe)
When I set the band/mode to JTAlert, the band map (not UDP band map) reports
“I’m lost”, guess it not seeing the frequency
On Thu, Feb 25, 2021 at 3:04 PM Bob <
k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something).
So, I'd guess in Logger32 you'd configure like this:
a) Open the UDP BandMap.
Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open
one of the receive only UDP sockets on port 2223 (or whatever).
c) Kick back and make a not to yourself - Damn This DXing is fun.
SeventyThree(s).
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen <
khansen@...> wrote:
Sorry, should be 2333 of course
All,
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
de KB2SSE
Ken
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
-- ScanAm Technical Services, LLC
|
|
|
There's no radio being polled, and no frequency information from JTAlert. I thought that under those conditions, the BandMap was supposed to default to 20m. Oh well, never mind. SeventyThree(s).
On 02/26/2021 8:59 AM Kenneth Hansen <khansen@...> wrote:
It does, but not frequency, so I believe that is why the band map says “I’m lost”
On Fri, Feb 26, 2021 at 8:52 AM Bob <
k4cy@...> wrote:
There's supposed to be some kinda JTAlert window that Logger32 can detect, and once found, read the band/mode from the windows caption. That's the theory anyway. SeventyThree(s).
On 02/26/2021 8:47 AM Kenneth Hansen <
khansen@...> wrote:
Good morning,
Found an undocumented feature (I believe)
When I set the band/mode to JTAlert, the band map (not UDP band map) reports
“I’m lost”, guess it not seeing the frequency
On Thu, Feb 25, 2021 at 3:04 PM Bob <
k4cy@...> wrote:
I don't think so. JTAlert connects to JTDX on UDP port 2237. JTAlert forwards QSL Logged messages only on UDP port 2333 (or something).
So, I'd guess in Logger32 you'd configure like this:
a) Open the UDP BandMap.
Set the Band/Mode option to be from JTAlert. Close the UDP BandMap (There's nothing to see).
b) Open
one of the receive only UDP sockets on port 2223 (or whatever).
c) Kick back and make a not to yourself - Damn This DXing is fun.
SeventyThree(s).
there's no data to be displayed in the UDP MandMap.
On 02/25/2021 2:43 PM Kenneth Hansen <
khansen@...> wrote:
Sorry, should be 2333 of course
All,
I’m looking at section 32.3 in the manual.
Does the UDP band map work together with JTAlert?
I did set the UDP port to 3332 in Logger32, but when I open the socket, JTAlert stops updating.
What am I missing?
de KB2SSE
Ken
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
--
ScanAm Technical Services, LLC
|
|
|
