Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+OPERA\s+and\s+QRS\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LF\:\s+OPERA\s+and\s+QRS\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: LF: OPERA and QRS (score: 1): Author: qrss <[email protected]>; Date: Wed, 01 Feb 2012 11:07:17 +0000; Thanks for responses. I have clipped the wings of the FANT0M for a try anyway, now QRS1.024 73 Eddie How about comparing like for like in the timing of Data Bits, OPERA uses digital techniques and no; /rsgb_lf_group-archives/html/rsgb_lf_group/2012-02/msg00023.html (9,406 bytes)
2. LF: OPERA and QRS (score: 1): Author: qrss <[email protected]>; Date: Wed, 01 Feb 2012 10:20:44 +0000; We all seem to have agreed to compare OPERA with a QRS speed which takes the same time to send a call sign, correct or not? A QRS beacon can send the call continuously all day and successive periods; /rsgb_lf_group-archives/html/rsgb_lf_group/2012-02/msg00192.html (8,735 bytes)
3. Re: LF: OPERA and QRS (score: 1): Author: Andy Talbot <[email protected]>; Date: Wed, 1 Feb 2012 10:40:46 +0000; Ah, now you're into the realms of soft decision decoding. How does the brain interpret a faulty QRSS symbol? Or a faulty callsign? Do you see the callsign of a well know LF operator if the gap betwee; /rsgb_lf_group-archives/html/rsgb_lf_group/2012-02/msg00521.html (11,058 bytes)

Current List: 1 - 3
Page: [1]