-
Notifications
You must be signed in to change notification settings - Fork 148
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1,798 changed files
with
1,680,300 additions
and
181,134 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# Example | ||
|
||
## SAMFi-OS_OrangePi_zero | ||
|
||
Before you config the [SAMF-OS_OrangePi_zero](https://github.com/FYSETC/FYSETC-SAMFi-OS). You need an TF card with at least 8G capacity. | ||
|
||
### Step 1 | ||
|
||
Download and flash the OS image with `balenaEtcher` software to your TF card. Insert your flashed TF card to OrangePi-zero and connect Ethernet cable then power on. Find the ip address of OrangePi-zero on your router, host name is `orangepizero`. | ||
|
||
 | ||
|
||
### Step 2 | ||
|
||
You can find the firmware `klipper.bin` in `OrangePi-zero` folder after you download the github repository. It is also stay in the OS path `firmwares\spider.bin` after you login the OS with SSH. | ||
|
||
Original SSH account and password: | ||
|
||
``` | ||
account: fysetc | ||
password: fysetc123 | ||
``` | ||
|
||
Enter DFU mode(set a jumper on `3.3V` and `BT0` pin and re-power on the board ), and flash the firmware with the command below after you connect your OrangePi and Spider with USB cable. | ||
|
||
``` | ||
dfu-util -R -a 0 -s 0x08008000:leave -D firmwares/spider.bin | ||
``` | ||
|
||
or follow the instructions [here](https://github.com/FYSETC/FYSETC-SPIDER#44--firmware-upload) for firmware uploading. Remember to remove the `3.3v` `BT0` jumper and click the reset button after you flashed the firmware. | ||
|
||
 | ||
|
||
### Step 3: | ||
|
||
Prepare the `pinter.cfg`, using the command below | ||
|
||
``` | ||
cp klipper_config/spider.cfg klipper_config/printer.cfg | ||
``` | ||
|
||
You probably need to change `id` by `ls /dev/serial/by-id` command. | ||
|
||
I use the spider github voron2.4 config for this example, you need search this file for "SpiderVersion" and uncomment the appropriate line for each for different spider board version, and need to change it according to your machine. Now visit the webpage with your orangepi-zero IP address. Good to go. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
近期,关于3.3V的故障,有一些客户提出了一些新的想法,如果你有兴趣的话,可以尝试。这样以给我们提供一些反馈数据,这有助于我们做进一步的判断。 | ||
|
||
原因:3.3v 烧毁问题有可能是主板残留电能导致。 | ||
|
||
分析:蜘蛛主板上前端(MAIN_PWR)有一颗 470uF 的大电容,并且每个驱动位置(VMOT)有 100uF 的电容(共计8个),VMOT 与 MAIN_PWR 通过二极管连接。工厂测试时,主板通电,直止所有功能测完后断电。 | ||
此时主板上仍然有储存的电能存在,MAIN_PWR 的电能可以通过相连的LED等外设消耗掉,但是由于二极管的存在,VMOT的电能没有外接设备进行消耗,可能会存在很长时间(不确定多长)。 | ||
而且有的客户拿到板子后,会先不插驱动上电,检查过后,再插上驱动,然后上电,这样一个过程会再次储存电能,并且没有足够的时间使得电能释放。 | ||
这种情况下,驱动的插入,相当于是带着电能操作,有很大的概率会烧掉驱动(2209的额定电压本来就低)。 | ||
|
||
纠正做法:在插入驱动之前将主板的电能都放掉。 | ||
1.彻底断掉主板电源(完全去掉接线),等待 24v、5v和3.3v的LED完全熄灭。 | ||
2.用一个 100K 电阻(或者导线)接 MAIN_PWR 的 +/- 极。 | ||
3.用一个 100K 电阻(或者导线)接 VMOT 的 +/- 极。 | ||
4.等待5-10分钟,插上驱动,进行固件等操作。 | ||
|
||
Recently, some customers have put forward some new ideas about the 3.3V failure. I recommend you can try it before you power up your spider. Glad that you can provide us with some feedback, which will help us to make further judgments. | ||
|
||
Reason: 3.3v burning problem may be caused by residual power on the motherboard. | ||
|
||
Analysis: The front end (`MAIN_PWR`) on the spider motherboard has a large capacitor of `470uF`, and each drive position (`VMOT`) has a capacitor of `100uF` (a total of 8). `VMOT` and `MAIN_PWR` are connected through a diode. During the factory test, the main board is powered on, and the power is turned off after all functions are tested. | ||
At this time, there is still stored electrical energy on the motherboard. The electrical energy of `MAIN_PWR` can be consumed by peripherals such as connected LEDs. However, due to the existence of diodes, the electrical energy of `VMOT` is not consumed by external devices and may exist for a long time (not sure how long). | ||
Moreover, after some customers get the board, they will power on without plugging in the driver. After checking, plug in the driver and then power on. Such process will store electrical energy again, and there is not enough time for the electrical energy to be released. | ||
In this case, the insertion of the stepper driver is equivalent to operating with electrical energy, and there is a high probability that the stepper driver will be burned (the rated voltage of the 2209 is inherently low). | ||
|
||
Corrective action when you get Spider: Discharge the power of the motherboard before inserting the driver. | ||
1. Power off the motherboard completely (remove the wiring completely), and wait for the 24v, 5v and 3.3v LEDs to be completely off. | ||
2. Connect a 100K resistor (or a cable) to the +/- pole of `MAIN_PWR`. | ||
3. Connect a 100K resistor (or a cable) to the +/- pole of `VMOT`. | ||
4. Wait for 5-10 minutes, plug in the driver, and perform firmware and other operations. | ||
|
||
 | ||
|
||
 |
Binary file not shown.
Binary file not shown.
Oops, something went wrong.