EBO Idea Exchange
Have ideas on how to improve the EcoStruxure Building Operation? Please share and get votes from our Community to influence development efforts.
Visit the brand new Software & Firmware Center, within EcoXpert Extranet
What are the main changes vs the previous solution :
For a better user experience and usability, files will be organized by “Software packages” related to versions (ex : EBO 2022).
A package now includes all needed items for the installation of a given version:
User | Likes Count |
---|---|
6 | |
5 | |
4 | |
2 | |
2 |
When you write from a StruxureWare program to a Lon device or a Xenta, you can define when the signal is written. It comes in handy that you can select "on change" as a StruxureWare point can be scanned VERY fast, and only populate the value to the Lon device or Xenta when a given value has changed.
But what happens when you want to consume data from a Lon device or a Xenta into a StruxureWare program or an alarm? Either you will consume a lot of bandwith, or you will have to make SNVT's on the local node (in the case of Lon devices) or internal variables in the StruxureWare server, and bind Xenta points to that. On binds to internal points you can define the read interval.
So why can't you define read interval on binds from a Xenta directly to a StruxureWare program?
Actually my idea is, that a lot more should happen in the background. StruxureWare should automatically make an invisible internal point when you bind from a Xenta point to a StruxureWare program or alarm. At least it should be possible to define read interval directly on a bind from a Xenta or Lon device to a StruxureWare program or alarm.
Link copied. Please paste this link to share this article on your social media post.
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.