VzBoT3D / docs

VzBot Documentation
https://docs.vzbot.org/
13 stars 23 forks source link

Printer configs are wrong / links broken #68

Closed HumbleDeer closed 1 year ago

HumbleDeer commented 1 year ago

As per user @_blkmrkt on Discord:

Z and E swapped in the config?

I think that extruder and stepper_z are swapped in this template: https://docs.vzbot.org/assets/images/manual/vz330_mellow/electronics/Printer_config/printer.cfg

That config doesn't agree with this diagram: https://raw.githubusercontent.com/VzBoT3D/VzBoT-Vz330/master/Wiring%20Diagram/VZBOT%20330%20WIRING%20DIAGRAM%20AWD%20WITH%20CPAP.png


Broken hyperlink

This hyperlink is broken on https://docs.vzbot.org/vz330_mellow/electronics/Printer_Config btw, I had to manually replace the %-encoded symbols in order to download it. It looks like this currently: https://docs.vzbot.org/assets%5Cimages%5Cmanual%5Cvz330_mellow%5Celectronics%5CPrinter_config%5Cprinter.cfg


CPAP pin low on startup

I'd also add a line about setting the CPAP pin to LOW when configuring the STM32 firmware, otherwise it's a menace. Adding !PF8 to GPIO pins to set at microcontroller startup helped in my case.

Perhaps you could insert this screenshot/step into https://docs.vzbot.org/vz330_mellow/electronics/Firmware? It'll prevent hearing loss for billions of people. https://github.com/VzBoT3D/docs/assets/16231288/96002d76-4bcc-410e-b818-6e0b0226048f

HumbleDeer commented 1 year ago

Z and E swapped in the config?

I have confirmed this to be true. The config has extruder on Driver 0 and Z on Driver 1, but the wiring diagram shows them being set up as Z on Driver 0 and extruder on Driver 1.

Do we change the config file, or the wiring diagram?

image

Broken hyperlink

Addressed in commit "Printer configs are wrong / links broken"

The link contained backslashes, which are Windows specific; fine for local path stuff on windows but not on Linux servers

CPAP pin low on startup

Addressed in commit "Printer configs are wrong / links broken"

This fix already existed on one of the Firmware pages. It has now been extended to all Firmware pages.