For simplicity it is normally recommended that any other APN s configured on the terminal are deleted.

Transcription

1 This quick start guide is designed to provide a simple overview of the configuration of the key features of the 9502 M2M Terminal, for further information on any of these features please refer to the appropriate section of the user manual. IP Settings The default IP address of the M2M terminal is shown below, by default the terminal has DHCP enabled allowing connected devices to automatically obtain their IP configuration from the terminal. Default IP Address: By default the DHCP server feature is enabled on the LAN interface, this can be disabled if required from the IP Address/DHCP Settings page within the M2M terminal web interface. APN Settings The APN settings should be configured as follows: APN Name: telespazio.bgan.inmarsat.com Username: <leave blank> Password: <leave blank> For simplicity it is normally recommended that any other APN s configured on the terminal are deleted. Antenna Alignment WARNING: Alignment mode disables all transmissions from the terminal, ensuring the antenna is safe to approach/handle from all sides For safety reasons, do not attempt to align the antenna without alignment mode enabled. Before the M2M terminal can be used to transfer data, the antenna must be correctly aligned to the appropriate satellite, this may be simply achieved using either the audio or web based alignment tools provided by the terminal. To place the terminal in alignment mode, ensure the terminal is powered on and then short press the black button on the base of the terminal (for less than 2 seconds), the terminal will indicate that it is in alignment mode by blinking the power, GPS and net LED s. Once a GPS fix has been obtained, the GPS LED will then remain constantly illuminated whilst the others will continue to flash, note that a valid GPS fix is required before commencing antenna alignment. Once a GPS lock has been obtained the web interface on the M2M terminal, the approximate azimuth and elevation required to successfully align the antenna is displayed on the homepage. Commercial In Confidence Wireless Innovation Ltd June 2012 Page 1

2 From the home page of web interface the current received signal strength is also reported, this is updated in real-time so may be used as a reference to align the terminal, a signal level of 50dB or higher is required for reliable operation. To assist in pointing an audio alignment aid is also provided, simply use the 3.5mm audio port to connect either headphones or a speaker to the terminal As the signal strength increases the pitch of the audio tone will get higher and faster. (This feature also allows the antenna to be aligned without the use of a PC). Alignment Mode Enabled Current Receive Signal Strength Azimuth & Elevation Required for Alignment of Antenna Figure M2M Terminal Web Interface Home Page. Once the antenna has been successfully aligned (Signal Strength is reported as greater than 50dB) the terminal can be switched back to operational mode by short pressing the black button on the base of the terminal when all three LED s on the base of the M2M terminal go solid the terminal is successfully connected to the network and a data session has been established. Note that once a link is successfully established by the M2M terminal the LED s will then be extinguished to save power. Commercial In Confidence Wireless Innovation Ltd June 2012 Page 2

3 Configuring NAT Forwarding The M2M terminal is optimized for use in scenarios where the host IP device is directly connected to the terminal via an Ethernet cable, by default when the M2M terminal establishes a data session it will automatically establish NAT forwarding to the first LAN connected device it detects via ARP. NOTE: The M2M terminal does not allow only specific ports to be forwarded, rather if NAT forwarding is enabled then all inbound socket connections are automatically forwarded to the internal host. To enable NAT forwarding to a specific internal host each time a data session is started the Always on Context feature should be enabled through the web interface on the M2M terminal by completing the following stages: From the IP Addressing/DHCP Settings page, ensure that the Network Operating Mode is set to NAT mode note that changing this setting requires a reboot of the terminal. Ensure NAT Mode is Selected Figure 2.0 Enabling NAT mode from the Web Interface. Commercial In Confidence Wireless Innovation Ltd June 2012 Page 3

4 Next the Always on Context feature should be enabled from the M2M Setup page from the terminals web interface, by ensuring the ON radio button is ticked as shown in figure 3.0 below. Enter the internal IP address of the NAT host device (the local device to which all inbound IP connections should be forwarded) in the Static ACA IP Address field, the example shown in figure 3.0 below assumes the local device has been configured with an IP address of Finally ensure the APN used by the Always on Context is set to telespazio.bgan.inmarsat.com. Ensure the Always on Context is Enabled Internal IP Address of NAT Host Device Figure 3.0 Enabling the Always on Context Feature from the Web Interface. Commercial In Confidence Wireless Innovation Ltd June 2012 Page 4

5 Configuring the Network Keep Alive The M2M terminal can operate a keep-alive feature, specifically designed to ensure always on network connectivity even if the terminal transmits no application traffic for extended period of time. The M2M terminal will PING up to three user defined hosts on a user defined schedule, if the remote hosts cannot be reached, the terminal will automatically reboot and re-start the data session. For optimum device connectivity it is recommended that this functionality be enabled. The network keep-alive feature can be enabled from the M2M Setup page of web interface on the M2M terminal as shown in figure 4.0 below. Enable Keep Alive (Context Watchdog) Hosts to be Pinged to Verify IP Connectivity Keep Alive Ping Interval Figure 4.0 Enabling the Network Keep-Alive Feature from the Web Interface. To configure the network keep-alive functionality, firstly ensure the Context Watchdog feature is enabled by checking the ON radio button. Define up to three host IP addresses that the terminal will attempt to PING in order to verify network connectivity. Do ensure the hosts entered are reachable from the M2M terminal via the WAN (Network) interface and that they will respond to PINGs. Commercial In Confidence Wireless Innovation Ltd June 2012 Page 5

6 Finally, enter the required keep-alive PING interval in the Time Between Pings field. The optimal time delay between PINGs will be dependent on the traffic characteristics of the actual application being deployed using the M2M terminal, however in general it is recommended that an interval of no greater than 360 minutes is selected. NOTE: All IP Traffic generated using the keep-alive functionality is rated and charged in the same manner as other traffic generated by the terminal. Based on sending a single 30 byte ping to a known host (and receiving the response back), users should allow for the following approximate monthly usage: Ping Interval Estimated Monthly Usage 15 Minutes 400KB 30 Minutes 200KB 60 Minutes 100KB 120 Minutes 50KB Once all the settings have been modified it is nessassary to reboot the M2M terminal to apply the changes and connect the NAT device. Note that the terminal does not need to be realigned after each restart it will automatically bypass the alignment stage during the boot process and attempt to establish a data connection. For further information or support, please contact the Wireless Innovation helpdesk: support@wi-ltd.net UK Phone: US Phone: Commercial In Confidence Wireless Innovation Ltd June 2012 Page 6