The aim of this tutorial is to configure a SpringPark as a Network SmartReader using MQTT. The SpringPark in this configuration acts as an MQTT client and sends its tags to the broker.
Cloud
How to setup and use a SpringPark as an Amazon AWS client
The aim of this demonstration is to configure a SpringPark as a Network SmartReader/AWS client. The SpringPark in this configuration acts as an AWS IOT Core client (using TLS). It sends its tags/informations to Amazon’s cloud and can also receive commands.
We won’t cover the AWS’s side (lamba function, certificates, policies, …) but focuse on the device’s side.
For this howto, we will assume that:
- your SpringPark is using a default (from factory) configuration.
- you have some networking basis.
- you have some MQTT basis.
How to setup and use a SpringPark as a SmartReader/HTTP client
The aim of this tutorial is to configure a SpringPark as a Network SmartReader/HTTP client. The SpringPark in this configuration acts as an HTTP client (default factory port is 80) and sends its tags to the server.
For this howto, we will assume that:
- your SpringPark is using a default (from factory) configuration.
- you have some networking basis.
HTTP client feature added to FunkyGate-IP/RDR
What is still possible: the Classical Access Control Architecture
SpringCard FunkyGate-IP/RDR is a network-attached wall smart reader, targetting physical Access Control and adopted by modern office buildings, airports, sensitive areas. The FunkyGate-IP+POE/RDR is the powered-by-the-network version. In a classical Access Control Architecture, the FunkyGate-IP/RDR acts as a TCP/IP server, and the Door Controller or the Access Control Central Computer connects to every reader as a client. The communication uses a custom client/server protocol, designed for reliability, security and speed.