Recent changes to Home

Home modified by Ingo

Ingo — Mon, 16 Jul 2018 20:14:06 -0000

--- v19
+++ v20
@@ -1,3 +1,5 @@
+[[download url=https://forge.codesys.com/svn/drv,mcp3008,code/trunk/mcp3008.package]]
+
 [TOC]

 # Hardware

Home modified by Ingo

Ingo — Mon, 16 Jul 2018 20:04:42 -0000

--- v18
+++ v19
@@ -45,4 +45,4 @@
 * Just create a variable of type DWORD,
 * go to the "I/O Mapping" page of the MCP3008 device,
 * double click on your desired I/O channel,
-* and click on the button [...] to select your variable.
+* and click on the button "..." to select your variable.

Home modified by Ingo

Ingo — Mon, 16 Jul 2018 20:04:22 -0000

--- v17
+++ v18
@@ -14,7 +14,7 @@
 You need to have the device description and driver library installed from the "MCP3008" project.

 # Usage
-This driver can be used in a similar way as most other CODESYS devices. Except, that the outputs are not mapped through the I/O mapping, but they are provided as an output of the FB from the device tree.
+This driver can be used in a similar way as most other CODESYS devices. You add it to your project and map your input variables.

 ## Wiring
 The chip has to be connected to a free SPI port. We assume, that you connect the chip with a chip select that coresponds to your SPI port. ATM we don't support to use general GPIOs for chip selects. Also no daisy chaining is supported, as the device doesn't support that.
@@ -40,8 +40,9 @@
 The first number specifies the SPI bus. The second number specifies the chip select.

 ## Use the A/D values
-After the configuration is done, the input of the MCP3008 can be used directly from the output of the function block.
+You can easily map the analog input channels to some variables within your project.

-~~~
-ch1 := MCP3008.auiValue[0];
-~~~
+* Just create a variable of type DWORD,
+* go to the "I/O Mapping" page of the MCP3008 device,
+* double click on your desired I/O channel,
+* and click on the button [...] to select your variable.

Home modified by Ingo

Ingo — Thu, 07 Jun 2018 19:50:23 -0000

--- v16
+++ v17
@@ -19,7 +19,7 @@
 ## Wiring
 The chip has to be connected to a free SPI port. We assume, that you connect the chip with a chip select that coresponds to your SPI port. ATM we don't support to use general GPIOs for chip selects. Also no daisy chaining is supported, as the device doesn't support that.

-This example shows the wirering of an MCP3008 with a Raspberry Pi on SPI port 0 and chip select 0. This corresponds to "spidev0.0".
+This example shows the wiring of an MCP3008 with a Raspberry Pi on SPI port 0 and chip select 0. This corresponds to "spidev0.0".

 [[img src=MCP3008_bb.png width=30%]]
 [[img src=MCP3008_schem.png width=30%]]

Home modified by Ingo

Ingo — Thu, 07 Jun 2018 19:49:14 -0000

--- v15
+++ v16
@@ -16,7 +16,7 @@
 # Usage
 This driver can be used in a similar way as most other CODESYS devices. Except, that the outputs are not mapped through the I/O mapping, but they are provided as an output of the FB from the device tree.

-## Wirering
+## Wiring
 The chip has to be connected to a free SPI port. We assume, that you connect the chip with a chip select that coresponds to your SPI port. ATM we don't support to use general GPIOs for chip selects. Also no daisy chaining is supported, as the device doesn't support that.

 This example shows the wirering of an MCP3008 with a Raspberry Pi on SPI port 0 and chip select 0. This corresponds to "spidev0.0".

Home modified by Ingo

Ingo — Thu, 07 Jun 2018 19:48:24 -0000

--- v14
+++ v15
@@ -19,7 +19,7 @@
 ## Wirering
 The chip has to be connected to a free SPI port. We assume, that you connect the chip with a chip select that coresponds to your SPI port. ATM we don't support to use general GPIOs for chip selects. Also no daisy chaining is supported, as the device doesn't support that.

-This examle shows the wirering of an MCP3008 with a Raspberry Pi on SPI port 0 and chip select 0. This corresponds to "spidev0.0".
+This example shows the wirering of an MCP3008 with a Raspberry Pi on SPI port 0 and chip select 0. This corresponds to "spidev0.0".

 [[img src=MCP3008_bb.png width=30%]]
 [[img src=MCP3008_schem.png width=30%]]

Home modified by Ingo

Ingo — Thu, 07 Jun 2018 19:47:23 -0000

--- v13
+++ v14
@@ -17,7 +17,7 @@
 This driver can be used in a similar way as most other CODESYS devices. Except, that the outputs are not mapped through the I/O mapping, but they are provided as an output of the FB from the device tree.

 ## Wirering
-The chip has to be connected to a free SPI port. We assume, that you connect the chip with a chip select that coresponds to your SPI port. ATM we don't supporr to use general GPIOs for chip selects. Also no daisy chaining is supported, as the device doesn't support that.
+The chip has to be connected to a free SPI port. We assume, that you connect the chip with a chip select that coresponds to your SPI port. ATM we don't support to use general GPIOs for chip selects. Also no daisy chaining is supported, as the device doesn't support that.

 This examle shows the wirering of an MCP3008 with a Raspberry Pi on SPI port 0 and chip select 0. This corresponds to "spidev0.0".

Home modified by Ingo

Ingo — Thu, 07 Jun 2018 19:46:40 -0000

--- v12
+++ v13
@@ -14,7 +14,7 @@
 You need to have the device description and driver library installed from the "MCP3008" project.

 # Usage
-This driver can be used in a similar way as most other CODESYS devices. Except, that the outputs are not mapped through the I/O mapping, but they are privided as an output of the FB from the device tree.
+This driver can be used in a similar way as most other CODESYS devices. Except, that the outputs are not mapped through the I/O mapping, but they are provided as an output of the FB from the device tree.

 ## Wirering
 The chip has to be connected to a free SPI port. We assume, that you connect the chip with a chip select that coresponds to your SPI port. ATM we don't supporr to use general GPIOs for chip selects. Also no daisy chaining is supported, as the device doesn't support that.

Home modified by Ingo

Ingo — Thu, 07 Jun 2018 19:45:05 -0000

--- v11
+++ v12
@@ -10,7 +10,7 @@

 [[img src=mcp3008.gif width=30%]]

-# Prerequisits
+# Prerequisites
 You need to have the device description and driver library installed from the "MCP3008" project.

 # Usage

Home modified by Ingo

Ingo — Mon, 04 Jun 2018 16:57:57 -0000

--- v10
+++ v11
@@ -8,7 +8,7 @@

 This is far beyond what we are able to read via Linux over SPI.

-[[img src=mcp3008.gif]]
+[[img src=mcp3008.gif width=30%]]

 # Prerequisits
 You need to have the device description and driver library installed from the "MCP3008" project.
@@ -21,8 +21,8 @@

 This examle shows the wirering of an MCP3008 with a Raspberry Pi on SPI port 0 and chip select 0. This corresponds to "spidev0.0".

-[[img src=MCP3008_bb.png]]
-[[img src=MCP3008_schem.png]]
+[[img src=MCP3008_bb.png width=30%]]
+[[img src=MCP3008_schem.png width=30%]]

 ## Add the device
 The device is named MCP3008 and has to be inserted below an SPI Master of your CODESYS project.