Community.Acanac.com

I guess asking support got nowhere. They didn't even bother to check the line, I just got this response:

"As Bell sets the setting on fast path by default.
If your setting is currently on Interleaved, it means your line can not handle fast path setting and we can not do any specific action regarding this issue."

Here are today's modem readings.
Bearer Generic Info Downstream Upstream
Margin (dB) : 14.0 16.0
Attenuation (dB) : 39.0 24.0
OutputPower (dBm) : 19.5 11.5

The new SpeedTouch that I'm using has been rock solid, compared to the Aztech that I was sent. I never had to power cycle the modem once.

I plugged in the Aztech just now to see the difference in margins, and the Aztech reports:
US Margin 8
DS Margin 8
Trained Modulation ADSL_G.dmt
LOS Errors 0
DS Line Attenuation 42
US Line Attenuation 26

That's one huge discrepancy in my margins, and 3dB in downstream attenuation is quite a bit of a difference as well.

I guess the Bell tech/whoever took a look at the stats when the Aztech was connected and decided to throw me down to interleaved.

Any suggestions?

Suggestions? Depends on --

ADSL Line:
. what is your latency? (use traceroute and/or ping your BAS)
. what is your error rate? (need to do this over time. at least a day or week)
. do you have disconnection problems?
. what is your RCO? (used up capacity -- lower is better, close to 100% is not so good)

User:
. do you need less latency?
. are you in a hurry?
. are you somewhat tech-savvy? (can you telnet and get the the line data below?)

You might want to set up your modem and let it run for a month. Don't resync it!

Then, if you can say "the line has been up without resync and without significant errors for a month, my RCO is only 65%" and ask to be swiched to fast path. Be sure to remind whomever that yours is a Business Account..

[too bad about the text space mangling]

------------------------------------------------------------------------

______ SpeedTouch 5x6
___/_____/\
/ /\ 6.2.29.2
_____/__ / \
_/ /\_____/___ \ Copyright (c) 1999-2007, THOMSON
// / \ /\ \
_______//_______/ \ / _\/______
/ / \ \ / / / /\
__/ / \ \ / / / / _\__
/ / / \_______\/ / / / / /\
/_/______/___________________/ /________/ /___/ \
\ \ \ ___________ \ \ \ \ \ /
\_\ \ / /\ \ \ \ \___\/
\ \/ / \ \ \ \ /
\_____/ / \ \ \________\/
/__________/ \ \ /
\ _____ \ /_____\/
\ / /\ \ /___\/
/____/ \ \ /
\ \ /___\/
\____\/

------------------------------------------------------------------------
_{planiwa}=>adsl info expand=1

Modemstate : Up
xDSL Type : ADSL
xDSL Standard : ITU-T G.992.1
xDSL Annex : Annex A
Channel Mode : Interleaved
Uptime (days hh:mm:ss) : 56 days, 13:33:08

Number of resets : 1

Total Available Bandwidth Cells/s kbit/s
Downstream : 14188 6016
Upstream : 1886 800

Intrinsic/Actual and Maximum Bandwidth % kbit/s
Downstream : 56 10688
Upstream : 62 1280

Bearer Generic Info Downstream Upstream
Margin (dB) : 19.5 17.0
Attenuation (dB) : 3.0 1.0
OutputPower (dBm) : 7.5 12.5

Vendor Chipset Local Remote
Country : B5 FF
Vendor : BDCM GSPN
VendorSpecific : 0000 0800
StandardRevisionNr : 00 01
Vendor System
Country : 0F 00
Vendor : TMMB ----
VendorSpecific : 3C61 0000
StandardRevisionNr : 00 00


Transfer statistics
Errors
Received FEC : 22781
Received CRC : 458
Received HEC : 453
Transmitted FEC : 0
Transmitted CRC : 0
Tranmsitted HEC : 0

Near end failures since reset
Loss of frame : 0 failures
Loss of signal : 0 failures
Loss of power : 0 failures
Errored seconds : 8 seconds

Near end failures last 15 minutes
Loss of frame : 0 seconds
Loss of signal : 0 seconds
Loss of power : 0 seconds
Errored seconds : 0 seconds

Near end failures current day
Errored seconds : 0 seconds

Near end failures previous day
Errored seconds : 0 seconds
{planiwa}=>

And sometimes Acanac has to send more than one ticket until Bell finally put you on fast path

_________________

YOU CAN NOW DOWNLOAD THE ACANAC COMMUNITY TOOLBAR HERE:
http://acanaccommunityforum.ourtoolbar.com/
WORKS WITH IE AND FIREFOX

Thanks for the tips!

Prior to me doing a switch over to the Aztec:
Receive FEC error count: 2034
Receive CRC is 0
Transmit FEC error count: 0
Transmit CRC is 0
My Downstream RCO is 81%
Upstream RCO is 64%

0 near end failures on all stats.
Uptime: 2 days, 7:31:41
no disconnects as compared the the Aztec. Downloading too much and the Aztec modem would start going wonky in about 12-18 hours. I could go a couple of days, but that would only if I used minimal bandwidth.

Number of resets: 1

Total Available Bandwidth: Cells/s, kbit/s
Downstream: 14188, 6016
Upstream: 1886, 800
Intrinsic/Actual and Maximum Bandwidth: %, kbit/s
Downstream: 81, 7360
Upstream 64, 1244

The lower the latency the better. The company I work for develops software and hardware to encode video data (closed captioning, etc.) in real time remotely through an encripted gateway. The lower the round-trip latency the better the results. The next evil is the packet drops down stream. Still trying to figure out the best way to handle those in a timely fashion.

The routine stuff that's run are cron jobs overnight to sync various data, repositories, etc. that I can finally do without loosing the connection at night.

I don't bother telnetting, I just wrote my own quick and dirty proggie to do it for me . I have it logging my stats, etc. as it goes, periodically.

I'm not in a huge hurry, I'd just like to get this done and over with so I can move on, it's one less sticky note on my desk to deal with.

Thanks again for your help

Just leave your speedtouch modem connected and send another ticket asking nicely to be put on fast path, obviously that modem can handle noise better than the aztech one, no biggie, they will understand one way or another.

_________________

lucask, I've been told a couple times that it relates to attenuation. You're in the mid-to-upper 60's, which puts you about 3.5km from the central office, which at least in my case would mean my speed profile dropping if I were to be put on fastpath. So it seems to be something most suitable to those closer in.

I'm pretty sure we would all like to see the Aztec modem stats.
Can't seem to find them.

whiteman

Reading comprehension difficulties?

lucask repeatedly posted his ATN as around 24 / 39.
"mid-to-upper 60's" is 600 times as lossy as 39.



lucask posted his Aztech stats in this message: viewtopic.php?p=53304#p53304

Why the harshness?

Anyway, I meant combined. I'm used to taking them both into account and dividing by 18.

Now that's very, very interesting. Why would one do that? Is there any scientific justification for doing so? US ATN and DS ATN are completely separate quantities. Why would anyone consider them to be additive? What would the sum represent? And what would "18" represent? There is reputable published work that relates DS ATN alone directly to wire length, for a given wire gauge and other factors. But I am not aware of anything published that adds US ATN and DS ATN.

There appears to be no scientific basis for doing anything like this. It seems to be a completely unsubstantiated folk-supersition, which those who practice it never validate.

The fact that many people repeat, without questioning, what they read on the Net, does not make it reasonable.

But, perhaps, you know the scientific reason for this? If so, please tell.

It's like accusing the boarder guard for why we lost the war.

_________________

I'm sure you're aware of other formulae as well one being DS Att. / 13.81.

But this one in particular I believe was started on the Teksavvy forum and was credited to a Teksavvy Tech. (could be wrong).

The way I took it was a rule of thumb, approximation and not very accurate but did give you a rough idea how far you were from the CO.

I edited it out of my post on Noise Margins and Attenuation for that very fact.

_________________

Remember, Don't over Quote .

Fergless, right, that's where I saw it most recently (it's still there if you look down the thread), though I think I first saw it somewhere in one of the sprawling DSLReports FAQs too. I've also seen /9 for just DS, and you mention 13.81, which I have not seen (does one result in km and one miles?).

Yep, I just got rid of it in the Topic Post, that's a pretty old post, 8 months ago. (Wasn't a Mod. then.)

Here's an Australian thread using 13.81, could be the wire gauge is different there, who knows.
http://phoneworks.net.au/adsl_troubleshoot.php#3

Here's a thread with the * 250 formula.
http://www.dslreports.com/forum/r219963 ... e-with-DSL

If people find these things useful then that's great, if not keep looking.

Brings to mind the quick calc. I use for Kilometres to Miles as I was brought up on the old system and never could visualize a Kilometre. LOL

Not totally scientific, but a fairly accurate approximation.

_________________

Remember, Don't over Quote .

Im a network support specialist for TELUS, and I basically reset ports all day long and get a general idea what the norms are when it comes to ATTN / distance ratio.
While of course unsubtantiated, Downstream (important) ATTN / 13.8 give a VERY close approximation to loop length providing there isnt somthing completely aggregarious connecting to the modem, such as a line filter attached the the patch cord going to the modem, rust on the terminals, bad demarc etc.
This is my 2nd post but unfortunately you guys will be seeing more of me here now heh
/JJ