A few days ago I came across some transmissions that caught my attention for at least three good reasons:
1. the frequency used, i.e. 7312.7 KHz/USB, within the 42 meter broadcast band;
2. the use of different traffic waveforms, ie PSK8 serial Tone and STANAG-4539, in ARQ and non-ARQ modes. The ARQ mode is easily recognizable by the difference between the frequencies of the subcarriers (around 50Hz) of data and ACK segments (1);
| Fig. 1 - different traffic waveforms |
3. the use of a waveform composed of GMFSK-2000Bd + MFSK8 for the link setup procedure (Figure 2): as far as I know, this particular waveform is used by both Thales and Harris. Notice that the MFSK8 part is 188-141A compatible (125Bd & 250Hz separation between the 8 tones) but use a diferrent tone library.
| Fig. 2 - GMFSK + MSK8 link setup waveform |
Figure 3 shows the 8-ary constellation (states and transitions) as well as the rasters of the two PSK8 modulated waveforms A and B. In the phase states, and especially looking at the transitions, one can easily notice the presence of a PSK2 modulation which is certainly used for the synchronization sequences visible in the bitmaps below. As usual, the resulting PSK2 symbols are then mapped and scrambled to appear, on-air, as a PSK8 costellation. Bot the the waveforms have an ACF of 106.6 ms that makes a 256 PSK8 symbols frame at the modulation rate of 2400Bd. However, although of the same length, two different framings are adopted, in particular the Type B waveform uses a framing similar in composition to that of STANAG-4285.
| Fig. 3 - constellation and bitmaps of the PSK8 Serial Tone waveform |
| Fig. 4 - PSK8 ST type "A" waveform: demodulated bitstream |
![]() |
| Fig. 5 - sync sequence symbols, PSK8 type "A" waveform |
![]() |
| Fig. 6 - sync sequence symbols, PSK8 type "B" waveform |
![]() |
| Fig. 7 - sync sequence symbols, PSK8 type "B" and "A" waveforms |
![]() |
| Fig. 8 - comparison between sync sequences of PSK8 Type "B" and STANAG-4285 |
STANAG-4539
As per STANAG-4539, both the QAM16 and PSK8 waveforms have the same 287-symbol framing (119.6ms ACF, 2400Bd) although the user data rate is different: 6400bps and 3200bps respectively for QAM16 and PSK8.
| Fig. 9 - constellations and bitmaps of STANAG-4539 QAM16 and PSK8 waveforms |
Figure 10 shows a detail of a bitstream obtained after removing the S-4539 QAM16 overhead and consists of 96-byte (768 bits) Protocol Data Units (PDUs), each PDU consisting of 3 bytes header followed by 93 bytes of data:
1st byte: a ID/value field, in this sample: 0x09 (LSB first)
2nd byte: down-counter field (LSB first)
3rd byte: up-counter field (LSB first)
As one can see looking at the values of the two counters in Figure 10, the sample consists of 55 PDUs, numbered from 0 (00000000) to 54 (00110110).
| Fig. 10 - headers and part fo bitstream after S-4539 QAM16 decoding |
It's worth noting that that patterns highlighted in the bitstream of Figure 4 (and the bitmaps of Figure 3) are most likely the two counter fields of Figure 11: if so, both tPSK8 ST and S-4539 traffic waveform transport the same datalink PDUs.
bytes 1-3: a ID/value field, [001111001111000001001111] 0x3CF04 (LSB first)
4th byte: up-counter field (LSB first)
| Fig. 12 - the emerging "secondary" datalink protocol PDUs |
This may be a hasty statement, but it seems that the "secondary" datalink protocol PDUs > 16 bytes length are fragmented into small segments and then incapsulated into the 45/95 bytes payload of the "primary" datalink protocol PDUs. By the way, at least in these samples, the "secondary" PDUs have been found only in the primary PDUs which have the first byte of the hedaer equal to 0x48, maybe just a mere coincidence (Figure 13,14).
| Fig. 13 |
![]() |
| Fig. 14 |
Since the lack of clear-text callsigns it's impossible to id the user, we may speculate just some guess about the manufacturer of the used devices:
![]() |
| L3Harris typical pattern in GMFSK-MFSK8 signals |
![]() |
| L3Harris VD mode bitstream |
(3) SA is a signal analyzer and not a decoder, therefore its phase-plane demodulator does not sync any particular protocol, as it happens for example in STANAG-4285 "suited" decoders. Working with phase keyed signals, the SA phane-plane demodulator produces right interpretations and views (number of phases, angles, modulation speed, carrier frequency,...) but it may return wrong demodulated streams due to the possible phase-offset errors.







