My Document - Navman Wireless

1 Provisioning
Provisioning
Table of Contents
1 Provisioning
3.1 Introduction
3.1.1 Purpose and Scope
3.1.2 Supporting Documentation
3.1.3 Glossary of Terms
3.2 Software Installation Instructions
3.3 Hardware Installation Instructions
3.3.1 Summary
3.3.2 Qube Setup
3.4 Software Configuration via COM ports
3.4.1 Ping
3.4.2 Adding provisioning files
3.4.3 Param files
3.5 Upgrade Process
3.6 Hibernate
3.7 Provisioning Qube 300 for Use with Peripherals
3.7.1 How to check Stream Assignments using Qube 300 ProvisionViaSerial Tool
3.7.2 Qube 300 Setup for MDT on RJ45 and Debug on 10-pin
3.7.3 Qube 300 Setup for M-Nav on RJ45 and Debug on 10-pin
3.7.4 Qube 300 Setup for M-Nav on RJ45, SAT Modem on 8-pin and Debug on 10-pin
3.7.5 Qube 300 Setup for M-Nav on RJ45, Debug on 8-pin and NavCAN on 10-pin
1
1
1
1
1
2
3
3
3
5
7
8
10
12
13
14
15
16
17
18
19
i
Document Control
Document Version History
This table shows a record of significant changes to the document.
#
2.1
3.0
Date
October 23, 2014
October 29, 2014
Reason for Update
FVT Draft 2.1
Production Release
Author
Martin Davies
Martin Davies
Copyright
Copyright © Navman Wireless Ltd
All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, of transmitted in
any form or by any means, electronic, mechanical, photocopying, recording or otherwise
without the prior written permission of Navman Wireless Ltd.
This document is the property of Navman Wireless Ltd and may not be disclosed to a third
party, other than to any wholly owned subsidiary of Navman Wireless Ltd, or copied without consent.
Document Information
Path/Filename
TBD
ii
3.1 Introduction
3.1 Introduction
3.1.1 Purpose and Scope
The purpose of this document is to give detailed instructions on how to provision a Qube 300
using the “Qube300ProvisionViaSerial” software. The program can upgrade multiple units in
parallel with a mixture of HSPA and GSM modem types.
The software is also capable of upgrading the QT100 platform; this can be done in parallel with
Q300 and requires no user interaction.
3.1.2 Supporting Documentation
Sharepoint Location
Qube 300 FRD
Program Location
TBD
Link
Link
3.1.3 Glossary of Terms
Term
HA
FW
COM port
Config/Param file
Description
Hosted Application
Firmware
Communications port AKA serial port, RS232 Port
A text file that details regional default configuration
1
3.2 Software Installation Instructions
3.2 Software Installation Instructions
The provisioning software is a ‘Click Once’ application that will auto update if a new version is
available upon execution.
The program can be downloaded from here.
Once installed the software is located in the Start > All Programs > Navman Wireless Ops Tools
folder.
To Create a desktop shortcut, right click on the program and select "Send to" Desktop.
In windows 8 simply search for “Qube300ProvisionViaSerial”.
2
3.3 Hardware Installation Instructions
3.3 Hardware Installation Instructions
3.3.1 Summary
The Qube 300 will from time to time need to have its FW, HA and PEG updated as new releases
come out that fix known issues and add new features.
This can be done in one of two ways
1. Over the air using the PULS website
2. Serially using the Qube 300 serial cables and the “Qube300ProvisionViaSerial” program
This document describes how to update a Qube over a wire (serial cable), in order to do so we
need to use both the RJ45 and the 10 way serial cable.
3.3.2 Qube Setup
Connect the RJ45/ 10 way serial cables, power and antenna. Antenna can be optional depending if you need a connection to the AVl2 servers or if you are simply upgrading stock units.
Once connected power up the units ensuring the green LED is lit. Once all units are confirmed
connected and powered up open the provisioning tool.
3
3.3 Hardware Installation Instructions
A Qube 300 with Power and both serial cables inserted ready up for provisioning.
4
3.4 Software Configuration via COM ports
3.4 Software Configuration via COM ports
The provisioning tool will automatically pick up and initialise the COM (serial) ports attached to
your computer. COM ports are checked each time the program is run and you can manually
select what ports to use.
In the example below I have 8 COM ports starting at COM 51 and ranging to COM 58.
Use the tick box in the top left hand corner next to the COM port number to select/unselect a
port.
5
3.4 Software Configuration via COM ports
You can use the “Select only…” option to select different devices depending on different criteria.
6
3.4 Software Configuration via COM ports
Once you have selected your desired ports you are ready to start the provisioning process.
Please note each Qube needs 2 COM ports as both the RJ45 and 10 Way cables are used.
Programming of the Qube HAS to be done on the RJ45 port, the 10 way serial cable is simply
used to reset the device in this use case.
3.4.1 Ping
If you would like to check the devices are connected correctly and can be access by the computer use the “Ping” option. This will attempt to query the device and will advise if successful.
7
3.4 Software Configuration via COM ports
Example below shows a successful ping to a Q300, we can see it was on the “TenWay” port and
that it’s a GSM device.
Also displayed is the units ESN (AVLID), device type (178), and current FW version (36z). If the
Ping is unsuccessful it will time out after 15 seconds.
Please note the RJ45 port will not normally respond to a ping, we would expect them to time
out.
3.4.2 Adding provisioning files
To start the provisioning process click the “Start Provisioning….” button on the menu bar.
8
3.4 Software Configuration via COM ports
You will be presented with a menu allowing you to enter the file locations for the different files
used in provisioning.
Ensure you add the correct files into the correct location else the device will be upgraded with
incompatible files, to undo run the process again with the correct files. You only need to set up
the files once, subsequent times the fields will be pre-populated.
If your region only uses one device type (IE HSPA only) you can simply leave the other fields
empty. The program will warn you they are missing by highlighting them in yellow but will
allow you proceed by clicking ‘OK’.
If the files you have selected no longer exist the program will flag them in red and will not
allow you to proceed until you have selected valid files. In the example above I do not have a
valid file for the Hosted app so it won’t let me proceed.
9
3.4 Software Configuration via COM ports
The Qube 300 and QT100 both have individual tabs allowing you to set up provisioning files for
both devices.
3.4.3 Param files
The Param files allow regional settings to be pushed down to the Qube giving it enough information to get online and contact your AVL2 server. Once contacted the server can be used to program customer specific settings (reporting times, event alerting, Overspeed etc.)
10
3.4 Software Configuration via COM ports
Above is an example of a config file pointing to the NZUAT server including server addresses
and APN’s.
You are able to add both a GSM and HSPA Param file, if you are using different APN’s on the
same device type (i.e. you have HSPA units that could use one of two different Telco’s) you will
need to manually change the file when starting the provisioning process.
If loaded with the incorrect param file restart the process or amend the details over a terminal
connection.
11
3.5 Upgrade Process
3.5 Upgrade Process
After adding the provisioning files click “OK” to begin the Provisioning process. The first step is
to reboot the device so it can be put into a state where it can be updated.
You will see all COM ports attempt to “Grab the RJ45”, only the 10 way serial cables will be successful. Once they detect the COM port has a 10 way plugged in they will issue a reset command that reboots the Qube.
After a reboot the program will successfully “Grab” the RJ45 port and start to upgrade the
device. The upgrade process is automatic and requires no user interaction.
The example above shows a successfully updated GSM Qube at the end of the provisioning process. As there is no SIM card inserted into the Qube the SIM card number was not read successfully and is highlighted in orange.
To cancel the upgrade for an individual Qube process use the “Cancel” button on each COM
port. To cancel all upgrades use the “Cancel” button located on the menu bar.
If an upgrade fails for any reason you can select the relevant COM port and start the process
again.
Debug logs are generated on each upgrade, to view the files click the Log button, this can be
handy when troubleshooting and should be included with any Bug reports. Files are located in
the C:\temp\Qube300Provisioning folder on the local hard drive.
12
3.6 Hibernate
3.6 Hibernate
In order to ship the devices we need to active the hibernate mode; this can be done using the
“Hibernate” command on the main menu and is similar to the shipping dongle used for Q3/4.
After Hibernation the Qube will not wake up until it has external power and the Ignition input is
on. At present there is no shipping dongle as per Qube 3/4 however this may change in later
hardware builds.
To activate hibernation the Qube’s ignition must be off, if not the program will prompt to turn it
off.
The example above shows a failed hibernate and the associated error message. If successful
the Qubes take around 30 second to shut down. To test if it’s successfully hibernated ensure all
LEDs are not lit and when the unit is shaken they do not light up.
13
3.7 Provisioning Qube 300 for Use with Peripherals
3.7 Provisioning Qube 300 for Use with Peripherals
When configuring the Qube 300 for use with peripheral devices such as NavCAN or M-Nav, the
Qube 300 must reboot in order to reconfigure the ports. As such it is important to ensure that
Qube 300s have completed applying settings and ports have been re-configured before disconnecting and finalising the provisioning process. The following section describes how to use
the provisioning tool to confirm serial port configuration.
14
3.7 Provisioning Qube 300 for Use with Peripherals
3.7.1 How to check Stream Assignments using Qube 300 ProvisionViaSerial Tool
15
3.7 Provisioning Qube 300 for Use with Peripherals
3.7.2 Qube 300 Setup for MDT on RJ45 and Debug on 10-pin
16
3.7 Provisioning Qube 300 for Use with Peripherals
3.7.3 Qube 300 Setup for M-Nav on RJ45 and Debug on 10-pin
17
3.7 Provisioning Qube 300 for Use with Peripherals
3.7.4 Qube 300 Setup for M-Nav on RJ45, SAT Modem on 8-pin and Debug on 10-pin
18
3.7 Provisioning Qube 300 for Use with Peripherals
3.7.5 Qube 300 Setup for M-Nav on RJ45, Debug on 8-pin and NavCAN on 10-pin
19
Download PDF