Hello @gbrunner

Note: I don't have the UHF RFID unit, so my conclusion could be incorrect.

My guess is the error stems from the GPIO conflict regarding GPIO16 and GPIO17. In the M5Stack Fire those two GPIOs are already used internally for the PSRAM.

Note from M5Stack Fire documentation：
GPIO 16 / 17 of FIRE are connected to PSRAM by default, so when you connect or stack other modules, you need to pay attention to avoid conflicts with these two pins to prevent the device from not working properly and generating instability..

Unfortunately in the early days (before M5Stack Fire existed) M5Stack engineers have chosen GPIO16 and GPIO17 to be used for the UART port C (blue). In other words port C (blue) is inoperable in this case I am afraid. M5Stack remedied this situation in some modules by using dip switches to allow for different GPIOs being used for UART modules, but I don't see dip switches in the M5GO base.

I guess you could try a different port (and adapt the program), use an M5Stack Base (where GPIO16 and GPIO17 are not blocked by PSRAM) or modify the M5GO to use different GPIOs for UART.

Thanks
Felix

Old versions of ESP32-Arduino on Arduino IDE...

Yes, it is possible and it is EASY!

Following the official guide showing how to install the current version:
https://docs.espressif.com/projects/arduino-esp32/en/latest/installing.html

The only change needed is to download a diffent/old version of the code...

I did a test going back to 2021/FEB/23, and it WORKS!

Besides this bug being just a temporary stuff, I will document better how to use old versions of code, for IDF and for Arduino IDE, because there are probably MANY situations in which we would like to use/test different versions other than the current version...

Regards,
Valter

Hello @oktawianito

good to hear. Thank you for reporting back. I appreciate it.

Thanks
Felix

I asked M5Stack support, their answer is:

The ‘stuck’ design is the original function of the joystick, which we called 'self-clock'. For the purpose of keeping the joystick in one direction continuously, without manual operation.

Best Regards,
support@m5stack.com

@felmue That makes total sense! Thank you so much!
I replaced the PaHub with the Hub expansion unit. Everything works now.

@felmue

Thank you for your time. I will investigate the CAN issue further and if I can get it to work on the M5Tough, I will have to use the Fire for now although I will have to make a watertight enclosure because this goes onto a tractor.

A big Thank You for the uiflow example. I looked at the documentation but couldn't find it....

If I get this to work, uiflow would make it so much easier to update the code in the field

Thanks again!
Hannes

Hello @dailletaille

glad it worked. Thank you for reporting back. My guess is something's wrong with the UIFlow block - it would not be the first time.

BTW: the GPIO output is not directly connected to the motor; there is a MOSFET in between to translate between 3.3 V and 5 V. But 0.5 V is definitely too low for it to fully switch on. See schematic here.

Thanks
Felix

seems to have some server DNS issues. it will work normally later.

through ssh

https://docs.m5stack.com/en/quick_start/unitv2/config

did you have to add a terminal resistor between the H and L lines?

actually, this program is for the M5Core.

(connect UNITCAM with M5Core, and then the M5Core will show the image in the screen)

@tobias-h said in UHF RFID Unit (JRD-4035) on Arduino Uno:

E.g. what board to select in the board manager ?

In the Arduino IDE select: Tools - Board - Arduino AVR Boards - Arduino Uno.

May I suggest you first get more familiar with the Arduino IDE, your Arduino Uno board and some simpler sketch examples for the Arduino Uno? Then maybe do some experiments with the serial connection (which is needed to talk to the UHF RFID Unit)?

Alternatively you can always get an M5Stack device for which the example has been written.

Thanks
Felix

@felmue Thank you for your response. I also came to the conclusion that this device is not suitable for LoRa PoP applications. That is really a pity. This one is suitable for LoRa PoP (I got that one working) : M5 LORA-MODULE-868MHZ. https://shop.m5stack.com/products/lora-module-868mhz?_pos=2&_sid=e21d4a90e&_ss=r

@m5stack It works now as expected.

Hello @ckuehnel

I did some experiments with the ATECC608A version in the M5Core2 AWS kit. Using the aforementioned libraries with I2C address 0x35 I can make it wake up and read information from it. However for me it did not show up using an I2C scan, even after waking it.

From the full datasheet I understand that 0x35 is the default I2C address which can be modified exactly once to something different. Looks like that has not yet happened with the ATECC608A in my M5Core2 AWS kit.

In contrast the M5Stack ID Unit uses the ATECC608B version for which I was not able to find the full datasheet (it looks like it requires an NDA). I assume that either the same mechanism exists regarding I2C address for the B version and 0x60 is the default or it already has been modified from 0x35 to 0x60 by M5Stack. (I don't have the M5Stack ID Unit so I cannot confirm whether it uses 0x35 or 0x60.)

Thanks
Felix