Initial commit

.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

.vscode/extensions.json

@@ -0,0 +1,10 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "platformio.platformio-ide"
+    ],
+    "unwantedRecommendations": [
+        "ms-vscode.cpptools-extension-pack"
+    ]
+}

.vscode/settings.json

@@ -0,0 +1,16 @@
+{
+	"files.associations": {
+		"*.ejs": "html",
+		"*.conf": "cisco",
+		"*.dis": "cpp",
+		"optional": "cpp",
+		"istream": "cpp",
+		"ostream": "cpp",
+		"system_error": "cpp",
+		"array": "cpp",
+		"functional": "cpp",
+		"tuple": "cpp",
+		"type_traits": "cpp",
+		"utility": "cpp"
+	}
+}

include/README

@@ -0,0 +1,39 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the usual convention is to give header files names that end with `.h'.
+It is most portable to use only letters, digits, dashes, and underscores in
+header file names, and at most one dot.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

lib/PN5180-Library

@@ -0,0 +1 @@
+Subproject commit ba9e3df1e034af3b4a810dbc574c8d4257971db0

lib/README

@@ -0,0 +1,46 @@
+
+This directory is intended for project specific (private) libraries.
+PlatformIO will compile them to static libraries and link into executable file.
+
+The source code of each library should be placed in a an own separate directory
+("lib/your_library_name/[here are source files]").
+
+For example, see a structure of the following two libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
+|  |
+|  |--Foo
+|  |  |- Foo.c
+|  |  |- Foo.h
+|  |
+|  |- README --> THIS FILE
+|
+|- platformio.ini
+|--src
+   |- main.c
+
+and a contents of `src/main.c`:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+PlatformIO Library Dependency Finder will find automatically dependent
+libraries scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

platformio.ini

@@ -0,0 +1,20 @@
+; PlatformIO Project Configuration File
+;
+;   Build options: build flags, source filter
+;   Upload options: custom upload port, speed and extra flags
+;   Library options: dependencies, extra library storages
+;   Advanced options: extra scripting
+;
+; Please visit documentation for the other options and examples
+; https://docs.platformio.org/page/projectconf.html
+
+[env:nodemcuv2]
+platform = espressif8266
+board = d1_mini
+framework = arduino
+upload_speed = 921600
+monitor_speed = 115200
+lib_deps = 
+	knolleary/PubSubClient@^2.8
+	bblanchon/ArduinoJson@^6.21.3
+	densaugeo/base64@^1.4.0

src/main.cpp

@@ -0,0 +1,178 @@
+// ESP-32    <--> PN5180 pin mapping:
+// 3.3V      <--> 3.3V
+// GND       <--> GND
+// SCLK, 18   --> SCLK
+// MISO, 19  <--  MISO
+// MOSI, 23   --> MOSI
+// SS, 16     --> NSS (=Not SS -> active LOW)
+// BUSY, 5   <--  BUSY
+// Reset, 17  --> RST
+
+#include <PN5180.h>
+#include <PN5180ISO14443.h>
+#include <PN5180ISO15693.h>
+
+#include <ESP8266WiFi.h>
+#include <PubSubClient.h>
+#include <ArduinoJson.h>
+
+#include "base64.hpp"
+
+#define PN5180_NSS 4
+#define PN5180_BUSY 16
+#define PN5180_RST 5
+
+PN5180ISO14443 nfc14443(PN5180_NSS, PN5180_BUSY, PN5180_RST);
+PN5180ISO15693 nfc15693(PN5180_NSS, PN5180_BUSY, PN5180_RST);
+
+const char *ssid = "PET Aflytningsvogn #43";
+const char *password = "zwr33htm";
+
+const char *mqtt_server = "192.168.24.215";
+
+const int deviceId = 7;
+
+WiFiClient espClient;
+PubSubClient client(espClient);
+
+void setup_wifi()
+{
+	delay(10);
+	// We start by connecting to a WiFi network
+	Serial.println();
+	Serial.print("Connecting to ");
+	Serial.println(ssid);
+
+	WiFi.begin(ssid, password);
+
+	while (WiFi.status() != WL_CONNECTED)
+	{
+		delay(500);
+		Serial.print(".");
+	}
+
+	Serial.println("");
+	Serial.println("WiFi connected");
+	Serial.println("IP address: ");
+	Serial.println(WiFi.localIP());
+}
+
+void reconnect()
+{
+	// Loop until we're reconnected
+	while (!client.connected())
+	{
+		Serial.print("Attempting MQTT connection...");
+		// Attempt to connect
+		if (client.connect("card-reader"))
+		{
+			Serial.println("connected");
+		}
+		else
+		{
+			Serial.print("failed, rc=");
+			Serial.print(client.state());
+			Serial.println(" try again in 5 seconds");
+			// Wait 5 seconds before retrying
+			delay(5000);
+		}
+	}
+}
+
+void setup()
+{
+	Serial.begin(115200);
+
+	nfc14443.begin();
+	nfc14443.reset();
+	uint8_t productVersion[2];
+	nfc14443.readEEprom(PRODUCT_VERSION, productVersion, sizeof(productVersion));
+
+	if (0xff == productVersion[1])
+	{ // if product version 255, the initialization failed
+		Serial.println(F("Initialization failed!?"));
+		Serial.println(F("Press reset to restart..."));
+		Serial.flush();
+		exit(-1); // halt
+	}
+
+	nfc14443.setupRF();
+
+	setup_wifi();
+	// client.setCallback(callback);
+	client.setServer(mqtt_server, 1883);
+	reconnect();
+}
+
+// read cards loop
+void loop()
+{
+	if (!client.connected())
+	{
+		reconnect();
+	}
+
+	client.loop();
+
+	uint8_t uid[255];
+	// check for ISO-14443 card
+	nfc14443.reset();
+	nfc14443.setupRF();
+	int8_t uidLength = nfc14443.readCardSerial(uid);
+	if (uidLength > 0)
+	{
+		Serial.print(F("ISO-14443 card found, UID="));
+		for (int i = 0; i < uidLength; i++)
+		{
+			Serial.print(uid[i] < 0x10 ? " 0" : " ");
+			Serial.print(uid[i], HEX);
+		}
+		Serial.print(", ");
+
+		unsigned char base64[32];
+
+		encode_base64(uid, uidLength, base64);
+		Serial.printf((char *)base64);
+		Serial.println();
+
+		DynamicJsonDocument doc(1024);
+
+		doc["deviceId"] = deviceId;
+		doc["cardUID"] = base64;
+
+		char buffer[1024];
+		size_t n = serializeJson(doc, buffer);
+
+		client.publish("card/read", buffer, n);
+	}
+	nfc15693.reset();
+	nfc15693.setupRF();
+	// try to read ISO15693 inventory
+	ISO15693ErrorCode rc = nfc15693.getInventory(uid);
+	if (rc == ISO15693_EC_OK)
+	{
+		Serial.print(F("ISO-15693 card found, UID="));
+		for (int i = 0; i < 8; i++)
+		{
+			Serial.print(uid[i] < 0x10 ? " 0" : " ");
+			Serial.print(uid[i], HEX); // LSB is first
+		}
+		Serial.print(", ");
+
+		unsigned char base64[32];
+
+		encode_base64(uid, 8, base64);
+		Serial.printf((char *)base64);
+		Serial.println();
+
+		DynamicJsonDocument doc(1024);
+
+		doc["deviceId"] = deviceId;
+		doc["cardUID"] = base64;
+
+		char buffer[1024];
+		size_t n = serializeJson(doc, buffer);
+
+		client.publish("card/read", buffer, n);
+	}
+}

test/README

@@ -0,0 +1,11 @@
+
+This directory is intended for PlatformIO Test Runner and project tests.
+
+Unit Testing is a software testing method by which individual units of
+source code, sets of one or more MCU program modules together with associated
+control data, usage procedures, and operating procedures, are tested to
+determine whether they are fit for use. Unit testing finds problems early
+in the development cycle.
+
+More information about PlatformIO Unit Testing:
+- https://docs.platformio.org/en/latest/advanced/unit-testing/index.html