suppliers:hvac.io:vigilia
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
suppliers:hvac.io:vigilia [2020/09/30 17:09] – old revision restored (2020/09/20 21:27) 148.251.69.139 | suppliers:hvac.io:vigilia [2020/09/30 17:11] – old revision restored (2020/09/20 21:27) 148.251.69.139 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
====== Vigilia ====== | ====== Vigilia ====== | ||
Line 6: | Line 7: | ||
---- | ---- | ||
- | |||
[[https:// | [[https:// | ||
Line 16: | Line 16: | ||
**[[https:// | **[[https:// | ||
- | ===== Installation ===== | + | ====== Installation |
- | **//(For the upcoming version of Vigilia - not yet active)//** | + | ===== Server Installation |
- | [[.:vigilia: | + | This is only if you want to host your own Vigilia server. |
+ | Otherwise, you can simply use those provided by [[https://HVAC.IO|HVAC.IO]]. | ||
+ | [[.: | ||
- | ===== Supported | + | ===== Recording a BACnet |
- | Vigilia supports multiple VLANs and completely detach the control networks from the recorded data. This separation allows users to freely share the historical data with everyone without ever putting the control network at risk. | + | [[.: |
- | ==== Type A ==== | + | ---- |
+ | |||
+ | |||
+ | ====== Supported Network Configurations ====== | ||
+ | |||
+ | Vigilia supports multiple VLANs and completely detach the control networks from the recorded data. This separation allows users to freely share the historical data with everyone without ever putting the control network at risk. | ||
+ | |||
+ | {{ : | ||
+ | ===== Type A ===== | ||
Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central Vigilia server. | Type A is used to maximize shareability and allows multiple BACnet networks to send their data to a central Vigilia server. | ||
Line 37: | Line 47: | ||
- | ==== Type B ==== | + | ===== Type B ===== |
Type B is defined as the Vigilia server being installed within the enterprise network. This allows whoever is in charge of the BACnet network to also be in complete control of all the recorded data. (Building manager, IT departement, | Type B is defined as the Vigilia server being installed within the enterprise network. This allows whoever is in charge of the BACnet network to also be in complete control of all the recorded data. (Building manager, IT departement, | ||
Line 44: | Line 54: | ||
- | ==== Type C ==== | + | ===== Type C ===== |
Type C is similar to type B, except that it isn't accessible by the Internet. Only users from within the | Type C is similar to type B, except that it isn't accessible by the Internet. Only users from within the | ||
Line 51: | Line 61: | ||
- | ---- | + | ====== API ====== |
- | + | ||
- | + | ||
- | {{ : | + | |
+ | For an example application, | ||
- | ===== API ===== | ||
Developers can take a look at the [[http:// | Developers can take a look at the [[http:// | ||
Line 73: | Line 80: | ||
- | TODO: DOCS |
suppliers/hvac.io/vigilia.txt · Last modified: 2020/09/30 22:09 by frozenlock