#Compound Call Signs (2024)

Jacques Pecourt

• All Messages By This Member

This subject has been addressed many times before and I understand the restrictions related to exchanges with portable stations ( i.e. PE/ XX2XX or XX2/stayhome) using a compound call sign myself. I do not call these stations or answer the ones calling me. However, there are frequent other occurrences I cannot understand. For example, I had successful contacts with 2I0IUE, E20WXA but I cannot make exchanges with 3DA0AQ ( in all cases slashed0) . Using the available /bin/code ft8 confirms that, in the later case, the numeral0being in the fourth position of the call is the reason for a decoding failure. In all 3 cases, the calls have 6 characters. Is the position of the numeral the reason for the failure? By failure, I mean that the signal report I am attempting to send ( -10 or R-10) disappears. End and lost contact !

Can someone explain this situation to me. Thank you

Jacques.

W2/F2YS

• All Messages By This Member

Jacques Pecourt

• All Messages By This Member

Bill,

Thank you for your timely answer. Youconfirmed what I found, the 3DA0AQ not different in the number of charactersinvolved (6) from the other 2 callsigns falls into the “nonstandard” category. Thereis nothing that can be done about it. Looking closely at the “message bits”, all 3decoded examples have a length of 77 bits however, the 2 others call have anumeral 0 for the first decoded bits followed on the 27th or 28^thposition by an alternance of numbers 0 to 7 . The 3DA decode alternance startsmuch sooner (9^th bit). Way above my level of understanding and Ijust must accept the facts.

Thank you as always for the great support.Stay well and 73’s.

Jacques.

W2/F2YS

On Mon, 6 Sept 2021 at 16:08, Bill Somerville <g4wjs@...> wrote:

On 06/09/2021 19:08, Jacques Pecourt wrote:

This subject has been addressed many times before and I understand the restrictions related to exchanges with portable stations ( i.e. PE/ XX2XX or XX2/stayhome) using a compound call sign myself. I do not call these stations or answer the ones calling me. However, there are frequent other occurrences I cannot understand. For example, I had successful contacts with 2I0IUE, E20WXA but I cannot make exchanges with 3DA0AQ ( in all cases slashed0) . Using the available /bin/code ft8 confirms that, in the later case, the numeral0being in the fourth position of the call is the reason for a decoding failure. In all 3 cases, the calls have 6 characters. Is the position of the numeral the reason for the failure? By failure, I mean that the signal report I am attempting to send ( -10 or R-10) disappears. End and lost contact !

Can someone explain this situation to me. Thank you

Jacques.

W2/F2YS

Hi Jacques,

3DA0AQ is a non-standard callsign in WSJT-X 77-bit payload modes like FT8, FT4, MSK144, Q65, and FST4. If you check the WSJT-X User Guide here:

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.4.0.html#COMP-CALL

you will see this statement "Except for the special cases involving /P or /R used in VHF contesting, WSJT-X 2.4 offers no support for two nonstandard callsigns to work each other." this is why you are having issues.

73
Bill
G4WJS.

• All Messages By This Member

Take me off this email list please.

From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of Bill Somerville <g4wjs@...>
Sent: Monday, September 6, 2021 8:15:34 PM
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Subject: Re: [WSJTX] #Compound Call Signs #issue

Hi Jacques,

you do not need to understand the source encoding of callsigns at the bit level, the rule that defines a standard callsign for the WSJT-X 77-bit protocols is included in the WSJT-X User Guide here:

The important part being "A standard amateur callsign consists of a one- or two-character prefix, at least one of which must be a letter, followed by a digit and a suffix of one to three letters."

The above constraint allows a standard callsign to be uniquely encoded as a 28-bit number. Apart from /P and /R suffixes appended to standard callsigns, non-standard callsigns up to 11 characters long are encoded as a 58-bit number which does not leave room in the message payload for a second callsign, either standard or non-standard, so the other callsign is represented by a 12-bit non-unique hash code and a one bit flag to encode if the hash code represents the first or the second callsign. Full details are here:

73
Bill
G4WJS.

On 07/09/2021 00:54, Jacques Pecourt wrote:

Bill,

Thank you for your timely answer. You confirmed what I found, the 3DA0AQ not different in the number of characters involved (6) from the other 2 callsigns falls into the “nonstandard” category. There is nothing that can be done about it. Looking closely at the “message bits”, all 3 decoded examples have a length of 77 bits however, the 2 others call have a numeral 0 for the first decoded bits followed on the 27th or 28^th position by an alternance of numbers 0 to 7 . The 3DA decode alternance starts much sooner (9^th bit). Way above my level of understanding and I just must accept the facts.

Thank you as always for the great support. Stay well and 73’s.

Jacques.

W2/F2YS

On Mon, 6 Sept 2021 at 16:08, Bill Somerville <g4wjs@...> wrote:

On 06/09/2021 19:08, Jacques Pecourt wrote:

This subject has been addressed many times before and I understand the restrictions related to exchanges with portable stations ( i.e. PE/ XX2XX or XX2/stayhome) using a compound call sign myself. I do not call these stations or answer the ones calling me. However, there are frequent other occurrences I cannot understand. For example, I had successful contacts with 2I0IUE, E20WXA but I cannot make exchanges with 3DA0AQ ( in all cases slashed0) . Using the available /bin/code ft8 confirms that, in the later case, the numeral0being in the fourth position of the call is the reason for a decoding failure. In all 3 cases, the calls have 6 characters. Is the position of the numeral the reason for the failure? By failure, I mean that the signal report I am attempting to send ( -10 or R-10) disappears. End and lost contact !

Can someone explain this situation to me. Thank you

Jacques.

W2/F2YS

Hi Jacques,

3DA0AQ is a non-standard callsign in WSJT-X 77-bit payload modes like FT8, FT4, MSK144, Q65, and FST4. If you check the WSJT-X User Guide here:

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.4.0.html#COMP-CALL

you will see this statement "Except for the special cases involving /P or /R used in VHF contesting,WSJT-X 2.4 offers no support for two nonstandard callsigns to work each other." this is why you are having issues.

73
Bill
G4WJS.

The only link in reply or forward. I everyone’s email, up to over a 100 a day.

Get Outlook for iOS

From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of William Smith <w_smith@...>
Sent: Tuesday, September 7, 2021 6:40:00 AM
To: main@wsjtx.groups.io <main@WSJTX.groups.io>
Subject: Re: [WSJTX] #Compound Call Signs #issue

At the bottom of every single email sent to this list are links for unsubscribing, muting topics, etc.

> On Sep 7, 2021, at 6:37 AM, Jim-KM4JSI <KM4JSI@...> wrote:
>
> Take me off this email list please.
> […]
>
>
>

The attachment doesn’t work

Get Outlook for iOS

From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of Jim-KM4JSI via groups.io <KM4JSI@...>
Sent: Tuesday, September 7, 2021 6:46:29 AM
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Subject: Re: [WSJTX] #Compound Call Signs #issue

Unsubscribe: https://WSJTX.groups.io/g/main/leave/???

We have groups.io with our ham club and I can control my account there. Here I ask a question now I am getting everyone’s email related to WSJTX, and I end up fix it myself.

Get Outlook for iOS

From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of Jim-KM4JSI via groups.io <KM4JSI@...>
Sent: Tuesday, September 7, 2021 6:48:08 AM
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Subject: Re: [WSJTX] #Compound Call Signs #issue

Chuck Moore

• All Messages By This Member

Reino Talarmo

• All Messages By This Member

From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of Jim-KM4JSI via groups.io <KM4JSI@...>
Sent: Tuesday, September 7, 2021 6:48:08 AM
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Subject: Re: [WSJTX] #Compound Call Signs #issue