| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | netcomm |
BG> atdt024361785 (Paul's M34F from another M34F) BG> Calling FROM my place, incidentally, where we already BG> KNOW that the line quality leaves quite a lot to be desired. BG> Terminal : 57600 8 data bits No Parity BG> Line : 28800 V.34 BG> Current EQM : 024 BG> I've absolutely no idea how Rockwell interpret BG> their Eye-Q Monitor reading, nor even what it means, Its based on the root mean square of the error vector. I assume you understand the basics of a trellis constellation pattern. At a particular symbol rate and constellation pattern, you have an array of points which are the discrete states that the carrier can have, the constellation of valid points. Now each point is the ideal coordinates for that particular point, if the observed signal is close to one of those, its taken as that value. The difference between the ideal location of each point and the one actually seen is essentially due to the noise and jitter and group delay etc on the line. The root mean square is just a mathematical way of expressing how far away a particular point is from the correct location, the error. You can go and take a bex and have a good lie down now |-) BG> so all I can do is take notice of the manual when it tells me BG> that values in excess of 10 are very poor (10 "what's", BTW?). Its just a scaling of the root mean square of the error vector which produces the EQM number. I think calling >10 'very poor' is mad. Its more usual to reduce the carrier rate if the EQM is >20. BG> Therefore, a reading of 24 would more than likely be atrocious. Thats going too far. And clearly thats mad if it gets a 28800 anyway. PE> A 28800 connect to me on reportedly bad lines. BG> Agreed, although we still don't really BG> know what YOUR lines are like either. Sure we do, from te FNQ Courier/Courier stats. We also know that they cant be too bad with the very high level of 28800 connects with M34F pairs. BG> atdt38681597 (David's Courier from an M34F) BG> Again, from my place. BG> Terminal : 57600 8 data bits No Parity BG> Line : 26400 V.34 BG> Current EQM : 009 PE> And a 26400 connect to David on a better line. BG> Yeah, that was a bit of a surprise. Wonder why? Somethings seriously fucked there somewhere. We do know that Daves line is MUCH better than Pauls, so that result is completely mad on the connect rate, tho the EQM makes sense. BG> Dave was going to take some line level stats while he still had the BG> M34F, so that we could attempt to determine where our individual line BG> losses are occurring, and if possible, to what degree. Bloody hard to BG> do though, when the Rockwell's and the USR's stats vary so wildly. BG> And Dave's M34F (at least) appears to be broken here as well. Yeah, its a problem. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.