SatSig topic:

HX50 Issues, Please Help

(Read 10941 times)

Oct 27^th, 2009 at 8:34pm

I am having some issues with my HX50.

I am in Iraq, my signal strength has been at 92 for months, everything has been working just fine until yesterday when the system was going in and out.

Weather has been fine, dish is still at 92 signel. It seems to pull up google 95% of the time but anything past that doesn't want to work.

Been getting

Terminal Receive Error (603)

Web Acceleration Client Error (509.2) - Upstream TCP Receive Failure (Web Server)

from time to time along with a couple others, been writing everything down

Network Time: TUE OCT 27 21:08:42 2009
------------------------------------

Adapter Main Statistics:
------------------------
Signal Strength.............. 83
Stream Msg-Ackd/Nakd........ 36128/18
Flags............... 0x00000000
NonStream Msg-Ackd/Nakd..... 198/16
Stream Error Rate....... 0.05%
NonStream Error Rate....... 7.48%
UpTime (d:h:m:s).. 000:00:49:26
Aloha Starts................ 194
WakeUp Aloha Starts.......... 0
Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000
Frames Received............. 271312
Addresses Open............... 7
Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 007:E:11272
Miscellaneous Problems...... 0
Rate Code........ 256k 1/2 (TC)
No Receive Outroute Lock.... 2731
Inroute Group................ 1
No FLL Lock................. 869
Inroute...................... 7
No Network Timing Sync...... 260
IQoS ID...................... 4300
Current Modcod............... 8-PSK 8/9 (16)

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 )

any ? please ask

Oct 27^th, 2009 at 9:47pm

Well, I see signal strength of 83. Not 92. And your Rate Code sucks. This suggests that either your dish moved, or something's partially blocking it. I'm guessing those errors you're seeing are caused by the resultant packet loss.

//greg//

Oct 28^th, 2009 at 6:59am

I have the same issues as you. I have had good service up until yesterday. Now I get DNS errors and when I ping it only get a reply 25% of the time. There site says everything is okay but something is not okay. Does your Accelnet work. I do not use it that much but it does not connect to the server anymore. And my strenght is also always 88-91.

------------------------------------
Network Time: WED OCT 28 07:01:21 2009
------------------------------------

Adapter Main Statistics:
------------------------
Signal Strength.............. 91
Stream Msg-Ackd/Nakd........ 16651/0
Flags............... 0x00000000
NonStream Msg-Ackd/Nakd..... 1067/280
Stream Error Rate....... 0.00%
NonStream Error Rate....... 20.79%
UpTime (d:h:m:s).. 000:03:37:19
Aloha Starts................ 2254
WakeUp Aloha Starts.......... 1
Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000
Frames Received............. 1252978
Addresses Open............... 7
Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 021:E:13794
Miscellaneous Problems...... 1
Rate Code........ 256k 4/5 (TC)
No Receive Outroute Lock.... 19
Inroute Group................ 1
No FLL Lock................. 471
Inroute...................... 1
No Network Timing Sync...... 175
IQoS ID...................... 1
Current Modcod............... 8-PSK 8/9 (16)

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 )

Oct 28^th, 2009 at 9:16am

This is Bentley Walker, we are aware of this problem and it is being investigated, please don't adjust your equipment at this time as it looks like an ISP upstream problem, I will advise you soon as its rectified.

A Walker

Oct 28^th, 2009 at 9:32am

Thanks, Do you ever rest. You gotta take a break sometimes. But as a cutomer I am very happy you work hard to make us happy.

Oct 28^th, 2009 at 10:19am

Unless it was a one-time occurrence when those stats were snapshot, Sooby's reduced SQF and FEC rate warrants further investigation as well

//greg//

Oct 28^th, 2009 at 11:43am

Dear All

The issue turned out to be a problem with the upstream ISP which has been resolved , we will work with the customer to improve his modulation code

A Walker

Oct 28^th, 2009 at 12:47pm

Looks Like Things are back up and running, just got off work so good so far.

Thanks A Walker

Network Time: WED OCT 28 12:44:06 2009
------------------------------------

Adapter Main Statistics:
------------------------
Signal Strength.............. 92
Stream Msg-Ackd/Nakd........ 1058/0
Flags............... 0x00000000
NonStream Msg-Ackd/Nakd..... 16/1
Stream Error Rate....... 0.00%
NonStream Error Rate....... 5.88%
UpTime (d:h:m:s).. 000:00:02:22
Aloha Starts................ 16
WakeUp Aloha Starts.......... 0
Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000
Frames Received............. 13605
Addresses Open............... 7
Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 007:E:11272
Miscellaneous Problems...... 0
Rate Code........ 256k 2/3 (TC)
No Receive Outroute Lock.... 26
Inroute Group................ 1
No FLL Lock................. 430
Inroute..................... -1
No Network Timing Sync...... 16
IQoS ID...................... 4300 Current Modcod............... 8-PSK 8/9 (16)

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)

Oct 28^th, 2009 at 1:25pm

Quote:

, we will work with the customer to improve his modulation code

Actually - assuming an earlier BW statement that 9/10 rate not being available still holds true - the ModCod is ok. It's the FEC part of the Rate Code that warrants attention. The first stat suggested it could have been on the verge of falling back to 128k. By comparison, my SQF is currently 83, with (the max authorized) Rate Code of 256k 4/5 (TC). SQF and Rate Code recovered somewhat in the 2nd set, but FEC remains short of the desired 4/5 rate. POL angle maybe?

Plus - both sets of stats reflect a very short uptime. I'd be curious why it appears this modem restarts more than usual. Mine runs for weeks at a time without ever seeing a restart. Last time for example, was 11 days ago when I swapped out an UPS.

//greg//

Oct 28^th, 2009 at 1:53pm

Regarding receive signal quality at a remote site (SQF)

If the value has been around 92 for a long time and now is around 82 then something has changed, e.g. lower transmit power from the teleport, rain fade at teleport or remote site, cross pol carrier started interfering, and quite likely: remote site dish has become mispointed or LNB cable corroded.

It is important to point dishes accurately to the maximum SQF value, whatever that value may be. Different networks (e.g. Iraq and USA) will have different peak values as will different sites in the same network, according to location in the downlink beam pattern. Just to get the value above some idea of a good enough signal (e.g. 75 or more) is not acceptable. The reason is that you must get the receive beam accurately centered (peaked SQF) so that the narrower transmit beam is centered also. When the satellite downlink power is very high is quite possible to have good quality downlink but still be mispointed so far off that the remote site uplink is struggling. This being indicated by it having to drop down from say 4/5 to 2/3 to 1/2 rate code. This should normally happen only during heavy rain to keep the service working.

When I saw the first posting above (Receive SQF reduced from 92 to 83 and transmit Rate Code down to 1/2, my thoughts were the same as Greg: Dish mispointed causing both receive and transmit to deteriorate simultaneously. Water inside the feed horn or obstruction can cause simultaneous deterioration in both directions.

sooby25rs Can you tell us what was done to restore your SQF back up from 83 to 92 ?

Best regards, Eric.

Oct 28^th, 2009 at 5:10pm

My issues with the system first started 2 or 3 days ago, before we had a storm come through last night. When I posted the first time with th 82 was during a little ran before the storm came in, I said I normal have a 93 because the system for the most part has been running for the past 3-4 months with no major problems. After the storm came through it moved my dish about a inch or so enough for me to lose all signel... Seeing as I had to go to work I shut the system down to work on it after I got back, started everything back up moved the dish a inch or so got my singal back to 91, the system updated and restarted and thats when I posted the system stats, that being the reason why the short up time.

I don't have the dish itself polarized but instead I have my LNB at the 45ish degrees nagitive i think, been thinking of changing it to have the LNB at 0 and the dish canted?

Oct 30^th, 2009 at 11:12am

Quote:

I don't have the dish itself polarized but instead I have my LNB at the 45ish degrees; been thinking of changing it to have the LNB at 0 and the dish canted

If you have the modern 1.2m Prodelin dish with a large polarisation scale on a grey wedge shaped plastic boss behind the dish and a feed horn throat marked with a "505", then..

The feed horn must be set so that the 505 is always directly away from the feed arm. The fat lump on the opposite side of the feed throat will be directly underneath towards the feed support arm. This applies regardless of polarisation setting.

The polarisation should be set by turning the entire dish.

Best regards, Eric

Oct 30^th, 2009 at 7:22pm

I am using the 1.8 dish, not the 1.2, the feed horn is set right the the whole LNB is what i am using for my polarisation, i am going to put my LNB back to 0 degrees and move the dish to my 45 degrees polisation when i can tomorrow

Oct 30^th, 2009 at 8:55pm

Worth doing if your feed horn throat has "505" on it. Set the feed horn so that the "505" is directly away from the feed support arm, then turn the entire dish for the polarisation adjustment (assuming a wedge shaped boss and giant circular polarisation scale behind the dish).

If your feed horn throat does not have "505" on it there will be no benefit. The tiny picture on this page satellite dish pointing angles Iraq shows how the LNB will look as viewed, with you standing behind the dish and looking over top of the dish towards the satellite. The exact polarisation adjustment angle is given for your location.

Best regards, Eric.

Oct 31^st, 2009 at 12:04am

Quote:

i am going to put my LNB back to 0 degrees and move the dish to my 45 degrees polisation when i can tomorrow

Earlier you said you were set at "45ish degrees nagitive". Since you've only generally described your location as Iraq, I don't know how accurate the 45 part is. Be aware that to minimize phase distortion and adjacent satellite interference, the POL angle should be accurate to within 1 degree. But from anywhere in Iraq to W3A, the POL angle should be positive. That is, rotated clockwise as viewed from behind the dish. That holds true regardless of whether you rotate the TRIA or the reflector itself.

//greg//

Oct 31^st, 2009 at 1:00pm

Ar Remadi is my location, for some odd reason i forget what sat i am bouncing off of, and yes i am positive not nagative POL

Oct 31^st, 2009 at 2:17pm

Look at your config page to see what satellite longitude.
Then the calculator page will give you the exact polarisation adjustment amount.

Best regards, Eric.