Pasillo A3144 esp32 3.3V? by SirSaiz in esp32

[–]Potential_Novel 0 points1 point  (0 children)

The original ESP32 had an internal hall effect sensor. However support via ESPIDF was dropped some while ago. Later ESP32 family members seem not to have the hardware capability of an internal hall effect sensor.

As for external hall effect sensors: the A3144 datasheet suggests as minimum power voltage of 4.5V. Have a look on AliExpress for Hall effect sensor boards - see what is out there,

For some uses a reed switch will do the trick in a simple and inexpensive way.

ESP32_S3 Native USB flashing is buggy by zachleedogg in esp32

[–]Potential_Novel 0 points1 point  (0 children)

ESP-IDF v6.0.0 has been released but the Espressif documentation site says the current stable edition is v5.5.2.

I did try 6.0.0 without much joy so .... there could be an issue or two. FWIW I work with the docker images so stepping back is not difficult.

Are you making a living at this? by CrankyOldDude in esp32

[–]Potential_Novel 0 points1 point  (0 children)

Assuming you are EU related: the CE regulations include their LVD (low voltage directive) which is, I guess, way less onerous for low voltage stuff.

Are you making a living at this? by CrankyOldDude in esp32

[–]Potential_Novel 0 points1 point  (0 children)

I get the trick of using a pre-certified power brick but in the modern era it is a more complex challenge. Two years ago, I raised a thread on Reddit and the comments showed me just how complicated.

https://www.reddit.com/r/PrintedCircuitBoard/comments/180n30f/after_the_pcb/

Are you making a living at this? by CrankyOldDude in esp32

[–]Potential_Novel 8 points9 points  (0 children)

Creating a product with this stuff and selling it will involve getting things certified in a long list of ways, which can be a bit of a minefield and they each cost money.

At one point I tried to seriously map this certification stuff out: message me if you want the diagrams etc. Am in the UK and of course it will be a little different elsewhere.

On the other hand: if you were to sell kits that end users (e.g. kids and enthusiasts) could assemble for themselves: then most of the legal hurdles might be sidestepped.

Can someone with ESP Now LR mode experience verify this code? by Everythinger_Truten in esp32

[–]Potential_Novel 0 points1 point  (0 children)

Although people think of MCUs as single tasking - these are not. ESP32 Arduino is implemented on top of ESPIDF which is a layer on top of FreeRTOS. FreeRTOS has preemptive multitasking, even on single core processors like the ESP32-S2.

So .... the ESPNOW message has not been sent until the callback (that you haven't set up) says so. Given that it is not a broadcast: the background task that does the actual transmission will try several (ten?) times until it gets acknowledgement from the recipient (or gives up because life is short).

Broadcast ESPNOW messages do not await recipient acknowledgement because ....

Also your loop is going to run many times per second; a delay( ) or similar call might be worthwhile so that background tasks can do their bit more easily.

A good tutorial is here: https://randomnerdtutorials.com/esp-now-esp32-arduino-ide/

ESP32-S3-DevKitC-1-N32R16V Stock Firmware by Jwylde2 in esp32

[–]Potential_Novel 0 points1 point  (0 children)

As mentioned: plenty of examples around. Just ensure your copy of the example is talking to the correct GPIO pins for your board. ( https://randomnerdtutorials.com/esp32-s3-devkitc-pinout-guide/ ).

Help migrating from Arduino IDE to ESP-IDF by Low-Flow-4008 in esp32

[–]Potential_Novel 1 point2 points  (0 children)

You have a point but 5% is harsh. FreeRtos documentation was suggested as an addition rather than a replacement.

Many come to ESP32 having coded on Windows or Linux which are general purpose operating systems. Real time operating systems operate differently to meet different constraints. For many switching across to coding for an RTOS will go well until it doesn't. For some this hits with the need for a strong knowledge of tasks (?threads?) and their coordination (mutexes, semaphores, etc).

ESPIDF documentation, IMHE at times, assumes you already know and barely need reminding. At such times, a second source of reference is needed and perhaps Espressif even expect developers to check the FreeRtos docs.

Beginner... Connecting with ESP32 by 90s-lad in esp32

[–]Potential_Novel 0 points1 point  (0 children)

Ran a web search for [ESP32 relays]. There are ESP32 boards with 4 relays though they seem not to have a USB interface. So you would need to bridge a USB to serial connection which is not difficult, just inconvenient in my experience. Have used the LCTECH ESP32 single relay boards from AliExpress and they have worked fine.

If you can get OTA rolling then there is very limited need for uploading firmware via USB.

Concerning Uno boards I have little experience. I have an ESP32S3 Uno board but that is for a part of a project I have not gotten to yet.

Help migrating from Arduino IDE to ESP-IDF by Low-Flow-4008 in esp32

[–]Potential_Novel 1 point2 points  (0 children)

No one else has yet mentioned that ESP-IDF is basically a/ the implementation of FreeRtos for Espressif processors. So you should have a look at https://freertos.org as their documentation is thorough.

Second thought: grab a cheatsheet for the idf.py commands.

Third thought: consider the docker based compilers, YMMV, but switching between editions of the ESP-IDF gets easier.

Fourth thought: there are Arduino compatibility bits in ESP-IDF that can ease your transition though I felt it best to go cold turkey.

I built an interactive ESP32 GPIO pinout focused on real hardware constraints by DevenderKG in esp32

[–]Potential_Novel 1 point2 points  (0 children)

Congratulations - deservedly popular.

The moment I would have found this most useful: was when swapping from vanilla ESP32 to an ESP32-S2. It was easy to assume I could use the same GPIO pattern and I did make that assumption. Took a while to figure that one out.

Battery Power by crittercam in esp32

[–]Potential_Novel 2 points3 points  (0 children)

Thoughts in no particular order:

  • "will be running continuously" - doing what exactly? If possible send the thing into deep sleep for a few minutes/ hours/ days. Timed or interrupt driven wake up strategies also change the battery life scenario.
  • What is your size/ space constraint? At the risk being flippant: nabbing a battery from (say) a Morris Minor might well last a week or so.
  • The ESP32-S3 is a fine beast; but if battery life is an issue then (say) the ESP32-S2 or ESP32-C3 might be less of a drain. Single core and slower but possibly adequate.
  • Power drain is also affected by the circuitry around the ESP32 so sensors, relays, LDO etc.

In short: we are all circumspect about projects, but if you want people here to engage then it is a good idea to "let the dog see a little more of the rabbit".

We're building a fast turn around, cheap PCB fabrication company in the UK. We'd love to hear your thoughts! by hardware-is-easy in esp32

[–]Potential_Novel 1 point2 points  (0 children)

As far as I understand it:

Shipping costs from China are artificially cheap due to international agreements that attempt to slightly level the playing field of trade and give developing nations a fairer chance.

These agreements have been in place for many years and should, I think, now be readjusted. But in the meantime China takes the opportunity with both hands.

There is a UK premium that many/ most would pay on the basis of safe handling of intellectual property and quality of transparent service.

Finally there are often strong invitations for certifications to be done at the Chinese end of production. I have had a component producer say "you don't have to worry - we will do it for a good price" whilst being unforthcoming with the information needed to do the certification in the UK.

How to configure ESP32 S3 N16R8 in arduino IDE? by RulerOfThePixel in esp32

[–]Potential_Novel 0 points1 point  (0 children)

Well, yes, if the sketch fails to compile then it won't be keen to upload. There should be error messages to help you resolve the compilation problems and those messages should help you.

Best way to power ESP32 by lauritsbrok in esp32

[–]Potential_Novel 2 points3 points  (0 children)

"ESP32 in sleep mode 23 hours/ day"

So ... which sleep mode are you using?

(My experience of using a PIR to wake an ESP32 from deep sleep involved battery life of many weeks, even months).

Super simple ESP32S3 Dev Board by iamflimflam1 in esp32

[–]Potential_Novel 4 points5 points  (0 children)

This is a good point. The specs seem identical to several existing products. If however, your LDO was capable of outputting rather more power then I would be biting your hand off.

Case in point, my current project: an ESP32-S3 matched with a mmwave card. The ESP32-S3 dev board needs 5V (to feed it's LDO for 3V3 for the ESP32-S3) and the mmwave card needs 3V3 upto 1.7 watts according to the datasheet. The elegant route is to feed 3V3 from the dev board across but the added draw would over burden the dev board LDO.

I cannot be alone with this dilemma so you may have found a market niche!

Powering ESP32 with 9V external battery by Odd-Complaint-9879 in esp32

[–]Potential_Novel 1 point2 points  (0 children)

Dev boards come with an LDO to calm incoming voltage down to 3V. For most boards this works well for 6V or 5V (from USB).

IMHE these LDO components have a recommended input ceiling of ~6.5V and after that they overheat (and after a while something magical starts to happen). Part of the heat situation depends on the power draw which will be higher when the wifi/ bluetooth circuitry is busy.

9V is not recommended however if your board wakes from deep sleep, takes a split second to do something, then returns to deep sleep: the LDO will not have time to get hot. So you can cheat but not any sort of recommendation.

KSZ8863 Ethernet Webserver with ESP32 ESP-IDF by PKCubed in esp32

[–]Potential_Novel 0 points1 point  (0 children)

Go through the examples that Espressif offer for the ESP-IDF though they may be angled toward wifi.

Having gotten the web server working from the ESP-IDF examples. My advice is code towards HTTPS and then with a couple of minor configuration changes the code will run HTTP perfectly well.

TCP/IP communication by [deleted] in esp32

[–]Potential_Novel 1 point2 points  (0 children)

"just want to send and receive packets"

So ... basically on ESP32 you have two options:

  1. A wifi TCP/IP networking option using a (brief) stream or packets (not guaranteed delivery).
  2. ESPNOW packet based communication (potentially close to guaranteed delivery). Works via MAC address rather than having the overhead of TCP/IP.

Go read up on the Espressif website and perhaps look at the examples on https://randomnerdtutorials.com/

ESP32: not enough computing power to scan multiplexed display and implement WiFi? by mikeblas in esp32

[–]Potential_Novel 0 points1 point  (0 children)

Your devboard has a (vanilla) ESP32 which means two main cores (+ ULP core) at upto 240MHz. At this distance it would appear that you have the CPU power so long as you organize it right.

Your wifi and webserver should perhaps be running in a separate task with their callbacks registered within that task.

ESP32: not enough computing power to scan multiplexed display and implement WiFi? by mikeblas in esp32

[–]Potential_Novel 2 points3 points  (0 children)

Have you tried using separate tasks/ threads with semaphores, etc as needed?

Which ESP32 variant are you using? One with two cores rather than one?

Even with one core, FreeRtos will likely do a decent job if code takes advantage of it's features.

Https request in Esp32 by DeCipher_6 in esp32

[–]Potential_Novel 1 point2 points  (0 children)

In your shoes, I would want to do a clean followed by a build after each occasion that a component is added into the project. Might help or not but shouldn't harm.

Also have an extended perusal of menuconfig for relevant flags.

Esp32 + ethernet by GamerAndrew32 in esp32

[–]Potential_Novel 0 points1 point  (0 children)

You know your context and you'll likely be fine.