-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please provide Altium-Designer Project #5
Comments
@vcc-gnd any plans to publish the schematics? |
Schematics have long been available: https://github.com/vcc-gnd/YD-ESP32-S3/tree/main/5-public-YD-ESP32-S3-Hardware%20info It's not exactly the "source code" in KiCad or whatever, but since the board isn't much more than a bug-fixed Espressif reference board like DevKitC or so, there shouldn't be any barriers keeping you from remixing it. |
@robertlipe .. It's resolved. I don't want to redraw the whole board. If it's already available. |
OK. I have no involvement in the project (I'm just a customer) but was pointing out that schematics ARE available. Just trying to help since they're in kind of a goofy place. (It's hardly an 'example'.) It's your choice whether to leave it open or close it, of course. Unfortunately, this is another of those projects that's not really an open source community, collaborative project as much as it is a place to publish some files, toss it over the wall, and then ignore any questions, input, or suggestions. Even the bizarre LED issue that comes up over and over still isn't really documented. Such as it is, that's still WAY more than a lot of similar (Asian, cough) products that show up on the market with no doc at all. These boards are documented just well enough to keep me buying them. Good luck |
Hello,
I bought your Board and it works fine for me. I want to Add some Components on the Back. Is there a possibility that you can publish the schematics from Altium? So that I don't need to re-draw and make mistakes and I can just start from a working Board?
Would be great and thank you in advance!
The text was updated successfully, but these errors were encountered: