h3n3/klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Deploying to gh-pages from @ Klipper3d/klipper@3417940fd8 🚀

Browse Source
This commit is contained in:
KevinOConnor
2023-12-19 00:04:07 +00:00
parent bc70664085
commit 128f06b0a6
78 changed files with 695 additions and 695 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
zh/Config_checks.html
View File

@@ -1449,28 +1449,28 @@
<p>本文档提供了一系列帮助验证 Klipper printer.cfg 文件中的引脚设置的步骤。推荐在完成<a href="Installation.html">安装文档</a> 中的步骤后执行本文档中的步骤。</p>
<p>在执行此指南的过程中，可能需要修改 Klipper 的配置文件。请务必在每次修改配置文件后发送 RESTART 命令，以确保修改成功生效（在 Octoprint 终端标签中输入 "RESTART"（重启），然后点击 "Send"（发送））。在每次重启之后最好再发出一次 STATUS （状态）命令，以验证配置文件是否成功加载。</p>
<h2 id="_2">验证温度<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<p>Start by verifying that temperatures are being properly reported. Navigate to the temperature graph section in the user interface. Verify that the temperature of the nozzle and bed (if applicable) are present and not increasing. If it is increasing, remove power from the printer. If the temperatures are not accurate, review the "sensor_type" and "sensor_pin" settings for the nozzle and/or bed.</p>
<p>首先验证温度报告是否正确。导航到用户界面中的温度图部分。验证喷嘴和床（如适用）的温度是否存在且没有升高。如果它正在增加，请断开打印机的电源。如果温度不准确，请查看喷嘴和/或床的“sensor_type”和“sensor_pin”设置。</p>
<h2 id="m112">验证 M112<a class="headerlink" href="#m112" title="Permanent link">&para;</a></h2>
<p>Navigate to the command console and issue an M112 command in the terminal box. This command requests Klipper to go into a "shutdown" state. It will cause an error to show, which can be cleared with a FIRMWARE_RESTART command in the command console. Octoprint will also require a reconnect. Then navigate to the temperature graph section and verify that temperatures continue to update and the temperatures are not increasing. If temperatures are increasing, remove power from the printer.</p>
<p>导航到命令控制台，并在接线盒中发出M112命令。此命令要求Klipper进入“关闭”状态。它将导致显示一个错误，可以通过命令控制台中的FIRMWARE_RESTART命令清除该错误。八达通还需要重新连接。然后导航到温度图部分，验证温度是否继续更新，温度是否没有升高。如果温度升高，请断开打印机电源。</p>
<h2 id="_3">验证加热器<a class="headerlink" href="#_3" title="Permanent link">&para;</a></h2>
<p>Navigate to the temperature graph section and type in 50 followed by enter in the extruder/tool temperature box. The extruder temperature in the graph should start to increase (within about 30 seconds or so). Then go to the extruder temperature drop-down box and select "Off". After several minutes the temperature should start to return to its initial room temperature value. If the temperature does not increase then verify the "heater_pin" setting in the config.</p>
<p>导航到温度图部分，键入50，然后在挤出机/工具温度框中输入。图中的挤出机温度应开始升高（大约在30秒内）。然后转到挤出机温度下拉框，选择“关闭”。几分钟后，温度应开始恢复到其初始室温值。如果温度没有升高，则验证配置中的“heater_pin”设置。</p>
<p>如果打印机带有热床，则用热床重复上述测试。</p>
<h2 id="enable">验证步进电机 enable（启用）引脚<a class="headerlink" href="#enable" title="Permanent link">&para;</a></h2>
<p>Verify that all of the printer axes can manually move freely (the stepper motors are disabled). If not, issue an M84 command to disable the motors. If any of the axes still can not move freely, then verify the stepper "enable_pin" configuration for the given axis. On most commodity stepper motor drivers, the motor enable pin is "active low" and therefore the enable pin should have a "!" before the pin (for example, "enable_pin: !PA1").</p>
<p>验证所有打印机轴是否可以手动自由移动（步进电机已禁用）。如果没有，则发出M84命令以禁用电机。如果任何轴仍然不能自由移动，则验证给定轴的步进器“enable_pin”配置。在大多数商用步进电机驱动器上，电机启用引脚为“低激活”，因此启用引脚应在引脚之前有一个“！”（例如，“enable_pin:!PA1”）。</p>
<h2 id="_4">验证限位开关<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>
<p>Manually move all the printer axes so that none of them are in contact with an endstop. Send a QUERY_ENDSTOPS command via the command console. It should respond with the current state of all of the configured endstops and they should all report a state of "open". For each of the endstops, rerun the QUERY_ENDSTOPS command while manually triggering the endstop. The QUERY_ENDSTOPS command should report the endstop as "TRIGGERED".</p>
<p>If the endstop appears inverted (it reports "open" when triggered and vice-versa) then add a "!" to the pin definition (for example, "endstop_pin: ^PA2"), or remove the "!" if there is already one present.</p>
<p>手动移动所有打印机轴，使其不与端挡接触。通过命令控制台发送QUERY_ENDSTOPS命令。它应该以所有配置的端站的当前状态进行响应，并且它们都应该报告“打开”状态。对于每个endstop，在手动触发endstop的同时重新运行QUERY_endstops命令。QUERY_ENDSTOPS命令应将endstop报告为“TRIGGERED”。</p>
<p>如果endstop出现反转（触发时报告“打开”，反之亦然），则在端号定义中添加一个“！”（例如，“endstop_pin:^PA2”），或者如果已经存在“！”，则删除该“！”。</p>
<p>如果限位状态根本没有变化，则通常表示限位器连接到不同的引脚。 但是，它也可能表示需要更改引脚的上拉设置（endstop_pin 名称开头的“^” - 大多数打印机需要使用上拉电阻并且应该存在“^”）。</p>
<h2 id="_5">验证步进电机<a class="headerlink" href="#_5" title="Permanent link">&para;</a></h2>
<p>Use the STEPPER_BUZZ command to verify the connectivity of each stepper motor. Start by manually positioning the given axis to a midway point and then run <code>STEPPER_BUZZ STEPPER=stepper_x</code> in the command console. The STEPPER_BUZZ command will cause the given stepper to move one millimeter in a positive direction and then it will return to its starting position. (If the endstop is defined at position_endstop=0 then at the start of each movement the stepper will move away from the endstop.) It will perform this oscillation ten times.</p>
<p>使用STEPPER_BUZZ命令验证每个步进电机的连接。首先手动将给定轴定位到中间点，然后在命令控制台中运行<code>STEPPER_BUZZ STEPPER=stepper_x</code> 。STEPPER_BUZZ命令将使给定的步进器向正方向移动一毫米，然后返回其起始位置。（如果在position_endstop=0处定义了端止点，则在每次移动开始时，步进器将远离端止点。）它将执行十次此振荡。</p>
<p>如果步进电机根本不动，则需要验证步进驱动的“enable_pin”和“step_pin”设置。 如果步进电机移动但没有返回其原始位置，则需要验证“dir_pin”设置。 如果步进电机的振荡方向不正确，则通常表示需要反转驱动的“dir_pin”。 即通过添加“!” 到打印机配置文件中的“dir_pin”设置来完成（如果已经存在"!"，则将其删除）。 如果电机移动明显大于或小于一毫米，则需要验证“rotation_distance”设置。</p>
<p>对配置文件中定义的每个步进电机运行上述测试。 （将 STEPPER_BUZZ 命令的 STEPPER 参数设置为要测试的配置部分的名称。）如果挤出机中没有耗材，也可以使用 STEPPER_BUZZ 验证挤出机电机的接线（使用 STEPPER=extruder）。 否则，最好单独测试挤出机电机（参见下一节）。</p>
<p>在验证完所有限位器和所有步进电机后，应测试归位机制。 发出 G28 命令以归位所有轴。 如果打印机不能正常归位，请断开打印机电源。 然后，重新执行限位器和步进电机验证流程。</p>
<h2 id="_6">验证挤出机电机<a class="headerlink" href="#_6" title="Permanent link">&para;</a></h2>
<p>To test the extruder motor it will be necessary to heat the extruder to a printing temperature. Navigate to the temperature graph section and select a target temperature from the temperature drop-down box (or manually enter an appropriate temperature). Wait for the printer to reach the desired temperature. Then navigate to the command console and click the "Extrude" button. Verify that the extruder motor turns in the correct direction. If it does not, see the troubleshooting tips in the previous section to confirm the "enable_pin", "step_pin", and "dir_pin" settings for the extruder.</p>
<p>为了测试挤出机电机，有必要将挤出机加热到打印温度。导航到温度图部分，并从温度下拉框中选择目标温度（或手动输入适当的温度）。等待打印机达到所需温度。然后导航到命令控制台并单击“挤出”按钮。确认挤出机电机的转动方向正确。如果没有，请参阅上一节中的故障排除提示，以确认挤出机的“enable_pin”、“step_pin”和“dir_pin”设置。</p>
<h2 id="pid">校准 PID 设置<a class="headerlink" href="#pid" title="Permanent link">&para;</a></h2>
<p>Klipper支持挤出机和热床加热器的<a href="https://en.wikipedia.org/wiki/PID_controller">PID控制</a>。为了使用这种控制机制，必须对每台打印机的 PID 参数进行校准（在其他固件或示例配置文件中找到的 PID 设置往往效果不佳）。</p>
<p>To calibrate the extruder, navigate to the command console and run the PID_CALIBRATE command. For example: <code>PID_CALIBRATE HEATER=extruder TARGET=170</code></p>
<p>要校准挤出机，请导航到命令控制台并运行PID_calibrate命令。例如：<code>PID_CALIBRATE HEATER=挤出机TARGET=170</code></p>
<p>调整测试完成后，运行 <code>SAVE_CONFIG</code> 以保存新PID设置到printer.cfg文件。</p>
<p>如果打印机有加热床，并且支持PWM（脉宽调制）驱动，那么建议对加热床使用PID控制。 （当使用 PID 算法控制床加热器时，它可能每秒打开和关闭十次，这可能不适用于使用机械开关的加热器。）一般的热床 PID 校准命令是：<code>PID_CALIBRATE HEATER=heater_bed TARGET=60</code></p>
<h2 id="_7">下一步<a class="headerlink" href="#_7" title="Permanent link">&para;</a></h2>

12
zh/Measuring_Resonances.html
View File

@@ -2474,18 +2474,18 @@ Recommended shaper_type_y = mzv, shaper_freq_y = 36.8 Hz
<p><strong>Warning!</strong> It is not advisable to run the shaper auto-calibration very frequently (e.g. before every print, or every day). In order to determine resonance frequencies, auto-calibration creates intensive vibrations on each of the axes. Generally, 3D printers are not designed to withstand a prolonged exposure to vibrations near the resonance frequencies. Doing so may increase wear of the printer components and reduce their lifespan. There is also an increased risk of some parts unscrewing or becoming loose. Always check that all parts of the printer (including the ones that may normally not move) are securely fixed in place after each auto-tuning.</p>
<p>此外，由于测量中的一些噪音，每次校准得到的调谐结果会略有不同。不过，这些噪音一般不会对打印质量产生太大影响。然而，我们仍然建议仔细检查建议的参数，并在使用前打印一些测试件以确认它们是正确的。</p>
<h2 id="_14">离线处理加速计数据<a class="headerlink" href="#_14" title="Permanent link">&para;</a></h2>
<p>It is possible to generate the raw accelerometer data and process it offline (e.g. on a host machine), for example to find resonances. In order to do so, run the following commands via Octoprint terminal:</p>
<p>可以生成原始的加速度计数据并离线处理（例如在一台电脑上），以查找共振频率为例，在Octoprint的终端内运行如下命令：</p>
<div class="highlight"><pre><span></span><code>SET_INPUT_SHAPER SHAPER_FREQ_X=0 SHAPER_FREQ_Y=0
TEST_RESONANCES AXIS=X OUTPUT=raw_data
</code></pre></div>
<p>ignoring any errors for <code>SET_INPUT_SHAPER</code> command. For <code>TEST_RESONANCES</code> command, specify the desired test axis. The raw data will be written into <code>/tmp</code> directory on the RPi.</p>
<p>忽略<code>SET_INPUT_SHAPER</code>命令的任何错误。对<code>TEST_RESONANCES</code>指定测试的方向。原始数据保存至<code>/tmp</code>目录内。</p>
<p>在一些正常的打印机活动中，也可以通过运行命令 <code>ACCELEROMETER_MEASURE</code>两次来获得原始数据——首先是开始测量，然后是停止测量并写入输出文件。有关更多详细信息，请参阅<a href="G-Codes.html#adxl345">G-Codes</a>。</p>
<p>The data can be processed later by the following scripts: <code>scripts/graph_accelerometer.py</code> and <code>scripts/calibrate_shaper.py</code>. Both of them accept one or several raw csv files as the input depending on the mode. The graph_accelerometer.py script supports several modes of operation:</p>
<p>这些数据可在以后通过<code>scripts/graph_accelerometer.py</code>和scripts/calibrate_shaper.py`脚本进行处理，在不同的工作模式下，两种脚本支持一个或多个原始数据csv文件作为输入。graph_accelerometer.py支持以下几种模式：</p>
<ul>
<li>plotting raw accelerometer data (use <code>-r</code> parameter), only 1 input is supported;</li>
<li>plotting a frequency response (no extra parameters required), if multiple inputs are specified, the average frequency response is computed;</li>
<li>comparison of the frequency response between several inputs (use <code>-c</code> parameter); you can additionally specify which accelerometer axis to consider via <code>-a x</code>, <code>-a y</code> or <code>-a z</code> parameter (if none specified, the sum of vibrations for all axes is used);</li>
<li>绘制原始加速度数据图（使用<code>-r</code>参数），仅支持一个输入；</li>
<li>绘制频率响应图（无需额外参数），如果指定了多个输入文件，将计算他们的平均值；</li>
<li>在多个输入之间比较频率响应曲线（使用<code>-c</code>参数）；通过<code>-ax，</code>-ay<code>或</code>-az`参数，可以额外指定哪个轴参与比较（在未指定时将计算所有轴振动的总和）;</li>
<li>plotting the spectrogram (use <code>-s</code> parameter), only 1 input is supported; you can additionally specify which accelerometer axis to consider via <code>-a x</code>, <code>-a y</code> or <code>-a z</code> parameter (if none specified, the sum of vibrations for all axes is used).</li>
</ul>
<p>Note that graph_accelerometer.py script supports only the raw_data*.csv files and not resonances*.csv or calibration_data*.csv files.</p>

BIN
zh/_klipper3d/__pycache__/mkdocs_hooks.cpython-38.pyc
View File

Binary file not shown.

2
zh/search/search_index.json
View File

File diff suppressed because one or more lines are too long

106
zh/sitemap.xml
View File

@@ -2,267 +2,267 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-12-18</lastmod>
<lastmod>2023-12-19</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>

BIN
zh/sitemap.xml.gz
View File

Binary file not shown.