FTTP means you have Fiber To The Premises (i.e. fiber directly to the side of your house, terminated at an optical network terminal, an ONT).  If you have this, this is the way your neighborhood was wired.

You cannot change between FTTP and FTTN (Fiber to the Node).

At this time, FTTP customers are limited to 2HD channels.  The rumor is that this will be increased in the future, possible the near future.

I am on pair bonding and the reccomended profile is the 25 meg profile, does this mean that I cannot get the 32 meg or does it mean I might get degraded service if I get it?

---

spd2demun wrote:

Very good job!  Just got to use this on desktop today (have the old 2Wire on laptop).

 

FYI, the Recommended Profile is correct for me.

 

I like being able to see what channels others are watching, LOL!

---

You can also identify which stbs are which, also.

---

Mobutu wrote:

I am on pair bonding and the reccomended profile is the 25 meg profile, does this mean that I cannot get the 32 meg or does it mean I might get degraded service if I get it?

---

32/5 profile is not available with pair bonding as far as I know.  The maximum available profile is 25/2.

Yeah, I understand that part, but if it WERE, would the line appear to support it?

I'll have to see the posted screenshot.  The moderator hasn't approved it yet so I can't see it.  Once it's approved, I'll tell you.

---

Mobutu wrote:

Yeah, I understand that part, but if it WERE, would the line appear to support it?

---

OK, I can now see your screen shot.

On the surface, it would appear that the 32/5 profile would theoretically be possible with a 58Mbps max rate.  But there's other factors.

To get the additional distance for the iNID, there's more to it than just the max rate.  Pair-bonding installations use a different VDSL frequency plan for each line, restricting the frequencies to those less than 3.75 MHz.  This increases the service distance.  But a drawback is that it moves all upstream bandwidth to a narrow range at the very low end of the spectrum.  Not much more than 1 Mbps of raw bandwidth can be transmitted upstream on each line in a pair-bonding installation.  Subtract out the bits reserved for error correction, and the maximum upstream aggregate bandwidth using both lines is only about 1.5 Mbps.

So while the line might appear to support 32 Mbps down, it would never handle 5 Mbps up without changing the VDSL frequency plan and allowing the profile to use frequencies up to about 5.1 MHz.  And there's no guarantee that those frequencies will work at the long service distances typical for pair bonding installations.

Awesome, thanks for the explanation.

New channel database released, version 2010-08-14-1838-001, 1070 channels.

• Add 38 national channels
• Add 143 local channels

Have you looked at a plot of max profile rate against distance from VRAD?  I'm interested in the distance at which "most" people roll over from the 25/2 to the 32/5 profile.  RealTime shows me 1600' but my line stats are not good enough to support 32/5.  However, if it turned out that 1600' was generally a good distance to have the 32/5 I'd have a stronger argument to have a tech come out again to check my line and maybe do something to improve it.  I had one out when i changed over to UVerse voice and asked him about line quality and he recommended sticking with 25/2 because the line couldn't support 32/5.  Realtime shows the same recommendation.  Bitloading graph doesn't show any sinusoid superimposed which your guide gives as a signature of a bridge tap (is it an obvious sinusoidal variation or is it subtle?).

Really would like 3HD/1SD ....

---

SkepticalScot wrote:

Have you looked at a plot of max profile rate against distance from VRAD?  I'm interested in the distance at which "most" people roll over from the 25/2 to the 32/5 profile.  RealTime shows me 1600' but my line stats are not good enough to support 32/5.  However, if it turned out that 1600' was generally a good distance to have the 32/5 I'd have a stronger argument to have a tech come out again to check my line and maybe do something to improve it.  I had one out when i changed over to UVerse voice and asked him about line quality and he recommended sticking with 25/2 because the line couldn't support 32/5.  Realtime shows the same recommendation.  Bitloading graph doesn't show any sinusoid superimposed which your guide gives as a signature of a bridge tap (is it an obvious sinusoidal variation or is it subtle?).

---

Ya, I've got enough people in the database now to do this kind of analysis.  It'll have to wait until the weekend, though, as I'm occupied most of this week.

What kind of pattern a bridge tap makes on the bitloading graph depends on the nature of the bridge tap wire:

• Generally, the pattern is a sinusoidal variation in the tops of the graph, but not always.
• The number of oscillations in the sinusoid between two given points on the graph indicate the length of the tap wire.  Short tap wires have fewer oscillations, long tap wires have more.
• The shape and amplitude of the sinusoids is related to how far back on your line the tap wire bridges from.  Tap wires that are farther away from your demarc point exhibit less sinusoidal variation and more overall attenuation.  Tap wires that are closer to your demarc point show large sinusoidal variations, and when they get really close, begin to turn into more of a horn shape, with a pointed bottom and flared top (see this bitloading graph for an example).

SJ, you need to let ATT buy you out, or hire you! 

here are the Dallas SD/HD Channels and their ip addresses

NBC - KXAS 5  = Channel 5 / 1005

SD IP 239.192.42.2

HP IP 239.192.42.19

ABC - WFAA = Channel 8 / 1008

SD IP 239.192.42.3

HD IP 239.192.42.18

CBS - KTVT = Channel 11 / 1011

SD IP 239.192.42.4

HD IP 239.192.42.20

KTXA 21 (CBS Sister Station in DFW) = 21 / 1021

SD IP 239.192.42.6

HD IP 239.192.42.23

You already have the Fox stations in you database.

Not sure what happened to the 1.4.1 thread, but $25 donated here.  Thanks for a great piece of software and your help to the community!

---

wiltshp wrote:

Not sure what happened to the 1.4.1 thread, but $25 donated here.  Thanks for a great piece of software and your help to the community!

---

You're welcome, and thanks for your support!

The 1.4.1 thread was renamed to the U-Verse Master Thread, I'm going to try to keep all updates in that thread from now on so that I don't create a new thread for each version release.

Also, U-Verse Realtime now has a new home at www.uverserealtime.com.

I'm a new customer (less than 2 weeks) and stumbled across your software the other day and its very informative.

I kept my Comcast internet but I can connect wirelessly to the RG to run the program. It appears you are trying to create a database from the captured data but I have no apparent way to transmit mine to you. If there were some way to save the data to a file I could do that and help build up your database.

---

Don_H wrote:

I'm a new customer (less than 2 weeks) and stumbled across your software the other day and its very informative.

 

I kept my Comcast internet but I can connect wirelessly to the RG to run the program. It appears you are trying to create a database from the captured data but I have no apparent way to transmit mine to you. If there were some way to save the data to a file I could do that and help build up your database.

---

Thanks, and welcome to U-Verse.

The program is only designed to report the line stats data over the Internet.  What you could do is to configure a computer to connect to both the RG and the Comcast Internet simultaneously.  You can do this by giving the computer two IP addresses, one on Comcast (with appropriate subnet mask, default gateway, and DNS), and the other with an IP address on the RG's network.

Then, run UVRT, and uncheck the "Automatic" checkbox next to the IP address and fill in the IP address of the RG.

In this configuration, UVRT will retrieve stats from the RG and transmit them to the database using your Comcast connection.

If you can't configure the computer like this, it's OK if the line stats don't get reported, as your configuration is rare.

Okey Dokey.

Connected Cat5 from router to laptop, connected wireless to RG, ran RealTime, changed IP to 192.168.1.254, it appeared to download something (I think the guide DB) and everything appears to be OK.

It went thru "Gathering Statistics" probably 15 times so I assume the data got sent to your database.

One thing to mention.

The installer unpacked the RG, plugged it in to power and I never saw him change any settings so I assume I have the defaults from the factory.

Yep, a normal U-Verse installation requires nothing to be configured on the RG.  They just have to call and register it's serial number with the AT&T customer management system.

And yes, if you saw it download a new channel database, that means it had internet access.  The line stats would have been reported as soon as the first statistics gathering interval was completed.

SomeJoe, still only automatically finds 2 HD on the Ingress profile even though I'm 1 SD/ 3 HD on Wan and Ingress profiles.  Manually entering them on the config page fixes it, but wanted to let you know about this.  On Win7 hooked up by ethernet.

Chris

______________________________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
1-866-465-1496 for direct TS to avoid Mr. Voice recognition
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

My coax boxes don't show up on that tab all the time.

Ethernet ones stay listed, and keep their names that I give; but when I go to the MDC, the Ethernet boxes are back to MACs.

Ya, spd, I don't know exactly what's going on with your coax STBs.  I have a feeling that your RG might be such an early model that it doesn't bridge packets from coax to Ethernet all the time.

Chris,

There's no way for UVRT to detect your WAN, Ingress, and Egress profiles.  It infers the most likely settings using your line profile.  For a 32/5 profile, it's currently programmed to infer 1SD/3HD WAN, 2SD/2HD Ingress, and 1SD/2HD Egress.

Since we're in the middle of the rollout to 1SD/3HD Ingress, the inference from the line profile will be correct for some people and incorrect for others.  Once the rollout is finished and almost everyone has 1SD/3HD Ingress, I'll issue a new version that defaults to 1SD/3HD Ingress for 32/5 lines.

Spd has been a Uverse sub since it was dial up.   j/k

Actually true in a way, SBC before ATT/UV! 

And thanks, SJ, so my old 5/0 provisioning doesn't play into this? 

Ya, I don't think the 0HD/5SD has anything to do with it.  It feels like a hardware issue to me.

  And the one I have now is actually my 3rd.

See the master thread: U-Verse Realtime Master Thread