-
Notifications
You must be signed in to change notification settings - Fork 20
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
Is 4-wire RJ11 cable NOT supported by the 16SoundsUSB? #4
Comments
Hello, Two things:
You should be able to confirm that the cables you have in hand are straight (Amazon) and crossed (ours) either visually (looking at the wire colors at both ends of the cable) or with a multimeter. You could buy new cables, or buy your own connectors and crimp tool, to recycle the cables you have in hand and allow you to make custom-length cables in the future. I hope this helps you. Let me know if it does not. I will look over our documentation and add a note regarding the type of cable if it isn't clear already. I'm sorry you had this problem. Vincent R |
Thank you so much, Vincent!!! I double checked both sides of the wire, I then found out their difference. And yes, the original cable is "crossed", whereas the one I bought from Amazon is not. Again, thank you so much :). |
I'm glad I could help you figure this out. Let us know if you have more questions! (I'm closing this issue since it is resolved) |
Hi there,
Our lab bought a 16SoundsUSB from your lab a few months ago.
But now, we are trying to replace the original cable with a shorter one since the original cable is too long.
We bought some RJ11 cables from Amazon, and here is the link. However, these Rj11 cables do not work at all...
I was wondering what kind of cable is support by the 16SoundsUSB, and where can I find some shorter alternative cables.
Looking for your response, and thanks in advance :).
PS: I also took a picture of our RJ11 cable and the original cable. The left one is the RJ11 bought from Amazon, and the right one is the original cable.
The text was updated successfully, but these errors were encountered: