Fix MCP3xxx Readme

hardware/mcp3008/README.md

@@ -39,7 +39,7 @@ You can also select device id 0 or 1 (CE0 or CE1) depending on how you have wire
 
 And you can also select the SPI bus number 0 or 1 depending on how you have wired up your device. Defaults to 0 for spidev0.
 
-Outputs a numeric `msg.payload` with a range of 0 to 1023, where 0 = 0V and 1023 = 3.3V (assuming you use the default 3.3V voltage reference).
+Outputs a numeric `msg.payload` with a range of 0 to 1023 for MCP30XX family, where 0 = 0V and 1023 = 3.3V (assuming you use the default 3.3V voltage reference). For MCP32XX and MCP33XX the range returned is 0 to 4095.
 
 **Hint**: use a `range` node to adjust the values to the range you want.
 

hardware/mcp3008/package.json

@@ -1,6 +1,6 @@
 {
     "name"          : "node-red-node-pi-mcp3008",
-    "version"       : "0.4.0",
+    "version"       : "0.4.2",
     "description"   : "A Node-RED node to read from the MCP3008 Analogue to Digital Converter",
     "dependencies"  : {
         "mcp-spi-adc": "^3.2.0"

hardware/mcp3008/pimcp3008.html

@@ -52,7 +52,8 @@
     such as the rasp.io/analogzero.</p>
     <p>You can either set a channel in the edit dialogue, or you can set the <code>msg.payload</code>
     to select the channel dynamically. If so then the expected payload must be a value from 0 to 7.</p>
-   <p>Outputs a numeric <code>msg.payload</code> with a range of 0 to 1023, representing 0V to 3.3V.</p>
+    <p>Outputs a numeric <code>msg.payload</code> with a range of 0 to 1023 for MCP30xx or 0 to 4095 for
+    MCP32xx and MPC33xx, representing 0V to 3.3V.</p>
     <p><i>Hint</i>: use a <code>range</code> node to re-scale the values to ones you want.</p>
     <p>Also sets <code>msg.topic</code> to <i>adc/{the pin number}</i></p>
     <p><b>Warning</b>: Input voltages must not exceed 3.3V</p>