We would suggest creating a couple issues here:
https://github.com/OpenEVSE/openevse_esp32_firmware/issues
1. RFID should work fine on the Olimex32 assuming there is an I2c port available. I would guess all that is needed is to define the i2c pins in platform.ini. Here is an example of the OpenEVSE board vs. Olimex.
[env:openevse_wifi_v1]
board = esp32dev
lib_deps =
${common.lib_deps}
${common.neopixel_lib}
adafruit/Adafruit MCP9808 Library @ 2.0.2
build_flags =
${common.build_flags}
${common.src_build_flags}
${common.debug_flags}
-D NEO_PIXEL_PIN=17
-D NEO_PIXEL_LENGTH=14
-D WIFI_PIXEL_NUMBER=1
-D WIFI_BUTTON=0
-D WIFI_BUTTON_PRESSED_STATE=LOW
-D RAPI_PORT=Serial
-D DEBUG_PORT=Serial1
-D I2C_SDA=21
-D I2C_SCL=22
-D ENABLE_MCP9808
-D ENABLE_PN532
-D TX1=16
[env:olimex_esp32-gateway-f]
# For hardware RevF and RevG
# https://github.com/OpenEVSE/ESP32_WiFi_V3.x/blob/master/docs/wired-ethernet.md
board = esp32-gateway
build_flags =
${common.build_flags}
${common.src_build_flags}
-D WIFI_LED=33
-D WIFI_LED_ON_STATE=HIGH
-D WIFI_BUTTON=34
-D WIFI_BUTTON_PRESSED_STATE=LOW
-D DEBUG_PORT=Serial
-D RAPI_PORT=Serial2
-D ENABLE_WIRED_ETHERNET
-D RESET_ETH_PHY_ON_BOOT=1
-D RX2=16
-D TX2=32
2. Feature Request for TFT/LCD. Serial pass through from Debug to OpenEVSE to use Wired Ethernet as the primary communications module.
Fabrice
Good morning,
I received the new LCD 3.5 today, which I ordered because I needed it for RFID. everything is ok and super nice.
So now in the end I have a problem so I can no longer use my Olimex32 Ethernet?
so at the beginning:
ESP32 RFID ok but WIFI :-(
Next
Olimex32 Ethernet Ok but no more RFID :-(
Next
I order the new LCD 3.5 RFID OK but no Ethernet
well I understood that LCD 3.5 and the openevse v5.5 and com series. but it is not possible to do anything with the LCD 3.5 debug serial port. just to have the MQTT I don't know ????