Writing a configuration with springcoreconfig.exe

SpringCore is the umbrella name to the new generation of SpringCard devices (Puck, SpringPark, etc.) that share the same MCU platform and the same overall architecture. springcoreconfig.exe, a software from the SpringCore Tools suite, is the command-line utility to manipulate device configurations. It is typically intended to upload a complete configuration at once, but is also able to edit registers one by one.

This article shows how springcoreconfig.exe works.

Read More

Flashing a new firmware with springcoreflash.exe

SpringCore is the umbrella name to the new generation of SpringCard devices (Puck, SpringPark, etc.) that share the same MCU platform and the same overall architecture. springcoreflash.exe, a software from the SpringCore Tools suite, is the command-line utility to change a device’s firmware (i.e. to “flash” a firmware).

This article shows how springcoreflash.exe works.

Read More

Retrieving device’s data with springcoretool.exe

SpringCore is the umbrella name to the new generation of SpringCard devices (Puck, SpringPark, etc.) that share the same MCU platform and the same overall architecture. springcoretool.exe, a software from the SpringCore Tools suite, is the command-line utility to retrieve and display all device’s technical data.

This article shows how springcoretool.exe works.

Read More

Installing the SpringCore Tools on Windows, macOS and Linux

SpringCore is the umbrella name to the new generation of SpringCard devices (Puck, SpringPark, etc.) that share the same MCU platform and the same overall architecture.

To manage, configure and update these devices, SpringCard has developed SpringCard Companion, a complete and versatile hybrid solution that combines the ergonomics of a modern web application with the power of a gateway service running on Windows 10 (or later).

Read More

Getting started with SpringCard Companion

SpringCard Companion is the new all-in-one solution to manage, configure and update the latest generation of SpringCard “SpringCore” devices (Puck, SpringPark, etc). SpringCard Companion is an hybrid application that combines a clean, efficient and always up-to-date web front-end with a tiny local software, the Companion Service, that is the gateway between the cloud and the devices connected to your computer or local network.

As such, the Companion Service is also the base component to connect any application built for the web with the ‘physical world’ of PC/SC couplers and Smart Readers, using only simple WebSocket and REST API calls.

Before you start using SpringCard Companion Web application (available at companion.springcard.com) you should install the Companion Service on a Windows computer.

Read More

Securing the connection to the MQTT broker using TLS and SpringCore client certificates

The aim of this tutorial is to configure a SpringPark as a Network SmartReader/MQTT client with a mosquitto broker. The SpringPark in this configuration acts as an MQTT client (using TLS). It sends its tags to the mosquitto broker hosted at mqtt.springcard.com. 

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.

Read More

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.

Read More

How to setup and use a SpringPark as a SmartReader over TCP

The aim of this tutorial is to configure a SpringPark as a Network SmartReader. The SpringPark in this configuration acts as a TCP server (default factory port is 4000) and sends its tags to the client connected to this port.

For this howto, we will assume that:

  • your SpringPark is using a default (from factory) configuration.
  • you have some networking basis.

Our SpringPark will output tag information using the SCRDR format (cf. SCRDR Protocol).

Read More