QuinLED-Dig-Uno and QuinLED-Dig-Quad Pixel Controller Group Buy

I appreciate everyone's flexibility on the connector of the color, but I'm waiting on the extra 10 pin female headers or I would send them out with the "wrong" color.
I had enough parts to complete the kits for Aurbo, Cranberry and Utimgr - those were dropped off at the post office this morning.
Rest of the parts should be here in the next couple days and won't take long to ship them out!

Question for Martin if he sees this - otherwise I can make a separate post. I programmed my ESP32's with the Espixelstick firmware as DigUno's. I see where I can set the temperature to be in Celsius or Fahrenheit, but I can't find on any of the pages what temperature is being read.... Am I missing it? If I program them with the WLED fw it shows the temperature so I don't think it's a hardware issue.
 
Thanks Martin, I was already using a CI build, but that helped me figure it out. Looks like in GPIO_Defs_ESP32_QUINLED_QUAD.hpp the temperature sensor is incorrectly set to Pin 18 - it should be pin 13. Pin 18 conflicts with the SD card clock signal. In GPIO_Defs_ESP32_QUINLED_UNO.hpp it's set to pin 13, and in WLED the Quad temperature sensor is set to pin 13 as well.
For others using a CI build - the 2 most recent CI builds I was having a hard time connecting to the ESP in Chrome. I had to go back 3 builds to the build from 8/16.
 
Thanks Martin for the fix!

All - last of the parts showed up today. Everything is packed and ready to go out tomorrow.
2 of the 3 packages I mailed on Saturday were delivered today so seems the mail is speedy this week!
 
I assumed its compatible with the WeMOS D1 (my goto IoT board) running ESpixelstick firmware. However its a 9 pin socket (btw...mine didn't have those sockets included, and thats fine I have plenty of 8 pin) so is the WeMOS plugged into the first set of 8, starting at the edge of the board or?
 
Just conjecture, but there are some ESP32 mini development boards (e.g. some ESP32-S3) boards that have 9 pins on each side, so maybe the person who designed these boards was trying to leave all options open. I'd carefully check that the power and ground pins of the ESP modules line up with the power/ground pins of the PCB, a picture of the boards in question (individually and mated) might be a good idea.

Edit - I might have misunderstood. Was the question about more pins on the ESP board than the QuinLED board?
 
It was both and yes...I intend to make sure things line up before I power it on. Thanks for the responses.
 
P. Short said:
there are some ESP32 mini development boards (e.g. some ESP32-S3) boards that have 9 pins on each side
Click to expand...
These boards were designed to be compatible with the generic MH-ET D1 Mini 32 (ESP32). The wide white silkscreen matches the pinout of the ESP2866, as far as power, ground and reset. Meant to be backward combatable to older design prototypes.
 
The original D1 mini (ESP8266) is 2x8 pins. The QuinLED ESPs are ESP32 based and 3x9 pins. The ESP32 D1 mini boards are 4x10 pins. All our “compatible“ with the DigUno and DigQuad, but with the 8266 you can’t drive all 4 pixel outputs on the Quad.
 
I was using the web based flash tool, selected the platform "QUINLED UNO", but its telling me it does not support the ESP8266 devices (WeMOS D1). So do I need to order up a ESP32 device?
 
The Flash Tool only supports the official configurations for the platforms in the list. Putting an ESP8266 CPU board on an UNO base board is not such a configuration. You will need to create a custom build to support that configuration.
 
OK, sounds like its going to be easier to order a ESP32 board, being more of a hardware guy than software, creating a custom build is a bit out of my wheelhouse (unless there is a guide on how to do that...I do code, but wouldn't call myself a coder).
 
Do you know how to use VSCode + Platform IO?

ESPS V4 has most of the platform ugliness stuck in a bunch of files called PlatformName_GPIO_Defs.h
You would need to modify the file for your platform to define the GPIOs you want to use. Then modify platformio.ini for your platform to use the type of CPU Board you are using.
Kick off a build & upload of the code.
Kick off a build & upload of the File System
Use your new device.

While there is almost no coding involved, it is easier to buy the proper CPU board.
 
Short answer is no on VSCode and PlatformIO. Yes its only Sept, but I don't have time to learn the process at this time (although I would be interested) as I need to finish up the trees, candy canes and deer and test them in a final configuration using the target hardware (QuinLED boards).

I'm looking at getting something like this to test with
www.ebay.com

Type-C Mini ESP32-C3 WIFI Bluetooth Development Board ESP32-C3-MINI-1 Module USA | eBay

Stable performance, this product uses the ESP32-C3FN4 chip and built-in stacked 4 MB flash ESP32-C3-MINI module module. Module Model: ESP32-C3-MINI-1. Interface: TYPE-C. Antenna diversity. The ESP32-C3 integrates 2.4 GHz Wi-Fi and Bluetooth 5(LE) with long range support, helping to build IoT...
www.ebay.com
 
You must log in or register to reply here.
Back
Top