March 2018 |
[an error occurred while processing this directive] |
|
Join Project Sandstar
Articles |
Interviews |
Releases |
New Products |
Reviews |
[an error occurred while processing this directive] |
Editorial |
Events |
Sponsors |
Site Search |
Newsletters |
[an error occurred while processing this directive] |
Archives |
Past Issues |
Home |
Editors |
eDucation |
[an error occurred while processing this directive] |
Training |
Links |
Software |
Subscribe |
[an error occurred while processing this directive] |
Abstract: Project Sandstar
Background:
Sandstar integrates sandstar engine, haystack and sedona into a seamless whole:
Methods:
Device template is created in order to abstract system calls to GPIO,
I2C, UART and other hardware level communication. Within this file we
have utilized a tag called “channel”. A zinc in the form of grid with
records where “channel” tag which is type number is generated. Within
the zinc file we are forming all tags necessary to convert raw data
into cur val data form. This consists of tags that defines programming
data type, port definition, sandstar engine, localization conversion
and last regular haystack tags are defined for application abstraction.
Sandstar C/C++ engine consumes both files and communicates to both
Sedona and Haystack rest api.
Results:
Abstraction in both hardware level and point definition level enables
us to generate portable Sedona code. With the abstraction of IO, sedona
code can be written in a way it covers all potential input, output and
setpoint types. With the power of haystack ops (Rest api), we can add a
record to the sandstar engine thus enabling the branch of the Sedona
code that is waiting to be activated. We call this feature
meta-morphing programing. On the roadmap, having haystack client in
sedona will help us to have P2P device communication along with
historical data and analytics based control.
Conclusion:
Sandstar project will change how we think of DDC. Major improvements
are hardware independent sedona code, historical data based control
logic, driver abstraction via haystack can be achieved now. With the
improvements to haystack ops where Sedona components can be created
changed deleted and linked, artificial intelligence can be utilized to
generate and improve upon human generated DDC code.
https://project-haystack.org/forum/topic/595
Here is a demo on control trends :
https://youtu.be/WkJGU_kJvE0?t=3176
[an error occurred while processing this directive]Please join to the working group if you find this interesting and useful.
[an error occurred while processing this directive]
[Click Banner To Learn More]
[Home Page] [The Automator] [About] [Subscribe ] [Contact Us]