iDirect 3000 series telnet session.

Ok so I put in
tx power
and got -25 as my answer
Then I put in
tx power -29 for a temporary change
that worked
then I put in
options set MODEM_PARAMETERS tx_power_in_dbm = -29.000000

and reset the modem.

It reads -29 now and everything is right as reign but they had to manually reset the modem because I could not figure out the proper syntax for the reset command.

So please tell me how to do resets in the future threw the telnet. Thanks.

Ultumix, your Hub Operators are steering you wrong.  

Here is why:

The iDirects Modem power is determined by its ablity to meet the configured UCP for the network you are operating in.  

In most cases, the configured UCP is 9dB upstream C/N.  

So, that said, your modem is going to do whatever it takes to achieve 9dB upstream C/N....whether it take -25 or -29, you modem is instructed (by the NMS) to achieve 9dB.  So, you can adjust the tx value in telnet all day long, but it isnt going to do any good....because the HUB (NMS) is going to detect your bursts arriving TOO LOW on the UCP and bring your TX back (up) to nominal (thus achieving the config'ed 9dB).

Be advised, your idirect modem doesnt care WHAT kind of RFT it has onboard (BUC size, reflector size, etc). It only knows that it MUST acheive 9dB C/N on the upstream.  You as the operator must be sure that you have the right sized BUC and aperture to meet the link budget...as required by the satellite broadband provider (ISP).  

So, one would hope that you did your homework with regards to procuring the right sized BUC and aperture to get the job done.  For all we know, you could be trying to close too large of a link for the size of RFT you have....(your BUC may be inferior for the link you are closing)....which could overpower the craft, or possibly saturate the BUC (thus causing CRC_Errors on the line cards at the hub).

How are they assessing that you are 4dB hot?  Was this observed on a test freq in pure carrier?  If not then they probably have no idea what they are talking about.  Who is your provider?

Also, modifying falcon (or the options file) wont do you any good.  Your best bet is to get another peak and pol, ensure that your system is pointed and poled properly.  From there have the re-assess your carrier and see where you stand.  Once that is complete (if you are still too hot), you more than likely have a BUC that is inferior in its ability to meet their budget.  Eric can chime in, but that is how I see it.

If everything is fine with the hub then there more than likely wasnt a problem to begin with. 


Glad to hear that it has been resolved.

Dear UltiMix..

Below are the most known Idirect Commands and a small explaining about what it would effect:

DID             Show modem identification number
TERMINATE       Kill process
acq             ACQ/UCP control
arp             ARP control
btp             Tx Debug
clear           Clear screen
console         Console control
cpu             Show CPU utilization percentage
delay           Usage: delay <msecs to sleep>
dgm_pkg_rx      Datagram Package Download Receiver
dhcp            DHCP server command
dma             DMA Stats
dns             DNS control
dumpb           Dumps bursts received on TDMA RX2 of
eloop           Display Event loop status
eth             Show the output of ifconfig command
extras          Extras option file manipulation
fll             FLL/DAC sampling
gecho           Global echo
gpspollinterval seconds
gre             gre protocol
hdlc            HDLC Stats
heap            Memory Usage
hookstatus      Protocol Hookup status
hub_fsd         Hub FSD
icmp            ICMP protocol inpection layer console
igmp            Multicast control
inroute_list    Inroute List
ip              Router control
ipv4            IPv4 protocol acceleration control layer
ktun            Kernel Tunnel Command
laninfo         View IP address/netmask
latlong         LAT LONG
mac             MAC control
mem             Resource information
mesh            Forces the remote out of mesh
meshdebug       Mesh Debug
mnc             MnC server command
mux             MUX Table Dump
nat             NAT Control
netstat         Show the output of a netstat command
nms_echo        NMS event echo
nmsr            Debug NMS Reporting object (event essage sender)
offline         Offline
online          Online
oob             OOB control
oobc            OOBC layer stats and params
options         Options file manipulation
ota             OTA stats
package_info    Detail installed package information
pad             PAD control
params          View/Edit global params
pasoc           command for the packet socket layer
passwd          Change password
pcmd            Periodic Console Command
peek            raw memory read - can be dangerous
phy             read PHY status register
ping            Ping Utility
pm              Pad upper Mux stats
poke            raw memory write - can be dangerous
ps              Show the output of the ps command
qos             QoS control
remotestate     Displays the current remote state
reset           Reset machine or restart service
rlock           Locks the remote to work in a specific network
rmtarp          Mesh ARP table
rmtstat         Toggle printing Remote Status messages
sar             SAR control
satmac          satmac layer stats
sd              Sar lower Mux stats
service         Service start/stop command
sn              Show modem serial number
spoof           Spoof Command
stats           View/Edit global stats
systray         Systray status sender command
timer           Timer control
tlev            Trace control
ucp             Display UCP information
udp             Udp Command
udp_compress    UDP Payload compress
uptime          System and application uptime
version         Build information
versions_report Full operating environment report
vlan            VLAN control
x509            Manage X509 Certificates and RSA keys
xoff            disallow messages from other processes
xon             allow messages from other processes

i wil try to find you a full syntax guide for using them..

Regards..

thanks ashrafbomba, I'll do just that, i guess that was the case, cos it was a really conflict session on the IP addressing for my clients...thank you for your support and suggestions.

cheers!!