Excellent report, Bruce. Thanks for posting.One of those 22 m carriers may well have been EH, but the other was probably not RY (unless your attention span is shorter than 12 seconds, which I don't believe :). Here's how to tell that it wasn't.
Recall that QRSS is not a mode of operation itself, but is kind of an umbrella term that covers a variety of modes and protocols, so long as they (a) are being sent at a VERY slow symbol rate ...seconds per bit, typically, rather than the other way around... and (b) are intended to be decoded readily by eye if viewed on a waterfall display having a similarly slow rate. When we specify "QRSSn" in a beacon listing, that's a way of suggesting a set of viewing parameters to optimize changes of seeing whatever is being sent, be it CW, slow FSK, DFCW, Hellschreiber, or other graphical mode such as NC's squarewave. If no specific mode is described, assume CW--or else something so utterly unworldly that it's too hard to put into words. ;)
A QRSS3 setting in Argo, for instance, constitutes a "matched filter" in terms of FFT bin width, integration time, windowing, etc., to visually display any type of signal which changes its amplitude or frequency, or both, at a multiple of three seconds. (QRSS10 for 10 second modulating intervals, QRSS60 for 60 s, etc.) It displays ONLY amplitude and frequency regardless of the signal type, and makes no attempt to decode anything, leaving that to the observer's eye or to other software, if any.
One fairly self-evident example of QRSS3 is ordinary on-off keyed Morse CW being sent with a dot length of 3 seconds...and by definition, inter-element spacing also 3 s, dash and inter-character spacing of 9 s each, etc. In "plain Jane" CW QRSS, you can copy by timing out the elements -if- they're strong enough to be audible anyway.
For other slow modes, it's harder to tell who's who by ear alone. In FSK Morse CW QRSS3 (such as EH) the carrier rises a very few Hz when keyed, but never shuts off during transmission! Unless you have perfect absolute pitch, run at a very low BFO frequency, and/or the sender is wasting bandwidth with excessive Δf, you'll never detect or decode it by ear. Either carrier that stayed on continuously could be EH, therefore, but statistically the upper one is more likely at this time of year.
As for the DFSK used at RY (dual frequency shift keying; invented by Reginald Fessenden as part of a frequency hopping cryptographic technique, but a great time-saver when running unencrypted), that one employs only one 3-second interval per dot -or- dash element, the frequency being varied by a few Hz to signify which it is. Like FSK, you normally won't hear the difference in pitch, but the carrier shuts off between characters and words. (Some ops also drop carrier for a fraction of a second between individual elements, creating a small blip in the display to indicate the correct timing, so that multiple dots or dashes in a row do not merely look like an oversized dash to the eye.) John's "RY" therefore would sound as nine seconds [mostly] on, three off, 12 [mostly] on, then off again until the next ID. The mystery signal not turning off after 12 seconds, tops, is what tells you it's not RY.
On 22 m I always find it the most fun to simultaneously listen by ear and watch Argo. You never know what you'll encounter.
John