Skip to content
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

FYSETC v1.0 driver jumper configuration image confusion #203

Closed
kc8rwr opened this issue Jan 9, 2019 · 2 comments
Closed

FYSETC v1.0 driver jumper configuration image confusion #203

kc8rwr opened this issue Jan 9, 2019 · 2 comments

Comments

@kc8rwr
Copy link

kc8rwr commented Jan 9, 2019

The image http://marlinfw.org/assets/images/docs/hardware/tmc_drivers/FYSETC_tmc2130._SPI.jpg found on the page http://marlinfw.org/docs/hardware/tmc_drivers.html is confusing or perhaps wrong.

This is an image of the FYSETEC v1.0 driver, outlining its three jumpers and explaining how to set them for SPI mode. The problem is that one larger jumper is clearly closed but the label over it says open. The other two smaller jumpers are open but the label over them says closed! Which is it supposed to be?

Perhaps the image indicates how the driver comes from the factory and the labels indicate that all three jumpers need to be changed to the opposite of their factory settings to get SPI mode. This isn't very clear in the text. The text does say that the big jumper to the left of the chip needs to be opened but for the other two it just says that they need to be configured "as shown".

Assuming that what is meant is "open the big jumper which comes closed and close the two little jumpers that come open from the factory" then it would be much more clear if either the image showed the "after" picture instead of the "before" or if the text stated everything explicitly. "Open the big jumper and close the two little ones". As it is I think someone installing one of these drivers for the first time might be a little nervous from this ambiguity and be forced to go look up the datasheet before proceeding.

@thinkyhead
Copy link
Member

Thanks for the report. I will try to find the person who wrote that article and supplied the image to see if they can improve both.

@shitcreek
Copy link
Contributor

Updated the image to address any confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants