I am having a bad day typing here. The topic states "D3" will not lock, obviously this should read Nomad2 will not lock on DirecTV (101). I cannot change it. Don or Michael, if you see this would you please make the topic change for me. Thanks.
As Bill said, you could have edited yourself by editing the first post, but I've done it now.
As far as the Nomad, serial numbers mean nothing to me. Roughly how old? There have certainly been Nomads needed firmware changes to find each of the satellites.
Do you have a cable? You've been around long enough that you might go back to the D1 days, and still have a cable lying around. Very hard to tell what is happening, and of course what version of firmware, without a cable.
Look on the bottom of the Nomad 2 and you will see the software version number. That is what it will be unless someone has updated it.
Has the system worked recently? If not, how long ago did it work?
Does the LNB light come on?
-------------------- Don Marr WWW.OREGONRV.NET 541-683-5361 See where I am Country Coach Concept 40' F1 - D3|7000s|99W|LinkSys wireless with 1000mw WiFi amp & Ext. antenna Posts: 3379 | From: Eugene, OR | Registered: Jun 2004
| IP: Logged |
Thanks for the info everyone.Sorry I did not see the edit capabilities. The version on the bottom of the unit is Rev 26. The unit worked last Thursday and stopped when I moved to Bandon, OR on Friday. The LNB light does come on. The unit searches, finds a sat, tries to peak, fails and moves on. It continues to search, peaks, fails and moves on. I just received the cable and adapter yesterday so I now have a way to connect.
If you connect to it and then search, and capture the output to a text file, you can open it in notepad and look through what it is doing.
I believe it is entirely possible that, in a particular location, the dish might hit 110 and mis-identify it, such that it makes the dish search incorrectly. If that's the case you will see the same two or three satellites found when you search the capture file for the string "Current Sat:"
I saw an example of that just today while testing a new Nomad SD (firmware firmly beta!!). The dish went up and found 61, about where I would expect it to be. Based on that, it has a "window" where 101 is expected and it went over there. It quickly found 91 (I know because of subsequent searching with better firmware) but identified it as 148.
That caused the dish to try a new "window" high and to the other side of 61. As it found nothing and widened the window, it eventually found 61 again and repeated. A search of the log for "Current Sat:" looked like this:
Current Sat: 61 Current Sat: 148 Current Sat: 61 Current Sat: 148 Current Sat: 61
ad infinitum. It would repeat until manually stowed.
If you find that anything like that is happening, and it may involve more than two but will repeat, you need to try newer firmware. Probably the new beta, since that has the 110 item fixed.
Here are the search results BEFORE I installed the new software: Sat Table Num Long TR Pol AZ EL Status --- ---- -- --- ---- ---- ------ 00 061 25 0 0000 000 0 01 072 19 0 0000 000 0 02 082 19 0 0000 000 0 03 091 19 0 1045 524 2 04 101 19 0 0000 000 0 05 110 19 0 0000 000 0 06 119 19 0 1088 535 2 07 129 19 0 0000 000 0 08 148 19 0 0000 000 0 End of table.
I installed the new Nomad2 Beta v33.6a software successfully. Ran a "Test Dish" which completed without errors. I run the "Find" sequence which completes after finding several satellites and ends with the DVB, Peak & Stow buttons flashing at 1 second intervals. According to the manual this means "Main satellite not found but secondary was". Looking for advice on what to do next.
I noticed on another topic (Dish messing with us again) that they had loaded 33.6a and "the only problem being is it's taking 5 seconds per line and there are 3457 lines, WOW" My load record showed 3456 lines loaded. At the end of the load it gave a message "Local>300FC - Unknown command" and then the "local" again. I entered "Default" per the manual. Could the difference in lines of code loaded be part of my latest condition as reported in my last post?
Results of call to MotoSat - Problem resolved by installation of new software and following their instructions for changing the "Zone" programming in the Nomad2 to "None". Just a personal note to say they were very responsive and helpful in my request for assistance. I know not everyone has had that experience, but they were excellent in handling my call today. Thanks to all on the forum who gave assistance also. Where would we be without this medium of information! Methinks it's time for another donation!!
Im very thankful for the "zone" setup, Its strange though that not until this week, we gotta away with not setting the zone here in Vegas. We were using no lights zone settings I guess for awhile. We got edumacated today. Plus with what other product can you get less than 5 minute signal lock on a multiple satellite signal antenna system?
-------------------- Mr. Ashley Teasley Satellite World, Inc 702-564-0790 Las Vegas, Nevada firstname.lastname@example.org www.satworld.biz Satellite Internet & TV, KVH, Directv & Dish Network Authorized Retailer Posts: 678 | From: Las Vegas, Nevada | Registered: May 2003
| IP: Logged |
I am having similar problems. I stowed my dish Saturday Night in anticipation of the remnants from IKE blowing through NW Arkansas. When I tried to deploy the dish (HDSL5) Sunday it would search for about 10 minutes and then stow and give the DVB Peak and Stow error. My question is about zones. Do they apply to DTV the updated manual on the MotoSat site suggests the zones are only for Star Choice?
-------------------- Wayne Routhier 05 Alpine F1 D3 HN7000S HD SL5 Posts: 205 | From: Brownsvile TX | Registered: May 2003
| IP: Logged |
I found that my SL5 would only find 101 in my current location, and it took new firmware for the SD controller to make it work; assumption is that it is the 110 issue. My Nomad2 is toast so I can't test that one.