Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Upgrading a Xenta 102-AX to version 2.16 or later

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
  • Upgrading a Xenta 102-AX to version 2.16 or later
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close

Related Forums

  • Intelligent Devices Forum

Previous Next
Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • sesa119747
    sesa119747
  • Cody_Failinger
    Cody_Failinger

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Building Automation Knowledge Base
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
0 Likes
2443 Views

Link copied. Please paste this link to share this article on your social media post.

Trying to translate this page to your language?
Select your language from the translate dropdown in the upper right. arrow
Translate to: English
  • (Français) French
  • (Deutsche) German
  • (Italiano) Italian
  • (Português) Portuguese
  • (Русский) Russian
  • (Español) Spanish

Upgrading a Xenta 102-AX to version 2.16 or later

Picard Product_Support
‎2018-09-07 09:33 PM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-05 08:22 AM

Issue

Upgrading a Xenta 102-AX to v 2.16

Product Line

TAC Vista

Environment

  • Xenta 102-AX
  • LonMaker
  • NL220

Cause

Firmware upgrade

Resolution

The following instructions will describe the firmware upgrade process for three different LNS environments: LonMaker 3.1, LonMaker Turbo 3.2, and NL220.

The NXE, APB, and XIF files for upgrading the 102-AX are now available on The Exchange Download Center.

Preparation
 

  1. Always remember to make backups before beginning this process.
  2. Record the Neuron IDs for all Xenta 102-AXs that will be receiving the upgrade. If you do not record the Neuron IDs ahead of time, you will have to press the service pin on every controller being upgraded. A list of all Neuron IDs can be obtained in one of the following ways:
    1. Through TAC Vista Server
      1. Open TAC Vista Server
      2. Click on Reports > LonWorks Networks, Survey

        vistalonworkssurvey.png

         

      3. This process will open a .txt document which lists all controller names and Neuron IDs in the Vista database.
    2. Through Echelon LNS Utilities
      1. Navigate to Start > Programs > Echelon LNS Utilities > LNS Report Generator
      2. Select the LNS Network

        lnsselectnetwork.png

         

      3. Hit Generate

        lnsreportgenerator.png

         

      4. This will generate a .csv file in the designated location with controller names and Neuron IDs. This can be viewed using Microsoft Excel.
    3. Through NL220
      1. Choose either Subsystem or Channel view
      2. Depending on the view, right click either on the Subsystem or the Channel
      3. Select Print > Print list of nodes
      4. Select Export

        nlexportnodes.png

         

      5. Choose desired file format
      6. Hit OK
  3. If changes have been made to the configurations of the 102-AXs through any means other than the LNS plug-in (I/STAT, M/STAT, Vista Workstation) these parameters will first need to be uploaded to the LNS database. If this step is skipped, then any configurations made this way will be erased during the upgrade.
    1. In LonMaker 3.1
      1. Right click on a device
      2. Select Resynch CPs...
      3. Repeat for each 102-AX
    2. In LonMaker Turbo 3.2
      1. Right click on a device
      2. Select Commissioning > Resynch CPs...
      3. Repeat for each 102-AX
    3. In NL220
      1. Right click on a device
      2. Select Copy configuration values in memory
      3. Repeat for each 102-AX
  4. Download the NXE and XIF files for version 2.16 from The Exchange Download Center.
  5. Please note that during the upgrade process, the 102-AX will not function properly.
  6. In a multiple LIP or router database the dummy database can be created on a notebook PC.
    This allows for a local FT10 connection to the Lon network after the router. The existing network topology is not needed on the dummy database in this case.
     

Performing the Upgrade in LonMaker 3.1

It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created.

  1. Launch LonMaker
  2. Select New Network
  3. Set the new network to be Online and Network Attached. Do not register any plug-ins.
  4. Add a generic device *Note: The network has to represent the topology of the physical connection to the FT-10 channel
  5. Check Commission Device box, hit Next.

    lm31newdevice.png

     

  6. Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.

    lm31browsexif.png

     

  7. Specify channel. Hit Next.

    lm31specifychannel.png

     

  8. Default Properties selections are okay. Hit Next.

    lm31deviceproperties.png

     

  9. Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.

    lm31setneuronid.png

     

  10. Check the box for Load Application Image. Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.

    lm31loadappimage.png

     

  11. Set the desired state to Online. Set the Source of Configuration Property Values to Current values in device. This is an important step. If you do not set to current values in device, your previous configuration parameters will be erased. Press Finish to begin the download.

    lm31currentvalues.png

     

  12. Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.

    lm31loadingimage.png

     

  13. To upgrade the next 102-AX, right click on the device and select Replace. Repeat these steps for each 102-AX in the system.

Performing the Upgrade in LonMaker Turbo 3.2

It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created.

  1. Launch LonMaker
  2. Select New Network
  3. Set the new network to be Online and Network Attached. Do not register any plug-ins.
  4. Add a generic device
  5. Check Commission Device box, specify channel, hit Next.

    lm32newdevice.png

     

  6. Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.

    lm32browsexif.png

     

  7. Default Properties selections are okay. Hit Next.

    lm32deviceproperties.png

     

  8. Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.

    lm32setneuronid.png

     

  9. Check the boxes for "Load application image" and "Update firmware in device to match application image." Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.

    lm32loadappimage.png

     

  10. Set the desired state to Online. Set the Source of Configuration Property (CP) Values to "Application image file." Set the Device Specific CPs to "Preserve device values." This is an important step. If you do not preserve device values, your previous configuration parameters will be erased. Press Finish to begin the download.

    lm32currentvalues.png

     

  11. Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.

    lm32loadingimage.png

     

  12. To upgrade the next 102-AX, right click on the device and select Commissioning > Replace. Repeat these steps for each 102-AX in the system.

Performing the Upgrade in NL220

It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created.

  1. Launch NL220
  2. Log in and create a New project. Do not register any plug-ins.
  3. In SmartChannel, set the new network to be Attached.
  4. Under the Device Templates tab, right-click and select New Device Template.
  5. Create the New Device Template from interface file. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit OK.

    nlnewdevice.png

     

  6. On the Channel tab, right-click and select New node on
  7. Name the device and choose Create node from a device template. Select the newly created 2.16 device template. Uncheck Set all configurations to manufacturer's default.

    nlnewnode.png

     

  8. Right-click on the new device and select Install (network > commission in newer versions). Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you are going to service pin the controller, do it now.

    nlsetneuronid.png

     

  9. Right-click the device and select Download program. Choose Upgrade system version. You will receive a warning stating that upgrading the system image can leave the device in a bad state and break communication. You should only use this option if you are sure of what you are doing. Confirm, Yes, you want to continue. Configuration download should be set to Keep current configuration on node.

    nlloadappimage.png

     


    nlconfirmdownload.png

     

  10. Allow approximately 50 seconds for the application image to finish loading.
  11. To upgrade the next 102-AX, right click on the device and select Network > Replace. Repeat these steps for each 102-AX in the system.
Labels (1)
Labels:
  • TAC Vista
Tags (1)
  • Find more articles tagged with:
  • 3899
Was this article helpful? Yes No
No ratings

Link copied. Please paste this link to share this article on your social media post.

To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of