IP Kamera IP Kamera| This function block can be used to
transfer images from an IP camera to the visualization. Communication with the camera only takes place in the internal network, port forwarding is not necessary as the camera is read by the controller and forwarded to the app via a secure connection. Communication with the camera takes place exclusively via http queries. The camera must also support this. If there is a snapshot function in the web interface of the camera, this can generally also be read out. Cameras that are only displayed via an APP from the manufacturer cannot be connected. Livestream and sound are also not possible. |
Eingänge |
||
| FG |
Enable |
Optional enable, if the input is not
linked, the block is always enabled. |
| ST |
Snapshot
Trigger |
With this input a snapshot is taken
and optionally an email is sent. |
| SD | Snapshot reset | Resets the output number of snapshots. Controlled by the control element. |
Ausgänge |
||
| ST |
Status | 0 if query successful otherwise an error code (for support only). |
| SA |
Snapshot
Count |
Number of snapshots |
Parameter |
||
| URL
Http |
URL of the snapshot function of the camera. When this URL is called, a still image must be returned. | |
| Username |
Username |
|
| Password |
Passord |
|
| Options |
Special options for the query. This
option is available for support only. |
|
| Snapshot |
||
| Trigger |
Trigger for recording a snapshot, for example a motion detector. In this case, a still image is stored and can be displayed via the control element. | |
| Ringbuffer |
Number of images saved before the oldest is deleted. | |
| Delay |
Delay between trigger and recording. | |
| Mail |
||
| Active |
Enable mail sending. With each snapshot trigger, an email is sent with the saved image | |
| Address |
Email address | |
| Subject |
Subject | |
| Body |
Body | |
| Extension |
Extension of the image file, usually png or jpg. The controller itself cannot determine the image type, so the extension must be specified manually. | |