Today, I started back into my C++ coding and research for my DMX controller.
For work, I bought the City Theatrical DMXCat in the meantime to get some semblance of what I am after out of a device. I have even used it on set a few times.
I will probably also get an Android tablet and make it an entire controller in a case with independent power. It has a lot of promise, but I might be working on something that can do more.
Been looking into the ESP32 micro-controller lines. I see that they can do BLE and have an even faster clock speed than the Teensy 3.6 and have Wifi built-in. It sucks that Wifi and BLE are so hard to do but PJRC is WAY behind on this one and I need this device now. I have considered putting an ESP 8266 on the Pockonsole board.
However, I won’t be able to parse wifi data through CoAP unless I want to go with the much more capable ESP32..because BLE is a huge part of the requirement.
Perhaps that is how it will end up. Looking into this guy’s work (https://github.com/oneam/Esp32LedControl), I might already have all that I need to do this. It’s just parsing the CoAP data into a 512 value array of 8 bit ints then into the DMX Protocol working with ESP32’s UART that I need help on.
Also, an 8266 interfaced with the Teensy 3.6 doesn’t do BLE, so it is kind of useless in being a open source DMXCat replacement. I used to think that MQTT was the way to go, but this CoAP standard seems even more interesting and robust because you can have BILLIONS of nodes asynchronously communicating.
As always, I want to think beyond current capabilities at the outset. So CoAP looks REALLY good to ensure that…and would take care of much of the asynchronous behavior that has to happen that I have NO CLUE about at the moment.
Imagine an asynchronously programmed mesh network of LED’s !?!?!? It would be mind-blowing what lighting affects could be achieved.
More on this later. I need to think on it. Just learning about CoAP now.