Poor performance HX50 BW @ Balad IRAQ - Part 2

(Read 5419 times)

keasley

Member
★★
Offline

Posts: 13
IRAQ

Apr 27^th, 2009 at 3:49am

Greg,
I did swap out the TX&RX cables and did a loop resistance using a Fluke multimeter using your instructions (<1.2 was the results) on testing the center and housing on each cable, center on both and housing on both. I also did cable test using a TWINA/TRIAX tester by Trompeter and the cables passed.

Had a power outage, an opportunity to verify the elevation, polarization and azimuth. After redoing everything on the dish. I got a signal strength of 85 & lock. Below are the stats after 6hrs of uptime.

Satellite Statistics Summary
------------------------------------
Network Time: MON APR 27 02:35:51 2009
------------------------------------
Adapter Main Statistics:
------------------------
Signal Strength.............. 82 Stream Msg-Ackd/Nakd........ 440715/4447
Flags............... 0x00000000 NonStream Msg-Ackd/Nakd..... 59/12
UpTime (d:h:m:s).. 000:06:44:44 Aloha Starts................ 61
WakeUp Aloha Starts.......... 0 Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000 Frames Received............. 3830128
Addresses Open............... 7 Frame Errors: CRC/Bad Key... 2/0
Carrier Info....... 007:E:11272 Miscellaneous Problems...... 2
Rate Code........ 256k 4/5 (TC) No Receive Outroute Lock.... 0
Inroute Group................ 1 No FLL Lock................. 0
Inroute...................... 9 No Network Timing Sync...... 2014
IQoS ID...................... 4300    Current Modcod.............. 8-PSK 5/6 (15)

Ranging Reason: Ranging Done
Inroute Group Selection: Ranged at inroute rate selected by IQoS
Receive Status: Receiver operational. (RxCode 5)
Transmit Status: Transmitter ready. (TxCode 8)
--------------------------------------------------------------------------------
-----
TxMonitor
Tx Code [05].. 214
Tx Code [07].. 3
Tx Code [10].. 2
Concerned about TxCode-05 "Network Timing Sync" issues. Is that normal? What can cause this and the amount within the uptime?
--------------------------------------------------------------------------------
-------
------------ Signal Quality --------------
LDPC Bit ERR (in 1 LDPC) ... 0x0005
BCH Bit ERR (in 1 LDPC) .... 0x0
BCH Bit ERR (in 8 LDPC) .... 0x00
Error Pkt Cnt .............. 0x00010caa
Total Pkt Cnt .............. 0x1a3247e5
Per ........................ 1.5649E-04

Error BCH Frames ........... 0x0000072e
Total BCH Frame ............ 0x00bf23da
Error Ratio ................ 1.4673E-04

Channel Psedo BER Err ...... 0x003fffff
LDPC Psedo BER Err ......... 0x00000c00
Moving Average Over .........0x00000007 (Frames)

EsNo ....................... 11.448795
uwp SQF..................... 84
----------------------------------------------------------------------------
--- Histogram Since Last Lock ---
   Nominal FreqOffset: -3550 KHz
Initial Carrier FreqOffset: -28 KHz
Current Carrier FreqOffset: -35 KHz
------------------------------------------------------------------
--------- Allocated Inroute Message Statistics --------
Stream Messages ACK'd......... 451474 Stream Messages NAK'd....... 4540
NonStream Messages ACK'd...... 60    NonStream Messages NAK'd.... 12

Aloha Starts.................. 62    Ranging Starts.............. 0
WakeUp Aloha Starts........... 0       DNCC Busy................... 0

Allocated Stream Bytes........ 117853083 Used Stream Bytes........... 109623124

------------- General Transmit Statistics -----------
Tx Superframes Count.......... 787973 Tx Superframes Size......... 110221541

No Frame Information.......... 2       Not Sync'd to Network Timing 2057
No Receive Demod Lock......... 0       No FLL Lock................. 0
No Transmit Synth Lock........ 0       Miscellaneous Problems...... 2
--------------------------------------------------------------------------------
--------

Is there anything else I can do, other than continue peaking, if that is feasible? Also, I am going to request Public IPs due to continued timing out of DNS Proxy (25-35%) rate per hour. I am also wondering if I am getting enough power? I still have not gotten the RFI reading on my site from the HUB. Will be asking about that on Monday. Well thanks again Greg & Erick for your assistance.

Survived Afghan&&Surviving IRAQ&&HX50 2x 2048/256

IP Logged

USN - Retired

YaBB Moderator
★★★★★
Offline

Posts: 837
Kentucky (USA)

Reply #1 - Apr 27^th, 2009 at 5:14am

Yeah, 214 repetitions of TX5 is reason for concern. It means that your modem lost synchronization with the network timing loop 214 times - since it was last restarted I believe. You may possibly have noted that each TX5 is accompanied by the TX and System LEDs going out on the modem. Any packets that are in transit when that happens require retransmission, which accounts for the DNS timeouts. And your transmission errors still suck. Both symptoms - and the DNS timeouts - are consistent with an inroute problem. I'm just a little mystified though, why the Rate Code has stayed at 256k 4/5 all this time. Or are you in fact paying for a 512k plan?

I know the cable testing was tedious, but it's part of the process of elimination. Next you have to get the NOC to evaluate your transmitter isolation (POL) and check your carrier for signs of RFI. It would also be really helpful if someone in the area had a spare transmitter that you could borrow for a day.

But those new statistics now look like you actually went the wrong way when you tried to optimize the pointing angles. When done correctly, you should not have to "continue peaking". One good job of pointing and locking down the dish should hold through 70-80 mph winds. We had a baby hurricane blow through here last fall - 75 mph winds are pretty rare for Kentucky - my 98cm dish didn't budge. Or was the weather bad when they were recorded? Cuz I see SQF down a good seven points from the previously reported high of 89, and Current Modcod dropped back to 5/6. That said, these numbers could be related to weather issues at the NOC end as well, if the operators failed to increase power during a storm.

Anyway, you still have to eliminate POL error and local RFI and a weak transmitter. If/when all those check out ok, it's probably time to replace the modem. But I don't think it will get that far.

//greg//

USN (Ret)

IP Logged

keasley

Member
★★
Offline

Posts: 13
IRAQ

Reply #2 - Apr 28^th, 2009 at 2:51am

Spoke with the HUB about the TxCode(5), They said everything looks fine on their end. I ask that they evaluate my Transmitter Isolation (POL) and check for signs of RFI and they requested that I put in a ticket for for the evaluation and request a "Clean Carrier" (don't know what that means). I am submitting a ticket for that as I write this.

About what I am paying for, I am paying for 2 subscriptions on the HX50 "HX Corporate 2000 Plus plans, that is 2 x $1,132 per month (both are 2048/256 up/down).

The subscription plan I am paying for advertises this:
Hx Corporate 2000 Plus 2048 256 Hx Corporate 2000 Plus
GOS Average 1200 60 GOS Average
Level 1 Quota MB 700 90 Level 1 Quota MB
Penalty Kbps 512 45 Penalty Kbps
Level2 Quota MB 2200 150 Level2 Quota MB
Penalty Kbps 256 30 Penalty Kbps

The typicall system performance advertised:
   Peak Hours    Off Peak Hours
FTP Download
Minimum Burst    64 Kbps    64 Kbps
Maximum Burst       1200 Kbps       2048 Kbps
Average Throughput 900 Kbps       1200 Kbps

E-mail upload
Minimum Burst    16 Kbps    16 Kbps
Maximum Burst 120 Kbps 256 Kbps
Average Throughput 60 Kbps    80 Kbps

It is a hit and a miss about the GOS. I and other (who has BW service) experience slowness during late afternoon and evening hours daily, more so on the weekends. But we are assuming that it everyone fighting for the bandwidth. But overall, I am satisfied with the service. I just want to clear up the the Network timing and Transmission issues.

About the new statistics, the HUB was having bad weather when I was doing adjustments, several hours after I posted, I notice the signal strenght drop to 59 to 65 for about 45mins. I did have a chance to check the weather in England and it was thunderstorming. Guess no one was at home at the NOC during that time. I will keep monitoring and post updates as I get a "Clean Carrier" and Public IPs. thanks again Greg.

Ken

Survived Afghan&&Surviving IRAQ&&HX50 2x 2048/256

IP Logged

Eric Johnston

Senior Member
★★★
Offline

Posts: 2109

Reply #3 - May 1^st, 2009 at 10:56am

Here is some information intended to help anyone with a Prodelin dish with a mode matched feed (Feed has "505" marking on the top of the horn throat) and a giant circular polarisation scale behind the dish.

On the throat of the horn is a "505" marking. ?You must always have the 505 directly away from the feed arm and the fat lump, underneath, towards the feed arm.

You may adjust the polarisation to any required angle (though full 360 deg and for both Horizontal and Vertical) using the scale behind the dish.

These new design Prodelin dishes give superior cross-pol performance to all other single reflector antennas*, but only if you follow these assembly instructions above.

Best regards, Eric.

* except for ERA diamond antennas which use the same mode matched feed.

IP Logged

keasley

Member
★★
Offline

Posts: 13
IRAQ

Reply #4 - May 1^st, 2009 at 4:50pm

Eric & Greg,

Thanks for the replies. The Mode Matched Feed is assembled exactly as pictured. I added the 3.5degs to the POL on the back and did the rest of the assembly and alignment of the dish as you described in Eric's previous posts. I really do appreciate your work and post of how you assembled your HX50 modem and dish. Really helped me out a lot. I believe BW and I working together has gotten my site up and running alot better. See below.

Satellite Statistics Summary
------------------------------------
Network Time: FRI MAY 01 15:06:13 2009
------------------------------------
Adapter Main Statistics:
------------------------
Signal Strength.............. 87 Stream Msg-Ackd/Nakd........ 1517652/13664
Flags............... 0x00000000 NonStream Msg-Ackd/Nakd..... 171/17
Stream Error Rate....... 0.89% NonStream Error Rate....... 9.04%
UpTime (d:h:m:s).. 001:05:44:50 Aloha Starts................ 175
WakeUp Aloha Starts.......... 0 Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000 Frames Received............. 15616765
Addresses Open............... 7 Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 007:E:11272 Miscellaneous Problems...... 848
Rate Code........ 256k 4/5 (TC) No Receive Outroute Lock.... 0
Inroute Group................ 1 No FLL Lock................. 0
Inroute...................... 6 No Network Timing Sync...... 3354
IQoS ID...................... 4300    Current Modcod.............. 8-PSK 8/9 (16)
--------------------------------------------------------------------------------
----------------
------------ Signal Quality --------------
MPEG2 Pkt Discard Config.... 0 (discard if BCH or CRC Error)
LDPC Bit ERR (in 1 LDPC) ... 0x0277
BCH Bit ERR (in 1 LDPC) .... 0x0
BCH Bit ERR (in 8 LDPC) .... 0x00
Error MPEG2 Pkt Cnt ........ 0x000495d4
Total MPEG2 Pkt Cnt......... 0x7cf75434
MPEG2 Pkt Error Rate ....... 1.4333E-04

Error BCH Frame Cnt ........ 0x00001f2b
Total BCH Frame Cnt ........ 0x0387eaf9
BCH Frame Error Rate ....... 1.3469E-04

Channel Psedo BER Err ...... 0x003fffff
LDPC Psedo BER Err ......... 0x000016c0
Moving Average Over .........0x00000007 (Frames)

EsNo ....................... 12.028715
uwp SQF..................... 88
----------------------------------------------------------------------------
TxMonitor
Tx Code [05].. 373 [00:00:02:31]
---------------------------------------------------------------------------
CLP Stats
Close Loop Power Control Statistics
-------------------------------------------------------
Current Inroute Type ... 1       Sun Outage occurred ..... 0
Current SymRate ........ 256    Current FecRate ......... 4
Global update count .... 0       Update reset count ...... 244
ULFE bin size .......... 5       ULFE bin count .......... 57
Stream SINR feedback ... 88    Aloha SINR feedback ..... 0
Current PCE ............ -0.823997 Current STF ............. -2.617559
Current Bin ID ......... 11    Current Bin Value ....... 14.160884
Power Mode ............. 0       Current Power Setting ... 44
Tx power increments .... 2149062    Tx power decrements ..... 238777
STF over upper limit ... 0       STF over lower limit .... 35756
Max power occurred ..... 70946

Max PCE ................ 77.176003 Min PCE ................. -59.823997
Max STF ................ 20.224565 Min STF ................. -51.877680
Too Low Feedback ....... 5       Too High Feedback ....... 0

256 1/2 : Max EsNo 99 @ Power Setting 52, Min EsNo 26 @ Power Setting 126
256 2/3 : Max EsNo 96 @ Power Setting 1, Min EsNo 49 @ Power Setting 100
256 4/5 : Max EsNo 105 @ Power Setting 39, Min EsNo 10 @ Power Setting 103

Mean Power Contrl Err (clear sky) ... 0.000000 Variance Power Contrl Err (clear sky) ... 0.000000
Mean Power Contrl Err (rain) ........ -0.317500 Variance Power Contrl Err (rain) ........ 36.673037
--------------------------------------------------------------------------------
--------
AIS Stats
Adaptive Inroute Selection (AIS) Statistics
-------------------------------------------------------
Current Rate................ 256 4/5 AIS Preferred Rate........... 256 4/5
AIS Highest Rate............ 256 4/5 AIS Lowest Rate.............. 256 1/2
Total PC Ingress........... 1031       Total Egress ................ 527
Total Aloha Ingress........ 0    Total Egress Due to GLB ..... 0
Last AIS Type ............. Egress    Number of Stream Runs ....... 1271846

Reference Delta Power....... 64 Average Delta Power.......... 29
Current Power Adjustment.... 26 Delta Uplink Power........... 35
--------------------------------------------------------------------------------
--------------

I still have the TxCode(5)/No Network Timing Sync issues plus I manually turned off the Turbo Page due to too many 504 and other TPC/TPS errors. I am also getting numerous DNS Proxy errors, I believe that to be latency issues (inroute or outroute; can't remember which one from my side). Other than that, my site is running alot better.

I am constantly monitoring and keeping logs of what is happening here for my sake and troubleshooting. I do appreciate all the assistance I have gotten from both of you. Thanks again. Ken

Survived Afghan&&Surviving IRAQ&&HX50 2x 2048/256

IP Logged

USN - Retired YaBB Moderator ★★★★★ Offline Posts: 837 Kentucky (USA)	Reply #5 - May 1^st, 2009 at 6:53pm I still believe all your problems are related to an inroute issue. Pretty sad that you can't get the NOC to look at your carrier. Tx error rate still sux (compared to most that is). But you mentioned DNS proxy errors. I understand DNS errors, but why are you using a proxy? //greg//
Back to top	USN (Ret) IP Logged

Pages: 1

Send Topic | Print

Disclaimer, Terms of Use and Privacy Forum User Agreement Forum rules Cookie policy.