docs: Note the use of the virtual_sdcard feature
Note that virtual_sdcard helps on slower machines. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
parent
b139a8561f
commit
82a65e9f4a
16
docs/FAQ.md
16
docs/FAQ.md
|
@ -97,11 +97,17 @@ baud rate to 250000 when using Klipper.
|
||||||
### Can I run Klipper on something other than a Raspberry Pi 3?
|
### Can I run Klipper on something other than a Raspberry Pi 3?
|
||||||
|
|
||||||
The recommended hardware is a Raspberry Pi 2 or a Raspberry
|
The recommended hardware is a Raspberry Pi 2 or a Raspberry
|
||||||
Pi 3. Klipper will run on a Raspberry Pi 1 and on the Raspberry Pi
|
Pi 3.
|
||||||
Zero, but these boards don't have enough processing power to run
|
|
||||||
OctoPrint well. It's not uncommon for print stalls to occur on these
|
Klipper will run on a Raspberry Pi 1 and on the Raspberry Pi Zero, but
|
||||||
slower machines (the printer may move faster than OctoPrint can send
|
these boards don't have enough processing power to run OctoPrint
|
||||||
movement commands).
|
well. It's not uncommon for print stalls to occur on these slower
|
||||||
|
machines (the printer may move faster than OctoPrint can send movement
|
||||||
|
commands) when printing directly from OctoPrint. If you wish to run on
|
||||||
|
one one of these slower boards anyway, consider using the
|
||||||
|
"virtual_sdcard" feature (see
|
||||||
|
[config/example-extras.cfg](../config/example-extras.cfg) for details)
|
||||||
|
when printing.
|
||||||
|
|
||||||
For running on the Beaglebone, see the
|
For running on the Beaglebone, see the
|
||||||
[Beaglebone specific installation instructions](beaglebone.md).
|
[Beaglebone specific installation instructions](beaglebone.md).
|
||||||
|
|
|
@ -54,7 +54,6 @@ sudo systemctl start octoprint
|
||||||
Make sure the octoprint web server is accessible - it should be at:
|
Make sure the octoprint web server is accessible - it should be at:
|
||||||
[http://beaglebone:5000/](http://beaglebone:5000/)
|
[http://beaglebone:5000/](http://beaglebone:5000/)
|
||||||
|
|
||||||
|
|
||||||
Building the micro-controller code
|
Building the micro-controller code
|
||||||
==================================
|
==================================
|
||||||
|
|
||||||
|
@ -92,3 +91,13 @@ Remaining configuration
|
||||||
Complete the installation by configuring Klipper and Octoprint
|
Complete the installation by configuring Klipper and Octoprint
|
||||||
following the instructions in
|
following the instructions in
|
||||||
[the main installation document](Installation.md#configuring-klipper).
|
[the main installation document](Installation.md#configuring-klipper).
|
||||||
|
|
||||||
|
Printing on the Beaglebone
|
||||||
|
==========================
|
||||||
|
|
||||||
|
Unfortunately, the Beaglebone processor can sometimes struggle to run
|
||||||
|
OctoPrint well. Print stalls have been known to occur on complex
|
||||||
|
prints (the printer may move faster than OctoPrint can send movement
|
||||||
|
commands). If this occurs, consider using the "virtual_sdcard" feature
|
||||||
|
(see [config/example-extras.cfg](../config/example-extras.cfg) for
|
||||||
|
details) to print directly from Klipper.
|
||||||
|
|
Loading…
Reference in New Issue