 I try to make a very quick one because for this thing, this is the ESP32, 31 actually. It's the beta version of ESP32 I just received from Expressive. This is a small little, it's just a small little board I received with a small little breakout board and this whole thing. So I just set it up and I put a CD screen on that. I'm not sure whether the demo works, sometimes it works, sometimes it's not. I'm not sure it's the whole problem but what happens is now is I'm doing one small little web socket server and for this web page, actually what it does is grab all the video, then it's streamed to the LCD screen. So yeah, it's screened but sometimes it works, sometimes it's not working very well. I'm not sure it's an SDK. It's okay because it's. It always works. It's stuck somewhere. I'm not sure it's their firmware problem or the hardware problem or it's my web server problem or my web browser problem. I have absolutely no clue until they have a proper debugger for the chip. Currently we only rely on the serial port to get some data and the data is not very clear. So would this be more difficult than the old one? They have RTOS SDK, which is a free RTOS. To me it is much easier because there's RTOS and there's a LWIP stack so that many of those are existing jobs based on LWIP. Even the HDB server, which is coming with LWIP to contribute libraries, I can compile it into the server without any code change. Just take the C file, compile and put in. It becomes an HDB server. Actually I'm using the USB open RTOS which is different variant which is more free. The web server code I wrote to work on my laptop first and then I just compile it and it works on the USB. So that's the same benefit eventually. But you have the same code everywhere you can run it. It's not working. Sometimes it's working. I spent about two days to write the firmware before this JavaScript thing. It's about 20 minutes. I know nothing about JavaScript. I just googled a type in. I said grab video frame JavaScript thing. Some people already did that. So you receive it and then you send it back also? No. Oh, sorry. What happens is the left side, this is a video. It's a fixed video. Then the left side is actually a camera. Then you draw to the camera and I change this to 16 bit color because original was 32 bit and I reduce it to 32 bit color. For this screen it's 160 by 120 or 28. So I can roughly calculate it's about 40 kilobyte per second. Sorry, per frame. So I'm running about 10 frames per second. So it's about 400 kilobyte per second stream to the screen. It looks like it works and actually it can go faster. Probably somebody could write and take the code or something. Definitely. What we know is that this is a dual-core processor. There's one processor for the Wi-Fi and another processor is an application processor. But for the SDK that gives us, there's only one processor being used. And that's why we have plenty of RAM because another processor is not underutilized. It gives us a lot of RAM. The SDK is the Wi-Fi one. Sorry? The one that is used in SDK is the Wi-Fi one. It is the Wi-Fi one. So the other one there, there's currently no way to use it. Currently there's no way to use it. And it's supposed to have Bluetooth and currently the SDK doesn't open that port. But it is continuously evolving. Are the two cores similar or is it different cores? I suppose there's one low-energy core and one full-power core. So that you can sleep the high-power core all the time. Sure, sure. This is what we know now. But this time the documentation and everything is much, much better. Of course. They learn a lot. So how much RAM does it have when you install it? Okay, this is a very confusing topic now. The claim says there's 400 kilobytes of RAM. What we know is it has to be divided by two processors. So you have half. But when we have SDK, we try to get the heap size. It's about 17K. Okay. And they claim that this is beta testing. So they guarantee that in the end we will see about three times of the free RAM, 200K of RAM. So that's what we know now. But this thing is still evolving. And this is not the final product yet. We don't know. Then it gets them to be a very nice size for doing live programming. I asked them to send one to me too. So I'm waiting for one to win. Alright. So this is the one. Is there any indication of the price? No. When will it be in a few months? Supposed to be the first quarter of 2016. Nothing. Alright. So once again leave the demos off. I leave it here. Ten like.