-
-
Notifications
You must be signed in to change notification settings - Fork 439
Battery connector spec [TC-342] #275
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
Labels
Comments
Hey @John-Page ! |
Here https://docs.arduino.cc/hardware/mkr-wifi-1010
under tech specs, power, battery connections.
and here
https://docs.arduino.cc/static/fc77c3c3c77d69764ba7773df64c99db/ABX00023-datasheet.pdf
under Chapter 4 (pdf page 8), it fails to mention the connector at all.
In both cases it should be specified at JST PH. JST is the maker like
Molex. You have to know it is type PH. This problem is probably on all
the Arduino boards that have this connector also.
Cheers!
John P
…On Wed, Jun 8, 2022 at 6:46 AM Pablo Marquínez Ferrándiz < ***@***.***> wrote:
Hey @John-Page <https://github.com/John-Page> !
Could you point the board's documentation you are talking about?
Thanks :)
—
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH5SSZ4QIUX2FM5LUUWBSH3VOCP5FANCNFSM5X5QB5OA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Got it, thanks for spotting it! 😄 |
1 task
1 task
@John-Page the MKR board product pages & tutorials have been updated with the "JST PH" specification. This can be viewed in (#416). Datasheet is not changed yet. Thank you for reporting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
It is not enough to say the battery connector is a JST type. There are hundreds of different JST connectors. All references to this should state that the connector is JST-PH which is the specific type. If you purchase batteries for this they often come with the wrong kind of JST plug.
The text was updated successfully, but these errors were encountered: