Pages: 1

HX50 with LintasArta

(Read 8072 times)

portalindo

Member
★★
Offline

Posts: 5
Indonesia

May 1^st, 2012 at 5:33am

Hi all, i'm a newcomer to this forum, and with hx50 systems as well, i hope there's somebody could answer my questions below :
My longitude is 99 deg 18 min east, latitude 1 deg 54 south, 113 east for my satellite using ku-band 128k/512k service, the best and maximum sqf that i got is around 58-60 sometimes without pointing the antenna the signal rise to 80, i've been using the service for about 8 months by now, the last 2 months the access always drop between 9am to 9pm, at that time even to resolve the dns is hard and the ping time is about >3000ms. But between 9pm to 9am the access back to normal, below is my summary and ranging report

Satellite Statistics Summary
------------------------------------
Network Time: TUE MAY 01 11:45:51 2012
------------------------------------
Adapter Main Statistics:
------------------------
Signal Strength.............. 60 � � �Stream Msg-Ackd/Nakd........ 10932/868
Flags............... 0x00000000 � � � NonStream Msg-Ackd/Nakd..... 29/2
Stream Error Rate....... � 7.36% � � �NonStream Error Rate....... � 6.45%
UpTime (d:h:m:s).. 000:00:51:60 � � � Aloha Starts................ 29
WakeUp Aloha Starts.......... 0 � � � Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000 � � � Frames Received............. 83980
Addresses Open............... 7 � � � Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 113:E:20620 � � � Miscellaneous Problems...... 0
Rate Code........ �256k 4/5 (TC) � � �No Receive Outroute Lock.... 0
Inroute Group................ 2 � � � No FLL Lock................. 0
Inroute...................... 6 � � � No Network Timing Sync...... 0
IQoS ID...................... 3 � � � Current Modcod............... 8-PSK 2/3 (13)

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 )

Ranging Stats

------------------------------------
Network Time: SUN FEB 26 14:40:48 2012
------------------------------------
State: Not Currently Ranging

Previous Ranging Info [1]
Previous Ranging Info [2]
Previous Ranging Info [3]
Previous Ranging Info [4]
Previous Ranging Info [5]
--------------------------------------------------------------------------------

Successful Rates � � �| Unsuccessful Rates � �| Failed Rates � � � � �|
----------------------+-----------------------+-----------------------+
512k Turbo Code 1/2 � � � � � � � � � � � � � � 512k Turbo Code 2/3 � �
� � � � � � � � � � � � � � � � � � � � � � � �512k Turbo Code 4/5 � �
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �
--------------------------------------------------------------------------------

NOC-Sat Delay (AnE).......... 2392971 � Remote-Sat Delay (BnD).... 2411077
Remote Distance To Sat (D)... 960745 � �SFNP Interval............. 3600000
Ranging ID................... 16 � � � �Network Ranged On (L:H:F). 113:E:2062
NOC ID....................... 0 � � � � Ranged In Bootstrap Mode.. 1
Ranging Record Version....... 1 � � �

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

Rate......................... 512k Turbo Code 1/2 � �

Available.................... 1 � � � � Ranging Reason............. 3
Ranging Sessions Required.... 0 � � � � Minimum EsNo............... 34
Target EsNo.................. 44 � � � �SwitchUp EsNo.............. 180
Initial Power Setting........ 0 � � � � Final Power Setting........ 31
Initial Received EsNo........ 55 � � � �Final Received EsNo........ 44
Initial Received C/No........ 626 � � � Final Received C/No........ 615
Outroute SQF................. 54 � � � �Outroute C/No.............. 801
Initial Timing Offset........ 235 � � � Final Timing Offset........ 236
Power Control Type........... PWM � � � Estimated Rate............. Yes
Coding Type.................. BCH � � � Inroute Group ID Ranged.... 1

i dont know how to read the stats report, but after i search a few in this forum, i'm confuse with my ranging stats, how could i get a better ranging ? or is someone could tell me what should i do to make the access back to normal again? FYI my provider never mention about FAP things, and i know that because i already download many Gbytes without having problem with the connection or get the connection slowed �before.

May be i dont know where to start to search for the solution, but why the problem happens after 6 months without a problem? Please somebody enlight me, i do desperate with pointing things cause it doesnt make any different or any improvement with my access

Thanks

« Last Edit: May 1^st, 2012 at 9:51am by Admin1 »

YIM

IP Logged

Eric Johnston

Senior Member
★★★
Offline

Posts: 2109

Reply #1 - May 1^st, 2012 at 9:45am

Your polarisation setting may be slightly wrong.

What is your polarisation scale reading ?

A polarisation error, like 10 deg, would have little effect on your receive SQF, provided there is no one using the opposite polarisation. This may have been the case for your first six months operation and, recently, during the night 9pm - 9am. �Maybe some new, part time, daytime only, satellite service started 2 months ago. �Any error in your polarisation makes you vulnerable to cross-pol interference. Check your polarisation angle. �An error of 8 deg would definitely cause your symptom (SQF drops from 80 to 60 between 9am and 9pm) if someone else transmits during this period.

According to my calculations using https://www.satsig.net/maps/lat-long-finder.htm
your polarisation adjustment angle amount should be +82 deg clockwise, as viewed facing towards the satellite in the sky.

If you look at the circular white scales on the two yokes that hold the transmit/receive radio assembly you will see scales like this below:

Setting the polarisation is a two step process.
First set to nominal. Rotate until the tick mark is either at the centre bottom (zero) or at the side (90 deg). Which of these two options depends on the name of the polarisation you have been told to use. Sideways = Vertical name receive polarisation.
Second apply the adjustment amount. Consider the view in the direction towards the satellite in the sky. Then apply the adjustment amount; positive is clockwise. Note that the scale reading numbers may be misleading, going forwards or backwards from 0 or 90, so simply count the amount of adjustment required along the scale, ignoring the numbers.
In the example scale above the initial setting was sideways (vertical name receive polarisation) amount and the adjustment was +34 deg clockwise.

In your case, once +82 deg clockwise is applied you will end up with the tick mark at either +8 or -82 on the scale. �If you look at the scale at the other end, near the feed horn, the signs will the the other way round.

Whatever, the adjustment amount is +82 deg clockwise, as viewed while facing towards the satellite and starting at either 0 or 90. One option will be correct.

In your case you are already about right so all you need to do is loosen the clamps and make a small adjustment.

Best regards, Eric.

IP Logged

portalindo

Member
★★
Offline

Posts: 5
Indonesia

Reply #2 - May 1^st, 2012 at 12:27pm

Dear Mr Eric

Thanks alot for your fast response, i'm forget to mention that the equipment is 2nd hand, the dish itself is not hughes products, so i dont have that scales ring over the buc, but i will try use inclinometer instead, say that my rx polarization vertical and tx polarization is horizontal, its state in my modem manual commissioning page, the real look is lnb vertical and also the buc, should i made a change like the one in the commissioning page first before i make adjustment to buc polarization?

Regards
Portalindo Kasri �

YIM

IP Logged

Eric Johnston

Senior Member
★★★
Offline

Posts: 2109

Reply #3 - May 1^st, 2012 at 1:06pm

Your BUC/LNB should only look vertical/horizontal when the satellite is exactly due south, due north, due east or due west of your location.

In your case, the satellite is about 5 deg to the left of due east. �So your BUC/LNB should be tilted +82 deg clockwise or -8 deg anticlockwise.

ref: https://www.satsig.net/maps/lat-long-finder.htm

If you have your BUC/LNB approx upright right now it is about right as you are getting a reasonable signal. It has already been turned about 90 deg clockwise. �Turn it 8 deg anticlockwise, while facing towards the satellite.

If you use an inclinometer, put it sideways across the body of the BUC/LNB and tilt it down a little on the left (north) side, to get 8 deg slope. �
wxw
Best regards, Eric.

IP Logged

portalindo

Member
★★
Offline

Posts: 5
Indonesia

Reply #4 - May 2^nd, 2012 at 5:36am

Hi Mr Eric

You are truly live savior, it almost mid day at my place when i post this, the speed kinda slower because of the peak hour i think, but not dead as usual. I got better sqf around 70 by now, ping time avg 1500ms with full traffic on my router to the internet.

Thanks alot for you explanation to a newbie like me, hope there will be no problem in the future.

Regards
Portalindo Kasri

YIM

IP Logged

USN - Retired YaBB Moderator ★★★★★ Offline Posts: 837 Kentucky (USA)	Reply #5 - May 2^nd, 2012 at 12:16pm Please post a current modem statistics summary like that in your opening post. I'd like to see to what degree you were able to improve transmission. //greg//
Back to top	USN (Ret) IP Logged

portalindo

Member
★★
Offline

Posts: 5
Indonesia

Reply #6 - May 2^nd, 2012 at 4:20pm

Hi Mr Greg,

This is my reports after 5-6hours running, cause of the power failure.

Satellite Statistics Summary
------------------------------------
Network Time: WED MAY 02 22:39:21 2012
------------------------------------
Adapter Main Statistics:
------------------------
Signal Strength.............. 63 � � �Stream Msg-Ackd/Nakd........ 443626/1
Flags............... 0x00000000 � � � NonStream Msg-Ackd/Nakd..... 5/0
Stream Error Rate....... � 0.00% � � �NonStream Error Rate....... � 0.00%
UpTime (d:h:m:s).. 000:05:02:24 � � � Aloha Starts................ 4
WakeUp Aloha Starts.......... 1 � � � Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000 � � � Frames Received............. 2125376
Addresses Open............... 7 � � � Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 113:E:20620 � � � Miscellaneous Problems...... 1
Rate Code........ �256k 4/5 (TC) � � �No Receive Outroute Lock.... 16
Inroute Group................ 2 � � � No FLL Lock................. 428
Inroute...................... 5 � � � No Network Timing Sync...... 0
IQoS ID...................... 3 � � � Current Modcod............... 8-PSK 2/3 (13)

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 )

Ranging Stats

------------------------------------
Network Time: WED MAY 02 22:41:04 2012
------------------------------------
State: Not Currently Ranging

Previous Ranging Info [1]
Previous Ranging Info [2]
Previous Ranging Info [3]
Previous Ranging Info [4]
Previous Ranging Info [5]
--------------------------------------------------------------------------------

Successful Rates � � �| Unsuccessful Rates � �| Failed Rates � � � � �|
----------------------+-----------------------+-----------------------+
256k Turbo Code 1/2 � � � � � � � � � � � � � � 512k Turbo Code 2/3 � �
256k Turbo Code 2/3 � � � � � � � � � � � � � � 512k Turbo Code 4/5 � �
256k Turbo Code 4/5 � � � � � � � � � � � � � � � � � � � � � � � � � �
512k Turbo Code 1/2 � � � � � � � � � � � � � � � � � � � � � � � � � �
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �
--------------------------------------------------------------------------------

NOC-Sat Delay (AnE).......... 2392971 � Remote-Sat Delay (BnD).... 2410345
Remote Distance To Sat (D)... 960527 � �SFNP Interval............. 3600000
Ranging ID................... 16 � � � �Network Ranged On (L:H:F). 113:E:2062
NOC ID....................... 0 � � � � Ranged In Bootstrap Mode.. 1
Ranging Record Version....... 1 � � �

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

Rate......................... 256k Turbo Code 1/2 � �

Available.................... 1 � � � � Ranging Reason............. 0
Ranging Sessions Required.... 0 � � � � Minimum EsNo............... 34
Target EsNo.................. 44 � � � �SwitchUp EsNo.............. 0
Initial Power Setting........ 0 � � � � Final Power Setting........ 142
Initial Received EsNo........ 114 � � � Final Received EsNo........ 44
Initial Received C/No........ 655 � � � Final Received C/No........ 585
Outroute SQF................. 64 � � � �Outroute C/No.............. 810
Initial Timing Offset........ 0 � � � � Final Timing Offset........ 0
Power Control Type........... PWM � � � Estimated Rate............. Yes
Coding Type.................. BCH � � � Inroute Group ID Ranged.... 2

Timestamp.................... APR 30 08:14:35 (GMT) 2012

Rate......................... 256k Turbo Code 2/3 � �

Available.................... 1 � � � � Ranging Reason............. 0
Ranging Sessions Required.... 0 � � � � Minimum EsNo............... 60
Target EsNo.................. 70 � � � �SwitchUp EsNo.............. 0
Initial Power Setting........ 0 � � � � Final Power Setting........ 102
Initial Received EsNo........ 114 � � � Final Received EsNo........ 70
Initial Received C/No........ 655 � � � Final Received C/No........ 611
Outroute SQF................. 64 � � � �Outroute C/No.............. 810
Initial Timing Offset........ 0 � � � � Final Timing Offset........ 0
Power Control Type........... PWM � � � Estimated Rate............. Yes
Coding Type.................. BCH � � � Inroute Group ID Ranged.... 2

Timestamp.................... APR 30 08:14:35 (GMT) 2012

Rate......................... 256k Turbo Code 4/5 � �

Available.................... 1 � � � � Ranging Reason............. 3
Ranging Sessions Required.... 3 � � � � Minimum EsNo............... 76
Target EsNo.................. 120 � � � SwitchUp EsNo.............. 180
Initial Power Setting........ 0 � � � � Final Power Setting........ 0
Initial Received EsNo........ 114 � � � Final Received EsNo........ 117
Initial Received C/No........ 655 � � � Final Received C/No........ 658
Outroute SQF................. 64 � � � �Outroute C/No.............. 810
Initial Timing Offset........ 386 � � � Final Timing Offset........ 468
Power Control Type........... PWM � � � Estimated Rate............. No
Coding Type.................. BCH � � � Inroute Group ID Ranged.... 2

Timestamp.................... APR 30 06:33:48 (GMT) 2012

Rate......................... 512k Turbo Code 1/2 � �

Available.................... 1 � � � � Ranging Reason............. 0
Ranging Sessions Required.... 0 � � � � Minimum EsNo............... 34
Target EsNo.................. 56 � � � �SwitchUp EsNo.............. 0
Initial Power Setting........ 0 � � � � Final Power Setting........ 43
Initial Received EsNo........ 72 � � � �Final Received EsNo........ 56
Initial Received C/No........ 643 � � � Final Received C/No........ 627
Outroute SQF................. 53 � � � �Outroute C/No.............. 798
Initial Timing Offset........ 0 � � � � Final Timing Offset........ 0
Power Control Type........... PWM � � � Estimated Rate............. Yes
Coding Type.................. BCH � � � Inroute Group ID Ranged.... 1

Timestamp.................... APR 24 03:46:18 (GMT) 2012

Could you tell me how to read that report ?

Regards
Portalindo Kasri

« Last Edit: May 4^th, 2012 at 8:06am by Admin1 »

YIM

IP Logged

USN - Retired

YaBB Moderator
★★★★★
Offline

Posts: 837
Kentucky (USA)

Reply #7 - May 2^nd, 2012 at 9:45pm

Adjusting the POL angle seems to have done a very good job of taking down the transmission errors. Your modem is only reflecting 5 hours up up time, but zero error percentage speaks for itself.

But I think you're still not quite on the beam as far as Azimuth and/or Elevation. Correcting the POL angle fixed the error rate, while leaving your Rate Code unchanged. But I can't help but think a higher signal strength might improve that Current Modcod. I've only got a 98cm dish, and I have a signal strength of ~87 and a normal Modcod of 8psk 5/6 (15). On the rare day when my SS jumps to 92 or higher, the Modcod actually hits 8pak 9/10 (17). That's the top of the scale.

If you're happy with where you're at, no problem. It's just that the higher the SS and Modcod, the greater the rain fade margin. Pretty sure it's just a matter of a little more optimization of your Az and/or El. In case I'm wrong - if it's simply a matter of a weak transponder - mark the scales before you try to optimize. That makes it easier to fall back to where you started.

//greg//

USN (Ret)

IP Logged

portalindo

Member
★★
Offline

Posts: 5
Indonesia

Reply #8 - May 3^rd, 2012 at 7:06pm

Hi Mr Greg,

Thanks for your advice, the stats below is the result for that :
Satellite Statistics Summary
------------------------------------
Network Time: FRI MAY 04 01:26:51 2012
------------------------------------
Adapter Main Statistics:
------------------------
Signal Strength.............. 75 � � �Stream Msg-Ackd/Nakd........ 845718/77
Flags............... 0x00000000 � � � NonStream Msg-Ackd/Nakd..... 19/0
Stream Error Rate....... � 0.01% � � �NonStream Error Rate....... � 0.00%
UpTime (d:h:m:s).. 000:07:02:25 � � � Aloha Starts................ 18
WakeUp Aloha Starts.......... 1 � � � Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000 � � � Frames Received............. 3079536
Addresses Open............... 7 � � � Frame Errors: CRC/Bad Key... 4/0
Carrier Info....... 113:E:20620 � � � Miscellaneous Problems...... 0
Rate Code........ �256k 4/5 (TC) � � �No Receive Outroute Lock.... 17
Inroute Group................ 2 � � � No FLL Lock................. 428
Inroute...................... 3 � � � No Network Timing Sync...... 0
IQoS ID...................... 3 � � � Current Modcod............... 8-PSK 3/4 (14)

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 )

thats the highest that i could get, the speed more stable by now. Anyway i got another problem, with C-band still with the same provider, i will post it later when i'm on the site, but for this site, i'm very happy now Cheesy

.

Thank heaps for guiding me for mr eric and mr greg

Regards,
Portalindo Kasri

« Last Edit: May 4^th, 2012 at 8:06am by Admin1 »

YIM

IP Logged

USN - Retired YaBB Moderator ★★★★★ Offline Posts: 837 Kentucky (USA)	Reply #9 - May 4^th, 2012 at 12:32am Excellent, glad it worked. You'll appreciate the additional rain fade margin //greg//
Back to top	USN (Ret) IP Logged

Pages: 1

Send Topic | Print