#ep1 pwm
26 messages · Page 1 of 1 (latest)
The EPW5 target should work
thanks I'll try
The EPW5 image does indeed work just fine with the EP1. While configuring the outputs via the web page it serves, I noticed that there's the option to configure it for I2C. Are there any supported (or experimental) use cases for that ?
There is experimental gyro receiver support
Wow !
Sorta a super-stripped down FC for simple stability ?
That link points to a pretting involved discussion. Has anyone stretched the basic ESP8285 based 2.4G recevier hardware design to include a gyro (really an IMU right ?), Baro, and GPS ? The latter would be super useful simply for the "find my model" use case.
ESP8285 doesn't have enough IO
Oh, and receiver battery telemetry along with all those other new things that we could view using the INAV Lua screens
It is a small chip, but there are of course high pin count ESPs out there.
My in-progress DIY '8285 based RX seems to have quite a few unused outputs after talking to the SX1280. Like 5...
Which is probably why there's a EPW5 available...
But it really looks to me like we could have SPI based '1280 pins, an I2C bus, serial port for the GPS, and still have three GPIOs left for PWMs (just enough for a small fixed wing).
I'll do the PCB design.
8285 isn't recommended for new designs, consider the esp32-c3 instead
I've already got dev boards for both the '8285 and -C3 (and a few bare parts for each) sitting on my desk. The plan was to get things running with the '8285, and then shift to a new CPU if I needed to and if that new CPU support was ready. Does the configurator or development environment fully support the -C3 ? If so I'll prototype with that.
Since the ESP8285 is aging and only has 2 more years of support from Espressif, the C3 is a good replacement.
The C3 has a few more GPIOs, does not do stupid things with to the IO pins during boot ...
Great. And with a few more I/Os we should have plenty of pins for my FC-like 2.4G RX.
Why not use something like a Pico D4?
Just not familiar with it. I see it is a SIP-style module. the package is a bit larger, but it is probably a win if it really has integrated most of the support stuff. Same question then, is the -D4 a supported path (that isn't too crazy bleeding edge) in the dev environment ?