-
Notifications
You must be signed in to change notification settings - Fork 659
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
Ender 3 V2 (4.2.2 Board) #58
Comments
Is there a schematic for this board? |
any news??? is it top secret? |
v2 isn't Open Source |
@sexycyborg I have stock v1 with 4.2.2 board. It is not open source too? |
Considering V2 is derived from V1, isn't that a violation of the GPL license? |
No... the author of the original work is free to choose any license they want to. |
Well, Creality is not the author of the original work, it is derived from the Melzi boards which are under GPL. |
GPL is only valid for open source software, open source hardware needs an specific license. So, as long as Creality releases the sources for their Marlin implementation, they are not in breach of the GPL. |
If the entirety of the Creality Ender 3 v2 is not open source, this would be a clear violation of GPL considering v2 is not using the same Marlin derivative as the original Ender 3(evident by the screen UI), right? |
That is an entirely different can of worms. The point made was that the original author can change the license and while that is true this argument I stongly disagree with the assesment that GPL is an invalid license for open source hardware since we are talking about But okay let us say, for the sake of the argument, GPL is indeed an invalid license for schematic and layout files. This still may not apply to the V2 since it may be that it has seen enough changes to be recognized as original work. |
That looks helpfull, thanks, I just ordered an Ender3 Max and it should have either this one or the 4.2.7 installed or the next version. But please provided a source for that file, especially as it is not yours and there is no copyright string on the document and no license information. As it is you are violating someones copyright. Also, from the looks of it this appears to be redrawn in KiCad and if there is a public repository and if it has KiCad files, this might be even more interesting as this might allow changes and collaboration for these around who use KiCad. |
That is very unfortunate and I can not find it either. |
It’s probably from Jyers/Marlin#814 |
yes that is it, Since it been updated I have removed the old one. |
This is definitely a misreading of the argument about how the GPL applies to circuits. The argument here, "circuits cannot have the GPL applied to them," is rooted in the basis that circuits are not eligible for copyright, insofar as they are functional articles. Circuit diagrams can be protected by copyright as written/pictorial works (and so the GPL may apply to them, as it may be applied to any copyrightable work) but the physical, functional artifact of a circuit is not copyrightable, so the GPL doesn't have anything to say about it. There cannot be a copyright violation for the manufacture of a circuit for the same reason the GPL cannot apply to a physical circuit: the circuit is not copyrightable in the first place. From 17 USC S.101:
Related discussion: https://opensource.stackexchange.com/q/2223/50 |
Here's the schematic |
@jbrahy Thank you for sharing the schematic. Where did you get it? I believe the UCH245 pinout is slightly wrong. This is the pinout on the 4.2.3 board |
has anyone found out how to control the part cooling fan? |
You're asking in the wrong place and it's very annoying. Use your search engine instead of spamming us all with a notification because you want a howto |
wow lighten up a little sir! Given this poorly documented board the information on the internet is scarce and that was what led me to post it in here. I am sorry if I annoyed you. You can and should disable notifications if you don't want to be notified about this topic. Actually GitHub has improved its notification system quite considerably and you can fine tune your preferences of what you should be notified by default or not. Concerning the issue at hand, I could solve it, the fan pin is PA0 which one would easily find by looking at the board file. What I didn't realized is that it is the same pin that drives both the part cooling fan and the motherboard fan. Turns out my part cooling fan was simply stuck on the plastic housing of the hotend, a gentle push solved it. |
Thanks for the diagrams. Why is this such a hard concept for Chinese companies? They stole all of the manufacturing from the West, yet threw out all of our standards and QA etc. Do they really think we came up with all of the standards just to waste time, or does it hurt their ability to be dishonest? Or is it both? In the past you could go to a companies page or open a published book to view specs about components. Now you can't trust a single electronic component, much less complex things like mainboards. I wish more things were made in places other than China, THEY SUCK AT ELECTRONICS. |
No, what led you to post in here was a complete lack of regard for the intention of this thread.
How hard is it to post about the PCB in a thread about the PCB. This isn't the "How do I use my printer" or "let's rant about racist nonsense" thread. Actual tards. Editing this post, because unlike some people here I actually do understand how notifications work, and that people don't want to get spammed with offtopic stuff all day. Some education about some basic netiquette: TL;DR Hijacking threads ruins it for everyone, including you. You don't wanna do that. Don't do that.
Hijacking support threads shoots you in the foot and everyone else in the foot, too. Don't be this guy. Just start a new thread. If they turn out to be related, that's what links are for. You can always un-disconnect your thread, but you can never un-hijack it. |
|
@ghost Karen, is that you? |
I can't find any board images or diagram.
Please upload creality
The text was updated successfully, but these errors were encountered: