Gate ~ FMCU ~ management dashboard/en: Unterschied zwischen den Versionen
< Gate ~ FMCU ~ management dashboardZur Versionsübersicht zurückkehren
← Gate ~ FMCU ~ management dashboard/en
← Gate ~ FMCU ~ management dashboard/en
(Markierung: 2017-Quelltext-Bearbeitung) |
| Zeile 5: | Zeile 5: | ||
{| class="wikitable" | {| class="wikitable" | ||
!Contact | !Contact | ||
| − | |||
!Type | !Type | ||
!Impulse | !Impulse | ||
| Zeile 11: | Zeile 10: | ||
|- | |- | ||
|'''A8''' | |'''A8''' | ||
| − | |||
|Output | |Output | ||
| − | |Yes ( | + | |Yes (500 ms) |
|Person has entered | |Person has entered | ||
|- | |- | ||
|'''A9''' | |'''A9''' | ||
| − | |||
|Output | |Output | ||
| − | | | + | |Yes (500 ms) |
|Alarms* | |Alarms* | ||
|- | |- | ||
|'''E3''' | |'''E3''' | ||
| − | |||
|Input | |Input | ||
| − | | | + | |Yes (500 ms) |
| − | | | + | |Open Entry |
|- | |- | ||
|'''E4''' | |'''E4''' | ||
| − | |||
|Input | |Input | ||
| − | | | + | |Yes (500 ms) |
| − | | | + | |Open Exit |
|- | |- | ||
|'''E6''' | |'''E6''' | ||
| − | |||
|Input | |Input | ||
|Yes (200ms) | |Yes (200ms) | ||
| Zeile 41: | Zeile 35: | ||
|- | |- | ||
|'''E7''' | |'''E7''' | ||
| − | |||
|Input | |Input | ||
|Yes (200ms) | |Yes (200ms) | ||
|Card is invalid, do not open the gate | |Card is invalid, do not open the gate | ||
| + | |- | ||
| + | |'''E8''' | ||
| + | |Input | ||
| + | |No | ||
| + | |Fire Alarm | ||
| + | |- | ||
| + | |'''E9''' | ||
| + | |Input | ||
| + | |Yes (500 ms) | ||
| + | |Open Entry 70% | ||
| + | |- | ||
| + | |'''E10''' | ||
| + | |Input | ||
| + | |No | ||
| + | |Emergency State button** | ||
|} | |} | ||
<nowiki>*</nowiki>A9 Alarms: | <nowiki>*</nowiki>A9 Alarms: | ||
| Zeile 110: | Zeile 118: | ||
<br /> | <br /> | ||
| − | === Architecture === | + | ===Architecture=== |
The picture below gives a bird's eye view of the configuration management. | The picture below gives a bird's eye view of the configuration management. | ||
<br /> | <br /> | ||
| Zeile 119: | Zeile 127: | ||
The Schema contains a set of data for describing controls in form components: | The Schema contains a set of data for describing controls in form components: | ||
| − | * Which controls should contain a component | + | *Which controls should contain a component |
| − | * Validations rules if any | + | *Validations rules if any |
E.g. a form component can contain a text box and an input for integers. The data range for integer should 1-100. | E.g. a form component can contain a text box and an input for integers. The data range for integer should 1-100. | ||
| Zeile 129: | Zeile 137: | ||
<span name="Roadmap"></span> | <span name="Roadmap"></span> | ||
| − | === Roadmap === | + | ===Roadmap=== |
The features are planned for the upcoming release: | The features are planned for the upcoming release: | ||
| − | * Configurations page allows you to see the list of available configurations. You can: | + | *Configurations page allows you to see the list of available configurations. You can: |
| − | ** Clone an existing configuration to a new one | + | **Clone an existing configuration to a new one |
| − | ** Delete a configuration | + | **Delete a configuration |
| − | ** Make a configuration active. Only one configuration can be used by the server and it is called ''active''. | + | **Make a configuration active. Only one configuration can be used by the server and it is called ''active''. |
| − | * Apply button. This should apply changes on-the-fly. | + | *Apply button. This should apply changes on-the-fly. |
| − | * Restart button. This should restart the docker container and apply settings, which cannot be applied on-the-fly. | + | *Restart button. This should restart the docker container and apply settings, which cannot be applied on-the-fly. |
| − | * Extend the vue form generator library: | + | *Extend the vue form generator library: |
| − | ** Make the switch control consistent with the switch controls on other pages | + | **Make the switch control consistent with the switch controls on other pages |
| − | ** Add a control which allows you to manage an array of items (e.g. the list of connected gates). E.g. <nowiki>https://codepen.io/safx/pen/AhCtk</nowiki> | + | **Add a control which allows you to manage an array of items (e.g. the list of connected gates). E.g. <nowiki>https://codepen.io/safx/pen/AhCtk</nowiki> |
| − | * Import/Export of a Configuration.json. | + | *Import/Export of a Configuration.json. |
| − | * Reset any configuration to the default one (by removing the json file | + | *Reset any configuration to the default one (by removing the json file |
<br /> | <br /> | ||
| − | == Management of Events == | + | ==Management of Events== |
The following sections contains the term '''Path''', which means the path is part of the URL. E.g., path '''/events''' for the FMCU Server running under '''<nowiki>https://server.maxcrc.de/</nowiki>''' means | The following sections contains the term '''Path''', which means the path is part of the URL. E.g., path '''/events''' for the FMCU Server running under '''<nowiki>https://server.maxcrc.de/</nowiki>''' means | ||
<nowiki>https://server.maxcrc.de/events</nowiki> | <nowiki>https://server.maxcrc.de/events</nowiki> | ||
| − | == Events == | + | ==Events== |
Web path: | Web path: | ||
/events | /events | ||
| Zeile 178: | Zeile 186: | ||
Edit this section | Edit this section | ||
| − | == Event Definitions Page == | + | ==Event Definitions Page== |
Path: | Path: | ||
/event-definitions | /event-definitions | ||
| Zeile 200: | Zeile 208: | ||
Edit this section | Edit this section | ||
| − | == Event Definition Groups == | + | ==Event Definition Groups== |
Path: | Path: | ||
/event-definition-groups | /event-definition-groups | ||
| Zeile 221: | Zeile 229: | ||
Edit this section | Edit this section | ||
| − | == Event Subscriptions == | + | ==Event Subscriptions== |
Web path: | Web path: | ||
/event-subscriptions | /event-subscriptions | ||
| Zeile 250: | Zeile 258: | ||
Edit this section | Edit this section | ||
| − | == Configuration == | + | ==Configuration== |
Path: | Path: | ||
/configuration | /configuration | ||
In order the emails with events can be sent out, the '''Email''' section with the information like the hostname, port etc. of the outgoing server and credentials should be properly configured. | In order the emails with events can be sent out, the '''Email''' section with the information like the hostname, port etc. of the outgoing server and credentials should be properly configured. | ||
<br /> | <br /> | ||