summaryrefslogtreecommitdiff
path: root/OpenPLC_version_1/Documentation/Programming-OpenPLC.rst
diff options
context:
space:
mode:
Diffstat (limited to 'OpenPLC_version_1/Documentation/Programming-OpenPLC.rst')
-rwxr-xr-xOpenPLC_version_1/Documentation/Programming-OpenPLC.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/OpenPLC_version_1/Documentation/Programming-OpenPLC.rst b/OpenPLC_version_1/Documentation/Programming-OpenPLC.rst
index b5e768d..fd344f2 100755
--- a/OpenPLC_version_1/Documentation/Programming-OpenPLC.rst
+++ b/OpenPLC_version_1/Documentation/Programming-OpenPLC.rst
@@ -10,7 +10,7 @@ Now that the programmer is installed on the system, we need to adjust the
properties of the controller IC such that it meets the necessary requirements along with the peripherals installed on the board. Essentially, fuse bits are the ones that decide how the controller responds, like which clock frequency it responds to or its programming availabilities.
Setting up the fuse is a crucial task as the controller may not respond later if the fuse bits that are set are not in accordance with the attached peripherals. Before setting the fuses, the factory settings on the controller make sure it works on the internal oscillator of clock speed 1MHz. It’s mostly dependent on 2 fuses - lfuse and hfuse. Both of these have hex 8 bit values. When working on communication with the device, like UART, these fuse bits play a key role, if not defined, the
-controller works on the internal clock that’s much slower than the externalcrystal. For the controller, 16MHz external crystal was selected. This meant the controller shall configure this external crystal and work on it.
+controller works on the internal clock that’s much slower than the external crystal. For the controller, 16MHz external crystal was selected. This meant the controller shall configure this external crystal and work on it.
**WARNING:** Fuse bits control the way the controller responds. If
any mistake is made in setting up the fuse bits, then the controller
@@ -25,14 +25,14 @@ Type the following command into the Terminal:
Screen like below will pop up after giving the command line
-.. image:: ../Images/fuse1.png
+.. image:: ../assets/fuse1.png
:height: 540px
:width: 450px
:scale: 100
-You can read fust bits after setting up, as shown below,
+You can read fuse bits after setting up, as shown below,
-.. image:: ../Images/fuse2.png
+.. image:: ../assets/fuse2.png
:height: 540px
:width: 450px
:scale: 100
@@ -42,7 +42,7 @@ Now the external crystal is working in sync with the controller.
USBASP as ISP
-------------
-Step 1: We require a precompiled hex file to be burnt onto our microcontroller. In our case, we have generated it by doing simple ladder programming in LDMicro and then compiling it. Before that, ensure that the proper target controller from the drop-down menu is chosen. For input and output part, assign a certain pin no. of the controller to that of the desired application. Now, a certain name is given to the file(say, blink.hex) at the destination folder.
+Step 1: We require a pre-compiled hex file to be burnt onto our microcontroller. In our case, we have generated it by doing simple ladder programming in LDMicro and then compiling it. Before that, ensure that the proper target controller from the drop-down menu is chosen. For input and output part, assign a certain pin no. of the controller to that of the desired application. Now, a certain name is given to the file(say, blink.hex) at the destination folder.
Step 2: After being done with all the software part, one shall supply the power from 12V SMPS to the development board. Now check whether the
controller is powered up properly with 5 Volt or not from the appropriate Vcc and GND pins of the controller.
@@ -62,7 +62,7 @@ below, which means that the process of erasing and writing the internal
memory of the ATmega IC is in the process. On correct execution you shall
get such a result. Whilst it’s burning the code, the red light on the USBASP will be lit showing that it is communicating with the controller appropriately.
-.. image:: ../Images/usb.png
+.. image:: ../assets/usb.png
:height: 540px
:width: 450px
:scale: 100