Thanks for checking.Sorry, but I can not find anything PixelRadio Related.
I'd like to have one of these for my show next year. Before I go ordering everything I figured I would see if any of the offers for boards bare or otherwise were still available?
I'd take you up on a board and whichever components you have sufficient spares of. Shoot me a message and let me know how much you want for them and shipping.It's been almost a week since your post, so you may have already either had a response or ordered, but I have have five boards on the way, and would be glad to pass one along to you if you still need it. Regarding other parts in the BoM, I don't have a full complement of spares, but most of the components came in large quantities, and I could create a goodie bag if desired.
I found a link to this thread on Christmas Eve while searching for sources of low-power FM transmitters, and placed orders for most of the parts the next evening. In true male fashion, I rushed to the order phase before reading all of the docs, but the only part on the list that I am now unsure of is the 15-pin SIP socket for the MCU. After reading this thread I found that it must be a specific height in order to work with the 3D-printed end panels, and I ordered the sockets from a different trader that doesn't publish the height. Cross fingers they're compatible. Other than that, I feel good about the orders, and am anxious to get to building!
Will do!I'd take you up on a board and whichever components you have sufficient spares of. Shoot me a message and let me know how much you want for them and shipping.
I hope you caught that they need to be 1.2mm not standard 1.6 mm. Some of us missed that early in the process.but I have have five boards on the way
Feel free to use non-polar at C8 and C9. But the recommended electrolytics are fine because the QN8027 module's audio inputs provide the DC bias.Shouldn't C8 and C9 (the audio coupling capacitors) be non-polar?
Here's my best analogy to why this is not practical. Grandma's sweet little poodle is a baby brother to the wolf breed. But the differences are so extensive that expecting them to play well together will end up in a messy disappointment.While I haven't used it before, my understanding is that VS-Code is sort of the baby brother to Visual Studio. Could the required extensions be loaded into it?
Haha! Good analogy.Here's my best analogy to why this is not practical. Grandma's sweet little poodle is a baby brother to the wolf breed. But the differences are so extensive that expecting them to play well together will end up in a messy disappointment.![]()
andAs far as I know, VS Code extensions are javascript-based, while Visual Studio extensions are c#/.net based; I haven't heard of a way to write a single extension for both editors.
"the extension can be packaged as a VSIX file, which is what Visual Studio uses as the extension file" is just an illusion. The file extension doesn't matter at all, as VS .vsix are completely different from VS Code .vsix (manifest format and contents). They are just ZIP packages and incompatible with each other. Microsoft's choice of sticking to the same file extension is a mistake.
That's the info that I couldn't find anywhere in the PixelRadio docs, or in the mfg datasheet. Thanks for the explanation!the QN8027 module's audio inputs provide the DC bias.
I overlooked the comment where you were concerned about interaction between these two IDE's. I have Visual Studio and VS Code on the same workstation. No issues, they ignore each other.Regarding co-existance, I found numerous posts saying that VS-Code can safely co-exist with Visual Studio.
Hey! It's amazing what pops up when you spring clean. I have 5 blank boards and 1 with all the soldered parts. It does not have the ESP32 TTGO- T8 board nor do I have any spare parts. Just what's in the Pic. Let me know if you want anything.Thanks for checking.