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

Change the Device Instance ID of a VT7000 series BACnet thermostat

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
  • Change the Device Instance ID of a VT7000 series BACnet thermostat
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
  • DavidFisher
    DavidFisher
  • BillNeville
    BillNeville
  • Benji
    Benji
  • CraigEl
    CraigEl
  • 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
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
0 Likes
1908 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

Change the Device Instance ID of a VT7000 series BACnet thermostat

Picard Product_Support
‎2018-09-07 01:44 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 11:18 PM

Issue

Using the keypad on the stat to set the comm address may result in duplicate Device Instance IDs on a BACnet network.

Product Line

Andover Continuum, EcoStruxure Building Operation

Environment

Viconics

Cause

Find New BACnet Device does not result in new Viconics stat added to the system. This is due to the default assignment ID scheme used by Viconics. It is resulting in a duplicate Device ID on the BACnet network.

Resolution

By default, the Device Instance ID (called the Device Node ID in Continuum) is generated using the first two digits of the model of the thermostat + the comm (MAC) address assigned to the stat. Example: For a VT7200C5000 thermostats with MAC address 115, the default Device Instance would be 72115.

The problem is that when installing the same model stats on multiple MSTP networks on the same BACnet system, this scheme can easily result in duplicate Device Instance IDs.

The resolution is to change the duplicates or use a scheme to assign unique IDs manually to all the stats on a system. Any number between 1 and 4194303 (between 1 and 3FFFFF in Hex) is accepted by the thermostat.

One scheme would be to use the BACnet Network ID and append the MAC address to it. Since each BACnet Network ID must be unique across the entire system, and the MAC address on each BACnet Network must be unique, this assures the combination is unique across the system.

For example, if you have a bCX with an MSTP bus on comm2 that has a BACnet Network ID - Comm2 of 2765 and a stat with a MAC address of 9, assign it the Device Instance ID 2765009.

A BACnet Explorer that provides write access to the Device Instance ID is required to change the default Device Instance ID. See Changing the BACnet device instance of the SE7000 series room controllers for a link to the Viconics VT7000 BACnet Configurator utility.

For additional support on the above utility contact Viconics Support at 1-800-563-5660.

Labels (2)
Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
Tags (1)
  • Find more articles tagged with:
  • 12248
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