From www.AA6E.net
Jump to: navigation, search

(12/2/2010)

Today, we did a sequence of tests at increasing power levels on single frequencies in the 80 and then 40M bands. The general pattern is that a low-power (<= 100W) transmission causes a narrow (possibly single tone) range of tones to be swapped. After the swap (causing a narrow notch in the bitloading graph), another 30 sec transmission at 100W was enough to cause CRC errors and loss of RG sync. After the RG comes back, the bitloading graph shows a drastic change has occurred. The entire 80M band has been swapped out, and tones in the downstream 2 segment are allocated. Afterwards. even high-power operation may cause low to moderate FEC rates, but no further loss of sync is seen.

The same progression is seen with 40M tests. Low power works OK and adapts "gently" by reassigning one or a small number of tone channels. High power is likely to cause loss of sync, followed by a large swath of the download 2 tones being reassigned to the download 1 range. The former 80M gap is reclaimed. After the 40M resync, the number of reserve bits is reduced to ~1,000 from ~2,400 (on RG reset) and "bits in use" is increased to ~84.5% from ~69.9%. Max. downstream rate decreases to 28,486 kb/s from 34,640 kb/s. (The "recommended profile" drops to 19/2 from 25/2.)

Initial Bitloading plot, after RG reset but before any transmissions. (Left yellow area is "download 1" tone group. Green area is "upload" tone group. Right hand yellow is "download 2" tone group.) Bitloading-2010-12-02-20-12-55.png

After 20W 5-10 minute QSO, 3543 kHz, FEC > 100,000 errors/min, no CRC errors. Note narrow slot at 3543 kHz. Bitloading-2010-12-02-20-26-16.png

After 100W, 30 second carrier, high FEC, CRC --> RG lost sync. Note large gap around 80M ham band. Bitloading-2010-12-02-20-31-59.png

After 185W 30 sec. (tune), FEC = 0. Note change at ~3.3 MHz. Bitloading-2010-12-02-20-40-31.png

After 500W, 30 sec., FEC ~ 51,000. No major changes. Bitloading-2010-12-02-20-57-18.png

After 800W 30 second xmsn, high FEC/CRC -> lost sync. Region around 40M is zapped, with bit loading moving down to the 80M region. Bitloading-2010-12-02-21-15-48.png