> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/modules/cinterion-r-pls62-w-wireless-module/updating-software-cinterion-pls62-w-wireless-module.md).

# Updating software – Cinterion® PLS62-W Wireless Module

If you have the Cinterion® PLS62‑W Wireless Module version 2.0.5 or previous, you must install the Eseye Updater and update the device software.

You will install the following:

* USB Drivers – to enable the computer to access the

  Cinterion® PLS62‑W Wireless Module
* Module Exchange Suite (MES) tool – enables you to copy files into the

  Cinterion® PLS62‑W Wireless Module
* Eseye Updater – a tool for updating the current software
* Cinterion® PLS62‑W Wireless Module

  software (latest version)

### Before you begin

You need:

* Windows 10 computer, version 1909 or later, with administrator access.
* The

  Cinterion® PLS62‑W Wireless Module

  you want to update, which may exist within a

  smart terminal

  . Ensure it is powered on.
* A cable for connecting the Cinterion® PLS62‑W Wireless Module to the computer. Ensure the cable is connected to the device and the computer.

  If you are using the Intelligent Cloud Connect, you will need a USB 2.0 A male – B male cable.
* A customer login for Eseye Zendesk, to access and download the required zip files. If you do not have a customer login, contact Eseye Support: [support@eseye.com.](mailto:support@eseye.com)

## Installing the USB drivers and Module Exchange Suite (MES)

To download the USB drivers:

1. Using the Windows 10 computer, go to:

   <https://eseye.zendesk.com/hc/en-us/articles/360009436498>
2. Log into Zendesk to view the files.
3. Download **pls62-w\_rev02.000\_arn01.000.04\_drivers.zip**.
4. Extract all the contents of the zip file to here:

   C:\Drivers

To install the USB drivers:

1. Using the Windows 10 computer, open **Device Manager**.
2. Expand **Ports (COM & LPT)**.

   Five ports are listed. Their names may differ from those displayed in the example, depending on your computer setup.
3. Right-click the first listed port (in this example, **COM10**), then select **Update driver** in the shortcut menu.

   ![](https://893902233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR60wMwGxVlr3J15eCIGp%2Fuploads%2Fgit-blob-7faa802670089f46a6d23ad06676081a47a1e57d%2FDeviceManagerModemDrivers.png?alt=media)

   The Update Drivers - USB Serial Device window appears for that port.
4. Select **Browse my computer for driver software**.
5. Alongside Search for drivers in this location, select **Browse**.
6. Browse to C:\Drivers\USB.
7. Ensure the **Include subfolders** checkbox is selected.

   ![](https://893902233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR60wMwGxVlr3J15eCIGp%2Fuploads%2Fgit-blob-8072253b4527ec06882fc5d62189e7973400646c%2FBrowseForDrivers.png?alt=media)
8. Select **Next** to install the drivers.
9. If the Windows Security box appears, asking if you would like to install this device software, select **Install**.

   The Windows has successfully updated your drivers window appears.
10. Select **Close**.

    In Device Manager, the port name updates.

    ![](https://893902233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR60wMwGxVlr3J15eCIGp%2Fuploads%2Fgit-blob-f6684a0807821404eb15948a54bd02eb28d840c9%2FPortNameUpdate.png?alt=media)
11. Repeat this procedure for each of the listed ports.
12. When you have finished updating the drivers, you should have one USB Modem driver, three USB Com ports and a do\_not\_use port listed:

    ![](https://893902233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR60wMwGxVlr3J15eCIGp%2Fuploads%2Fgit-blob-cf1b97f7783440fede75ba49522de3f431dee3eb%2FDriverInstallationComplete.png?alt=media)

    **Note:** The do\_not\_use port is for diagnostics. The MES tool uses one of the USB Com ports. Use one of the alternative USB Com ports for the terminal emulator – this cannot use the same port as the MES tool.

To install the MESSetup.exe tools:

1. Using the Windows 10 computer, go to:

   <https://eseye.zendesk.com/hc/en-us/articles/360009436498>
2. Download **MESSetup.zip**.
3. Extract the contents to your **Downloads** folder, then run **MESSetup.exe**.
4. Depending on your user permissions, a message box may appear: Do you want to allow this app to make changes to your device? Select **Yes**.

   The InstallShield Wizard starts.
5. Select **Next** to view the License Agreement.
6. Select **Yes** to accept the terms of the license agreement and install the MES tool.

   **Note:** Selecting **No** will close the wizard.
7. Select **Finish** to exit the InstallShield Wizard.

## Preparing the Cinterion® PLS62‑W Wireless Module for the latest Eseye Updater

We highly recommend that you remove existing Eseye Updater software from the Cinterion® PLS62‑W Wireless Module, using the following procedure. If the Eseye Updater does not exist, you will receive an `Error` response. You can ignore this response.

{% hint style="success" %}
Use a terminal emulator to perform the following procedure. For more information, see [Attaching to the Intelligent Cloud Connect](https://docs.eseye.com/modules/cinterion-r-pls62-w-wireless-module/attaching-to-the-intelligent-cloud-connect.md).
{% endhint %}

To uninstall existing Eseye Updater software:

1. Using a terminal emulator, type:

   `at^SJAM=2,"a:/EseyeUpdater.jad",""`\<return>

   `at^SJAM=3,"a:/EseyeUpdater.jad",""`\<return>

   Both commands return the following response if previous Eseye Updater software was uninstalled:

   ```
   OK
   ```
2. Leave the terminal emulator open.

## Downloading the software update onto the modem

To download the software update onto the modem:

1. Using Windows File Explorer, browse to **This PC**.
2. In the right-hand display panel, right-click **Module**.

   ![](https://893902233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR60wMwGxVlr3J15eCIGp%2Fuploads%2Fgit-blob-c4367e21f46cc0041ac71cc2879724ea2b596992%2FSoftwareUpdate1.png?alt=media)
3. In the shortcut menu, select **Properties**.
4. On the**Port** tab, select a **COM Port** that enables you to connect to the Cinterion® PLS62‑W Wireless Module.

   For information about which port to use, see Installing the USB drivers and Module Exchange Suite (MES).

   Use a terminal emulator to test the connection on that port. For information about checking if a device is ready to receive AT commands, see [General AT Commands for the Cinterion® PLS62‑W Wireless Module](https://docs.eseye.com/modules/cinterion-r-pls62-w-wireless-module/general-at-commands.md).
5. Select **OK** to connect to the Cinterion® PLS62‑W Wireless Module through that port.
6. Double-click **Module** to view **Module Disk (A:)**.

   ![](https://893902233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR60wMwGxVlr3J15eCIGp%2Fuploads%2Fgit-blob-8573273e1bee084aa7850b5c54e181bf599aea0f%2FSoftwareUpdate2.png?alt=media)
7. Double-click **Module Disk (A:)**.

## Installing the latest Eseye Updater

To install the Eseye Updater:

1. Using the Windows 10 computer, go to:

   <https://eseye.zendesk.com/hc/en-us/articles/360008923637>
2. Download **ICC\_EseyeUpdater\_\_\<version>\_.zip**, where *\<version>* is the latest version.
3. Extract the contents to your **Downloads** folder.
4. Copy**EseyeUpdater.jad** and **EseyeUpdater.jar** from the extracted **EseyeUpdater** folder to the **Module Disk (A):** folder.
5. Using a terminal emulator, type:

   `at^SJAM=0,"a:/EseyeUpdater.jad",""`\<return>

   The following response occurs: `OK`

   **Note:** You will receive an `Error` response if you did not copy the files to the Module correctly, or if you have not removed a previous version of the Eseye Updater. For more information, see Preparing the Cinterion® PLS62‑W Wireless Module for the latest Eseye Updater and Downloading the software update onto the modem.
6. Using the terminal emulator, type:

   `at^SJAM=4`\<return>

   The response must include:

   ```
   SJAM: "a:/EseyeUpdater.jad","EseyeUpdater","Eseye","<version>",1,<filesize>,0,2
   ```

   where:

   *\<version>* is the latest version of the Eseye Updater software, for example: 2.0.6

   *\<filesize>* is the EseyeUpdater.jad filesize
7. Using Windows File Explorer, in the **Module Disk (A):** folder, delete the following files:

   * EseyeUpdater.jad
   * EseyeUpdater.jar

   ![](https://893902233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR60wMwGxVlr3J15eCIGp%2Fuploads%2Fgit-blob-3e7fff1319c8c70492d51918739fbd1428be745f%2FSoftwareUpdate3.png?alt=media)

## Installing the latest software update

1. Using the Windows 10 computer, go to:

   <https://eseye.zendesk.com/hc/en-us/articles/360008924537>
2. Download **ICC\_ETM\_&#x20;*****\<version>*****.zip**, where *\<version>* is the latest version.
3. Extract the contents to your **Downloads** folder.

   Ensure you perform steps 4 and 5 separately, in order.
4. Copy the **update** folder from the extracted contents to the **Module Disk (A):** folder.

   **Note:** If you have previously updated the software, you must overwrite the existing files.
5. Copy the **Update.flag** file to the **Module Disk (A):** folder.
6. Remove power from the

   Cinterion® PLS62‑W Wireless Module

   for 20 seconds.
7. Restart the Cinterion® PLS62‑W Wireless Module.

   The software update takes place.
8. Using a terminal emulator, type:

   `at^SJAM=4`\<return>

   The response must include:

   ```
   SJAM: "a:/EseyeUpdater.jad","EseyeUpdater","Eseye","<version>",1,<filesize>,0,2
   ```

   where:

   *\<version>* is the latest version of the Eseye Updater software, for example: 2.0.6

   *\<filesize>* is the EseyeUpdater.jad filesize

   **Note:** The JRC version may differ, depending on the firmware version installed in the terminal. We recommend that you update the Cinterion® PLS62‑W Wireless Module to the latest Thales-supported JRC firmware for Java® ME 3.2.
9. Ensure the EseyeUpdater, ETM and CertificateConfigApp versions match those listed above.
10. Delete the following files if they continue to exist in the **Module Disk (A):** folder:

    EseyeUpdater.jad

    EseyeUpdater.jar

    Etm.jad

    Etm.jar

    CertificatesConfigApp.jad

    CertificatesConfigApp.jar

## Uninstalling the Module Exchange Suite

If required, you may need to uninstall the Module Exchange Suite.

To uninstall the Module Exchange Suite:

1. In the **Downloads** folder, double-click **MESSetup.exe**.

   Depending on your account set up, a User Account Control popup may appear. Select **Yes**.

   The InstallShield Wizard appears with the options to Modify, Repair or Remove the current installation.
2. Select **Remove**.
3. Select **Next**.

   A message box appears, asking you to confirm your choice.
4. Select **Yes**.

   If you are currently using the files, the Files in Use page appears, listing the open applications.
5. Select **Automatically close and attempt to restart applications**.
6. Select **OK**.

   The wizard closes the applications and uninstalls the Module Exchange Suite. The Uninstall Complete page appears.
7. Select **Finish** to close the wizard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eseye.com/modules/cinterion-r-pls62-w-wireless-module/updating-software-cinterion-pls62-w-wireless-module.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
