Date   

locked Re: unsuccessful contacts with 7q7ru

Björn SM7IUN
 

Likely since LIDS are repeatedly calling him below 1000Hz. 
The Fox will not respond to them, they just QRM. 

Björn SM7IUN

Den sön 15 nov. 2020 kl 22:05 skrev ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io>:

Good afternoon group.


Since yesterday evening 7q7ru has heard my call and called me down to his frequency (Fox/Hound) 9 times with out a successfully confirmation.

After a few back and forth with the signal report (which has been very good reports) they throw me up to a higher frequency and leave me there and go on calling other calls or calling CQ.

Are they running a different software that is not compatible with JTAlert/WSJT-X?
or is it possible a setting has been changed with my software?

I tested my software by making other contacts (not Fox/Hound) so unless the problem id something with Fox/Hound my software is working..


Thanks for any help..


73,

W9RF - Joe



locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Roger,


I understand that but with signal reports +4 to him and -01 to me, I know he doesn't have a problem hearing me.

Now, why can't he decode me (maybe that should be my question)


6 times in a row last evening he pushed me to a higher 500-1000 freq and after a minute or so I went back above 1000 and called him again, after he called a few more calls I was called back down to his freq again.

This went on for over an hour and finally he went qrt.



On Sunday, November 15, 2020, 3:12:09 PM CST, Roger M via groups.io <ac6bw@...> wrote:


It is normal for the Fox to push you up to a higher offset frequency, between 500 - 1000 Hz, if he has not successfully decoded you after 3 cycles in the 0 - 500 Hz frequency slot. At that point, your QSO is in limbo. Your best course of action is to start over by calling him with a TX1 above 1000 Hz.
The SW on your end is working as it should.

--
73,
Roger
AC6BW


locked Re: WSJT-X rc2

g4wjs
 

On 15/11/2020 21:14, HamApps Support (VK3AMA) wrote:
FWIW, the original choice of the 239.255.0.0/16 subnet for the JTAlert multicast support was based on your recommendations in this posting
Quote...

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!


--
73
Bill
G4WJS.


locked Re: WSJT-X rc2

HamApps Support (VK3AMA)
 

On 16/11/2020 7:51 am, g4wjs wrote:

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 on the loop-back network interface, you can restore functionality by choosing your local subnet network interface in WSJT-X "Settings->Reporting->UDP Server->Outgoing interface".

Multicast addresses in the 239.0.0.0/16 block are potentially globally routed, that is not a good choice for getting traffic to a server on the same host or your local subnet.


--
73
Bill
G4WJS.

Bill,

JTAlert will work with a 224.0.0.0/16 multicast address. Try it.

From my JTAlert Help->About ...
   

FWIW, the original choice of the 239.255.0.0/16 subnet for the JTAlert multicast support was based on your recommendations in this posting
Quote...
Hi Tag and Ed,

modern multicast routing does not rely on TTL values to restrict routing span, best to use an administratively scopes address. I use 239.255.0.0/16 addresses which is site local, it is a bit like 192.168.0.0/16 or 10.0.0.0/24 addresses. better still use IPv6 multicast group addresses like ffx5::/16 which are all site local multicast addresses, e.g. ff05::, ff05::1, ..., ff05::ff:ff, ff15::, ff15::ff:ff, ...


To which Tag responded in this posting
Quote...
I have started recommending 239.255.0.1 to my user base.


I followed your lead in recommending 239.255.0.0 as the Multicast address to use for WSJT-X inter-operating with JTAlert.

What do you recommend now as a suitable address within the 224.0.0.0/16 subnet?

Since the "goal posts" have changed with 224.0.0.0/16 now being recommended, I'll update the JTAlert documentation to use an address in the now recommended range.

de Laurie VK3AMA



locked Re: unsuccessful contacts with 7q7ru

Roger- AC6BW
 

It is normal for the Fox to push you up to a higher offset frequency, between 500 - 1000 Hz, if he has not successfully decoded you after 3 cycles in the 0 - 500 Hz frequency slot. At that point, your QSO is in limbo. Your best course of action is to start over by calling him with a TX1 above 1000 Hz.
The SW on your end is working as it should.

--
73,
Roger
AC6BW


locked unsuccessful contacts with 7q7ru

Joe - W9RF
 

Good afternoon group.


Since yesterday evening 7q7ru has heard my call and called me down to his frequency (Fox/Hound) 9 times with out a successfully confirmation.

After a few back and forth with the signal report (which has been very good reports) they throw me up to a higher frequency and leave me there and go on calling other calls or calling CQ.

Are they running a different software that is not compatible with JTAlert/WSJT-X?
or is it possible a setting has been changed with my software?

I tested my software by making other contacts (not Fox/Hound) so unless the problem id something with Fox/Hound my software is working..


Thanks for any help..


73,

W9RF - Joe



locked Re: JTA/2.3.0-rc2 failing

g4wjs
 

On 15/11/2020 20:30, Gene, K5PA wrote:

[Edited Message Follows]

I think I had to restart WSJT-X after selecting the ethernet_32769 for the change to take effect.
But it worked afterwards.
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.



--
73
Bill
G4WJS.


locked Re: WSJT-X rc2

g4wjs
 

On 15/11/2020 20:25, Thomas Mills wrote:
Just loaded wsjtx rc2 and got a message that the network port was not working.  found this on the wsjtx release notes, so I guess 239.0.0.1 want work anymore?


 Due to  some users using  inappropriate multicast IP  addresses for
   their interoperating  servers the default behaviour now is  to only
   send multicast  UDP datagrams  to the loop-back  network interface.
   Users who  require WSJT-X UDP  Message Protocol datagrams  to reach
   other  hosts will  now  have  to configure  WSJT-X  to  send on  an
   appropriate  network interface,  and  use  an appropriately  scoped
   multicast group address for their  server applications.  If you are
   not sure then  224.0.0.1 (or ff02::1 if IPv6 is  desired) is a safe
   choice.
Thanks Tom WB4JWM
_._,_._,_

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 on the loop-back network interface, you can restore functionality by choosing your local subnet network interface in WSJT-X "Settings->Reporting->UDP Server->Outgoing interface".

Multicast addresses in the 239.0.0.0/16 block are potentially globally routed, that is not a good choice for getting traffic to a server on the same host or your local subnet.


--
73
Bill
G4WJS.


locked Re: JTA/2.3.0-rc2 failing

Gene, K5PA
 
Edited

I think I had to restart WSJT-X after selecting the ethernet_32769 for the change to take effect.
But it worked afterwards.


locked WSJT-X rc2

Thomas Mills
 

Just loaded wsjtx rc2 and got a message that the network port was not working.  found this on the wsjtx release notes, so I guess 239.0.0.1 want work anymore?


 Due to  some users using  inappropriate multicast IP  addresses for
   their interoperating  servers the default behaviour now is  to only
   send multicast  UDP datagrams  to the loop-back  network interface.
   Users who  require WSJT-X UDP  Message Protocol datagrams  to reach
   other  hosts will  now  have  to configure  WSJT-X  to  send on  an
   appropriate  network interface,  and  use  an appropriately  scoped
   multicast group address for their  server applications.  If you are
   not sure then  224.0.0.1 (or ff02::1 if IPv6 is  desired) is a safe
   choice.
Thanks Tom WB4JWM


locked Re: JTAlert Not Responding When Moving from DX to Local

HamApps Support (VK3AMA)
 

On 15/11/2020 8:21 am, Robert A Wilson wrote:
I converted the HRD database from Access to MariaDB and it seems to be working better.
Wise move.

You likely would have corrected the problem by creating a new HRD Access Log file, importing your old contacts, and setting JTAlert to use that new Log.

In recent months there have been a significant number of HRD users experiencing severe JTAlert slowdown to complete lockup. This was tracked down to a problem with their Access Log, either the log file or the ODBC DSN defined for the Log. The fix in all cases was to create a new HRD Access Log file.

de Laurie VK3AMA


locked Re: Text message window

HamApps Support (VK3AMA)
 

On 15/11/2020 3:29 am, Guy G4DWV 4X1LT wrote:
I can confirm that I have already done as you suggested. Please see screenshot. I have just loaded JTAlert and the text window appeared.

--
73 de Guy G4DWV 4X1LT
Guy,

Are you talking about the popup that is shown when you receive a Text Message (which should not now be happening) or the Text Message window which allows you to compose/send a message?

If it is the latter, does it appear automatically when JTAlert is started or at random times?

de Laurie VK3AMA


locked Re: Text message window

kk7h@...
 

GM All.
I have to agree with Keith & Dave, the text messaging is a great tool for the reasons stated above. I also use it to say Hello to friends.
73
Mike   KK7H


locked Re: Text message window

Dave (NK7Z)
 

Not to be snarky, but perhaps you have discovered why... They don't want to hear about it. It seems most stations have it off. Sad to see.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 11/15/20 8:47 AM, Keith Carter, KF4BI wrote:
Why does anyone want to turn messages off? I have wished many many times that a station had messages turned on so I could let them know that they were transmitting images or distortion or a broad signal that is occupying 3 slots on the band. Often someone needs to tell a station that their clock is off too much so they can quit useless calling. I'm sure much thought and work went into programming this very useful part of a great program and it's a shame folks disable it.


locked Re: Text message window

Keith Carter, KF4BI
 

Why does anyone want to turn messages off? I have wished many many times that a station had messages turned on so I could let them know that they were transmitting images or distortion or a broad signal that is occupying 3 slots on the band. Often someone needs to tell a station that their clock is off too much so they can quit useless calling. I'm sure much thought and work went into programming this very useful part of a great program and it's a shame folks disable it.


locked Re: JTA/2.3.0-rc2 failing

Al Groff
 

Mike,
  Email from Joe at 9 am on the WSJTX.groups.io reflector
AL, K0VM


On 11/15/2020 10:12 AM, Michael Black via groups.io wrote:
Where was the announcement for rc2?  It's not on the WSJT-X page.

Mike W9MDB




On Sunday, November 15, 2020, 10:04:14 AM CST, g4wjs <bill.8@...> wrote:


On 15/11/2020 15:59, Al Groff via groups.io wrote:
( jta 2.16.15, wsjt-x 2.3.0-rc2, Win10 20h02 )

can not get JTA and RC2 to interact...  What am I missing ?



AL, K0VM

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 *change* the "Outgoing interface" setting in WSJT-X "Settings->Reporting" to use the network interface on your machine that is your local subnet. Probably something like "wireless_0" or "ethernet_0".

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: JTA/2.3.0-rc2 failing

Al Groff
 

Bill,
  After selecting Ethernet in the dropdown, it gave me ethernet_32769 and that seems to be working..

Thanks

AL, K0VM


On 11/15/2020 10:03 AM, g4wjs wrote:
On 15/11/2020 15:59, Al Groff via groups.io wrote:
( jta 2.16.15, wsjt-x 2.3.0-rc2, Win10 20h02 )

can not get JTA and RC2 to interact...  What am I missing ?



AL, K0VM

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 *change* the "Outgoing interface" setting in WSJT-X "Settings->Reporting" to use the network interface on your machine that is your local subnet. Probably something like "wireless_0" or "ethernet_0".

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: JTA/2.3.0-rc2 failing

Michael Black
 

Where was the announcement for rc2?  It's not on the WSJT-X page.

Mike W9MDB




On Sunday, November 15, 2020, 10:04:14 AM CST, g4wjs <bill.8@...> wrote:


On 15/11/2020 15:59, Al Groff via groups.io wrote:
( jta 2.16.15, wsjt-x 2.3.0-rc2, Win10 20h02 )

can not get JTA and RC2 to interact...  What am I missing ?



AL, K0VM

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 *change* the "Outgoing interface" setting in WSJT-X "Settings->Reporting" to use the network interface on your machine that is your local subnet. Probably something like "wireless_0" or "ethernet_0".

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: JTA/2.3.0-rc2 failing

g4wjs
 

On 15/11/2020 15:59, Al Groff via groups.io wrote:
( jta 2.16.15, wsjt-x 2.3.0-rc2, Win10 20h02 )

can not get JTA and RC2 to interact...  What am I missing ?



AL, K0VM

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 *change* the "Outgoing interface" setting in WSJT-X "Settings->Reporting" to use the network interface on your machine that is your local subnet. Probably something like "wireless_0" or "ethernet_0".

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked JTA/2.3.0-rc2 failing

Al Groff
 

( jta 2.16.15, wsjt-x 2.3.0-rc2, Win10 20h02 )

can not get JTA and RC2 to interact...  What am I missing ?



AL, K0VM

4381 - 4400 of 36454