As usual, the boards will also come with a custom boot.py file that will set up the LAN for you. The flash memory will be partitioned with two nice 2.4 MB OTA partitions so we should be safe for a while as MicroPython keeps growing, and a nice 11 MB of flash will be available for the MicroPython file system! I'm hoping that version 1.17 will be released soon so I can give an official release to my CM to program in to the boards. Meanwhile, I have also managed to get a custom board config merged into upstream MicroPython so you can actually make use of all that flash memory! Up till now, I used the generic ESP32 images but they are made to use only 4 MB of flash. Nice progress! You can see the new RTL8201FI Ethernet PHYs and the ESP32-WROOM-32 E module with 16 MB of flash. Last night, I received this picture with surface mount components mounted: I think there shouldn't be confusion about which PHY this uses, since I have it in pretty big letters on the bottom. Īfter waiting for four months since I ordered them, Mouser finally shipped the SI3404A PoE chip to my CM, so they have started production.Revision 7 production progress Patrick Van Oosterwijck.But why do something ahead of time when you can do it when it's too late, right? 🙄 Now I only have to harass Mouser some more to try and get them to send me a PO for the new part numbers generated for this revision, after begging for months already. They are ready to ship them now and it's still looking good for getting stock mid-September. So an initial failure rate of 0.2%, and 0% after rework, that speaks very well to their build quality and processes. They reported two boards that failed on initial test, but they were able to correct the problem. Kingtop finished populating the through-hole parts and programmed and tested all boards: ) That worked, but hurt your hand when running too many boards. Much better looking than my fixture hacked together from two perf boards. To remove the biggest bottleneck in production called "me" from the equation as much as possible, I had my CM Kingtop build a fixture so they could program and test them, instead of me still having to do that with every board. MicroPython 1.17 dropped on Septemwhich meant that I finally had an officially released binary with support for the new wESP32 with 16 MB flash.
#LINKING ITEMS IN CHAT FOR POE ON A MAC FULL#
Other than those concerns, I want this module to be fully isolated (to prevent issues with long cabling), full featured (Ethernet, WiFi, Bluetooth LE, many ESP32 pins exposed), low cost and small.Ī quick progress report. I agree, so I made the USB programming/terminal port an optional module. Talking about the USB port, several potential users expressed the opinion to not burden every board with something that would likely only be used during once during programming and never again after that. Of course, from the USB port, only 5V will be available. So I settled for the following solutions: local power can provided either by adding a PoE injector, or through the (optional) USB port. Supporting both would require the circuit to support for a wide input voltage range making things more complex. The problem is that PoE uses 48V nominal to reduce wiring losses, but commonly available wall warts use lower voltages for safety. The ability to use local power instead of PoE is a nice feature, but also adds complexity and cost.
So I decided to take the middle road and do a 12.95W PoE class 3 design to start with. Some potential users also showed interest in compact, very low power systems, but there are plenty who were excited about the idea of having a decent amount of power available. So it seems prudent to not start at the highest power levels possible. While it would be nice to support as much power as possible, previous experience has taught me that high power opens all sorts of cans of worms related to heat dissipation and EMI. Or it could be set up as an access point for other WiFi or Bluetooth LE based sensors. So even if a deployment would be mostly Ethernet and PoE based, it would still be possible to connect a node with WiFi powered from another source if necessary. The nice thing about the ESP32 is that it's low cost and powerful, and provides WiFi and Bluetooth in addition to Ethernet. PoE capable network switches and injectors are also becoming quite common and have come down in price as well. Plenty for an ESP32 which takes only a watt or so, making it possible to power other loads. PoE can provide up to 12.95 W to a load while PoE+ specifies up to 25.50 W. I just completed an application-specific ESP32 based PoE board for a customer, and it got me thinking: how much interest would there be in a generic ESP32 PoE core board?īy using PoE, a single cable provides power as well as connectivity, easing deployment headaches for large installations.
0 kommentar(er)
