mesmerizer on a lolin d32 pro, i got it running! #461
heidepiek
started this conversation in
Show and tell
Replies: 13 comments 14 replies
-
Congrats. Your panels didn't need level shifters? Most seem not to.
International shipping from the US has seemed to be a challenge. If you're
looking for immediate satisfaction, there are a couple of designs around
with feature sets that are similar.
Of course, if you're spinning a PCB you can choose your own mix of ESP
modules, antenna placement, Power Delivery, audio inputs, and any other
features you consider important.
BTW, if you want more matrix effects, there's a git branch that has another
few dozen that landed on the cutting room floor.
Is that some beta version of CCRs Run In the Jungle?
…On Wed, Oct 11, 2023, 5:14 PM Marshall G Gates ***@***.***> wrote:
Nice!
—
Reply to this email directly, view it on GitHub
<#461 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD33ILRAZOCSEJ2YDSG3X64K5BANCNFSM6AAAAAA54NXJQM>
.
You are receiving this because you are subscribed to this thread.Message
ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7257317
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Welcome.
Unlike hobbyists, I find commercial designers for either strips or HUB75s
use level shifters because:
- They are required to meet the spec, even if they are not necessary for
most people.
- Because board manufacturers have to pay for returns, they are willing
to spend extra to be sure.
- Most people are succeeding without level shifters, but they are
running at reasonable temperatures with reasonable power supplies, and
short, quality cables.
It is important to understand your failure "using the wrong esps." to
eliminate future failures.
- What board/chip failed?
- How did it fail?
- Can you please include a copy-paste of any error messages,
screenshots, commands issued, product links, and anything else that is
relevant?
We may be able to help make the code or documentation work better. We may
be able to improve the error message or documentation so that other people
do not have the same problem. Even if you don't program (that's OK!) you
can still help the project.
Message ID:
… <PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7259242
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
FWIW, when I first started I used level shifters even for WS2812B, but have found they’re simply not required. The 3.3v data signal is regenerated at every LED and the 3.3v level has always been enough to register as “1”.
…-Dave
On Oct 12, 2023, at 2:19 AM, Robert Lipe ***@***.***> wrote:
Welcome.
Unlike hobbyists, I find commercial designers for either strips or HUB75s
use level shifters because:
- They are required to meet the spec, even if they are not necessary for
most people.
- Because board manufacturers have to pay for returns, they are willing
to spend extra to be sure.
- Most people are succeeding without level shifters, but they are
running at reasonable temperatures with reasonable power supplies, and
short, quality cables.
It is important to understand your failure "using the wrong esps." to
eliminate future failures.
- What board/chip failed?
- How did it fail?
- Can you please include a copy-paste of any error messages,
screenshots, commands issued, product links, and anything else that is
relevant?
We may be able to help make the code or documentation work better. We may
be able to improve the error message or documentation so that other people
do not have the same problem. Even if you don't program (that's OK!) you
can still help the project.
Message ID:
> <PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7259242
> @github.com>
>
—
Reply to this email directly, view it on GitHub <#461 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4HCF6VLBUCNI34P5TN6C3X66YYLANCNFSM6AAAAAA54NXJQM>.
You are receiving this because you are subscribed to this thread.
|
Beta Was this translation helpful? Give feedback.
1 reply
-
That's an impressive menagerie! Some of the effects you're showing actually
were ported to Mesmerizer, but didn't make the cut. You can build from that
branch
<https://github.com/PlummersSoftwareLLC/NightDriverStrip/tree/all-robertlipe-effects>
if you'd like to dumpster-dive.
Espressif's naming seems to be created to confuse and frustrate. Best I can
tell "devkit v1", like "DevKitC" or "DevKittM" refers more to the PCB,
pinout, voltage regulator, serial chip, geometry, etc. than to the actual
traits of the module that's resting upon it, much like the "D1 Mini" refers
to the shape and pinouts - which seemed to grow out of the test boards like
https://www.aliexpress.us/item/3256803832676168.html or back to 8266 days.
I could be wrong. You clearly have *plenty* of ESP32 experience, so we'll
move on.
The mesmerizer configuration DOES
<https://github.com/PlummersSoftwareLLC/NightDriverStrip/blob/d16dc796e72c18de0f0f02e203a3d2811e6bb52a/platformio.ini#L261>
require additional PSRAM beyond the 520K on the base module. Depending upon
which module <https://www.espressif.com/en/products/modules> was on that
board, it might work. The list is long, but in broad strokes WROVER is
probably OK and WROOM is probably not. It can get super confusing because
it's the total module and not just the SOC itself that determines your
fate. The raw ESP32-D0WD-V3, for example, may work or fail, depending on
whether it's packaged with PSRAM inside that little module.
This is one reason trying to name anything sensibly inside platformio.ini
is so hard - just figuring out what "ESP32" configuration someone really
really has is just crazy hard. It's even worse to try to support boards
that lay down the raw chips
<https://wiki.luatos.com/chips/esp32s3/board.html> and external SPI parts
and don't use modules at all. (I try to not think about regulatory
certification on such devices.) Trying to identify them well enough to
"support" them in platformio is hard.
If you're shopping, anything with a RISC-V core - i.e. all new parts. :-(
- right now is bad for us in a matrix build because Espressif hasn't
shipped any dual-core RISC-V parts yet. They've announced one, the P4, but
it doesn't include the WiFi feature that was their whole claim to fame.
It's odd.
I would not expect the "no serial data received" failure case, though. I'd
expect the chip to start to boot and then crash, but after generating
enough output that the monitor would have displayed something. I can't
explain that and I dont' have any without PSRAM do duplicate or improve
that exact combination.
D1-Mini with even ESP8266 is crazy popular with the WLED crowd. It's much
smaller/simpler code that works fine on those inexpensive boards.
If your first board has NO PSRAM, that would partially explain it. I'd
expect the 'mesmerizer' configuration to fail, but in a different way. I
may try simulating one without PSRAM (I think I can tinker with the esptool
boot configuration) and see if I can at least make it fail more gracefully.
Homebrew hardware (like yours, mine, and Marshall's) are just tough to
guide people through. Glad you found your way.
Thanx for talking it through. This was helpful. As a bonus, I just
discovered that I've spent too much money and time on another project
recreating a board that Espressifi actually sells. :-/
|
Beta Was this translation helpful? Give feedback.
2 replies
-
On Sat, Oct 14, 2023, 3:11 PM heidepiek ***@***.***> wrote:
I downloaded this branch:
https://github.com/PlummersSoftwareLLC/NightDriverStrip/tree/all-robertlipe-effects
Uploaded it and tryed it. But i uploaded the main branche again, missed
the analyzers.
Adjust the #if 1/#else tuning at
https://github.com/PlummersSoftwareLLC/NightDriverStrip/blob/87686904968a3eb655a5f128e70bdd6ca6a4ae55/src/effects.cpp#L366
to include exactly the effects you like.
Remove the #else to get them all. You can comment out individual ones with
// if you like instead of turning them off via remote or web.
I 3d printed a diffuser for the matrix. It`s now much smoother on the eyes.
Good call. Remember to account for heat dissipation if it's close.
I wil try to make a pcb for this really nice project. It will take a while!
Work, kids and a wife 😏
There are a couple of designs around. Adapting from a commodity board to
the HUB75 connector is easy, but net expensive.
Working with the modules electrically is easy. The ugly digital and rf
signalling is all inside the can.
If rf doesn't intimidate you and you want to lay smt chips (soc + flash +
sram) and build from scratch, know that Espressif has a free design check
service where they'll inspect your schematic, BOM, and layout to ensure
maximum awesomeness.
The S3 has a pin mux at the front end so you can put most any function on
most any pin to simplify layout with only a few extra lines of code.
I'd suggest remembering to bring out many if the extra pins to posts. Next
month you might want to add some random i2c or spi peripheral for sensors
or extra functions.
Enjoy.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Cool. Congrats!
WROVER-E is what the official Mesmerizer boards use. Clearly it gets the
job done.
If you want USB host or more flash/ram or more GPIOS, etc. there are other
modules out there with other ESP cores that aren't much more.
S3 is what Matrix Portal and Trinity both use. I don't remember their exact
configurations, but neither of them are using the latest, biggest chips.
Since nothing currently in the Mesmerizer base uses very much flash (I have
projects in progress that do) it's far from a deal-breaker. I like the S3
because I can JTAG them without extra cables.
…On Thu, Nov 2, 2023 at 3:06 AM mikejohnau ***@***.***> wrote:
Wrover is ok. Just got memerizer working with a wrover.
—
Reply to this email directly, view it on GitHub
<#461 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD3ZJT5746NZHNMQLNSDYCNH7HAVCNFSM6AAAAAA54NXJQOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINJTGY2DO>
.
You are receiving this because you commented.Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7453647
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Sure.. itsmpae5 I'd the doc for those xhos.
https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/jtag-debugging/
…On Thu, Nov 2, 2023, 7:30 AM mikejohnau ***@***.***> wrote:
*I like the S3 because I can JTAG them without extra cables.*
Can us non-programmer types get some some info on how to do this....?
—
Reply to this email directly, view it on GitHub
<#461 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD37S5AZGNPKSQ25ADTDYCOG55AVCNFSM6AAAAAA54NXJQOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINJWGIYTI>
.
You are receiving this because you commented.Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7456214
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Robert, this is kind of hard for beginners to understand all this. Jtag
isn't that just the connection to a loose wrover esp chip? 5V Gnd D+ and
D-?
Remember to distinguish between the ESP chip, the ESP Module, if used, and
the board if any, that it's on.
ESP Chips <https://www.espressif.com/en/products/socs>: ESP32, ESP32-S3,
ESP32-S (Their names are frustrating.)
ESP Module <https://www.espressif.com/en/products/modules>: Wrover, Wroom,
Mini (more form factors than actual products) will contain a chip and zero
or more PSRAM and SPI Flash modules.
ESP Boards <https://www.espressif.com/en/products/devkits>: the rectangular
things from Adafruit, Sparkfun, HiLetGo ,M5, generic
<https://github.com/witnessmenow/ESP32-Cheap-Yellow-Display>, etc. that
use a chip or a module an combine it with screens, connectors, buttons,
voltage regulators, etc. Boards can go from the size of a thumbnail
<https://www.aliexpress.us/item/3256805313615427.html?> (maybe too few pins
for a robust mesmerizer build. maybe
<https://wiki.seeedstudio.com/xiao_esp32s3_pin_multiplexing/#:~:text=The%20XIAO%20ESP32S3%20has%20up,pins%20for%20reading%20and%20writing.>.
It's right on the edge.) to the popular Mini form factor on up.
In a group like this, it's easy to forget who is working with each as
electronics nerds often "grow" between levels. We have people of all
different levels in the group.
JTAG is the debugging interface that lets programmers (or hardware people)
single step through code, inspect and modify program state, pause/resume
the program from running, etc. The advantage of JTAG over sofware debuggers
is that you can single step through boot or exception handlers or other
code that's problematic to debug when the debugger IS the exception
handler, for example.
Do you always use a wrover s3 loose chip on a homemade pcb or a shield?
That is not easy for beginners and end users right?
I don't build around chips. I build around modules and quite bare eval
boards all the time. I'll choose five $5 boards over a $25
commercially-named dev board in a cute plastic case every time. That's just
me.
You talk about a wrover chip every time,
I talk about lots of things. I talk too much. :-)
I tend to buy and collect and use relatively bare
<https://www.aliexpress.com/w/wholesale-esp32-s3.html> boards with lots of
GPIOs that I can build around. Sometimes I start with the raw modules but
they're a bit small for me and by the time I add voltage regulators and a
few connectors, they're not really any cheaper in low quantities. I'm much
happier working with .100 (2.54mm) posts than 1.27mm module pins and the
ability to breadboard is worth something to me.
If I'm just driving a WS2812 strip with existing effects, I'll use a $4
board and not think much about it.
If it's something I'm doing active development on, I'll want a board with
an S3 just so I don't have to deal with another tangle of wires to attach a
debugger. Whether I pick up this $4 board or that $4.50 board isn't very
interesting to me. Another USB cable, another dangling board, and five
extra dupont cables to use a debugger from my laptop at 4 a.m. is a
deal-breaker.
So a board with an esp32 wrover chip. But it does not work!
With enough determination, I bet it will. You may spend some time working
out things like the speed of the external flash (dual vs. quad vs. octal
SPI, for example) but I think any dual-core ESP32 xtensa board can be made
to boot and run NDL. It can admittedly be pretty frustrating to work out.
(And our current build system isn't helpful.)
I think because that board only has 4psram and 8ram (am I saying it right?)
I think I read somewhere in the discussion section that dave was talking
about minimum 8psram and 8ram.
The project currently uses very little flash. Boards with NO external RAM,
running with only the 520k, may have problems, but once you get the
external RAM working - and working within the rules of NDL, such as only
certain speeds of memory being practical to DMA from for frame buffers, but
fine for plain networking bufers, for example - the 2MB boards should work,
too.
What I personally find easy is an esp board with usb connection that I can
just hook up to the computer! That is why I want to make a shield with
headers that I can click on. Cheap and effective.
No arguments. I CAN SMD solder (on good days) but it's certainly not my
goto hobby.
That's what I think the jtag is for then.
JTAG can be used for uploading or for debugging.
The original ESP32 only had serial connections and had four external pins.
To connect it to a contemporary computer, your board has a USB->Serial
bridge (CH340, CH2102, etc.) and if you want to use JTAG, you have to
attach another cable with another dongle and attach the four individual
JTAG pins. This drives up the cost of the board, makes wiring fragile.
I advocate for ESP32-*S3* because the chip has a USB host/target controller
built in. The board doesn't HAVE to have another dumb serial bridge chip
that often costs almost as much as th eESP32 chip itself. On reset, that
same controller presents two interfaces to the host computer: one is a
serial port and one is the JTAG interface. Now you have serial console,
JTAG, and power all over one clean ESP cable.
As a bonus, once the chip is booted, if you load the right software into
the ESP32, it can pretend to be things like a disk drive. You can just copy
files to and from the host PC, for example. This isn't an area well
explored (well, at all) in the public NDL tree, but it's a reason I'm
willing to pay a few coins more for a board based around the ESP32-S3.|
S3 is what boards like https://esp32trinity.com/ and
https://learn.adafruit.com/adafruit-matrixportal-s3/overview use. Both
those boards are designed around the modules, making them safe to sell and
use in any country where Espressif has obtained certification.
You can also put a separate cable with the 5V Gnd d+ and d- soldered on the
pcb and a usb connector at the end.
That's exactly what these boards are doing for you.
My point is the S3 has USB interface right on the chip. You can literally
run the USB connector wires to the chip and connect to the "serial" port
that's on it. I advocate using boards (or modules) with the S3 because
they're more powerful boards and the cost isn't really higher because you
can save the cost of the USB/Serial bridge.
But to design a pcb for that is more difficult and more expensive than
what I had in mind.
There's another thread right now where someone IS designing their own PCB.
I don't always remember who is working on what.
Have no electronics training, over the years hobbyistically taught myself
things.
Same. I may have just gotten a head start. :-)
The nightdriver strip software is a mighty fine piece of enginering,
created and tweaked by clever people like you.
I think that the electronics/software ecosystem using open source software
(gcc, gdb, freertos, etc.) and relatively open, inexpensive parts is a
really exciting place these days. With an afternoon and some wire
wrapping/breadboarding, it's entirely possible to go from a pile of parts
to a working, programmable THING that does something useful. If you're
lucky - and determined - you'll learn something along the way because of
the efforts of OTHER smart people, also pulling themselves up by the
bootstraps, that have made their own efforts available for free and
documented them in videos or web pages and shared things along the way. I
think that's pretty cool.
Electronics wasn't like this even 25 years ago. The gap between blinking a
light with a 555 and building a useful computer was ridiculous. Parts like
ESP32, STM32, the various RISC-V SOCs, and Pi 2040 or the respective board
have made this whole field quite accessible to the masses. I love it! (This
is why when I was faced with an early involuntary retirement, I came back
to this place to 'play'.)
Such a dumbass like me is also trying to get this done on his matrix. But
that's not easy sometimes, the team nightdriverstrip is always willing to
explain.
We've reached a pretty happy core of people that are trying to help others
grow. Building that community is challenging.
But often it goes beyond the user. I think it would be easy that there
would be some more info on the start page like for example the pinout of
the matrix hub connection.
I struggled with myself in that very detail in the beginning. Of all
things, that header was the ONE file not indexed in my searchable tree
because it started with a capital letter. You're not wrong.
I think there's some awkwardness around describing too much of the
electronics of the official Mesmerizer hardware. I don't think it's been
spoken about, but if there's a business model around selling official
Mesmerizer hardware, it's possible that they may not want to make it too
easy to clone. (For example, I've asked about that crazy header on the
official board and couldn't get answers.) OTOH, the source is right there
and there are other ESP32/HUB75 boards around and the engineering involved
to reproduce a similar result isn't huge. With the source published,
secrets are hard to keep.
Pinout of the microphone.
In another thread, we recently (days ago) opened the can of worms that
there are actualy two types of microphones (analog and I2S) supported, each
with different pins and requirements. One isn't easily reconfigured to use
different pins via globals.h or platformio configurations at all.
pinout of the ir. minimum specs of the esp chip. Then it would be a bit
more user friendly. Sure everything is in the header files, but not
everyone can make sense of it.
In discussions with Rutger, I've grown to understand this is a
source-oriented DIY project that's oriented to the hardware hacker crowd.
Especially for the 2812 projects, the entry ticket is pretty low. You can
buy a $3 board, attach a string of lights, struggle with the power supply
issues, and have results in ten minutes. It would be cool to have a couple
of every <https://www.adafruit.com/search?q=esp32> popular board out there
and recommend pinouts for everything and have a configuration in
platformio.ini ready to roll. It would be crushingly expensive to collect
and support...and it kind of defeats the idea of letting hardware people
figure out what pins they attached the pushbuttons to and on.
I do very much agree that doc - internal and otherwise - in this project is
a problem. I've taken steps to help with this. I'm continuing to kick
around ideas for naming and configurations to separate our concepts of
display configuration (umbrella vs. spectrum), hardware configuration
(pinouts), effects, teasing apart our board/display molecules ("wrover" and
"spectrum" actually are completely independent, though platform.ini
disagrees - we could build a loland32_pro running the SPectrum display if I
wanted to) and a hundred other configurations - existing and otherwise -
that are desirable or nonsensical. I think that needs a deeper fix than
just documenting what we have. I've been thinking about it, but haven't
reached a proposal state yet.
So I agree. As we get more discussions going with people like yourself, we
see more configurations that people want to build and the problems they run
into, along with possible ways to make it easier. Every time we onboard
another committed dev, we generate a small flurry of doc (like this) and
changes to the official tree, configuration, and doc to make it easier for
the next person. Rutger also has been really big on adding doc and
improving messages in various places to let us all help 'see'
configurations that we may not be able to to build and run ourselves.
I don't think we're done yet. :-) Folks like you actually DOING THINGS with
the project instead of just building and running an existing configuration
are the lifeblood of projects like this.
Message ID:
… <PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7459301
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Indeed. I can type up a storm!
I'm also quite aware I'm sometimes best taken in small doses. Just ask my
wife. :-) For non-English speakers, I'm sure that's additionally
challenging.
I can also be really educational. Honest. Theres a week's worth of
classroom material in that post I just sent to you. Mentoring others that
take the time to digest and comprehend my writing is pretty gratifying. The
interns I mentored professionally loved me.
Because I've worked remotely for decades, I tend to answer everything that
might be asked about whatever I'm answering. This might reduce a day's
turnaround of time zone delays, for example. (You'll see I've done that in
this message. Instead of asking what "doesn't work" means and waiting for a
reply, I've offered at least five different ways we can work together.)
I just gave away my two most recent HUB75 boards this weekend. One was a
fragile mess of dupont wires because I knew he'd WANT to build something
else. The other I mounted to a small perfboard and just mounted a board, a
HUB75 socket, and the ability to use it for either a HUB75 or a couple of
GPIOs out to screw terminals so he could attach 2812 strings with different
firmware.
I don't have the Matrix or Trinity that I linked earlier, but if you want
one of those, I'll buy one for delivery here to the U.S. and will partner
with you to build up a Mesmerizer style project around it. I have drawers
full of microphones and IR diodes (and screens and GPS and accelerometers
and multiplexer and sensors and random transmitter/receiver pairs and ...)
so between us we can build up your dream board together. Both are open
source hardware with schematics
<https://learn.adafruit.com/adafruit-matrixportal-s3/downloads> available
so they're easy to modify.
I have enough things like both styles of mics that we can document how to
build/add either.
The boards I gave away were built around the LuaTOS ESP32-S3:
https://wiki.luatos.com/chips/esp32s3/index.html (extremely chinese - use
the translate in the left panel for your lanaguage ... and you have to do
it on every page change). These are even available on Amazon
<https://www.amazon.com/LuatOS-Development-Bluetooth-Interfaces-Compatible/dp/B0CDX87YX4>
in 3-packs. Tamshun
<https://www.amazon.com/Tamshun-ESP32-Development-Interfaces-Compatible/dp/B0CC8SC4XZ>
has sold the board under a few different SKUs - it's the same board with
the URL on the back rubbed off.
The other S3 board that I inventory in bulk are the YD-ESP32-S3's like
https://www.aliexpress.us/item/3256803838808294.html (link grabbed at
random. This is almost 2x the price I've been paying. $5.20 for a 16MB
board on my last order...) It's a clone of Espressif's own DevKitC (
https://mischianti.org/vcc-gnd-studio-yd-esp32-s3-devkitc-1-clone-high-resolution-pinout-and-specs/
)
Other projects are collecting information on boards like this. See
https://docs.zephyrproject.org/latest/boards/xtensa/esp32s3_luatos_core/doc/index.html
for example. The Arduino and PlatformIO projects are also collecting
pinouts and doc references in a consistent, useful way.
https://docs.platformio.org/en/latest/boards/index.html
If you link to the board you can't make work and details on WHY it doesn't
work, if it's inexpensive (say, under $25USD), I'll just buy it, have it
delivered here, and work with you to get it added to the project. But if
we're picking from scratch, let's go with something like the MatrixPortal
that'll be widely available, have some support, and should help more people.
I'm willing to toss some of my toy budget and my time into helping you -
and others - succeed. Others have helped me, directly and indirectly, since
the 80's and probably even 70's. If you want to partner up on a $$$ board,
I have an original, early-run ESP32-S3 box
<https://www.espressif.com/en/news/ESP32-S3-BOX-3> that I don't think I've
powered up. I bought it by mistake and earmarked it for a project before I
started accidentally collecting ESP32's in my RISC-V herd. That'd be
another nice feather in the project's cap to support if you want to partner
up on it. This would also motivate me to actually build up a real, sane
platformio and document pair instead of the slash and burn "build this
tree for this project" hacks I've done so far.
I have a box of other ESP32 hardware of different types including some
camera <https://www.amazon.com/gp/product/B0CGRK4PZ9> boards that look
need, but don't have enough GPIO pins free to be useful and some bare
<https://www.amazon.com/gp/product/B0B3MVGCFV> modules that I've used super
minimal <https://www.youtube.com/watch?v=J4Y7GZvlmQs> or mounted to boards
<https://www.aliexpress.us/item/3256803826692194.html>. (That video
highlights just how little support components you REALLY need with the
S3.) None of this is particularly how I'd build a NDL project and
certialnly not a HUB75 board, but it's an example of just how much ESP32
*stuff[1]* I now have.
So - if you want to work together to get a DIY/Third Party ESP32-S3
Mesmerizer built up, I'm interested in helping. Options above included:
1) Matrix Portal (I like this idea)
2) Trinity
3) You tell me what you have that didn't work and we'll try to
replicate/fix it.
4) You start with boards I've had success with
4a) LuaTOS
4b) YD-GND-32 or the Espressif boards it's based on. (esp. if I don't have
to buy one. :-)
5) ESP32-Box.
Between us, I'll bet we can get some blog pages out of it, some more
working blinking lights, and some patches contributed to the project to get
one of the above supported more officially.
Is your tolerance for reading English through a firehose high enough to
tackle it? :-) I don't really consider myself an electronics pro, so i'd
look forward to learning more from someone a few chapters ahead of me.
RJL
[1] The funny thing is that I don't even consciously collect ESP32s. I'm a
RISC-V devotee that has WAY more RISC-V stuff than ESP32. ESP32 leftovers
and hand-me-downs are just more plentiful.
P.S. I keep the original Mesmerizer hardware from Dave here for testing and
development. I don't want to send Rutger a patch that runs on one of my
hacked up boards but not the originals. So that's what I do my 'official'
development on - even if I sometimes take it to one of the others so I can
run GDB without attaching a JTAG project.
…On Fri, Nov 3, 2023 at 12:38 AM heidepiek ***@***.***> wrote:
Just out of bed, and curious as I am thinking would robert have already
answered. You sure talk a lot! Just as well, am much wiser now. Thanks for
the explanation! One more question: can you send me a link or a picture of
a s3 board you own and use for the mesmerizer? There are so many boards for
sale. And have purchased wrong ones a few times now. And yes, you may get
them running, but I don't have your brains😳
Thanks robert! much appreciated
Now off too work!
Greetzz harrie
—
Reply to this email directly, view it on GitHub
<#461 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD3YHNP6ZCNFLHKSSDIDYCR7PDAVCNFSM6AAAAAA54NXJQOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINRTGQ4DS>
.
You are receiving this because you commented.Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7463489
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
You haven't said what doesn't work, but the most troubling line in your
output is this:
(704) psram: PSRAM ID read error: 0xffffffff
This shows thatyou're building a configuration that's trying to use PSRAM,
but it's failing. The results are unlikely to be good.
If your chip has no PSRAM (I can't remember if USE_MATRIX *requires* it or
just really likes to have it) then your build configuration shouldn't use
it and if your chip DOES have PSRAM, this is the hint that it's not
working, such as having the wrong
${psram_flags.build_flags}
for your SOC.
I also suspect we have to be a little careful about phrasing, though
this may make matters even more confusing. AIUI, "Mesmerizer" refers to the
exact circuit board that ships from Dave's Garage. We can build HUB75
projects that aren't Mesmerizers.
I think more WROVERS have PSRAM than WROOMS. See
https://docs.espressif.com/projects/esp-idf/en/release-v4.2/esp32/hw-reference/modules-and-boards.html
to figure otu which SOC you really have.
(Action item to self. Add some debugging gibberish BEFORE this line that
shows us which of the zlllion ESP32's we actually have, the detected
physical configuration, etc.)
…On Fri, Nov 3, 2023 at 2:45 PM heidepiek ***@***.***> wrote:
Very nice of you to want to help me, and in different ways too. What I
would like is for you to assist me with the boards I have now that I can't
get to work. The other suggestions are not for me. Have a wife and kids
that need attention. Bought a house that also needs some remodeling. Busy
at work, so in the late evenings I am often tinkering in my shed.
Guess all the work then comes to you would we start a project. By now i
have the Olimex ESP32-WROVER-DevKit-Lipo up and running. Unfortunately not
on my shield. I have a shield from rorosaur made for an esp32 devkit v1.
[image: rorosaurus shield 1]
<https://user-images.githubusercontent.com/104028471/280394075-788b2043-c047-4e6a-bb1e-033d25329dd6.jpg>
[image: rorosaurus shield 2]
<https://user-images.githubusercontent.com/104028471/280394112-02c88042-a988-4770-b5bb-7c52cd5f1b67.jpg>
esp32 devkit v1
[image: esp32 devkit v1]
<https://user-images.githubusercontent.com/104028471/280394258-4f58c11d-d84a-4839-849f-3f0ca28c24af.jpg>
olimex esp32-wrover-devkit-lipo
[image: olimex esp]
<https://user-images.githubusercontent.com/104028471/280394871-572802e3-e2db-4ae0-9aff-1ccfd6414157.jpg>
I thought the olimex version was similar to the devkit, but the olimex has
more pins. And unfortunately a few in a different place! However, the
olimex is a wrover-e . Must upload it with the default_envs =
mesmerizer_lolin though
If I want to upload it with default_envs = mesmerizer it goes wrong!
Would the mesmerizer also want on an esp32 defkit v1? It has a wroom chip
not a wrover.
If I upload it with default_envs = mesmerizer_lolin i get this in the
serial:
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13232
load:0x40080400,len:3028
entry 0x400805e4
E (704) psram: PSRAM ID read error: 0xffffffff
E (705) esp_core_d⸮f.}⸮⸮⸮͡⸮ No core dump partition found!
E (705) esp_coreReplacing Idle Tasks with TaskManager...
(I) (PrintOutputHeader)(C1) NightDriverStrip
�[0m(I)
�[0m(I) (PrintOutputHeader)(C1)
------------------------------------------------------------------------------------------------------------
�[0m(I) (PrintOutputHeader)(C1) M5STICKC: 0, USE_M5DISPLAY: 0, USE_OLED:
0, USE_TFTSPI: 0, USE_LCD: 0, USE_AUDIO: 1, ENABLE_REMOTE: 1
�[0m(I) (PrintOutputHeader)(C1) ESP32 PSRAM Init: FAIL
�[0m(I) (PrintOutputHeader)(C1) Version 40: Wifi SSID: "heidepiek" - ESP32
Free Memory: 195852, PSRAM:0, PSRAM Free: 0
�[0m(I) (PrintOutputHeader)(C1) ESP32 Clock Freq : 240 MHz
�[0m(I) (setup)(C1) Startup!
�[0m(I) (setup)(C1) Starting DebugLoopTaskEntry
�[0m>> Launching Debug Thread. Mem: 195852, LargestBlk: 110580, PSRAM
Free: 0/0, (W) (ReadWiFiConfig)(C1) Retrieved SSID and Password from NVS:
"heidepiek", "********"
�[0m(W) (setup)(C1) Starting ImprovSerial for ESP32
�[0m[ 374][E][vfs_api.cpp:182] remove(): /improv.log does not exists or is
directory
Launching JSON Writer Thread. Mem: 187248, LargestBlk: 110580, PSRAM Free:
0/0, (W) (DeviceConfig)(C1) DeviceConfig could not be loaded from JSON,
using defaults
�[0m(W) (NotifyJSONWriterThread)(C1) >> Notifying JSON Writer Thread
�[0m
Starting SmartMatrix Mallocs
Heap/32-bit Memory Available: 175300 bytes total, 110580 bytes largest
free block
8-bit/DMA Memory Available : 143176 bytes total, 110580 bytes largest free
block
Total PSRAM used: 0 bytes total, 0 PSRAM bytes free
SmartMatrix Layers Allocated from Heap:
Heap/32-bit Memory Available: 148128 bytes total, 110580 bytes largest
free block
Starting SmartMatrix DMA Mallocs
sizeof framestruct: 00004000
DMA Memory Available before ptr1 alloc: 82788 bytes total, 77812 bytes
largest free block
matrixUpdateFrames[0] pointer: 3FFE46C4
DMA Memory Available before ptr2 alloc: 82788 bytes total, 77812 bytes
largest free block
matrixUpdateFrames[1] pointer: 3FFE86D4
Frame Structs Allocated from Heap:
Heap/32-bit Memory Available: 114912 bytes total, 77812 bytes largest free
block
8-bit/DMA Memory Available : 82788 bytes total, 77812 bytes largest free
block
Total PSRAM used: 0 bytes total, 0 PSRAM bytes free
Allocating refresh buffer:
lsbMsbTransitionBit of 0 requires 49152 RAM, 77812 available, leaving
28660 free:
Raised lsbMsbTransitionBit to 0/7 to fit in RAM
lsbMsbTransitionBit of 0 gives 76 Hz refresh, 180 requested:
lsbMsbTransitionBit of 1 gives 152 Hz refresh, 180 requested:
lsbMsbTransitionBit of 2 gives 300 Hz refresh, 180 requested:
Raised lsbMsbTransitionBit to 2/7 to meet minimum refresh rate
Descriptors for lsbMsbTransitionBit 2/7 with 16 rows require 12288 bytes
of DMA RAM
SmartMatrix Mallocs Complete
Heap/32-bit Memory Available: 102592 bytes total, 65524 bytes largest free
block
8-bit/DMA Memory Available : 70468 bytes total, 65524 bytes largest free
block
T�
I also have a couple of wemos esp32 d1 mini`s. Same story, i can upload
but then i get this in the serial:
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13232
load:0x40080400,len:3028
entry 0x400805e4
E (704) psram: PSRAM ID read error: 0xffffffff
E (705) esp_core_d⸮f.}⸮⸮⸮͡⸮ No core dump partition found!
E (705) esp_coreReplacing Idle Tasks with TaskManager...
(I) (PrintOutputHeader)(C1) NightDriverStrip
�[0m(I)
�[0m(I) (PrintOutputHeader)(C1)
------------------------------------------------------------------------------------------------------------
�[0m(I) (PrintOutputHeader)(C1) M5STICKC: 0, USE_M5DISPLAY: 0, USE_OLED:
0, USE_TFTSPI: 0, USE_LCD: 0, USE_AUDIO: 1, ENABLE_REMOTE: 1
�[0m(I) (PrintOutputHeader)(C1) ESP32 PSRAM Init: FAIL
�[0m(I) (PrintOutputHeader)(C1) Version 40: Wifi SSID: "heidepiek" - ESP32
Free Memory: 195852, PSRAM:0, PSRAM Free: 0
�[0m(I) (PrintOutputHeader)(C1) ESP32 Clock Freq : 240 MHz
�[0m(I) (setup)(C1) Startup!
�[0m(I) (setup)(C1) Starting DebugLoopTaskEntry
�[0m>> Launching Debug Thread. Mem: 195852, LargestBlk: 110580, PSRAM
Free: 0/0, (W) (ReadWiFiConfig)(C1) Retrieved SSID and Password from NVS:
"", "********"
�[0m(W) (setup)(C1) Starting ImprovSerial for ESP32
�[0m[ 374][E][vfs_api.cpp:182] remove(): /improv.log does not exists or is
directory
Launching JSON Writer Thread. Mem: 187248, LargestBlk: 110580, PSRAM Free:
0/0, (W) (DeviceConfig)(C1) DeviceConfig could not be loaded from JSON,
using defaults
�[0m(W) (NotifyJSONWriterThread)(C1) >> Notifying JSON Writer Thread
�[0m
Starting SmartMatrix Mallocs
Heap/32-bit Memory Available: 175304 bytes total, 110580 bytes largest
free block
8-bit/DMA Memory Available : 143180 bytes total, 110580 bytes largest free
block
Total PSRAM used: 0 bytes total, 0 PSRAM bytes free
SmartMatrix Layers Allocated from Heap:
Heap/32-bit Memory Available: 148132 bytes total, 110580 bytes largest
free block
Starting SmartMatrix DMA Mallocs
sizeof framestruct: 00004000
DMA Memory Available before ptr1 alloc: 82792 bytes total, 77812 bytes
largest free block
matrixUpdateFrames[0] pointer: 3FFE46C4
DMA Memory Available before ptr2 alloc: 82792 bytes total, 77812 bytes
largest free block
matrixUpdateFrames[1] pointer: 3FFE86D4
Frame Structs Allocated from Heap:
Heap/32-bit Memory Available: 114916 bytes total, 77812 bytes largest free
block
8-bit/DMA Memory Available : 82792 bytes total, 77812 bytes largest free
block
Total PSRAM used: 0 bytes total, 0 PSRAM bytes free
Allocating refresh buffer:
lsbMsbTransitionBit of 0 requires 49152 RAM, 77812 available, leaving
28660 free:
Raised lsbMsbTransitionBit to 0/7 to fit in RAM
lsbMsbTransitionBit of 0 gives 76 Hz refresh, 180 requested:
lsbMsbTransitionBit of 1 gives 152 Hz refresh, 180 requested:
lsbMsbTransitionBit of 2 gives 300 Hz refresh, 180 requested:
Raised lsbMsbTransitionBit to 2/7 to meet minimum refresh rate
Descriptors for lsbMsbTransitionBit 2/7 with 16 rows require 12288 bytes
of DMA RAM
SmartMatrix Mallocs Complete
Heap/32-bit Memory Available: 102596 bytes total, 65524 bytes largest free
block
8-bit/DMA Memory Available : 70472 bytes total, 65524 bytes largest free
block
T�
Maybe it is possible, maybe not. I hope you can shed some light on this.
greetz
Harrie
—
Reply to this email directly, view it on GitHub
<#461 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD344RIJXR5LA34NSYXDYCVCVRAVCNFSM6AAAAAA54NXJQOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TINZQGQ2DG>
.
You are receiving this because you commented.Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7470443
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Now, who's talkative? :-)
On Sat, Nov 4, 2023 at 12:32 PM heidepiek ***@***.***> wrote:
Sorry robert, what doesn`t work is that if i upload the sketch i got the
error in the serial and the esp keeps rebooting.
OK. Let's come back to that.
This goes for the esp32 devkit v1 and also for the wemos esp32 d1 mini.
This is an area where ESP32 terminology (wording) makes it hard to
communicate.
Devkit 1 is a BOARD designed for testing (with) MODULES. The board can come
with any of several MODULES. So knowing what board it is tells you things
like pinouts but it doesn't tell you anything about chip sizes.
D1 Mini is at least a branded product. We know what's on it:
https://www.wemos.cc/en/latest/d1/d1_mini.html
There is no PSRAM in the picture (that I can recognize) and PSRAM is not
mentioned.
Scratch D1 mini off the list.
i followed your link that you gave me
https://docs.espressif.com/projects/esp-idf/en/release-v4.2/esp32/hw-reference/modules-and-boards.html
And on my chip it says esproom-32
There may be a counterexample *somewhere* in Espressif 7,946 products that
are all named "ESP32", but I don't think that WROOM family generally has
PSRAM.
Your link tels me that it has no psram,mb
This is a link i found for my board :
https://einstronic.com/product/esp32-devkit-v1/
OK, this is a specific DevKit 1 board with a specfic ESP32-WROOM module on
it. Let's see...
Features
Development board based on ESP-WROOM-32 module (DOIT version)
30 GPIOs
ESP32 is a dual core 32-bit processor with built-in 2.4 GHz Wi-Fi and
Bluetooth
4MByte flash memory
520KByte RAM
2.2 tp 3.6V Operating voltage range
In breadboard friendly breakout
USB microB for power and Serial communication, use to load program and
serial debugging too
OK, so again, no mention of PSRAM.
520KByte Ram is that the psram? Or does a chip have flash,mb psram,mb and
520kbyte? This is not all clear to me. Sorry noob!
I think I'm seeing the hole you're falling into.
All ESP32 *chips* have some amount of RAM on the chip. That memory is
sliced up manu ways:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/memory-types.html
Depending on the exact chip, the unit of measure is "hundreds of KILObytes".
Some ESP32 modules have additional, external, Pseudo-Static RAM (PSRAM)
This memory is larger and generally measure in low (2, 4, 8, 16 ... and
soon, 32) MEGAbytes. It's slower than the memory on the chip (the forklift
has to go to the warehouse to get the pallets) and there are lots of goofy
rules about how it gets used:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/external-ram.html
Just to make things as clear as mud, there's no rule that the PSRAMS *have*
to be inside that tiny little canned module - it's just easier to get high
frequency designs stabilized by the people doing the SMT design that are
able to put it millimeters from the actual chip, but you CAN put PSRAM onto
the board. So you COULD poses an ESP32 module with no PSRAM that instead
uses PSRAM on the board...but your boards aren't saying they have that.
I like to tinker with the esp`s but do no know exactly how they work🙈 But
i now think these boards are not capable to run mesmerizer.
Yes, now that we both have a clearer understanding of what you have (older
stock or "bargain bin" parts - sorry). I thought WROOMs were NRND/EOLed a
few years ago.
In the platformio.ini file you have to configure what you want to build.
Right. Now that I'm actually awake, I've looked carefully at the code,
globals.h, and platform.ini. Every configuration that I can find that
tries to use HUB75 at least TRIES to use PSRAM.
Rutger has been chasing problems in configurations failing because they
can't allocate dozens/hundreds of bytes of memory. I was thinking those
were the 520K configurations without PSRAM.
It's entirely possible that our 2811 versions run (or almost run) in 520K
and the HUB75 versions just positively demand at least the 2MB of PSRAM,
but they don't actually plant a flag and demand it.
As annother action item for later in the day, I will take my official
Dave's Edition Mesmerizer and lobotomize (disable that part of its
brain) PSRAM. If it IS the case that we really do require PSRAM, I will
make it either a configuration error or a runtime error instead of a silent
crash somewhere later in the code.
It would not shock me if the matrix configuration just plain requires >=
2MB of memory. A single 32*64 frame in 32-bit color (maybe these are
16's...) takes 64KB. I know the code is drawing one frame (via DMA) while
building antoher (via CPU) so there's 128KB. Add the code and a network
stack and buffers and poof, 512K is gone pretty quickly. Oh, and wanting
network buffers for having multiple frames in flight and...
It's rare for us to have (32*64) pixels in a strip configuration.
At the risk of promoting the competition (again) I think the people trying
to run 2,000 neopixels are doing it (and suffering) with WLED. We never
really know how anyone's using "our" source, of course, but we just don't
hear a lot about people building really big strip configurations.
Let me test it and, if appropriate, more thoroughly kill the combination of
no-PSRAM + USE_HUB75. While I can bury it in the code and make it crash
more gracefully, I agree we also need a sign on the front door that lists
our minimum requirements.
For the mesmerizer that runs on my lolin D32 pro i use this in the
platformio,ini:
This is a third configuration in the same message. Are you confirming this
one runs for you?
default_envs = mesmerizer_lolin
You didn't show it here, but that configuration derives from
dev_mesmerizer and dev_mesmerizer and dev_mezmerizer sets build_flags to
include ${psram_flags.build_flags}... before I paste in
the next one, can you guess what's in psram_flags?
This is the "let's come back to that" part. This is why I say that every
configuration that's currently in the tree that sets a HUB75 configuration
currently at least tries to use PSRAM. There are only two such
configurations now in the tree and they both use PSRAM.
It's actually really hard to reason through our build flags and figure out
what is and isn't supported. Without actually being at the right computer
to prove it, I *think* that
* USE_HUB75 requires at least 2MB of PSRAM.
* At least some configuration of USE_281X is probably possible to build
without PSRAM, such as on modules you have.
I'm equally comfortable saying that there's surely some configuration of
USE_281x (a zillion lights each of 8 CHANNELS, a lot of BUFFERS,
REMOTE_DEBUG, ENABLE_WIFI, ENABLE_WEBSERVER, ENABLE_AUDIO, and the kitchen
sink ought to do it) that does not work on boards without PSRAM.
[platformio]
default_envs = mesmerizer
I think that that is for the board mr plummer made.
Mesmerizer <https://www.youtube.com/shorts/tIHFfz8zi9Y> is indeed the board
that Mr. P is making. (Was making? I can't tell.) It's the one that Rutger
and many others develop and test on. He has mentioned European shipping as
being expensive.
This project, in general, doesn't really cater to the rock-bottom hardware.
(I can't believe that we have dual-core, 8MB RAM/16MB flash, computers WITH
WIFI for $2.50 and we're talking about lower end boards as 'low end'. :-)
People are torturing themselves with ESP8266 and even Arduino - each of
which has their place - on apps like this just trying to save small change.
open source. maybe his intention is to sell the boards later, but it is so
expensive to get something from america here in the netherlands. So then I
don`t think harrie will get such a board.😳
I think you've bought at least two bargain boards. See what a saving those
were? (Never mind the thousands of dollars of your own tears and my
consulting fees you've rung up. :-)
I've linked you to two open source alternatives, one of which is sold by a
company inside the EU and one that ships from China. I don't KNOW the
software would interoperate seamlessly, but I'd bet they're no more than a
few pinout changes away. at least for a basic (remote + analog mic) HUB75
configuration.
boards I think. Have to settle for the setup I have now. Just placed an
order with jlcpcb.
Wait. JLCPCB is coming from China, too, just like the Makerfabs Trinity
board. I don't know if that's more or less than the Trinity from Eplop.co.uk.
Those boards are 50% more than the MatrixPortal. - which has a better ESP32
than the Trinity, but a worse power story.
Made a pcb with easyeda.
I hope you used a better module than WROOM. :-)
If you have an esp-wroom-32 lying around robert, you may try to get it
working. But it is not a must! Dave must have chosen the wrover for a
reason! I think.
I suspect it was a time-driven choice. From traffic in the archives, we can
estimate when it was designed and the ESP32-S3 (and the other boards
mentioned here) wasn't available yet and the WROOM with external PSRAM cost
more than WROVER with included PSRAM.
It's not how I'd build one today, but I think I understand how it arrived
with the BOM it has.
I'll confirm my hypothesis about HUB75 REQUIRING 2MB/PSRAM, add some
assertions to the code, better debugging to display what we really have on
boot, and somem doc improvements later this weekend.
Rutger, if you're still reading through all this, what configuration keeps
tripping the JSON parser up for not having dozens of bytes available? Is
that a real world configuration or is it like my "kitchen sink"
pathological example above?
RJL
… Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7475506
@github.com>
|
Beta Was this translation helpful? Give feedback.
3 replies
-
So robert, learned a lot these few days. Unbelievable how you just whipped
all that up.
Glad to help. I'm only just read a *few* chapters ahead of you. :-)
=Brian lough, I also bought some shields from him via tindie. But his shop
is closed.
Right, but he's licensed others to build it. That's what Open Hardware
License exists. Heck, not just the Gerbers, but also even the BOM is right
there and even for the same vendor you already use. Well, replace
that ESP32-WROOM-32D with an appropriate ESP32-WROVER-E or my pet ESP32-S3
module, but you get the idea. If I were spinning it, Id put the SD socket
onto the PCB, too...and Mic and IR jack. I'll be your first customer.
And then I have 10 pcbs! 5 times the shields and 5 times another pcb
Well, compare apples to like. These include the approximate equivalent of
your Lolin board. The ESP32 and serial bridge and voltage regulator and
such are all on Brian's (and the other) board.
project. The lolin D32 pro was more expensive with shipping than the pcbs!
So that nice pun of yours is correct! But I now have the fun of soldering
the pcb`s.
This is the esp i use:
https://www.tinytronics.nl/shop/nl/development-boards/microcontroller-boards/met-wi-fi/wemos-lolin-d32-pro-v2-esp32-ch340c-16mb-flash-8mb-psram
I know that comparing monetary units is confusing, but for my own notes,
that's a $10 board before shipping.
https://www.aliexpress.us/item/2251832696801305.html
Leave off the battery charger and the monitor socket and it becomes a $7
board
https://www.aliexpress.us/item/3256804457160611.html
which you can almost halve again:
https://www.aliexpress.us/item/3256805888447467.html
...and that's pretty close to the boards I've been using.
I think that this board can handle mesmerizer, dont you think? 😉
I think so.
Looking strictly at Wemos-branded boards at:
https://www.wemos.cc/en/latest/d32/d32.html
D1s and D32 mention no PSRAM.
D32 Pro has PSRAM - so 'probably'
S2 has single core. No.
C3 has single-core. No.
S3. Probably.
But I know I've bought the same part # from the same store in different
months and received different boards, so who knows - especially with the
generics. There really not much "engineering" happening on these boards.
The hard part is done in the modules. Voltage regulator, some buttons, a
few pullups here and there, maybe a serial/usb bridge, and you're done.
I'd "wire-wrap" (DuPont-up? Nobody wire-wraps any more....) one before
committing to a PCB, but I have commitment issues, but for $15PCB, I might
risk it and just be prepared to cut off a pin and/or bodge-wire around
things if needed.
Hope I don't get the bill for our consultations one of these days. Then I
have a lot to explain to the wife
Oh, don't worry. I won't actually *send* you a bill; I'll just submit it to
collections.
(This is honestly how the U.S. Healthcare system works...)
RJL
… Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/461/comments/7476497
@github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Just a brief introduction, my name is harry. Working as a warehouse manager and steel forge worker in a steel construction workshop. Been working with arduino
s and electronics for a few years now. In the course of it I have recreated several nice projects that people share on the worldwide web. A very nice plexiglass vu meter from manny miller (cinelights) A nice spectrum analyzer from mark donners, and many more nice projects from people sharing their knowledge. When I came across dave's site, and saw his nice spectrum analyzer. I thought, I want to build it too! Now I am not a programmer so I spent several evenings trying to get that on a ledmatrix. But at first not with success. It turned out I was using the wrong esp
s. So I bought a m5 stick c plus and put the software on it. And yes, a nice analyzer! Fanleds with the tapereel seemed great too. Also spent quite a few hours fiddling with it. Also got it working. And then... The mesmerizer, well that seemed great. Also tried everything. But also not the right hardware! Now I bought a lolin d32 pro. When I came home today it was in the mailbox. I had already studied platformio with nightdriver. And here is the result. Got it running! What a nice piece of software! Wonderfully made! I can't help you develop it even more and nicer unfortunately. As I said, programming is not my thing. Will there be a pcb we can purchase for the mesmerizer in the future? Or maybe the gerber files and the bomb and pick and place files will be included on the nightdriverstrip github site? Prefer gerber, because it's very expensive to ship things to the netherlands! But if I order some from jlcpcb it is still affordable. I read that dave also gave away pcbs to people participating in the project. Nice gesture from dave. Unfortunately that won
t include me, I can`t help in that area.I made a small video with my phone .Not the best quality, both video and audio. But this way you can see I got it working.
https://drive.google.com/file/d/1UixPTFBT--4wVH64qmRWbMXVQIDm6mWR/view?usp=sharing
Regards
Harry
The Netherlands
(ps)
English is not my native language, so sorry in advance if anything is incorrect
Beta Was this translation helpful? Give feedback.
All reactions