Having trouble with long wires (+-5m)

[podaen]

OS version: win7 Arduino IDE version: 1.6/1.8 Arduino Espressif sdk 2.0.2 MFRC522 Library version: 1.4.10 Arduino device: ESP32 MFRC522 device: RFID mini

https://nl.banggood.com/3pcs-RFID-Reader-Module-RC522-Mini-S50-13_56Mhz-6cm-With-Tags-SPI-Write-and-Read-p-1604816.html?utm_source=googleshopping&utm_medium=cpc_organic&gmcCountry=BE&utm_content=minha&utm_campaign=minha-beg-nl-pc&currency=EUR&cur_warehouse=CN&createTmp=1&utm_source=googleshopping&utm_medium=cpc_bgs&utm_content=sandra&utm_campaign=sandra-ssc-beg-nl-all-0910-13anv&ad_id=381659571753&gclid=Cj0KCQiAip-PBhDVARIsAPP2xc3f3JFAfeX_vbI8ORpCM8l008H68bLvHdPdFX7QN2CC4hxBUsgpKb4aAk6MEALw_wcB

I have two esp32 with the same connections

One with short wiring One with long wiring

The long wiring doesn't detect the rfid card, the short wiring does with the same shetch. What could be done to resolve this problem?

Before I had it working with sdk 1.0.6. Now I have sdk 2.0.2. In my search to detect the problem I did change anything... Or only changed the reset pin from 21 to 16 because I added an I2C keypad but that doesn't work ether on the long wiring, but I don't think this is a problem because with the short wiring it works. Evrything works before I connect the rfid.

#include <MFRC522.h> //library responsible for communicating with the module RFID-RC522
//#include <SPI.h> //library responsible for communicating of SPI bus
#include <SPI.h>

#define SS_PIN 5//14//5//10
#define RST_PIN 16//21//27//35//9
#define SIZE_BUFFER 18
#define MAX_SIZE_BLOCK 16
//#define greenPin 12
//#define redPin 32
//used in authentication
MFRC522::MIFARE_Key key;
//authentication return status code
MFRC522::StatusCode status;
// Defined pins to module RC522
MFRC522 mfrc522(SS_PIN, RST_PIN);

/* Set your new UID here! */
#define NEW_UID {0xDE, 0xAD, 0xBE, 0xEF}//old code C2 27 DA 1B , Card SAK: 08 , MIFARE 1KB

//#include "SdFat.h"
//#include "FreeStack.h"
//// **************** SD CARD
//const int SD_CS_PIN = 17;//22;// SS;//test multie spi devices
//#define SPI_SPEED SD_SCK_MHZ(4)
////const char MP3DirPath[] = "23/"; // MP3 path
////const char DirPath[] = "23/"; // MP3 path
//SdFat audio_SD;
//SdFile file;
//SdFile dir;
//int count = 0;

void setup()
{
    Serial.begin(9600);

    pinMode(19, INPUT_PULLUP);//miso needs a pullup (sd card reader)
    pinMode(RST_PIN, OUTPUT);

    SPI.begin(); // Init SPI bus

    //pinMode(greenPin, OUTPUT);
    //pinMode(redPin, OUTPUT);

    // Init MFRC522
    mfrc522.PCD_Init();
    Serial.println("Approach your reader card...");
    Serial.println();

    digitalWrite(RST_PIN, LOW);

    //Serial.println("SD Card directory sorting...");
    ////if (!audio_SD.begin(SD_CS_PIN)) {
    ////if (!audio_SD.begin(SD_CS_PIN, SD_SCK_MHZ(50))) {
    //if (!audio_SD.begin(SD_CS_PIN, SPI_SPEED)) {
    //    Serial.println("SD card error!");
    //    while (true);
    //}
    //Serial.print(F("FreeStack: "));
    //Serial.println(FreeStack());
    //Serial.println();

    //getMP3dir("01/");
    //getMP3dir("22/");

}
//
void loop()
{
    // Aguarda a aproximacao do cartao
    //waiting the card approach
    if (!mfrc522.PICC_IsNewCardPresent())
    {
        return;
    }
    // Select a card
    if (!mfrc522.PICC_ReadCardSerial())
    {
        return;
    }

    //// Dump debug info about the card; PICC_HaltA() is automatically called
    //// mfrc522.PICC_DumpToSerial(&(mfrc522.uid));</p><p> //call menu function and retrieve the desired option
    //int op = menu();
    ////Serial.println(op);
    //if (op == 0)
    //    readingData();
    //else if (op == 1)
    //    writingData();
    //else if (op == 2)
    //    writeNewUID();
    //else {
    //    Serial.println(F("Incorrect Option!"));
    //    return;
    //}

    readingData();
    //writeNewUID();//most card are not writeable //Mifare 1k cards don't have a changeable UID (according to the Mifare forum).

    //instructs the PICC when in the ACTIVE state to go to a "STOP" state
    mfrc522.PICC_HaltA();
    // "stop" the encryption of the PCD, it must be called after communication with authentication, otherwise new communications can not be initiated
    mfrc522.PCD_StopCrypto1();
}

//reads data from card/tag
void readingData()
{
    Serial.println("Reading data");
    //prints the technical details of the card/tag
    mfrc522.PICC_DumpDetailsToSerial(&(mfrc522.uid));

    //prepare the key - all keys are set to FFFFFFFFFFFFh
    for (byte i = 0; i < 6; i++) key.keyByte[i] = 0xFF;

    //buffer for read data
    byte buffer[SIZE_BUFFER] = { 0 };

    //the block to operate
    byte block = 1;
    byte size = SIZE_BUFFER; //authenticates the block to operate
    status = mfrc522.PCD_Authenticate(MFRC522::PICC_CMD_MF_AUTH_KEY_A, block, &key, &(mfrc522.uid)); //line 834 of MFRC522.cpp file
    if (status != MFRC522::STATUS_OK) {
        Serial.print(F("Authentication failed: "));
        Serial.println(mfrc522.GetStatusCodeName(status));
        //digitalWrite(redPin, HIGH);
        //delay(1000);
        //digitalWrite(redPin, LOW);
        return;
    }

    //read data from block
    status = mfrc522.MIFARE_Read(block, buffer, &size);
    if (status != MFRC522::STATUS_OK) {
        Serial.print(F("Reading failed: "));
        Serial.println(mfrc522.GetStatusCodeName(status));
        //digitalWrite(redPin, HIGH);
        //delay(1000);
        //digitalWrite(redPin, LOW);
        return;
    }
    else {
        //digitalWrite(greenPin, HIGH);
        //delay(1000);
        //digitalWrite(greenPin, LOW);
    }

    Serial.print(F("\nData from block ["));
    Serial.print(block); Serial.print(F("]: "));

    //prints read data
    for (uint8_t i = 0; i < MAX_SIZE_BLOCK; i++)
    {
        Serial.write(buffer[i]);
    }
    Serial.println(" ");
    Serial.println("Reading done");
    Serial.println("");
}

[podaen]

It has to be the long wiring, I triple checked evrything.

[podaen]

This is how I connected it

SDA 5 SCK 18 MOSI 23 MISO19 IRQ / GND GND RST 16 3V3 3V

[podaen]

I have it working, The ground was not connected and while testing I have added this line in the setup witch is wrong digitalWrite(RST_PIN, LOW);

[starfield33]

What I did was to put one ESP32 at each reader, and then let them communicate via wifi, Bluetooth, serial or Cbus. You then have ports to open doors & lights.

On 21 Apr 2022, at 10:17, Davy P. @.***> wrote:

 This is how I connected it

SDA 5 SCK 18 MOSI 23 MISO19 IRQ / GND GND RST 16 3V3 3V

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

[podaen]

It didn't work aqtually wel. It seems that multiple spi devices aren't really supported I suggest you add SdSpiConfig spiconfig (CS_PIN, SHARED_SPI, SD_SCK_MHZ(4)); to your library

I also tried this

    pinMode(RST_PIN, OUTPUT);//power on reset pin high
    digitalWrite(RST_PIN, HIGH);

    pinMode(SS_PIN, OUTPUT);//cs pin rfid high = disconnected from spi
    digitalWrite(SS_PIN, HIGH);//power down

it didn't work. The two seperatly it work, but when connecting the SCK, MISO, MOSI it doesn't work anymore.

[DrLou]

Though we haven’t tested this, empirically, here, I’ve been advised by colleagues expert in SPI that long distance connections shouldn’t be relied upon in designs.

We use SPI for a number of devices, and had envisioned distancing sensors, for example, at about 10 meters. My sense is that the voltage drops alone would make such a design troublesome.

Lou Picciano

On May 20, 2022, at 10:34 AM, Davy P. @.***> wrote:

It didn't work aqtually wel. It seems that multiple spi devices aren't really supported I suggest you add SdSpiConfig spiconfig (CS_PIN, SHARED_SPI, SD_SCK_MHZ(4)); to your library

— Reply to this email directly, view it on GitHub https://github.com/miguelbalboa/rfid/issues/583#issuecomment-1132970948, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABFSOOVIF5LZI5KCVU2NNLVK6PHZANCNFSM5T6J6ZOQ. You are receiving this because you are subscribed to this thread.

[podaen]

The length is not really an issue when they work sepratly, but together... I had a simulare issue on keypad with long wiring (non spi), they implemented scantime for that.

Anyway I had an other project with a display also connected with spi with a length few meters and after a couple of mounths it didn't work anymore ether. I dicided to, to connect them wireless. I think I am going to let it go. It will limit the distance of the rfid to the controller... In my case 5 meters would not be a problem.

I will use esp_now because I am using wifi on that particuare device. And wifi and bluetooth at the same time also doesn't work wel, but thanks for the info.

[Rotzbua]

As @DrLou mentioned I agree that is is an electrical engineering challenge. There are various reasons for failing. I know setups using 2m wiring having stability issues. They used thin not shielded wires. After switching to shielded quality wires it worked.

I do not see an issue in the code of this library. Due to this fact I would recommend @podaen to search help in an electrical engineering forum.

[starfield33]

Something that i am using with ESP32 is canbus and I’ve got that in multiple ESP32 boards talking to each other and they’re over some good distances. MCP2515 I’m looking for an ESP32 board with the MCP2515 bus module on it if anyone has seen one let me know. ;)

Very Best Regards, | Mit freundlichen Grüßen Graham Andrews

@. @. ‭ +44 (0) 7767 867944 Mobile - Europe

On 20 May 2022, at 19:22, Davy P. @.***> wrote:

 The length is not really an issue when they work sepratly, but together... I had a simulare issue on keypad with long wiring (non spi), they implemented scantime for that.

Anyway I had an other project with a display also connected with spi with a length few meters and after a couple of mounths it didn't work anymore ether. I dicided to, to connect them wireless. I think I am going to let it go. It will limit the distance of the rfid to the controller... In my case 5 meters would not be a problem.

I will use esp_now because I am using wifi on that particuare device. And wifi and bluetooth at the same time also doesn't work wel, but thanks for the info.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[podaen]

How long do you have it working... Year, month, days? And what protocol, RS485, RS232, ...

[podaen]

Is still SPI I see, but with a better error handling... Do you have it working with more than two devices? Or is it limited to two devices?

[podaen]

Is it this board you are using?