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

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Having set Link Addressing in a Sigma DNN3 can no longer communicate to the DNN3 and Link Addressing does not work.

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
  • Having set Link Addressing in a Sigma DNN3 can no longer communicate to the DNN3 and Link Addressing does not work.
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

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
1673 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

Having set Link Addressing in a Sigma DNN3 can no longer communicate to the DNN3 and Link Addressing does not work.

Picard Product_Support
‎2018-09-06 02:19 PM

on ‎2018-09-06 02:19 PM

Issue

Set-up the Link Addressing using the Pocket Terminal (LA +) for port 1 via the DNN3 service port and set port 2 on the DNN3 to be Serial PPP.  Can't communicate to the DNN3 from the Sigma server and global data is not being passed between the two VLAN's.

Environment

  1. Multiple Sigma controllers across at least two Ethernet VLAN's. 
  2. DNN3's (version 1.h) connected to each VLAN.
  3. Each DNN3 is connected to the VLAN via port 1 and port 2 is configured as a 'virtual' serial PPP port but not connected to a device.

Cause

  1. No routing information (static routes) entered into the DNN3's.   Although Link Addressing can be correctly configured the DNN3 devices also need to know where to transmit the point to point global data, that is the router device for the local Ethernet VLAN or default gateway.
  2. By having two ports configured on the DNN3 network routing messages RIP will be enabled and broadcast and will advertise the port 2 address as a potential but false route off the network, therefore RIP must also be disabled. 

Resolution

  1. Using Pocket Terminal or Windows Hyperterminal enter a default Static Route to the DNN3 via its service port.  Use the generic entry
    0.0.0.0/0 for the destination sub-LAN and mask.  For example;
    SR+ 0.0.0.0/0 192.168.1.253   1      (Where 192.168.1.253 is the default gateway and 1 is the DNN port number).
  2. RIP must also be disabled on the DNN3 port 1.  For example;
    RIPD 1
Labels (1)
Labels:
  • Satchwell BAS & Sigma
Tags (1)
  • Find more articles tagged with:
  • 4258
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