Help
  • Get started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Brand Logo
Help
  • Get started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
close
  • Community Home
  • Forums
    • By Topic
    • By Topic
      EcoStruxure Building
      • Field Devices Forum
      • SmartConnector Forum
      EcoStruxure Power & Grid
      • Gateways and Energy Servers
      • Metering & Power Quality
      APC UPS, Critical Power, Cooling and Racks
      • APC UPS Data Center & Enterprise Solutions Forum
      • APC UPS for Home and Office Forum
      EcoStruxure IT
      • EcoStruxure IT forum
      • EcoStruxure IT™ Advisor CFD
      Remote Operations
      • EcoStruxure Geo SCADA Expert Forum
      • Remote Operations Forum
      Industrial Automation
      • Alliance System Integrators Forum
      • AVEVA Plant SCADA Forum
      • CPG Expert Forum DACH
      • EcoStruxure Automation Expert / IEC 61499 Forum
      • Fabrika ve Makina Otomasyonu Çözümleri
      • Harmony Control Customization Forum
      • Industrial Edge Computing Forum
      • Industry Automation and Control Forum
      • Korea Industrial Automation Forum
      • Machine Automation Forum
      • Modicon PAC Forum
      • PLC Club Indonesia
      Schneider Electric Wiser
      • Schneider Electric Wiser Forum
      Power Distribution IEC
      • Eldistribution & Fastighetsautomation
      • Elektrik Tasarım Dağıtım ve Uygulama Çözümleri
      • Paneelbouw & Energie Distributie
      • Power Distribution and Digital
      • Solutions for Motor Management
      • Specifiers Club ZA Forum
      • Електропроектанти България
      Power Distribution NEMA
      • Power Monitoring and Energy Automation NAM
      Power Distribution Software
      • EcoStruxure Power Design Forum
      • LayoutFAST User Group Forum
      Energy & Sustainability Services
      • Green Building Scoring and Certification Forum
      Light and Room Control
      • SpaceLogic C-Bus Forum
      Solutions for your Business
      • Solutions for your Business Forum
      Support
      • Ask the Community
  • Knowledge Center
    • Building Automation Knowledge Base
    • Geo SCADA Knowledge Base
    • Industrial Automation How-to videos
    • Digital E-books
    • Success Stories Corner
  • Events & Webinars
    • All Events
    • Innovation Talks
    • Innovation Summit
    • Let's Exchange Series
    • Partner Success
    • Process Automation Talks
    • Technology Partners
  • Ideas
    • EcoStruxure Building
      • EcoStruxure Building Advisor Ideas
      Remote Operations
      • EcoStruxure Geo SCADA Expert Ideas
      • Remote Operations Devices Ideas
      Industrial Automation
      • Modicon Ideas & new features
  • Blogs
    • By Topic
    • By Topic
      EcoStruxure Power & Grid
      • Backstage Access Resources
      EcoStruxure IT
      • EcoStruxure IT™ Advisor CFD
      Remote Operations
      • Remote Operations Blog
      Industrial Automation
      • Industrie du Futur France
      • Industry 4.0 Blog
      Power Distribution NEMA
      • NEMA Power Foundations Blog
      Energy & Sustainability Services
      • Active Energy Management Blog
      Light and Room Control
      • KNX Blog
      Knowledge Center
      • Digital E-books
      • Geo SCADA Knowledge Base
      • Industrial Automation How-to videos
      • Success Stories Corner
  • companyImpact

How to configure multiple LNS databases in one Vista database.

Building Automation Knowledge Base

Access this self-service resource 24/7 and post your questions or scroll through forums for answers on building automation.

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
  • Communities
  • Knowledge Center
  • Building Automation Knowledge Base
  • How to configure multiple LNS databases in one Vista database.
Options
  • Article History
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
Invite a Co-worker
Send a co-worker an invite to the Exchange 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

  • Field Devices Forum

Previous Next
Contributors
  • RobertAndriolo
    RobertAndriolo
  • PeterLarsen
    PeterLarsen
  • Tim_Arion
    Tim_Arion
  • Product_Support
    Product_Support

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Building Automation Knowledge Base
Options
  • Article History
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
0 Likes
1314 Views
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
Share

How to configure multiple LNS databases in one Vista database.

Picard Product_Support
‎2018-09-06 01:01 PM

Last Updated: Spock RobertAndriolo Spock ‎2022-11-29 06:39 PM

Issue

In many situations, customers need to integrate more than one LNS database into a single Vista database.

Product Line

TAC Vista

Environment

  • Vista
  • LNS
  • LonMaker
  • NL220
  • TAC Vista System Plug-In

Cause

  • This is very common in retrofit situations where a new LonMaker or NL220 database is created for the new section of the building. Still, the existing system was programmed in a completely separate LonMaker or NL220 database.
  • This is common for multi-building systems like school districts that expand and add schools or buildings over time and integrate into one Vista database.

Resolution

Some general rules must be followed when integrating multiple LNS databases into one Vista database.

These rules are:

  1. You can not integrate more than 4 LNS networks to 1 Vista database when doing straight LNS server-to-Vista server communication.
    NOTE: If more than four networks are needed, the system must utilize the Loytec NIC852 key and the Orion stack.
    • When using the Orion stack and 1 Loytec NIC852 key will expand Vista's capability to 8 LNS networks simultaneously.
    • If more than 8 LNS databases are needed, then multiple Loytec NIC852 keys are needed.
    • Vista can only communicate to 4 Loytec NIC852 keys simultaneously for a maximum of 32 LNS databases per Vista server.
    • It is recommended never to use more than seven ports on the NIC852 for serviceability reasons, with Lonmaker or NL220 truly giving the system a 28-network limitation.
  2. The Menta file paths from the site or engineering PC will be stored within the path structure of the System Plug-In. If these files are not in the exact same path on the Vista server that the LNS database is being integrated to, all.MTA files will have to be browsed for every controller. It is recommended to save all Menta files from the engineering Vista database to a folder on the machine to ensure they are the most current files. Then copy that menta files directory to the new Vista server to ensure the System Plug-In will search and copy the same path when transferring the network to the vista database.
  3. Every LNS database integrated into the Vista server must have a unique domain ID. See the instructions and screenshots below.

The screenshots and instructions below detail how to build one Vista database with two LonMaker databases. The first database will be called NETWORK1, and the second database will be called NETWORK2.

Please follow these instructions:

  1. Restore and open the LonMaker database NETWORK1 on the machine running the Vista server database into which the LNS system will be integrated. The Vista server must be running and logged in to continue with the next instruction.


     
  2. From the Visio menu bar, choose LonMaker and Network Properties. Set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.


     
  3. In the NETWORK1 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.


     
  4. In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name.  LNS_Network Name is good practice. In the example below, it is LNS_NETWORK1. Click Apply, then OK, and close to close the TAC Network Settings window.


     
  5. In the TAC Vista System Plug-In, click the Update TAC Network Icon. 


     
  6. Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.


     
  7. Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.


     
  8. Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK1 is the LNS port, and NETWORK1 is the physical LNS database.

 

The steps to add the second LNS database are almost identical except for steps 2 and 4  above. Follow these instructions to integrate NETWORK2 into the Vista database.

  1. Restore and open the LonMaker database NETWORK2 on the machine running the Vista server database into which the LNS database will be integrated. The Vista server must be running and logged in to continue with the next instruction.


     
  2. From the Visio menu bar, choose LonMaker and Network Properties and set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.


     
  3. In the NETWORK2 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.


     
  4. In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name. In the example below, it is LNS_NETWORK2. LNS_Network Name is good practice. Click Apply, then OK, and close to close the TAC Network Settings window.


     
  5. In the TAC Vista System Plug-In, click the Update TAC Network Icon. 

    update tac network.jpg
     
  6. Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.


     
  7. Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.


     
  8. Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK2 is the LNS port, and NETWORK2 is the physical LNS database.


    As network 2 does not use the default Domain length of 1 and Id of 11 and uses a Domain length of 1 ID 12, any operator panel used in this system will need this domain setup to work this network.  You can adjust the OP Domain setting as described in the following article, "No Answer" on an OP when connecting to a Xenta 280/300/400
Labels (1)
Labels:
  • TAC Vista
Tags (3)
  • Find more articles tagged with:
  • 6814
  • PeterLarsen22
  • RobertAndriolo22
Was this article helpful? Yes No
No ratings
Share
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 forum after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the forum - 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 © 2023 Schneider Electric, Inc