Hi all,
I have this strange problem with my 3100 idirect series,anytime it gets into the network it will reboot itself after 30-45mins and it keeps on powering itself on and off (ie restarts when monitoring on hypertherminal).Unless i remove the TX cable, it will keep on restarting itself and it was on a -17 power whenever it enters the network

I know little about iDirect so this is just a guess.

Is the modem or power supply module rather warm ?

Connecting up the tx cable will increase the power.   Does something overheat after about 35 - 45 mins ?

Does it work better with a free airflow around the modem and power supply module ?

What temperature does rmtstat show ?

Best regards, Eric.

Short of an overheating issue (like Eric mentions above) I would say that you might have a problem with Redboot and Falcon.  Have you recently re-imaged this modem?  If so, from telnet type:

versions_report

Share your results with us.

I also want you to run:

options show

from telnet and look at look at the first block in the options file to ensure it matches your version (the versions and BSP of those in the versions_report).

Share your output results from the options show if you can.

Hi,
I will check all dat u mentioned but i also will like to mention that the site is located in the compound of a radio station,could it be an interference problem ?
Thanks

The Radio station is not likely the cause of rebooting (or reseting).  Has this modem recently been re-imaged?

Yes mike,it had a 7.1.1 image on it before and i now put in it a 6.0.9

Can you run a versions_report on it (from telnet) and post your results.  I bet the BSP is still 7.1.1

Hi mike,
I unfortunate dont possession of the modem rite now cos we are sending it to idirect for RMA,but i had done VERSION on the telnet and console and it gave me 6.0.9 ,and if it was still 7.1.1 i am sure that the net will never come up as AMBER  cos the satellite company had issues with different version rather than 6.0.9 and all that happened was that the NET will not come up atall.
Anyway thanks for the advises and maybe when the modem comes back and its working fine i will let the whole forum know my findings.

Hi mike,
Dis is what i got when i tried versions_report on the modem .What do u think?


[RMT:24402] admin@telnet:200.200.90.3;1111
> version
Application: falcon
Code Version: 6.0.9.0
Build Comment: Release build
Build Label: NetModem-6_0_9

[RMT:24402] admin@telnet:200.200.90.3;1111
> versions_report
Application: falcon
Code Version: 6.0.9.0
Build Comment: Release build
Build Label: NetModem-6_0_9
~~~~~~~~
falcon BUILD INFO:  built Wed Dec 7 16:36:09 EST 2005  by root  using g++ version 3.3 on Linux s1100bld 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386 GNU/Linux
~~~~~~~~
DID:    5005138   (0x4C5F52)
Model:     3100   (19)
SN:       24402   (0x5F52)
~~~~~~~~
iDirect Linux-BSP Release 7_1_1

~~~~~~~~
IMAGE                           VERSION
FpgaRx1Tdma_000xx              ( 011)
FpgaRx2Tdma_000xx              ( 011)
FpgaTxScpc_000xx               ( 015)
FpgaRx1Scpc_00xx               ( 019)
FpgaRx2Tdma_00xx               ( 011)
FpgaTxTdma_3S400_00xx          ( 021)
FpgaTxTdma_3S1000_00xx         ( 021)
FpgaRx1Peer_00xx               ( 019)
FpgaRx2Peer_00xx               ( 019)
FpgaTxPeer_3S400_00xx          ( 015)
FpgaTxPeer_3S1000_00xx         ( 015)


[RMT:24402] admin@telnet:200.200.90.3;1111

I am thinking that the 7_1_1 BSP (Board Support Package) may be causing your problem.  The thing is, I am not sure how to revert that software BSP.  The options file that is in this, is it 6.X?

Hi mike,
Yes the option file is 6.0.9 and i have replaced the modem with another 3100 some days back and there was no problem at at all, it then means that the modem was actually the problem so what did u say i can do to the old modem. RMA? or what do u suggest.
Thanks for all the responses

I would RMA it.  You could try to load 6.0.9 on it one more time just to be sure.  Your call.

I transition modems from 8.X to 6.X frequently and dont have any issues (even with a Phoenix BSP of 8.X).  So something obviously happened when you rolled it back (during the process).  

I would try loading 6.0.9 one more time (with iSite) and ensure it has a 6.0.9 opt in it.  If it continues to exhibit the problem, then RMA it.  Have fun with it...