how-to block ads
|
|  
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
 ·AT&T Midwest
2 edits | Re: Any 5100b technician page DMT/SNR data experts? Let me add some history. The 3.0/512 Pro profile as shown above worked for all of April 2005. Starting May 1, 2005, the line would lose sync twice a weekday. During the problem period, the line mysteriously grows 2000-4000 feet in length according to the DSLAM.
Recently, SBC has tried to solve the problem shown above by switching me to a replacement pair of wires, that exhibits the same problem I described in the earlier part of this thread.
The latest resolution was to switch me from the 1.5Mb/384 profile to 768/384. So far this weekend, the line hasn't lost sync at the lower speed, but it does exhibit what I believe to be amazingly similar graphs when compared to the same kind of graphs I was seeing at 3.0/512 profile speeds. Notice how the nice stair-step DMT graph goes into a jagged lower-quality signal during the problem?
Here's the line as it looks just before the problem.
Here's the line as it looks during the problem.
Here's the line quality after I power cycled the modem a short while later. (It stays looking basically like this from 1pm til 6am the next morning.)
Does anyone have any expert knowledge on the SNR/DMT values/graphs I'm getting from my 5100b?
By the way, I have QuickTime movies of the problem drawn graphically for the last 16 days.
Thanks,
--justbits | |
| joewho
Premium
join:2004-08-20
Las Vegas, NV
2 edits | I'm not an expert, but until someone arrives with a better answer.....
I can tell you that the first read out shows 0.0 snr, which means that there is no signal to noise margin.
The second graph shows a snr of 13 which is perfectly acceptable.
This means that there is noise on the line. Something that could possibly be corrected by you. No guarantee, but in order for sbc to zero in on the problem, they will probably ask you to check your set up from the nid to the inside wiring. To do this, the first thing you'll want to do is find a way to plug the modem in directly to the nid (gray box mounted outside, usually near the electric meter).
Just run a line fromt the modem to the nid. Unplug the phone wire, and plug in the modem. Check the stats and post them here.
This is a good start, I'm sure someone else with more expertise will reply soon. Good luck.
PS: Also, if you have a router, eliminate it from the setup temorarily. When you run the modem to the nid, also run it to the computer directly.
--
we're all connected | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts?said by joewho  :I'm not an expert, but until someone arrives with a better answer..... I can tell you that the first read out shows 0.0 snr, which means that there is no signal to noise margin. I gotta admit that I edited that. The 5100b modem reports erroneous SNRM when the signal to noise ratio goes off the scale. Notice the 126.0 and 127.0 samples in the SNRM Carrier Frequency data. It actually recorded an insanely large value for the SNRM (2147483646.0) that I replaced with 0.0 since it was unable to correctly calculate the SNRM. I figured 0.0 made more sense than an insanely large value due to the modem miscalculating the SNRM.
said by joewho :The second graph shows a snr of 13 which is perfectly acceptable. This means that there is noise on the line. Something that could possibly be corrected by you. No guarantee, but in order for sbc to zero in on the problem, they will probably ask you to check your set up from the nid to the inside wiring. To do this, the first thing you'll want to do is find a way to plug the modem in directly to the nid (gray box mounted outside, usually near the electric meter). Been there, done that.
I have a "Home Run". It's a known-good 8 foot CAT 5 cable going directly from the NID into a microfilter, split directly into the modem and 1 telephone.
I have tried 4 different modems. They all saw the loss of DSL sync problem. The last DSL sync time is on the graph. For the first failure case, the line dropped syn 26 minutes earlier. After 30 minutes of signals that looked poor and jagged like the first chart, the problem disappeared as the second chart showed.
I also literally turned off every electronic component in my house and disconnected the POTS telephone. The problem still occurred.
said by joewho :Just run a line fromt the modem to the nid. Unplug the phone wire, and plug in the modem. Check the stats and post them here. That's a "Home Run". That is exactly what I've been doing for the last 16 days.
said by joewho :This is a good start, I'm sure someone else with more expertise will reply soon. Good luck. PS: Also, if you have a router, eliminate it from the setup temorarily. When you run the modem to the nid, also run it to the computer directly. This isn't a Internet routing problem. The DSL modem loses sync during the problem period. The modem records a loss of sync.
For the first problem shown, the modem logged this:
2005/06/02 07:45:00
32 Time Since Last Sync 000 days 00:26:35
+001 days 22:44:12 E |DSL |Link Down
+001 days 22:44:12 E |DSL |State: WAITING
+001 days 22:44:20 E |DSL |State: INITIALIZING
+001 days 22:44:27 E |DSL |HYBRID 1
+001 days 22:44:27 E |DSL |Link up 17 US 512 DS 2464 (FAST:G.dmt)
Right before the problem occurred, I recored this:
2005/06/02 07:15:00
32 Time Since Last Sync 000 days 10:55:59
140 Current Rate 2496 512
141 Previous Rate 2432000 672000
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 2496 -
145 Current SNRM 14.0 -
146 Current LATN - -
147 Current SATN 53.0 -
148 Current TP - 0.0
Right afterwards:
32 Time Since Last Sync 000 days 00:01:40
140 Current Rate 2464 512
141 Previous Rate 2496000 672000
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 2464 -
145 Current SNRM 0.0 -
146 Current LATN - -
147 Current SATN 55.0 -
148 Current TP - 0.0
Does anyone know how to calculate Maximum Attainable Rate from the SNRM/DMT bit bin data? Are there any other interesting values I can calculate from these two hunks of data?
--justbits | |
| | | swflutka
join:2003-01-30
Griffith, IN
clubs: | Re: Any 5100b technician page DMT/SNR data experts? One thing that I see is that your modem is synced at 2464/512. Did you have them bump you back up or did they never reduce your sync to 768/364. Have you tried getting set to an interleaved profile? | |
| | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts? said by swflutka :One thing that I see is that your modem is synced at 2464/512. Did you have them bump you back up or did they never reduce your sync to 768/364. Have you tried getting set to an interleaved profile? Before I had a home run, the best the modem could do was 2464/512. After the homerun, I could do 3000/512. A temporary solution to the problem was to see if the problem still occurred at 2464/512 after the homerun was in place. It still did. Over time, the modem was daily syncing at slower speeds. It started at 2.6/512, then 2.4/512, then 2.0/512, then 1.9/512, then 1.8/512. For a while, it wouldn't sync higher than 1.8/512 unless I rebooted the 5360 modem.
An interleaved profile was tried. 1.5/384 INTL:G.dmt. Ping times went from 11ms to 54ms. The problem still occurred.
Here's some more history.
The problem occurs with 5100b firmware 1.0.0.36 and 1.0.0.39.
There are no remote terminals. I've been told that no RT is planned so it's not like they're in the middle of cutting in a RT.
The SBC provided Speedstream 5360 would fail to sync for the entire 30-45 minute duration that the failure was occurring. I think the problem duration is exactly 30 or 45 minutes. A SBC 5100b 5100b I borrowed from my brother drops sync, but then is able to resync 30 seconds to 5 minutes later at a lower sync rate. After the problem is over, the 5360 and 5100b were able to sync at full speed. To clear up the "jagged lines" graphs, all I have to do is power cycle the modem or force the modem to resync.
--justbits | |
| 
AlEinstein
join:2004-10-08
Hughson, CA
| Bits,
If your graphs are correct, you should not have the "holes" in the graph. The left "hump"(horizontally short)is your upstream and the right "hump" (horizontally long)is your downstream. Each graph you posted, except the first, report "holes" or slices in the downstream portion. On the graph they are the white "slices" where the red is missing so to speak. The overall shape looks decent. But the holes show trouble. 1 skinny one is sometimes OK, but you show more, and one of the graphs is just full of spikes. Spikes are ugly.
Are you CO or RT fed? Just curious. You may have said already.
According to your post, its good that you went right to the nid, homerun with the cat5 etc.
Any reply from posting to Direct? Probably have to wait till Monday morning I guess. Definitely will get some good analysis from those guys on your modem log and graphs.
The bottom line is, assuming outside trouble, (which I think is safe to do in this case) is to have a trouble ticket opened so a tech can dispatch and confirm bits graph holes and monitor the line with his/her test set etc and justify opening a trouble ticket to the line techs to find a pair thats not reflecting these holes and any other issues the tech may find. It may require a vendor meet too, just heads up.
Last thought, the 2Wire modems are great for analysis and troubleshooting. They give max attainable unlike the B modems. Hopefully Efficient will provide a firmware upgrade or the like to add that feature to an otherwise great modem in the B. | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts AlEinstein,
I am CO fed. No RT.
After having 3 horrible experiences with having to go through the same "script" with tier 1 tech support, I started reporting all information on the problem to a thread in SBC Direct. It's 5 pages long and detailed.
»[TROUBLE] Speed drop from 2400/443 to 1500/443
There have been 7 ASI trouble tickets so far. A bunch of them were closed with a simple resolution unrelated to the problem.
First visit by ASI: found two bridge taps.
Second visit by Ameritech: couldn't remove bridge tap due to satellite dish on telephone pole. See:
»OT: Satellite dish attached to utility pole?
And:
»Satellite dish on public utility pole? (part 2)
Another visit by Ameritech: Supposedly they came and removed the bridge tap(s).
Third visit by ASI: Saw a really noisy line. Still saw bridge taps. Said that DSLAM was estimating the line at 14,000 feet when in March it was estimated at 9,900 feet. The weather & temperature and humidity were pretty much the same from March until the middle of May. It's not a weather issue.
Fourth visit by Ameritech: Blamed inside wiring, even with a home run installed!
Fifth visit by ASI and Ameritech (last Monday): went through wire bundle and found a replacement pair of wire. Had to go through a bunch of pairs before finding a pair of wires that looked like it could support Pro package. Same problem occurs. This line fails even worse ... when the problem occurred on Tuesday, it couldn't even hold 784/384 and had to be forced to 384/384 to keep sync. With the line forced to 784/384, Friday and Saturday and Sunday no loss of sync occurred, but the intermittent high levels of noise (jagged/spikey graphs) still exist at approximately the same times that they have occurred in the past. We'll see if it doesn't lose sync today or tomorrow.
I think I missed a visit in there... oh wait! They did.  Last Friday, ASI was supposed to show up on-site, but missed the appointment because it was scheduled for 2008, not 2005.
I've seen people quote the Maximum attainable rate by looking at the technician data. There's gotta be a way to calculate/estimate it.
I've been trying to work with the 5100b's hidden XML interface to see if it isn't disabled in the XML interface, but am having no luck. If anyone knows anything about the 5100b XML interface, send me an IM.
--justbits | |
| | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
1 edit | Re: Any 5100b technician page DMT/SNR data experts?I don't believe I am near any AM transmitters.
Someone said that a T1 that's active could cause this kind of interference. I've doubted that all along. But, when there's supposedly "9 T1s in the same wire bundle as your pair", I suppose that sounds plausible, but the harmonic frequency interference doesn't seem to indicate T1 interference, does it?
I started noticing the problem on May 1st. It may have been going on significantly earlier than that start date. It may have been going on as early as September/October of 2004. I do recall connections dropping in the morning as far back as then, but I thought it was due to a faulty T1 modem that we had put in at my workplace 20 miles away from my residence (because I was working offsite at a customer 40 miles away from home & work using SSH tunnels within a SSH tunnel.)
I web surf every day, but May 1st was the first time that DSL was down for 30+ minutes. May 8th was the second time, which is when I really started to keep a log of the problem.
Basically, from August 2004 til May 2005, I was working at a remote site every day and using my workplace T1 as a tunnelling entry point. Since May 1, 2005, I've been relying on my home DSL as a tunnelling entry point. In the past, I would do frequent Saturday morning web surfing, but I never noticed a loss of DSL sync.
Here's a log that I've been keeping. Times in the PPPoE log are when the line lost sync. Duration of poor signal is unknown for those log entries.
Times in the 5100b section describe a loss of sync, followed by a period of poor signal. Since my pair replacement on 6/3, and the knocking of the speed down to 768/384, the loss of sync doesn't occur, so I have to reboot the modem nightly in order to clear up to signal so I can see when the problem situation occurs the next morning. If I was in a higher profile (1.5/384) the line would lose sync.
----------- SpeedStream 5360 in use.
----------- Logged loss of pppoe (observed loss of DSL sync):
May 4 08:22:05 firebox pppd[7618]: Connect time 1274.5 minutes.
(Lost log data for May 5 through May 8th)
Mon May 9 07:55:14 firebox pppd[28253]: Connect time 0.4 minutes.
Mon May 9 07:56:58 firebox pppd[28442]: Connect time 0.6 minutes.
Mon May 9 09:39:59 firebox pppd[28870]: Connect time 98.4 minutes.
Mon May 9 10:49:53 firebox pppd[28870]: Connect time 69.8 minutes.
Tue May 10 08:25:52 firebox pppd[31539]: Connect time 1282.7 minutes.
Tue May 10 09:56:11 firebox pppd[13376]: Connect time 1.2 minutes.
Wed May 11 09:18:24 firebox pppd[19720]: Connect time 832.3 minutes.
(Lost log data for May 12th)
Fri May 13 09:41:16 firebox pppd[26561]: Connect time 1.0 minutes.
Sat May 14 08:19:34 firebox pppd[26889]: Connect time 1355.1 minutes.
Sat May 14 11:26:20 firebox pppd[26889]: Connect time 186.8 minutes.
Sat May 14 11:28:16 firebox pppd[26889]: Connect time 1.9 minutes.
Sat May 14 12:56:13 firebox pppd[10098]: Connect time 86.9 minutes.
Sun May 15: no drop.
Mon May 16 07:14:50 firebox pppd[29602]: Connect time 708.5 minutes.
Mon May 16 07:20:23 firebox pppd[4266]: Connect time 5.1 minutes.
Mon May 16 11:01:02 firebox pppd[4545]: Connect time 219.0 minutes.
Mon May 16 11:01:02 firebox pppd[4545]: Connect time 219.0 minutes.
Tue May 17 08:10:06 firebox pppd[6917]: Connect time 1268.1 minutes.
Tue May 17 08:11:14 firebox pppd[19579]: Connect time 0.5 minutes.
Tue May 17 09:07:32 firebox pppd[19874]: Connect time 53.9 minutes.
Tue May 17 09:08:36 firebox pppd[20580]: Connect time 0.4 minutes.
Tue May 17 10:00:18 firebox pppd[20744]: Connect time 51.5 minutes.
Tue May 17 13:24:00 firebox pppd[21460]: Connect time 202.3 minutes.
Tue May 17 13:27:30 firebox pppd[23658]: Connect time 2.2 minutes.
Tue May 17 13:31:02 firebox pppd[23871]: Connect time 2.6 minutes.
Tue May 17 13:46:45 firebox pppd[24055]: Connect time 15.2 minutes.
Wed May 18 09:14:51 firebox pppd[24733]: Connect time 1161.2 minutes.
Thu May 19 07:14:49 firebox pppd[4330]: Connect time 629.7 minutes.
Thu May 19 07:21:04 firebox pppd[17820]: Connect time 1.2 minutes.
Thu May 19 07:30:23 firebox pppd[18336]: Connect time 3.2 minutes.
Thu May 19 08:34:42 firebox pppd[18762]: Connect time 59.5 minutes.
Thu May 19 08:35:48 firebox pppd[19532]: Connect time 0.4 minutes.
Fri May 20 08:47:45 firebox pppd[6201]: Connect time 84.0 minutes.
Sat May 21 09:35:33 firebox pppd[13357]: Connect time 876.7 minutes.
Sun May 22: No drop.
Mon May 23 07:36:41 firebox pppd[22143]: Connect time 2760.7 minutes.
Mon May 23 07:37:51 firebox pppd[22143]: Connect time 1.1 minutes.
Mon May 23 11:34:18 firebox pppd[17408]: Connect time 231.5 minutes.
Tue May 24 07:24:47 firebox pppd[216]: Connect time 1.0 minutes.
------------------------------ 5660 data:
Wed 20050525: 9:50am til 10:30am, 6:30pm til 8:10pm
------------------------------ 5100b graphical data available:
Thu 20050526: 7:20am til 8:10am, 9:20am til 10:05am
Fri 20050527: 7:15am til 7:58:49am, 8:40 til 9:30am
Sat 20050528: 9:15am til 9:50am
Sun 20050529: 11:05am til 11:45am
Mon 20050530: 12:15pm til 12:50pm (Labor Day)
Tue 20050531: 7:35am til 8:25am, 9:10am til 9:15am, 10:00am til 10:50am
Wed 20050601: 9:30am til 10:15am
Thu 20050602: 7:20am til 7:55am (SINUSOIDAL graph), 9:30am til 10:00am
Fri 20050603: 7:50am til 8:20am, 9:30am til 10:10am. (All drops before this point occurred
in the 3.0/512 profile. All drops after this point are in the 1.5/384 profile)
Sat 20050604: ??? Unknown. Lost log data from 11:30am til 2pm Sunday.
(May not have dropped.)
Sun 20050605: Dropped at 11:06am. Not able to regain sync until 11:30am.
Dropped PPPoE connections until 12:03pm. (This failure occurred while in the 1.5/384 prof ile.)
Mon 20050606: Dropped at 8:10am. Bad signal until 9:40am.
Line pair replaced after noon.
Tue 20050607: Dropped at 7:35am. Bad signal until 11:10am.
Wed 20050608: Dropped at 8:15am. Bad signal until 9:05am.
Bad signal 9:20 til 10:00am.
Thu 20050609: Dropped at 9:00am. Ok signal. Strange.
11:15 til 11:40 NO SYNC. 11:45 til 12:00pm poor signal.
Fri 20050610: Strange. No drop.
Sat 20050611: Strange.... no drop... but now I'm knocked down to
786/384! Come on! Reset modem at 11:31pm to clean up the
signal analysis.
Sun 20050612: No drop. Just a poor signal around noon.
As you should see, weekdays are pretty much the same schedule.
Weekends and holidays have a different schedule. Sometimes it doesn't occur at all on the weekend.
--justbits | |
| | |
AlEinstein
join:2004-10-08
Hughson, CA
| Re: Any 5100b technician page DMT/SNR data experts bits,
I'm not very strong on the radio interference thing like some of the guys here are EG RadioDoc etc.
I have had some experience with the T1 and "highcap" interference. 1 time it was solved by moving to a completly differenct "count" and the other time was solved by moving to an RT.
By the sounds of it moving to an RT isn't going to work for you.
If you're in a predominitely residential area then your "F2" lead shouldn't have many if any T1's. You mentions 9 (I think) T1's in your "wire bundle" I take it you've learned that from one or more of your many service calls from either network or asi. My question is, Are the T1's in the F1 lead or the F2 lead?. If they're in the F1 lead than you can definitely get changed to an entirely different "count/group" or "wire bundle" as you put it. Thereby getting away from, potentially, the T1 interference. But...If the T1's are in the F2 feed then your options are quite possibly narrowed. You still may be able to change your counts but there are some dependencies with that.
At the end of the day, you've done an excellent job with your docs and research. Kudos! The flip side is that the situation is what it is, and is difficult to say if there really is a solution. The T1's are definitely higher on the totem pole than the lowly dsl circuit is!  DOOOOH!
Keep up posted | |
| 
armyrebel4
Dream Chaser
Premium
join:2002-01-08
Springfield, IL
·AT&T Midwest
1 edit | This just pops up in my mind what condition is the wire coming up to your house? Is your house ariel fed or is it underground? Because when the techs come out to test your interface box they get a chirping noise on the linemans phone when there is dsl active on the line.
When the ASI Tech or the POTS Tech(your not RT fed) comes out to your house they do a signal strength test on the line. Then they get a whole slew of readouts.
If that dish is causing your rf frequency the wire is not shielded and the way they installed that dish is against state law. I bet you it's that box that picks up the signal for the dish. | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts? I am fed by ariel wire feed. That ariel feed has not been replaced in about 3 years.
Sometime this week, I'll be replacing the ground wire running to my chimney antenna. I'll also try disconnecting the TV antenna from the house electronics if I'm around when the problem occurs.
I don't get good cell reception in spots in my back yard where I can't see the cell tower. When I'm in line-of-sight, I get good reception. It's about 1000 feet away and on top of an apartment complex. The NID is not within line of sight with the cell tower.
--justbits | |
|
AlEinstein
join:2004-10-08
Hughson, CA
| bits,
just thought of one more thing.
Has network ever changed out your "protector" (lightning/power surge fuse) in the nid? Sometime these cause trouble and can't really be picked up on the test set except for by a trained eye and even then can easily be missed or not picked up by the test set.
This should be replaced just for good measure. Its on the network side of the nid/dmarc and can be accessed by either tech, network or asi. Technically its the networks techs job to test/replace it, but they're not always alert to this type of problem and since its on the network side of the nid, asi isn't always aware of this issue either. Basically it can be faulty (albeit slightly) and pass dial tone no problem but will mess with the DSL sig.
Please don't ask how I know this! Just ask one of the techs to change it for a new one for grins and giggles, NO ONE is out anything by doing it.
Also, a 3 year old aerial service wire is pretty darn new unless there is damage from storms or critters.
FYI
BTW, if your entire nid has been changed, very recently, during your whole trouble experience that is, then these protectors come new with the nid. | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts The lightning strike protector hasn't been changed as far as I know.
The NID has not been replaced since it was first installed in 2001. (For Rhythms Telocity service. I had 784/784 SDSL once upon a time.)
Since I started reading 5100b data, the modem has never been able to squeeze any DMT bits in sample 64 nor around sample 130. (Take a look at the charts I previously posted. Is that normal?
--justbits | |
| | | | | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data expertsHere's an example of the data as the problem was occurring this morning. I was screwing around with the wires this morning before 8:00am. The wiring hasn't changed since then. I thought I'd provide 4 samples. (I have samples for every 60 seconds this morning.)
7:25am (during problem period) (v1.0.0.39)
8:00am (during problem period - after replugging some wires)
10:10am (after problem period)
10:20am (after rebooting the modem)
During the problem : 20050616/072500.txt
CRC Errors 2 5
32 Time Since Last Sync 000 days 00:07:55
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 7.5 -
146 Current LATN - -
147 Current SATN 58.5 -
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 16.0 16.5 15.5 16.0 16.0 14.5 16.0 16.0 9.5
333d
15.0 16.0 15.5 9.0 16.5 16.5 14.0 13.0 16.5 16.5 15.0 16.5 16.5 16.5 16.5 16.5
333e
0.0 15.0 15.0 16.0 16.0 8.0 15.5 15.0 12.5 7.0 14.0 13.5 8.0 9.5 14.0 15.0
333f
12.5 15.5 15.5 15.0 13.0 15.5 15.5 13.0 15.0 16.0 16.0 12.0 16.0 15.5 12.5 11.0
333g
15.5 16.0 11.5 15.5 16.0 16.0 15.5 16.0 16.0 16.0 16.0 16.0 16.0 15.5 16.0 16.0
333h
17.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.0 16.0 16.0 16.0 16.0 0.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 4 4 4 5 5 6 6 6 6
334b
6 7 7 7 7 7 6 6 6 5 5 5 4 4 0 0
334c
0 0 0 0 0 0 8 8 9 9 9 9 9 9 9 9
334d
9 9 9 9 9 9 9 8 8 8 8 8 7 7 7 7
334e
0 7 6 6 6 6 6 5 5 4 5 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
334g
4 5 5 5 4 4 4 4 4 4 4 4 4 3 4 3
334h
2 2 2 2 2 2 2 2 2 2 2 2 2 0 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
During the problem : 20050616/080000.txt
CRC Errors 2 5
Rx Tx
32 Time Since Last Sync 000 days 00:05:00
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 15.5 -
146 Current LATN - -
147 Current SATN 59.5 -
148 Current TP - 0.0
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 17.5 20.5 17.5 18.0 18.5 21.0 17.5 17.5 21.0
333d
17.0 16.5 17.0 23.0 16.5 17.0 19.0 19.5 17.0 16.5 19.0 16.5 16.5 16.5 16.5 16.5
333e
0.0 19.0 19.0 17.0 16.5 23.5 16.5 16.5 18.0 27.0 17.5 19.0 25.5 19.0 17.5 17.0
333f
25.0 15.5 17.0 18.0 20.5 17.0 17.0 19.5 18.0 16.5 16.5 20.5 16.5 16.5 19.0 20.0
333g
16.5 17.0 23.5 17.0 16.0 16.0 18.5 16.0 16.0 16.5 16.5 16.0 16.0 16.5 16.0 16.0
333h
16.0 16.0 16.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 16.0 0.0 0.0 16.0 16.0 16.5 16.0 16.5 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 6 6 6 6
334b
7 7 7 7 7 7 6 6 5 5 5 5 5 4 0 0
334c
0 0 0 0 0 0 8 9 9 9 9 9 8 10 10 8
334d
10 10 9 8 9 9 8 8 8 8 8 8 8 8 7 7
334e
0 6 6 6 6 4 6 5 5 2 5 4 2 3 5 5
334f
2 5 5 4 4 5 5 4 5 5 5 4 5 5 5 4
334g
5 5 2 5 5 5 3 4 4 4 4 4 4 4 4 4
334h
3 3 3 2 2 2 2 2 2 2 2 2 2 2 2 0
334i
0 0 0 0 0 2 0 0 2 2 2 2 2 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
After the problem : 20050616/101000.txt
CRC Errors 3 5
32 Time Since Last Sync 000 days 02:14:34
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 14.5 -
146 Current LATN - -
147 Current SATN 59.5 -
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 14.5 15.0 16.0 15.5 15.5 14.5 15.0 16.0 15.5 16.0
333d
15.0 16.0 16.5 18.5 16.5 16.5 16.5 15.5 16.5 16.5 14.5 16.0 16.5 16.5 16.5 16.5
333e
0.0 16.0 17.0 16.5 16.0 14.5 16.0 16.5 15.5 16.5 16.5 18.0 19.0 17.0 17.0 16.5
333f
15.5 15.0 16.0 14.5 14.5 15.5 16.5 17.5 16.5 16.0 16.0 16.5 15.0 15.5 15.0 15.5
333g
15.5 15.5 17.5 16.0 15.5 16.0 17.5 16.0 16.0 15.5 15.5 15.5 15.5 15.0 16.0 16.0
333h
16.0 16.0 16.0 17.0 16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 16.0 0.0 0.0 16.0 16.0 0.0 16.0 17.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 6 6 6 6
334b
7 7 7 7 7 7 6 6 5 5 5 5 5 4 0 0
334c
0 0 0 0 0 0 8 9 9 9 9 9 8 10 10 8
334d
10 10 9 8 9 9 8 8 8 8 8 8 8 8 7 7
334e
0 6 6 6 6 3 6 5 5 2 5 4 4 3 5 5
334f
2 5 5 4 4 5 5 4 5 5 5 5 5 5 5 4
334g
5 5 2 5 5 5 3 4 4 4 4 4 4 4 4 4
334h
3 3 3 2 2 2 2 2 2 2 2 2 2 2 2 0
334i
0 0 0 0 0 2 0 0 2 2 0 2 2 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
After rebooting the modem a few minutes later:
20050615/102000.txt
CRC Errors 2 5
32 Time Since Last Sync 000 days 00:00:43
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 16.0 -
146 Current LATN - -
147 Current SATN 59.5 -
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 17.0 17.0 17.0 17.0 17.0 17.0 17.5 17.0 17.0 17.0
333d
17.0 17.0 17.0 17.0 17.0 17.0 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.0 16.5 16.5
333e
0.0 16.0 16.5 16.0 16.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5
333f
16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333g
16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5
333h
16.0 16.0 16.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 16.0 16.0 16.0 16.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 4 4 4 5 5 5 6 6 6
334b
6 7 7 7 7 7 6 6 6 5 5 5 5 4 0 0
334c
0 0 0 0 0 0 4 5 6 6 7 7 8 8 8 8
334d
9 9 9 9 9 9 9 9 8 8 8 8 8 7 7 7
334e
0 7 7 6 6 6 6 6 6 6 5 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
334g
5 5 5 5 5 4 4 4 4 4 4 4 4 3 3 3
334h
3 3 3 2 2 2 2 2 2 2 2 2 2 2 2 2
334i
0 0 0 0 0 0 0 0 2 2 2 2 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
I might be seeing coorelating trends in ECL and CVL. What do those stand for?
--justbits | |
| | | | | | | | | | |
armyrebel4
Dream Chaser
Premium
join:2002-01-08
Springfield, IL
·AT&T Midwest
4 edits | Re: Any 5100b technician page DMT/SNR data experts This one has me puzzled, SNR went up which is good. Attenuation is maxing out, which means signal loss but I had it maxed out at 60 and was getting good dsl.
Dish is removed.
Call pots repair and have them test the line.
Only thing I can think of is your line could be crossed, when your on the phone do you hear people in the background? Any echos? Scratching noise? (From the NID test outlet.)
If they switched the pairs that many times, I don't know what else to say. | |
| | | | | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL | Re: Any 5100b technician page DMT/SNR data experts I've only had pairs switched once, but it took a few tries for them to find a "good" pair.
I'll try just hooking up the phone and making calls during the problem period if I can. | |
| | | | | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
3 edits | This is just subjective, til I can provide recordings, but I believe I can hear noise at any time of day.
But, during the problem, the noise goes from being constant to getting louder and quieter every 30+ seconds, I think.
It's hard to keep your thoughts when you're punching digits on the phone trying to keep the line clear of dial tone or "cannot complete your call as dialed" messages.
I have some recordings, but I don't have time to clean them up or isolate the noise I'm hearing today.
I don't hear other people in the background. I didn't place any calls. I was just lifting the receiver and dialing 1-2-3-4-5-6-7 about 3 seconds apart.
I have a CAT 5 cable running from the NID into the telephone during the tests. If I were to do this test outside, the airplanes from O'Hare airport flying overhead would drown out any noise I might be able to hear myself.
telcotech: I didn't get a chance to ground the extra CAT 5 wires yet. I'll rewire the cable tonight.
By the way, here's a movie of what happened this morning.
Before 8am and after 9am, the signal looks basicly exactly the same. Around 7am, I can see a ramp-up period where the lowest download bit bins start lowering in SNR. This happens every day before the problem occurs. Sometimes, the SNR lowers, then it starts going way high and then the SNR graph goes jagged.
The DSL modem was not on all night. I still heard line noise this morning.
From 7am til 8am I was goofing around with the cables and doing recordings of just the POTS side of the world. The data from 7am til 8am will probably not be much use. The 8-9 data is kinda interesting and shows the noise I had before still exists.
Just to reitterate, the line is "clean" and produces a nice stairstep/plateau graph except for every weekday morning between 7-10am for a 30-45 minute interval.
 51002005061708.zip 789871 bytes
(51002005061708.mov)
--justbits
Edited for clarity of the last two sentences.
Added that it occurs for 30-45 minutes each time. | |
| | | | | | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts Just a random comment... I'm pretty sure my wires run under or over train tracks. Take a look at the CO and you can see that just north of Grand Ave is a set of train tracks.
»maps.google.com/maps?ll=41.92913···=k&hl=en
Is it possible that a diesel locomotive (that uses electric motors) is idling near enough to the wire group/count/bundle and that it could be causing excessive noise at a particular repeating schedule each day? What schedule do freight train opperators usually follow?
It seems plausible that if the train operator or idling procedure changed recently, they could be idling at a different spot since Friday last week.
--justbits | |
| | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Here's a summary of what I've been up to.
Last night, I compared 3 different modems data results to see how they all compared.
I have a 5660 (v2.3.0(7)).
I have a 5100b (v1.0.0.44).
I have a ADSL2/2+ diagnostic analyzer capable modem also. (Don't ask.) I'll refer to this as "PRIVATE".
Here's the results of plugging them in and forcing them to resync just a minutes or two apart from eachother.
These data points are to get a relative accuracy of the statistics provided by the different modems.
The line is configured for 1.5/384 Interleaved at this point.
2005/06/15 8:10pm 5100b
SNR: 16.0
ATN: 58.5
DMT: 472 bit bins
20050615/201033.txt
DMT SNR Data
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 17.5 17.5 17.5 17.5 17.0 17.0 17.0 17.0 17.0 17.0
333d
17.0 16.5 16.5 17.0 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5
333e
0.0 16.5 16.5 16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333f
16.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.5 16.0 16.0 16.0 16.0 16.0
333g
16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.5 16.0 16.5 16.0 16.0 16.0 16.0 16.0
333h
16.0 16.0 17.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.0 16.0 16.5 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 6 6 6 6
334b
7 7 7 7 7 7 6 6 6 5 5 5 4 4 0 0
334c
0 0 0 0 0 0 7 8 8 9 9 9 9 9 8 8
334d
8 8 8 8 8 8 8 8 8 8 8 8 7 7 7 7
334e
0 7 7 6 6 6 6 6 6 6 6 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
334g
5 5 5 4 4 4 4 4 4 4 4 4 4 4 3 3
334h
3 3 2 2 2 2 2 2 2 2 2 2 2 2 2 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2005/06/15 8:15pm 5660
Current Attainable Rate 573134 3200000
Current SNR Margin 13.5 16.0
Current Attenuation 59.0 31.5
Current Output Power 4.0 17.5
2005/06/15 8:17pm 5660. Changed some wires and resynced.
Current Attainable Rate 573134 3200000
Current SNR Margin 12.5 16.0
Current Attenuation 58.0 31.5
Current Output Power 4.0 17.5
2005/06/15 8:19pm 5660. Sampled again
Current Attainable Rate 573134 3200000
Current SNR Margin 13.5 16.0
Current Attenuation 58.5 31.5
Current Output Power 4.0 17.5
2005/06/15 8:20pm PRIVATE modem
SNR: 11.4 16.0
ATN: 62.5 31.5
PWR: 3.1 17.5
RAT: 2528 1088
2005/06/15 8:23pm PRIVATE (with noise margin checking)
SNR: 16.0 16.0
ATN: 62.0 31.5
PWR: 3.2 15.5
RAT: 3200 1088
2005/06/15 8:26pm PRIVATE (in ADSL2 diagnostic mode.)
SNR: 16.1 16.0
ATN: 62.0 31.5
PWR: 2.8 15.3
RAT: 3232 1100
2005/06/15 8:45pm PRIVATE (forced resync)
SNR: 16.5 16.0
ATN: 62.0 31.5
PWR: 2.8 14.9
RAT: 3328 1100
2005/06/15 8:56pm PRIVATE (another sample)
SNR: 16.1 16.0
ATN: 62.5 31.5
PWR: 2.9 14.9
RAT: 3328 1096
2005/06/15 9:10pm 5100b
SNR: 16.0
ATN: 58.0
DMT: 472 bits
20050615/211000.txt
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 17.5 17.5 17.5 17.5 17.0 17.0 17.0 17.0 17.0 17.0
333d
17.0 17.0 17.0 17.0 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5
333e
0.0 16.5 16.5 16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333f
16.0 16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.0 16.5 16.0 16.5 16.0
333g
16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5
333h
16.0 16.0 17.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.0 16.0 16.5 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 6 6 6 6
334b
7 7 7 7 7 7 6 6 6 5 5 5 4 4 0 0
334c
0 0 0 0 0 0 7 8 8 9 9 9 9 9 9 9
334d
9 8 8 8 8 8 8 8 8 8 8 7 7 7 7 7
334e
0 7 7 6 6 6 6 6 6 6 6 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 4 5 5 5 5 5 5 5
334g
5 5 5 5 4 4 4 4 4 4 4 4 4 4 3 3
334h
3 3 2 2 2 2 2 2 2 2 2 2 2 2 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
---------------------------------------------------
This morning.
Here's what it looked like after 9 hours.
20050616/070000.txt
32 Time Since Last Sync 000 days 09:48:05
Rx Tx
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 14.0 -
146 Current LATN - -
147 Current SATN 58.0 -
148 Current TP - 0.0
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 16.5 16.5 16.5 16.0 16.5 16.0 16.5 16.0 16.0
333d
16.0 17.0 17.0 15.5 16.5 16.0 16.0 16.0 16.5 16.0 16.0 16.0 15.5 15.5 15.0 15.0
333e
0.0 15.0 15.0 15.0 15.0 15.0 15.0 15.0 15.0 15.0 15.0 15.0 15.5 15.0 15.0 15.0
333f
15.0 14.5 15.0 15.0 15.0 15.0 15.0 15.5 16.0 14.0 15.0 15.0 15.5 15.0 15.0 16.0
333g
15.0 15.5 15.0 15.5 14.5 15.0 15.5 15.0 15.0 14.5 14.5 14.5 15.0 15.5 15.5 14.5
333h
15.0 14.5 14.5 14.5 14.5 15.0 15.0 14.5 15.0 14.5 14.5 15.0 14.0 16.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 6 6 6 6
334b
7 7 7 7 7 7 6 6 6 5 5 5 4 4 0 0
334c
0 0 0 0 0 0 7 8 8 9 9 9 9 9 9 9
334d
9 8 8 8 8 8 8 8 8 8 8 7 7 7 7 7
334e
0 7 7 6 6 6 6 6 6 6 6 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 4 5 5 5 5 5 5 5
334g
5 5 5 5 4 4 4 4 4 4 4 4 4 4 3 3
334h
3 3 2 2 2 2 2 2 2 2 2 2 2 2 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
By 7:15, the modem showed that the noisy interferror was starting up...
32 Time Since Last Sync 000 days 10:03:02
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 15.5 -
146 Current LATN - -
147 Current SATN 58.0 -
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.0 16.0 16.5 15.5 16.0 16.5 16.0 16.0 16.5 16.5
333d
16.5 18.0 18.0 17.0 17.5 17.5 17.5 17.5 18.5 18.5 18.0 18.0 17.5 17.5 17.5 17.5
333e
0.0 17.5 17.5 17.5 17.5 17.5 17.5 17.5 17.5 17.5 17.5 18.0 18.0 17.5 17.5 17.5
333f
17.0 16.5 17.0 16.5 16.0 16.0 16.0 16.0 17.0 15.5 15.5 16.0 16.0 16.0 16.0 17.0
333g
16.0 16.0 16.0 17.0 16.5 16.5 17.5 18.0 17.5 17.0 17.0 18.0 18.5 18.5 18.5 18.5
333h
18.5 19.0 18.5 19.0 19.0 19.0 19.0 19.0 19.0 18.0 18.0 18.5 17.0 18.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 6 6 6 6
334b
7 7 7 7 7 7 6 6 6 5 5 5 4 4 0 0
334c
0 0 0 0 0 0 7 8 8 9 9 9 9 9 9 9
334d
9 8 8 8 8 8 8 8 8 8 8 7 7 7 7 7
334e
0 7 7 6 6 6 6 6 6 6 6 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 4 5 5 5 5 5 5 5
334g
5 5 5 5 4 4 4 4 4 4 4 4 4 4 3 3
334h
3 3 2 2 2 2 2 2 2 2 2 2 2 2 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
I power cycled the modem to see if it would reallocate the DMT bits. Sure enough, it did!
32 Time Since Last Sync 000 days 00:00:46
Rx Tx
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 16.0 -
146 Current LATN - -
147 Current SATN 58.5 -
148 Current TP - 0.0
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 17.5 17.0 17.0 17.0 17.0 17.0 17.0 17.0 17.0 17.0
333d
17.0 17.0 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.0 16.0 16.5 16.5 16.0 16.0
333e
0.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333f
16.0 16.0 16.0 16.0 16.0 16.5 16.0 16.0 16.0 15.5 16.0 16.0 16.0 16.0 16.0 16.0
333g
16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333h
16.0 16.0 16.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 6 6 6 6
334b
7 7 7 7 7 7 6 6 6 5 5 5 4 4 0 0
334c
0 0 0 0 0 0 7 8 9 9 9 9 9 9 9 9
334d
9 9 9 9 9 8 8 8 8 8 8 7 7 7 7 7
334e
0 7 7 6 6 6 6 6 6 6 6 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 5 4 4 5 4 5 5 5
334g
4 4 4 4 4 4 4 4 4 4 4 4 4 4 3 3
334h
3 3 3 2 2 2 2 2 2 2 2 2 2 2 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
I decided to call ASI. I had ASI change my line from 1.5/384 INTL to 1.5/384 FAST this morning while the "noise source" was occuring. The line didn't drop sync (except when I was rebooting the modem or forcing a resync), but the noisy interferror was still present. The ASI tech I talked to couldn't see any problem on the line even though the 5100b could.
In Interleaved (INTL) mode, the 5100b was able to squeeze in 474 DMT bits.
5100-20050616/081800.txt.png
SNR: 14.5
ATN: 59.5
DMT: 474 bit bins
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 16.5 14.5 17.0 17.5 17.5 17.0 17.0 17.0 16.0
333d
15.5 16.5 16.5 14.5 16.5 16.5 16.5 16.5 16.5 16.5 18.0 16.5 16.5 16.5 16.5 16.5
333e
0.0 16.0 16.0 16.5 16.5 17.5 17.0 16.0 16.0 17.5 15.5 15.0 16.0 15.0 15.0 15.5
333f
19.0 16.5 16.5 16.0 15.5 16.5 16.0 14.5 15.0 16.0 16.0 16.5 16.0 16.0 15.5 16.0
333g
16.5 16.0 15.0 15.5 15.5 15.5 16.5 16.0 16.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0
333h
15.5 15.5 15.5 15.5 16.0 16.0 15.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 16.0 16.0 16.5 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 4 4 4 5 5 5 6 6 6
334b
7 7 7 7 7 7 6 6 6 5 5 5 4 4 0 0
334c
0 0 0 0 0 0 8 9 9 9 9 9 8 9 9 9
334d
9 9 9 8 9 9 8 8 9 9 7 8 8 8 7 7
334e
0 6 6 7 6 5 6 6 5 2 5 5 2 4 5 5
334f
3 5 5 4 4 5 5 5 5 5 5 4 5 5 4 4
334g
5 5 3 5 5 5 4 4 4 4 4 4 4 3 4 3
334h
3 3 3 3 2 2 2 2 2 2 2 2 2 2 2 0
334i
0 0 0 0 0 0 0 0 0 0 0 2 2 2 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
I suspect that when it's in INTL mode, it allocates significantly more bits for error correction purposes.
5100-20050616/081900.txt
SNR: 13.5
ATN: 59.5
DMT: 476 bit bins
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 16.5 16.0 16.5 17.0 16.0 15.5 16.5 17.0 18.0
333d
17.0 16.5 16.5 16.0 16.5 16.5 16.0 15.5 16.5 16.5 17.5 17.0 16.5 16.5 16.5 16.5
333e
0.0 15.0 15.5 16.0 16.5 17.0 16.5 16.5 16.5 16.5 16.5 16.0 14.0 15.0 16.0 16.0
333f
18.5 16.0 16.0 16.5 16.5 16.5 16.0 14.0 15.5 16.5 16.0 16.5 16.5 16.0 16.5 16.5
333g
16.5 15.5 12.5 15.5 16.0 16.0 16.0 16.5 16.5 16.5 16.5 16.5 16.5 15.5 16.5 16.5
333h
16.5 16.5 17.0 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.0 16.0 16.0
333i
0.0 0.0 0.0 0.0 0.0 16.0 0.0 0.0 16.0 16.0 0.0 16.5 16.0 16.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 4 4 5 5 6 6 6 6 7
334b
7 7 7 7 7 6 6 6 5 5 5 4 4 3 0 0
334c
0 0 0 0 0 0 8 9 8 9 9 9 9 10 9 8
334d
9 9 9 7 9 9 9 9 9 8 7 7 8 8 7 7
334e
0 7 7 7 6 4 6 6 5 2 5 5 3 4 5 5
334f
3 5 5 4 3 5 5 5 5 5 5 4 5 5 4 3
334g
5 5 4 5 5 4 4 4 4 3 3 4 4 3 3 3
334h
3 3 2 2 2 2 2 2 2 2 2 2 2 2 2 2
334i
0 0 0 0 0 2 0 0 2 2 0 2 2 2 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
In FAST mode a short while later, the modem could only allocate 440 DMT bits.
5100-20050616/083200.txt
SNR: 14.5
ATN: 58.5
DMT: 440 bit bins
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.0 16.5 15.5 16.5 16.5 16.5 16.5 16.5 16.5 17.0
333d
16.5 16.0 16.0 15.5 16.0 16.0 16.0 16.0 16.5 16.0 16.0 16.5 16.0 16.0 16.0 16.0
333e
0.0 16.0 16.0 16.0 16.0 15.5 16.0 16.0 15.5 14.5 16.0 16.0 16.0 16.0 16.0 16.0
333f
16.0 16.0 16.0 15.0 14.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 15.0
333g
16.0 16.0 15.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333h
16.0 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 4 5 5 6 6 6
334b
6 6 7 7 6 6 6 6 5 5 5 4 4 4 0 0
334c
0 0 0 0 0 0 8 8 8 9 9 9 9 9 9 7
334d
9 9 9 7 9 9 8 8 8 8 7 7 7 7 7 7
334e
0 7 6 6 6 3 6 5 5 2 5 5 4 5 5 5
334f
2 5 5 4 3 5 5 5 5 5 5 3 5 4 3 3
334g
4 4 4 4 4 4 3 4 4 3 3 3 3 3 3 3
334h
3 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Swapped in a 5660 at 8:33am:
Current Attainable Rate 492307 3134693
Current SNR Margin 9.0 16.0
Current Attenuation 58.0 31.5
Current Output Power 5.5 17.5
2005/06/16 8:35am: 5660 (forced resync)
Current Attainable Rate 492307 3134693
Current SNR Margin 10.0 16.0
Current Attenuation 59.0 31.5
Current Output Power 5.5 17.5
PRIVATE modem at 8:36am:
SNR 14.6 16.0
ATN 62.5 31.5
PWR 4.6 16.9
RAT 2656 1016
Forced DSL resync.
PRIVATE modem at 8:41am:
SNR 14.1 16.0
ATN 62.5 31.5
PWR 4.8 16.8
RAT 2560 1012
8:49 5100b (back to normal)
SNR 15.0
ATN 58.5
DMT 437 bit bins
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 16.5 17.0 17.0 17.0 17.0 16.5 17.0 16.5 16.5
333d
16.5 16.5 16.5 15.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 15.5 16.0 15.5
333e
0.0 15.5 15.5 15.5 16.0 15.5 15.5 15.5 16.0 16.0 15.5 16.0 16.0 16.0 16.0 15.5
333f
15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.0 15.5 15.5 15.5 15.5
333g
15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 16.5
333h
16.0 15.5 15.5 15.5 15.5 15.5 15.5 15.5 15.5 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 4 5 5 6 6 6
334b
6 7 6 6 7 6 6 6 5 5 5 4 4 4 0 0
334c
0 0 0 0 0 0 7 8 8 8 9 9 9 9 9 9
334d
9 9 8 8 8 8 8 8 8 8 8 7 7 7 7 7
334e
0 6 6 6 6 6 5 5 5 5 5 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 5 5 5 4 4 4 4 4
334g
4 4 4 4 4 4 4 3 3 3 3 3 3 3 3 2
334h
2 2 2 2 2 2 2 2 2 0 0 0 0 0 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
8:54
Current Attainable Rate 505263 3134693
Current SNR Margin 11.0 16.0
Current Attenuation 59.0 31.5
Current Output Power 5.5 17.5
8:59 5100b
SNR: 16.0
ATN: 58.5
DMT: 437 bit bins
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 17.0 16.5 17.0 16.5 16.5 17.0 16.5 16.5 16.5
333d
16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.0 16.5 16.0
333e
0.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.0 16.0 16.5 16.5 16.5 16.0
333f
16.0 16.5 16.5 16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.0 16.5 16.0 16.0
333g
16.5 16.0 16.0 16.0 16.0 16.5 16.0 16.5 16.0 16.5 16.5 16.0 16.0 16.0 16.5 17.0
333h
16.5 16.0 16.0 16.0 16.0 16.5 16.0 16.0 16.5 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 5 5 5 5 6 6
334b
6 7 6 6 7 6 6 6 5 5 5 4 4 4 0 0
334c
0 0 0 0 0 0 7 8 8 9 9 9 9 9 9 9
334d
9 9 9 9 8 8 8 8 8 8 8 7 7 7 7 7
334e
0 6 6 6 6 6 6 5 5 5 5 5 5 5 5 5
334f
5 5 5 5 5 5 5 4 4 4 4 4 4 4 4 4
334g
4 4 4 4 4 4 4 3 3 3 3 3 3 3 3 2
334h
2 2 2 2 2 2 2 2 2 0 0 0 0 0 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The effects of the noise source disappeared when I rebooted the modem at noon. The high SNR peak values seem to indicate that it is underutilizing a particular DMT tone frequency.
Right before reboot it has some high SNR peaks:
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 12.5 13.5 15.0 14.5 15.5 17.0 20.0 16.5 17.0 21.0
333d
17.5 16.5 16.5 16.5 16.5 16.5 18.0 18.0 16.5 16.5 18.0 16.5 16.5 16.0 16.0 16.0
333e
0.0 17.0 17.0 16.0 16.5 24.0 17.0 16.5 19.0 27.5 17.5 17.0 22.5 19.5 16.0 16.0
333f
26.0 16.5 17.0 19.5 25.0 18.0 17.0 19.0 17.5 16.5 16.5 17.5 16.5 17.0 19.5 20.5
333g
16.5 16.5 22.0 17.0 16.5 16.5 17.5 16.5 16.5 17.0 17.0 16.0 16.0 17.5 16.0 16.0
333h
16.0 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 0.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 4 5 5 5 6 6
334b
6 7 7 6 7 6 6 6 5 5 5 4 4 4 0 0
334c
0 0 0 0 0 0 8 8 8 9 9 9 8 9 9 8
334d
9 9 9 9 9 9 8 8 8 8 8 8 8 7 7 7
334e
0 6 6 6 6 3 6 6 5 2 5 5 3 4 5 5
334f
2 5 5 4 2 5 5 4 5 5 5 4 5 4 4 3
334g
4 4 2 4 4 4 4 4 4 3 3 3 3 3 3 3
334h
3 3 2 2 2 2 2 2 2 2 2 2 2 0 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
After reboot the high SNR peaks are gone and the modem starts using bits it previously was not using:
5100-20050616/121600.txt
Rx Tx
140 Current Rate 1536 384
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 1536 -
145 Current SNRM 16.0 -
146 Current LATN - -
147 Current SATN 58.5 -
333 Receive SNR ps
333a
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333b
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333c
0.0 0.0 0.0 0.0 0.0 0.0 16.5 16.5 16.5 16.5 16.5 16.5 17.0 16.5 16.5 16.5
333d
16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.5 16.0 16.5
333e
0.0 16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0
333f
16.0 16.0 16.5 16.0 16.5 16.5 16.0 16.5 16.5 16.0 16.0 16.0 16.0 16.0 16.0 16.5
333g
16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.0 16.5 16.5 16.5
333h
16.0 16.0 16.0 16.5 16.0 16.5 16.0 16.5 16.5 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333i
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333j
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333k
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333l
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333m
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333n
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333o
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
333p
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
334 ADSL DMT Bin Bits
334a
0 0 0 0 0 0 0 3 4 4 4 5 5 6 6 6
334b
6 6 7 7 6 6 6 6 5 5 5 4 4 4 0 0
334c
0 0 0 0 0 0 7 8 8 9 9 9 9 9 9 9
334d
9 9 9 8 8 8 8 8 8 8 8 7 7 7 7 7
334e
0 6 6 6 6 6 5 5 5 5 5 5 5 5 5 5
334f
5 5 5 5 5 5 5 5 5 5 5 4 4 4 4 4
334g
4 4 4 4 4 4 4 3 3 3 3 3 3 2 2 2
334h
2 2 2 2 2 2 2 2 2 0 0 0 0 0 0 0
334i
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334j
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334k
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334l
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334m
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334n
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334o
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
334p
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
If I have some time later, I'll post the graphical versions of the data.
--justbits | |
| | | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
1 edit | Re: Any 5100b technician page DMT/SNR data experts Just wanted to add that I isolated the DSL modem on a UPS the other morning and yanked the wall socket while the noisy interferror was occuring. Isolating the DSL modem to a UPS for 25 minutes didn't make the noisy interferror go away.
--justbits | |
| 
telcotech
join:2002-02-02
at&t
| Looks like you have an AC motor on a timer somewhere. Even if you isolate the modems power supply, the homerun from the NID could pick up RFI.
Most of the common causes would be an electric motor or an electric heater of some type, an electric water heater, spa/hot tub, pool pump, etc... since it seems to be consistent, it would suggest that it is something on a timer or something that gets used at a specific time each day.
Do you live in an apartment building? if so, it could be a neighbor.
Try this:
1. disconnect your IW from the nid, only connect the homerun to the DSL modem when the problem starts.
2. Take the spare pairs in the IW running to the modem connect them together and ground them.
3. Check your electrical outlets, the ground should not be connected to the service neutral, it should be grounded to the house electrical ground, some older homes get upgraded and the electricians would tie the service neutral to the ground tab at the outlets to pass an inspection, this can create a differential that can act as an antenna and bring noise into your house through your electrical system. Isolating the modem with a UPS would not filter this noise out. the computer, monitor, modem router and any other device that used AC power would need to be connected to the same UPS and the UPS would need to be run on backup battery power to actually isolate this type of interference.
4. If telco comes out again, have them check the bonding on the drop, it should be grounded at the NID or the PED or both. | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
1 edit | Re: Any 5100b technician page DMT/SNR data experts I am in a home in a residential neighborhood just off of a main street. That main street has a straight south run to the River Grove central office. I am for all intents and purposes almost exactly directly north (as the crow flies) from the central office. (within 300 feet I think)
I'll try grounding the extra wires. Should I ground it to the house grounded outlet or to a the pipe that holds the electric wires that runs into the house on the outside of the house? Or some other suggestion? I know there are a few outlets that have the grounded prong (circular) part of the plug that grounds by attaching to a screw in the outlet box.
I've never had a problem with this for years. Why the heck would the house electrical wiring suddenly start picking up that much RFI?
As part of my electrical isolation experiment a few weeks ago, I unplugged everything in my house, except for a few essentials. (Refrigerators, DSL modem, router, computer.) Turned off ceiling fans. Turned off all electrical lights. Turned off all Wireless devices. (Answering machine, phones, etc. Disconnected the telephone also. The problem still occurred in full force.
I'll check the house's electrical outlet grounding, but I really doubt that there's anything I can do within my premesis to fix this problem. I hadn't changed any wiring (electrical or telephone or for that matter anything else) in the house when the problem started occuring. If my wiring is picking up RFI, it's gotta be a pretty strong noisy signal that's being generated somewhere near my wire group/count.
The thing is, when the problem is occurring, the ASI on-site techs could see the problem on the line. The problem is that the most recent ASI on-site tech came on Saturday morning and observed the line when the problem wasn't occuring, so they closed my trouble ticket. :-P There is a very low occurance rate for Saturdays. I left a nice note inside the NID explaining the problem in detail but they left without seeing what I saw. Go figure.
I can hear audible noise on the line in the evening and during the morning. I'll try to take a recording this morning while the problem is happening. I heard the same thing without any DSL modem hooked up. I heard the same thing with and without a DSL microfilter installed.
By the way, my father worked for AT&T and then Lucent for many years. He worked in the River Grove CO many times. He pointed out the CO building to me the other day.
This is the URL given:
»www.mapquest.com/maps/map.adp?la···7&zoom=8
at: »/coinfo
for: 773-625-xxxx (RVGVILRG).
That URL can be seen on Google as:
»maps.google.com/maps?ll=41.92835···=k&hl=en
That URL is wrong! It's not pointing at the correct building.
This URL is right: (it's the
»maps.google.com/maps?ll=41.92913···=k&hl=en
OR:
»www.mapquest.com/maps/map.adp?la···9&zoom=8
Where should I post to get the CO data on broadbandreports.com updated?
--justbits | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| This morning, I did some wire checking and rewiring.
The NID has two CAT 5 cables wires running from it.
A "home run". The CAT 5 blue pairs connect to TELCO. All 3 other pairs are screwed into to NID ground which is connected to the electrical pipe ground on the back of the house.
The "POTS run". In the NID, the IW port is connected to a Z330 microfilter via a short 6 inch CAT 5 cable. The POTS side of the microfilter goes into a 8 foot CAT 5 cable. That CAT 5 cable goes into one wireless answering machine.
Inside the house, the grounded 3 pairs of wire connect to the ground on the power strip. This is done by taking the 3 pairs of wire and twisting them with another wall grade electrical wire. That wire connects via screw into a power strip ground prong. The power strip connects into a second power strip, which connects into UPS1. UPS1 is plugged into a grounded outlet. The powerstrip, UPS1 and NID all are on the same ground now. They all were before too, but I suppose it's arguably better.
From here on, nothing has changed, but I thought I'd describe it.
All outlets in the house that have grounded outlets have the ground wire screwed into the wall box. All devices are plugged into correctly grounded UPSes.
One pseudo grounded outlet screws the ground onto the electrical box outside plate. The plate is metal. The screw goes into a threaded hole that is provided by the electrical box.
I traced all ground wires to pipes and all pipes run to the house main electrical pipe inlet.
The back bedroom UPS1 is connected to a 10/100 BT switch, a Linksys router (wireless disabled), the DSL modem and a wireless answering machine. (Disconnecting and powering off the answering machine and all POTS connections has not caused the problem to go away in the past.)
The switch connects to a red Belkin 50 foot CAT 5e cable.
The red Belkin 50 foot CAT 5e cable connects to Switch 2. Switch 2 is powered by a second UPS.
UPS2 connects to computer 1 that also connects to the switch.
Switch 2 connects via CAT 5e cable to Switch 3.
Switch 2 connects via CAT 5 cable to a home media device on UPS3.
UPS3 has a TV antenna lightning strike protector on it. (I've disconnected this and seen no change in the problem while it was occurring.)
Switch 2 connects via green Belkin 50 foot CAT 5e to computer 2.
UPS3 connects to computer 2.
--justbits | |
| |
armyrebel4
Dream Chaser
Premium
join:2002-01-08
Springfield, IL
·AT&T Midwest
| alright, I've done as much as I can with this. I would follow up with beach boy or post in the sbc direct forum. Obvisously its interfearance coming from somewhere and you've done your best as far as what I can see. Anyone else have input on this one?
Erik
--
“True individual freedom cannot exist without economic security and independence. People who are hungry and out of a job are the stuff of which dictatorships are made.”- FDR | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts? I opened this discussion to get feedback on the 5100b technician data and to get some troubleshooting ideas outside of SBC Direct and SBC ASI. I am very thankful for everybody's suggestions. One of these days, I'll consider writing some software to make monitoring the 5100b accessible to more people than just myself.
I have an extensive thread going in SBC Direct. It's been open since 5/10/2005. Unless you're privleged to read all posts in SBC Direct, don't bother going to this URL:
»[TROUBLE] Speed drop from 2400/443 to 1500/443
beach boy and crew have a CO port change scheduled for my line. I'm assuming for the DSLAM. In the meantime, I'm using dialup.
--justbits | |
| | |
AlEinstein
join:2004-10-08
Hughson, CA
| Re: Any 5100b technician page DMT/SNR data experts Port change is a good idea. I'm still seeing a flucuating noise margin though. Bad ports usually throw errors and less frequently attribute flucuating noise.
I'm not into beating dead horses, or any state of a horse for that matter, but how about a new protector for sure and then a possible pair change after the port change??? Seems like not much effort in the interest of being thorough.
Einstein, OUT
Keeps us posted.
Bits, God bless ya, but you're darn close to making this into rocket science! Love those data report posts! I think my scroll bar is about worn out.
Take care, good luck | |
| Ainshi
join:2002-07-09
Woodstock, IL | Just as the sound from jet engines interferes with the alien morphing devices on Stargate SG-1, so too may your phone lines be affected! | |
| chris123
join:2002-07-23
Highland, IN
| Have you tried changing out your filter, or installing a proper whole house splitter? Check the for sale forum if you need to buy one.
I'm just shooting in the dark here, but I've heard other people say they go bad at times.
--
see my SBC Review @ »Review of AT&T Midwest by chris123 | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts I have tried swapping microfilters. I've had the microfilter located in the NID and inside my house. Since I've gone crazy trying to eliminate potential sources of interference, all I have is one wireless telephone hooked up to one microfilter. A whole house microfilter wont make any difference in this case.
--justbits | |
| | | joewho
Premium
join:2004-08-20
Las Vegas, NV | Re: Any 5100b technician page DMT/SNR data experts Maybe there's a wasp nest in the box on the pole... | |
| | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts It is extremely unlikely that an animal or insect would cause radio frequency interference that repeats for a pretty particular duration (45 minutes) during the week and at different times on weekends and holidays.
The more likely candidates we're exploring right now are improperly filtered coaxial cable TV cables on the utility pole, the neighbor who had the improperly installed satellite TV hookup, or possibly some AC/DC motor, like a hot tub, a spa, or a excercise machine that's placed too close to telephone wires. (All of these candidates are not present within my home.)
Just thinking about it... if the person who attached their dish to the utility pole wasn't smart enough to properly install their satellite dish, it's also likely that they also do not have proper cables or filters attached to that device to prevent them from causing excessive RF interference.
--justbits | |
| | | | |
armyrebel4
Dream Chaser
Premium
join:2002-01-08
Springfield, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts "For the purpose of constructing and maintaining such lines of telegraph or telephone, the parties in interest may set the necessary poles or posts on which to place the wires and insulators of such lines, in any of the public streets, highways or alleys, or in any private road leading to such highways, streets or alleys outside of the incorporated cities, villages or towns in this state along which such lines may pass: Provided, such poles or posts shall be placed along the boundaries of such highways, streets, or alleys, at such distances therefrom as the authorities having control thereof may direct. And provided further, that the wires necessary for such lines shall not be less than fifteen feet above the ground along such boundaries, and not less than twenty feet at any public or private crossing, and shall be so placed as not in any manner to interfere with such crossing.
Any person who shall unlawfully and intentionally injure, molest, or destroy any of said lines or the material or property belonging thereto, or shall in any manner interfere with the proper working of such lines, shall on conviction thereof, be deemed guilty of a petty offense and fined not exceeding $100. The fine shall be recoverable in the circuit court; Provided, that prosecution under the foregoing provision of this section shall not in any manner prevent a recovery by the person or persons entitled thereto, of the amount of damages done to such lines."
That's state law. Unless there is some kind of radiation leak lol, get cable man it's not worth the hassle.
--
“True individual freedom cannot exist without economic security and independence. People who are hungry and out of a job are the stuff of which dictatorships are made.”- FDR | |
| 
misskaz
@chcgil.ameritech
| I unfortunately can't offer any help, but I feel deja vu reading your posts. We have had very similar problems with our SBC DSL for months now. (We live in Chicago, too.)
Lately, we've been losing our DSL connection on a very regular basis - close to once a day at this point. It used to be once every few months, and has been happening more and more often. Every time we lose the connection, I have to reset and set up our router all over again or I can't connect to the internet wirelessly with the laptop. It's incredibly frustrating, to come home from work and need to get stuff done only to find that the internet's out AGAIN and you have to unplug things and plug them back in and re-do all the router settings.... argh! Today even that didn't work - connecting the modem directly to the computer gave me a "limited or no connectivity" warning about the connection.
We are also faced with a lot of noise on the voice line, although it's cleared up somewhat since my boyfriend found and cleared out a really dense spider web/nest from our network interface box.
I can't say we've done anywhere near the techy troubleshooting that you have (can I do that data capture with my SpeedStream 5360?) but yet another call to Tier 1 tech support at SBC this evening has introduced me to the possibility of interference causing the problem. Previously we thought it was just the ancient lines in this apartment building - and it may well be that's the case after all.
Honestly, I'm really close to cancelling SBC altogether, phone and internet, and getting a cable modem and VoIP. Oh yeah, have I mentioned that even though I've paid for their "line-backer" service for 3 years, which is supposed to cover tech visits even if the problem is the lines inside the house, SBC won't come out because they claim it's my landlord's responsibility. Funny how they didn't mention that when they asked if I wanted to pay an extra $5 a month for the service.
Anyway, good luck and I'll be following your threads to see if you get anywhere. | |
| |
See 9 replies to this post | |
| |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts I'm being patient because I'd rather have the problem completely fixed correctly, rather than quick fixed poorly, like they did when I was switch to a significantly poorer quality pair of wires on June 7th. (The change was from a pair capable of 5.4mb/1080 max attainable, to 3.2/600 max attainable.)
After reviewing yesterdays data and the day before, I think I might be seeing a larger trend across the entire day.
The lower download frequencies have significant SNRM degredation from 7am til just before 5pm. There's also typically a spurt of 100-300 CRC errors earlier in the morning too. Can't do it today or tonight, but sometime soon, I'm going to be reviewing the entire day's data for the last few weeks to see if I see the general trend during "business hours". I'd laugh if the hours match those of a local bank.
The "bit migration" problem occurs once or twice each morning. If it lasts for 45 minutes, it will usually only occur once. If it lasts for 35-40 minutes, it will usually occur twice. I need to reanalyze my data, but that's what I think I'm seeing.
I like your 3x5 crazy idea cards. Actually, a co-worker of mine who was having DSL problems proposed that some of the ASI telephone people have an 8-ball or a dart board that is weighted heavily on "inside wiring", "squirrels chewing on the wires", "high performance errors", and "bad modem". I would say "inside wiring" was the one that they hit me with the most.
--justbits | |
| | | klevin
join:2004-07-26
Takoma Park, MD | Re: Any 5100b technician page DMT/SNR data experts how do you get those nice graphs (spectrum analysis?) | |
| | | |
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
| Re: Any 5100b technician page DMT/SNR data experts I wrote some bash shell scripts.
I gather the technician data from the 5100b.
I parse out the SNRM & DMT data.
I put them into separate files.
I feed the data into gnuplot.
I gather and plot the data periodically (at least every 5 minutes) using a cron task.
I'm doing this on MacOS X, but I suppose it would be trivial to port to Linux or Cygwin.
--justbits | |
| | | |
|
