Alternate Pixel Controller

Not just ability, but time. I've programmed mbed platform and STM's (which make Arduinos look like kids' toys), but the whole display takes a gargantuan amount of time, and I have to set priorities. I'm dealing with mounting issues on the house, engineering a good mega tree, weatherproofing testing, trying to route long data lines over coax, Renard's to test, and assuming Renard's even work downstream from a smart receiver I still have to integrate all those AC lights into Xlights. Even the ws2811 packet stripper is higher priority, because that lets me make pixel sticks and meteor showers without having to loopback the data line; but even that I don't have the time or the Arduino minis for. Oh yeah, and a day job.

This hobby can be a real time-sink, especially if you're doing any soft of development.
 
Also off topic... but Computerchristmas.com is still alive on the "internet wayback machine." Kind of interesting to look back on some of those pages...

comp_christmas.jpg
 
Also off topic... but Computerchristmas.com is still alive on the "internet wayback machine." Kind of interesting to look back on some of those pages...

View attachment 45616

That's where i got my start. I built Hill Robertson's parallel port controller. I didn't build the full 320 channel but I think about half that using point to point wiring with bix block 8 pin jacks
https://web.archive.org/web/20081218100314/http://computerchristmas.com/christmas/link-how_to/HowToId-4/How_To_Build_A_Parallel_Port_Controller_Box
 
Phil
I know this is an old thread but I just stumbled across it a few minutes ago even though I was the first to respond to this thread 2 years ago! My brain is slipping a few gears and it shows...

Question: Could this Px11 variant be fitted with a WT32-ETH01 instead of a Wemos Mini D1?

The WT32 is based off the ESP32 and the WeMos is based off the ESP8266

My understanding is they work on the same principles.

This is almost an exact match for what I was failing miserably at describing with regards to modifying a PX1 to be connected via e1.31/sACN

I'm not up to speed with any of this, but based on the circuit diagram in the first post; I can see a modification where a WeMos or WT32 module connects to an RJ45 plug instead of the PIC16F1825's, which in turn runs to a Px1 or even a daisy chain set of Px1's. This method effectively mimics an e1.31 Bridge board?

another alternative would be to sandwich stack the WeMos or WT32 as shown on your layout, then stacked again into the PIC16F1825 socket on an existing Px1 unit. (Sandevice e680 upgrade pcb is an example if I butchered my explanation) This method effectively mimics a Wireless Ren?
 
You are correct Martin, I purchased a few after you suggested them back then.

I'm still puttering with a wired concept versus wireless.

Now that you nudged my brain a bit, I will explore the idea of swapping the espixelstick v4 esp32 module with my WT32 module that has the wired option to reach my goal.

Running anything wireless around my house encounters a lot of RF interference for some reason which is very annoying.
 
Firmware would be the biggest issue, so sticking with hardware that already has espixelstick and/or wled support would likely be the way to go. In any case, I've long since forgotten anything about this 'project'.
 
Just out of curiosity, what are you really interested in? Is it for small pixel-count controllers, or something with high pixel-counts for megatrees or matrix panels or the like?
 
Last edited:
FYI: ESPS V4 supports four platforms that have CAT5 Ethernet connectors on them. That list include WTS32-ETH. However, I do not like that design because it does not have the NODEMCU USB Connector. That does not make it work worse, it just makes it harder to program. Here is a list of the currently supported platforms:

espsv3, d1_mini, d1_mini_pro, d32_pro, d32_pro_eth, esp32_cam, esp32_ttgo_t8, d1_mini32, d1_mini32_eth, esp32_bong69, esp32_wt32eth01, esp32_quinled_quad, esp32_quinled_quad_ae_plus, esp32_quinled_quad_ae_plus_8, esp32_quinled_quad_eth, esp32_quinled_uno, esp32_quinled_uno_ae_plus, esp32_quinled_uno_eth, esp32_quinled_dig_octa, esp01s, d1_mini_mhetesp32minikit, olimex_esp32_gw, d1_mini_twilightlord, d1_mini_twilightlord_eth, esp32_devkitc, esp32_quinled_uno_eth_espsv3, esp32_quinled_uno_espsv3, m5stack_atom, esp3deuxquatro_dmx, esp32_wasatch, esp32_tetra2go, esp32_kr_lights_msm, d1_mini_lolinsd, esp32_ka, esp32_breakdancev2
 
Yeaaaaa.. backs away slowly, "Oh Look, SQUIRREL!"


Thanks guys for convincing me to stick with what I have for now.
 
Don't take it the wrong way Martin, I seem to struggle with humour too! lol

Just to muddle my brainbox more, I just found my long-ago misplaced pci-e 6 port serial card buried under coils of cat5 cable!
So I can use 4 or more Px1's along with my 2 LedTriks units. (I modified TimW's LTC11 source code which allows 2 separate Trik-C to run off the same computer)
 
Not to be overly critical, but is there someplace containing that list (along with date, firmware version, and controller versions) other than sporadic, hard to find forum posts?
 
Back
Top