posted
I have had iderect now for about one year. When it works, it does everything I need. The problem I have is most of the time when I move (like from San Jose, CA a couple hundred miles south or east) I have to call the support number, they do something on there end and it work. If I am in an area with no cell, I am out of luck (about 1/2 the time). Yesterday it was working fine in San Jose, I move a bit further than normal to Las Vegas- No work. I get good Signal and good quality in all cases, But the Tx function comes on and off. I did not have this problem with HNS, but had FAP which killed my application of the network. I am on 105. Support has talked about 99. Am I the only one with this type of problem? Is 99 a possible solution??
Posts: 28 | From: San Jose, ca | Registered: Mar 2007
| IP: Logged |
posted
Gary, you did not say who your iDirect provider is. Is it one of the "standard" mobile providers, like Ethersat, AtContact, or Mobilsat?
Since you mention 105 I would have guessed Ethersat, but I don't think they use 99 also.
One problem we've consistently had is the proper setting of the initial TX Power. When they set it too low you end up needing a new options file when you move to an area with a poorer signal.
To combat that John Watson and I added some "power ramping" to our iDirect Modem Tool - it will push power up a bit (but not excessively) over the course of 15 minutes or so if TX does not lock. You can download the tool from the Articles section above left.
posted
Thanks Don, I have downloaded the utility, but do not know the IP of the modem. It connects to the controler fine. My controler is at 192.168.1.250. I tried 192.168.0.1 for the modem but that does not work. I am on Ethersat as far as I know. I see looking at the map that there are now more on 99. It looks like you stayed on 105. Any widsom regarding the two?
Posts: 28 | From: San Jose, ca | Registered: Mar 2007
| IP: Logged |
posted
Don, Stupid me, I found my setup sheet with the IP. The utility started at -13 and went to -10, but no luck. Scott (Moto) suggested that I run a new coax to the modum to check this out. I doubt that that will help, but am concerned about the connector at the antenna and the barrow connector for the short extention required for the Idirect conversion. Both are taped but who knows.
Posts: 28 | From: San Jose, ca | Registered: Mar 2007
| IP: Logged |
posted
I used to have an issue with Tx dropping (and also therefore my connection) several times per hour. Based on comments here, I found turning off the D3 after I got connected alleviated that. Further, it seems a new router resolved it fully so that I no longer turn off the D3 and only drop connection in the thickest of weather.
Also, Don's iDModTool definitely has helped me get online faster/better as I typically have to bump it a few counts left or right in AZ to get the best SQ and thus the best chance to connect. Connection times have been pretty quick for me lately.
posted
There are multiple mods of nonconnectization. Mine was (and maybe is to be again?) alleged and apparent interference with non-satellite signals. The definite symptom of the problem I had (have?) is the drop of SNR below 7.5 ish in the best, calmest, sunniest and clearest of weather.
I ignore the controller Q and use Don's tool. The controller Q must be heavily weighted by SNR as their trend tracks very well. Once pointed, I turn off the controller until I move.
Let it be known also that switch out of modem and LNB and bypass of receive cable did nothing for my SNR symptoms.
"Now, listen, you don't go any one special place. That's cornball style. You just go." -- Johnny in the movie The Wild One Posts: 1120 | From: not Hereford, AZ | Registered: Aug 2003
| IP: Logged |
UBBFriend: Email this page to someone!
Printer-friendly view of this topic
