Im having an issue with my HX 50 modem. ever since i opened my account with Bentley Walker the system will run but about 3 minutes into operation the Transmit light along with the System light goes out and my system stops responding. The issue last for anywhere between 40 seconds to several minutes. I recieve error codes while trying to use the system. My signal is 91% and there is no weather activity during these episodes. Ive written Bentley about the issue and have gotten no response

Any Ideas?
Joe

It would help immensely Joe, if you'd actually LIST the error codes you're getting. Knowing all the symptoms goes a long ways in the direction of finding the cause.

//greg//

Greg
The most common code i get is 710 (Cannot communicate with NOC)
i get a couple of other ones from time to time, if i see them tonight ill post them

here are the current diagnostic coded from the modem
0000-4000-0400-0043(Hourly)
0000-8005-1202-0489(Recent)

Don't know about the 710, I'm accustomed to the TX/RX Error Code breakdown. But the other two I can generalize upon: the first one is an uplink error. You say hourly, from which I assume cyclic. That suggests RF interference. The second one is related to uplink queuing/DNS acceleration/Web acceleration. These are typically NOC problems, but COULD be caused by packet loss - which IS an uplink problem too.

//greg//

ok,i think ur HX is on W3A satellite
and has not got new software in complete

Pls redo the command called RD in the modems main menu ( via telnet)
it will redownload software and all will b ok

Im not sure where the re download function is.

here are the codes out of my advanced tables
maybe you guys can figure out my problem
Joe

Network Time: WED APR 15 15:15:35 2009
------------------------------------

Adapter Main Statistics:
------------------------
Signal Strength.............. 91      Stream Msg-Ackd/Nakd........ 1366468/147087
Flags............... 0x00000000       NonStream Msg-Ackd/Nakd..... 1270/1649
Stream Error Rate.......   9.72%      NonStream Error Rate.......  56.49%
UpTime (d:h:m:s).. 000:21:44:38       Aloha Starts................ 1285
WakeUp Aloha Starts.......... 0       Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000       Frames Received............. 9916126
Addresses Open............... 7       Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 007:E:11272       Miscellaneous Problems...... 23
Rate Code........  256k 1/2 (TC)      No Receive Outroute Lock.... 21
Inroute Group................ 1       No FLL Lock................. 439
Inroute...................... 9       No Network Timing Sync...... 7764
IQoS ID...................... 4300     Current Modcod.............. 8-PSK 8/9 (16)


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 )

I think your problem is the system has not got the latest software download . simply do an RD

A Walker

Hi Joe,

To do the RD command simply open a command prompt window and type the following :

Telnet 192.168.0.1 1953

then press enter twice and you should see a menu come up. At this point type RD and press enter this will cause the modem to reboot and then download the lastest version of the software.

If you have any problems with this or have any problems please contact me on Paul@bentleywalker.com

Regards
Paul

If refreshed firmware doesn't do the trick, take note of the horrible transmission error percentage - and the lousy transmit rate code

//greg//

Here is the last 24 hours. I did as instructed.
is this about right?


Network Time: THU APR 16 18:02:39 2009
------------------------------------

Adapter Main Statistics:
------------------------
Signal Strength.............. 91      Stream Msg-Ackd/Nakd........ 601428/17700
Flags............... 0x00000000       NonStream Msg-Ackd/Nakd..... 4939/549
Stream Error Rate.......   2.86%      NonStream Error Rate.......  10.00%
UpTime (d:h:m:s).. 000:23:54:46       Aloha Starts................ 5110
WakeUp Aloha Starts.......... 0       Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000       Frames Received............. 8812413
Addresses Open............... 7       Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 007:E:11272       Miscellaneous Problems...... 151
Rate Code........  256k 4/5 (TC)      No Receive Outroute Lock.... 21
Inroute Group................ 1       No FLL Lock................. 439
Inroute...................... 7       No Network Timing Sync...... 4441
IQoS ID...................... 4300     Current Modcod.............. 8-PSK 8/9 (16)


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)

Nope. Error percentage still sucks. Did the RD command actually result in a successful firmware update? I have no idea why that suggestion was made, but those guys run NOCs. So perhaps they're privvy to inside info that you and I aren't.

To me, it still looks like a hardware problem on the TX path.

//greg//

How would i know if the firmware update was good?

my percentages are getting worse now

6% stream loss and 18% nonstream loss

and the weather was crappy yesterday, but today is nice and sunny

Go back to that user interface page where you got the statistics earlier, look in the upper left hand corner. If your page is the same as mine, there should be the modem serial number, the Main (installed) firmware version, and the Fallback (default) version number. The RD command that you were given stands for Reset to Default, which is the version that was installed prior to the current. There's also a RF command which stands for Reset to Factory, but on newer modems the Default version and the Factory version are often one in the same. Anyway, RD tells the modem to replace the current version with the default version. The RF command tells the modem to replace the current version with the Factory version. That's a little confusing, because sometimes the default and factory versions turn out to be one in the same.

Anyway. A version change also forces a modem restart, which is then recorded in the Reset Log (it's in the left hand column under Logs). The time, type, and reason for reset is recorded. A successful RD will be logged as such. I assume an unsuccessful will as well, I just don't know how it will be worded. Then on some subsequent connection with the NOC, the outdated version will be detected and the NOC will attempt to push the current version back over the satellite. When that's installed, there will be another reset - which the modem dutifully records.

Long story short, evidence should be in your Reset Log

//greg//

Main.bin: [5.8.0.48]
Fallback.bin: [5.8.0.35_PID]    

Greg: how much interferance can i expect from an overhead power line?

I'm a HN7000S in North America, so my version is different than yours. But your numbers represent a normal presentation. If there are no messages in your reset log suggesting an unsuccessful firmware load, I'd say that the RD recommendation was a waste of time. But you still should confirm with your provider the exact version that you should be operating under.

Ordinarily, power lines don't present much potential for interference. Do you know how to do resistivity testing on the cables?

//greg//

Well now i have a new problem..... im writing this post from my work computer because my satellite modem has stopped working entireley. the transmit and system lights wont come on and the recieve light is just blinking every 5 seconds..

Where are you located?  I am in balad.  I might be able to help.  If your in phone distance I can call, just email me.  Ken

Are you still getting the same problem as you had originally ?