posted
Last week I relocated, when I deployed could not get Tx lock. I called MS and they downloaded an options file that got it going. Just relocated again today and again cannot get Tx lock. Is this happening to anyone else? I'm sure many of you are tired of my moaning, but something just does not seem right that this keeps happening and nothing I can do until MS business hours.
posted
It is finally online. Though Sunday, I called Franco's cell and left a message. Not sure if he monitors calls on the weekends and is able to bump the config or if something else was up and it cleared itself...
posted
In my limited experience, most of the time when I've had trouble getting TX Lock it has been because the initial TX power value is too low to get it to "catch." For example starting at -26 when I needed -17.
Waiting it out eventually works, but a new options file with a better starting number is the "solution."
Unfortunately the amount of power needed is not uniform throughout the footprint.
Are you using our iDModTool at all? Since John and I put it together I've been using it steadily, and it really gives me a handle on where my TX power settles at any given location.
If you use it now it will show your current value, and you can compare with what your options file says (telnet, then options show) for initial power.
posted
Did the tx LED come on at all? If not, they likely had you deactivated (that is speculation, so treat it as such). When that happens, it could be a number of things (again, specualtion).
The fact that they had to push you leads me to believe they possibly:
1. changed the upstream bit_rate(s) for the inroute group (possibly making them bigger or smaller). Check your bit rates to see if they are the same. 2. Adjusted your entry power. The contour line you were previously operating at may have required less power. (this also plays into #1, above, because if the carrier specs changed, you might need more power as well).
The fact that you required a push to enter the upstreams, points to a tx power adjustment. Especially if your upstream bit_rates havent changed. However, in that type of scenario your TX LED would be on as you would be attempting to burst in.
-------------------- Mike Posts: 567 | From: North Carolina | Registered: May 2007
| IP: Logged |
posted
Oh yes, it kept trying. I typically watch the D3 status page more than the D3 panel (in the back, in a cabinet), but every few seconds the Tx status would say "... available for Normal Operations", at which time I suspect the Tx light is on as it tries to connect but when it does not get ACQ! it goes back to "disabled". Does this endlessly.
When I first deployed, did not check bit rates, but noticed my Tx power was -17dB and it would not connect. Now that it is connected, I see it is -11.20dB. I guess I could use some guidance as to what to do when I deploy but can't get Tx lock in a reasonable amount of time, especially when outside of MS working hours.
Seems we need an EtherSat "Life Alert" system where I can push a button and say "I've fallen offline and I can't get online!" Waiting and wondering is not working for me.
quote:Originally posted by DonB: Are you using our iDModTool at all? Since John and I put it together I've been using it steadily, and it really gives me a handle on where my TX power settles at any given location.
No, I have not downloaded that utility. I will check it out, but from your brief description not sure how that helps solve my problem of not being able to get online when I move.
As I said, when I first deployed, it was trying to connect at -17dB. I just checked my options file and my tx power is set to -14, so I assume Franco must have picked up my message and tweaked my settings. Also, since my last post, Tx power is now at -10dB. That is pretty hot, isn't it?
So does the 3100 steadily increase Tx power as it tries to connect and fails? A better understanding of what happens as it tries to get online would help, as well as what I should do when it is struggling, especially outside of MS hours.
posted
No, it does not increase power to connect. If it is set to -17 it will stay -17 until lock, and in my experience if you need -10 you will probably never lock at -17. Changes to power only occur after connection.
I have only seen a need for -10 (which is about the max your transmitter is built for) when beam 2 in Cheyenne was failing a few weeks ago, before they moved us to beam 1, and earlier this week when I was on the fringe of the footprint AND skimming a tree.
posted
If it was trying (to TX) then that confirms you were in fact activated on the hub and the upstreams more than likely had not changed. So, the push was indicitave of a power adjustment (in your opt).
As Don mentioned above, the initial power max is the max, and until they adjust it in your opt (or you adjust it yourself in notepad and plug it back in the remote), it will not venture above the max. When you move from contour line to contour line (which is common for you migratory RVer's) your initial tx value is a moving target.
-------------------- Mike Posts: 567 | From: North Carolina | Registered: May 2007
| IP: Logged |
posted
This morning, I see my Tx power is -9dB. In my options file, I see the following parameters:
tx_power_in_dbm = -14.000000
[UCP] max_power_level_in_db = -9.000000
Is this telling me my initial power will be -14dB and then AFTER connecting (if I can), the system can crank it up as high as -9 if needed?
This just seems to be a flaw in the system to me. These are billed as "mobile internet systems", but I am beginning to understand and need to accept that when I move I should NOT be surprised when I cannot connect without intervention from the network admin.
Or possibly it will connect after an hour or two when one of my "weak" transmissions finally filters into the system? As with this last time, not sure if it was the passage of time (well over an hour) or Franco responding to my phone message that made it connect.
posted
Originally posted by TK: Is this telling me my initial power will be -14dB and then AFTER connecting (if I can), the system can crank it up as high as -9 if needed?
Exactly. The big question remains: Why do you need such high power? That seems very worrisome to me. What are your weather conditions?
not sure if it was the passage of time (well over an hour) or Franco responding to my phone message that made it connect.
Since you said it was trying at -17, and now the opt shows -14 initial, there had to be a new opt file sent. I can't say if it was before or after you got TX lock.
posted
Scott called earlier saying my upstream c/n is low. I get this call every couple of weeks it seems. They normally have me do a dish calibration, but this time he wants to do a cros-pol.
Yes I am wondering if we are witnessing my transmitter die a slow death. No weather here.
posted
I was at -14.2 yesterday when you last posted. This morning without changing anything I was at -10 (which is my max per opt file). Weather was overcast. I'm still a bit fringe on the footprint, and Rcv SNR was around 12.
I have moved and am in a bit better position, footprint-wise. Still overcast, but Rcv SNR is 13. TX Power settled at -18 here.
posted
You have a higher Rcv SNR than I do, but are having to use much more TX power.
Could be a weak transmitter, but one troubleshooting item that we've learned with Hughes and might be important in this case is to check cable ends/connections.
UBBFriend: Email this page to someone!
Printer-friendly view of this topic
