Thanks to both of you who replied, I got it working with your help!

The problem was the port I was connecting to. Using a USB-A to USB-C cable, connected to the Mac Mini M1's USB-A port got it to work and the device now shows up as /dev/tty.wchusbserialXXXXX

Very happy about this, just in time before the weekend. ;)

Thanks again!

@taako What country are you in and what are the wiring regulations?
you want a waterproof and wether resistant box along with cable glads for the power cable which prevent the ingress of water and critters.

@holofloh You weren't lying... Great results with M5Stamp C3

If anyone comes across this thread who are also disappointed by their generic WROOM-32 modules. Just buy the M5Stamp C3, they aren't much more (actually the same price when compared to the generic WROOM-32 modules on amazon!!) and they made my phone RSSI go from -80ish to -60 at the same distance and lower transmission power! My Watch transmission power i kept the same but it went from -85 to -60ish as well! That's a truly insane gain for such a small little thing. The generic modules trace antenna just doesn't cut it!

Plus they have a fun RGB LED you can configure!

I'm convinced, I'm going full M5Stamp!

At a glance I would say commenting out noInterrupts() and interrupts() is the correct thing to do. Can anyone tell us why are they even there?

The purpose of noInterrupts() is to prevent interrupt handlers from running in the middle of a critical section of code. But this makes no sense -- we are already in an interrupt handler here, where protection from other interrupts is already in effect until the function returns. At least that's the case for other Arduino microcontrollers -- admittedly, I haven't coded much for ESP32. Someone say something if I misunderstand this here.

Furthermore, setting a byte size variable to a constant value like 1 isn't the sort of thing that counts as a critical section of code that would ever need noInterrupts() in the first place.

I say it's safe to comment these two lines out and then I raise the question why were they ever there.

Hey! THis thread is pretty old, but I hope my 2 cents would still be helpful. In case you're still looking for a camera for OCR, the M5Camera and UnitV are both good options, but keep in mind that OCR technology is not solely dependent on the camera. The software you use is equally important. Have you considered trying out this automatic document scanning and OCR service? It can help you recognize text, numbers, and even colors from an image. You can find more info at https://smartengines.com/. Best wishes!!

Yes, you have to "switch" the lines between the IR Unit and the Atom :
One side is Tx -> RX, the other side RX -> TX

White line: IR Unit receives the signal and transmitts it(TX, marked "data" IN) ) to the Atom,. Atom is receiver (RX), (G32 as input)

Yellow line: Atom is the sender (TX) (G26 as output), IR Unit receives the data (RX) (marked "data" OUT) and transmitts the signal via IR (25Hz carrier) Check if it works with a mobile phone camera ...

The cause is the ESP32 bug.

M5Stack Community :
M5.BtnA.wasPressed() conflicts with WiFi
https://forum.m5stack.com/topic/3262/m5-btna-waspressed-conflicts-with-wifi

This is a report of measures for the A button of M5Stack and the B button of M5Stick C to operate without permission.
ButtonA on M5Stack does not work properly : May 02, 2021

void setup(){
WiFi.begin();
WiFi.setSleep(false);
}

or

#include <driver/adc.h>
void setup(){
adc_power_acquire(); // ADC Power ON

:

blog :
ButtonA on M5Stack does not work properly : May 02, 2021
https://macsbug.wordpress.com/2021/05/02/buttona-on-m5stack-does-not-work-properly/

0_1673987001392_p.jpg

Check out the code on my implementation on M5 Seismometer. I only worked on accelerometer, not gyro, but the calibration method is the same. You can also find the datasheet under /doc folder.

@robjasey Cool, can't wait to see the finished project and please consider writing it up and posting to hackster.io which is where you can find a turntable project of mine.

Hi @Ricky_M5Station

thank you for confirming the fix works.

I've created a PR to fix the issue.

Thanks
Felix

@wsanders
They won't work with phones as phones use the NFC version of RFID which works on a different band.

@teastain Thanks!

@viquaheeg520 I have a number of cameras that have caught fire whilst operating on charge. The ESP32 has cracked and literally let the smoke out. Not sure if that is related but clearly I can't risk using the 30 or so units we bought.

It's built like this image. My solar panel is a 5 volt 60mA panel. The battery is a 500mA lipo battery. The output on the right (in the image the dc-dc step up, my timercam is connected) in the image connects to the onboard connector of the Timercam. I've used the original plastic shipping case to construct a waterproof case for the components.
alt text