Initial Driver Setup Procedures, Inmarsat Launch Pad Installation and

List of Known Issues

Dated: 17 April 2007

Prepared by : Kalaivanan.K

SW Release Package                                                : R 1.0.0

FW Upgrade Utility                                         : FirmwareUpgradeWinv0.4.0

WideyeSabreSetupUDP driver Installer        : v1.0

This document describes the initial setup procedures required to follow before anyone using the UT (User Terminal) with the new firmware release package (R 1.0.0).

Initial Setup Procedure

Please do the following initial setup in the given sequence before starting to use the UT with upgraded firmware.

Remove Old Wideye Drivers  (does not apply if first time use of a new UT)

1)      Remove Wideye Sabre 1 program in Add/Remove Programs of the Control Panel.

2)      Close when removal is complete.

3)      Check that the Wideye Virtual Ports are removed in Ports of the Device Manager.

Installing the VSP/UDP Driver

1)      Please unplug the Ethernet cable from the UT.  The UT should not be connected to the PC at this time.

2)      Run “WideyeSabreSetupUDPv1.0.exe” on PC/Laptop with Windows 2K/XP, which will uninstall the previously installed VSP version (either VSP/TCP or VSP/UDP, if present) and then it will install the new VSP/UDP v1.0. At the end of the installation, the installer will prompt the user to restart the PC. Please select “Yes” to restart the PC.

3)      After restarting, please check the (Control Panel -> System -> Hardware Tab) Device Manager, under Ports (COM & LPT) and see if two new virtual COM ports (namely “Lotus UDP port (COMx)” and “Lotus UDP port (COMx+1)”) are added to the list.

4)      Please check the Device Manager, under Modems and see if two new modem ports are added namely : Wideye SABRE Ethernet modem port 1 and Wideye SABRE Ethernet modem port 2

5)      Open Sabre 1 Configuration Utility (using the shortcut created on the desktop : )

6)      Under Config tab, please select the first virtual COM port assigned by the VSP/UDP Configuration Utility and then click on APPLY button.

7)      Under Config tab, please select the second virtual COM port assigned by the VSP/UDP and then click on APPLY button

8)      Make sure for each port that the “IP Address On BGAN” at the bottom of the tab is set to 192.168.1.35

9)      Click on OK and then close the configuration utility. This needs to be done only once after every installation of new VSP/UDP driver.

Firmware Upgrade of UT:     Already done

1)    Power ON the UT

2)      Plug-in the Ethernet cable to connect the UT and PC.

3)      Run “FirmwareUpgrade.exe” v0.4.0 and select the new SW release package “R000.4.2.zip” and upgrade the UT with the new firmware package.

a.      Close Upgrader & reboot.

4)      After successful FW upgrade and reboot, UT will automatically start acquire new GPS fix. After new GPS fix is obtained, please power off the UT to save the GPS information to non-volatile memory.

5)      Power ON the UT and then use it with LaunchPad as per normal for testing.

Before Using UT  (This is not necessary with a new UT terminal, only use this if it becomes necessary to uninstall the drivers and then reinstall.)

IMPORTANT  - Clear User data by resetting to factory defaults by following these steps.

1)      To go to Main screen press back button to see “No Bgan Service”.

2)      Press Menu and scroll to “Settings” & press enter

3)      Scroll to “Reset Settings” & press enter and then enter the security code.

·         Security Code: 0000 

(0 is displayed by default so just hit enter 4 times then the down arrow once to change the default number to “OK” and enter – the display will go to “Resetting” then to “Restarting” and then the UT will go blank and reboot itself).

Inmarsat Launch Pad Installation.

Launch Pad is a self executable file, simply double click on the file name BGANLaunchPadInstaller.exe, the Launch Pad will automatically install on your PC.  Then follow the Driver Installation instructions above.

List of Known Issues - Troubleshooting

1)      During FTP upload/download in Bridge Mode, when TCP_PEP (version 17.3) is enabled on Windows-XP machine, bluescreen will appear if user opens Ethereal software. Without Ethereal, there is no bluescreen. When tested with TCP_PEP v13.0, there is no bluescreen even if the Ethereal is running. This issue did not happen in Windows-2K machines but it was not extensively tested on Win-2K machines.

2)      “DUN auto-disconnect” feature is not yet included in the VSP/UDP driver. So, when there is a data connection in Bridge mode, unplugging the cable will not close the DUN client and it requires PC reboot to close it.

3)      Sometimes, Launchpad will display “Can’t find a suitable modem” when a data connection is initiated. This happens only when the DUN client is not properly disconnected during earlier operation and it is holding on to one of the modem ports.

If this happens,

a.      Close the LaunchPad.

b.      Go to Device Manager, expand Modems and select the Wideye SABRE Ethernet modem port 2. Using your mouse, right click to disable the modem port once and then re-enable it back.

c.      Start the LaunchPad and retry the data connection. This time it should generally work.

d.      This problem will be resolved when “DUN auto-disconnect” feature is included in the VSP/UDP driver.

4)      After resetting the UT to factory defaults via LaunchPad, the user must wait until the UT acquires a new GPS fix before attempting to register the UT to network (since the stored GPS values will be reset during the factory reset operation). If the user attempts to register to network before a new GPS fix is obtained, the UT will not be able to offer the required services to the user.

08-06-2006 - Partners and end-users are being advised of a quick and easy way to increase the speed of BGAN's standard IP data traffic in the "send" direction.

The throughput speed of BGAN traffic in the "send" direction (i.e. data sent from the terminal) will be enhanced if the window size on the receiving PC or server is correctly set.

And Inmarsat has prepared a small software file, available for download here, which automatically configures the client computer or server.

The window size on an IP connection effectively sets the number of packets ¿in flight¿ between origin and destination, at any given time.

Setting an optimum window size is particularly relevant for channel Partners undertaking customer demonstrations, and for end-users

users who frequently access the same servers with applications such as FTP (e.g. media customers, or corporate customers accessing intranet sites).

The optimum window size for BGAN is 128k (default setting on many systems is 64k).

Disclaimer: Modifying the computer registry may cause problems that may require you to reinstall the operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk. Inmarsat will not be liable for any issues or problems that may arise in using this software.

To set the window size for systems running Windows XP or Windows 2003, follow the instructions below:

How to use automatic registry key entry to manage a client computer's or server's TCP parameters:

1. Inmarsat supplies two .reg files that will automatically configure the client computer or server to use the recommended TCP parameters. Choose the appropriate file to match your operating system.

2. The two files are:

• WinNT.reg (for use with Windows NT)
• WinXP_Win2k_Win2ksvr_and_Win2k3svr.reg (for use with Windows XP, 2000 Professional, 2000 Server and 2003)

3. Save the relevant .zip to your desktop and uncompress.

4. Double click the .reg file to change parameters. When the following screen appears click "yes" to continue: