posted
This is the second time I have awoken to find my D3 reporting msg-25 on the SQ, Tx and Rx lines, but I am still online. The 3100 reports Lat/Long not available and showdebug on the D3 shows no activity. What could this be all about?
posted
The msg -25 means that the D3 is not seeing a connection to the modem. Power cycling the D3 will clear this error. I believe the showdebug option on the D3 only works when you start a new search. I am not sure how you were able to stay on-line if the Lat/Long was not being sent to the 3100 but it sure would be good to know.
-------------------- Bill Adams Winegard Company Posts: 15680 | From: Traveling the Western US | Registered: May 2003
| IP: Logged |
quote:Originally posted by Bill Adams: I am not sure how you were able to stay on-line if the Lat/Long was not being sent to the 3100 but it sure would be good to know.
I know, odd huh? And why all of a sudden the D3 can't see the modem though the router is still working? That sensing is through the router and not the coax, right? I am going to leave it in this odd state until DonB chimes in, in case there is any testing I can do to try to figure out what is going on.
posted
I doubt there's much to figure out other than power cycling the D3 to bring it back to life. MotoSAT would be the ones to ask how it is that you are on-line despite the no GPS info but if you have been calling them a lot this may simply be dismissed.
-------------------- Bill Adams Winegard Company Posts: 15680 | From: Traveling the Western US | Registered: May 2003
| IP: Logged |
posted
Can't remember what version of iDirect you are running, but I know that version 6 would continue to remain on-line until the modem was rebooted and then it would lose xmit until the D3 would start feeding lat and long data again.
In version 8 the modem retains the last Lat and long it received and will run without the continous stream of info from the D3.
PV
-------------------- Hyperlink VR7 + iDirect 3100 on Anik F2 Posts: 141 | From: Edmonton, Alberta | Registered: Jan 2004
| IP: Logged |
posted
I would guess that the D3 sends Lat/Long Waaaaaaaaaaay more often than the 3100 needs to see it. Probably once is enough - the only time you see a problem is when the Lat/Long is an invalid piece of data.
UBBFriend: Email this page to someone!
Printer-friendly view of this topic
