 GNet BB0060B vs 'DMT v2.20' capture (2009-Jul-20) |
Hi TilHasBB,
I guess you may not have noticed this but the ST546v6 records
made using 'DMT v7.35' are over one year and a half old as it
was done during the 2007-2008 winter. My phone-line has some
different characteristics now because i've moved to another city
one year ago (in July 2008). My measuring method has changed
as well since i no longer trust single 'DMT' readings, even if there
was only one "reset" event as displayed on additional captures.
This month's records show that the Error Rate counter doesn't
represent the situation accurately at all times. For example, the
evening of July 10 was real "quiet" while the early morning of
July 9 proved to be extremely "noisy". The same is true of my DS
SNR Margin level which varied somewhere between 4 and 7.5 dB.
Consequently, it seemed to me that one reasonable solution was
to use six-days "averaged" curves for my late comparison. It's a
time-consuming process but i no longer have to worry because
of marginal events which might corrupt my captures otherwise.

If i follow that same logic, the 'DMT' spectral response shown
in a capture will vary as a function of the date and time when
it was taken. This could give rise to a stimulating project but
the SpreadSheet averaging work involved can be overwhelming.
I'm inclosing a 'DMT' capture of my un-tweaked GNet BB0060B,
i put it on-line around 20:30 last night and looking at it you'll
see what i mean by "variations": it's like i've moved elsewhere!
I'm now trying to imagine a way to shield my damned drop-line,
actually: it seems it keeps degrading while i keep cleaning it up!

In any case, to answer your questions, there's an RF Choke on
every transformer used by my MoDems already. There's a strong
AM station around here (CHRC 800 KHz), i'll try to find out if RF
Choking as a significant effect on the corresponding bins...
...stay tuned...
