no functional change

[digitaldcpower] / README.htm

diff --git a/README.htm b/README.htm
index 00e9973..0a2061f 100644 (file)
--- a/README.htm
+++ b/README.htm
@@ -1,10 +1,16 @@
 <h2>Tuxgraphics Digital DC Power Supply Unit</h2>
 <h2>Tuxgraphics Digital DC Power Supply Unit</h2>

+Software for the version 3 hardware.

 <pre>
 
 <pre>
 

-Compile the software and program the microcontroller:
+Compiling the software and programming 
+the microcontroller (atmega8 or atmega8a):
+==========================================

 
 1) edit and adapt the file hardware_settings.h 
    (calibration and selection of the right hardware type).
 
 1) edit and adapt the file hardware_settings.h 
    (calibration and selection of the right hardware type).

+   You can as well just copy one of the pre-set versions
+   on top of hardware_settings.h. 
+   Example: cp hardware_settings.h-22V hardware_settings.h

 
 2) load and compile:
 make 
 
 2) load and compile:
 make 


@@ -15,9 +21,9 @@ make fuse
 
 This should result in the following settings:
 
 
 This should result in the following settings:
 

-avrdude: Device signature = 0x1e9307
-avrdude: safemode: lfuse reads as A4
-avrdude: safemode: hfuse reads as D9
+  Device signature = 0x1e9307
+   lfuse reads as A4
+   hfuse reads as D9

 
 Fuse Low Byte details
 
 
 Fuse Low Byte details
 


@@ -30,15 +36,15 @@ CKSEL2    Select Clock source              = 1
 CKSEL1    Select Clock source              = 0
 CKSEL0    Select Clock source              = 0
 
 CKSEL1    Select Clock source              = 0
 CKSEL0    Select Clock source              = 0
 

-The make fuse needs to be done only once
-unless you change the Atmega8 chip. make/make load
+The "make fuse" needs to be done only once
+unless you change the Atmega8/Atmega8a chip. make/make load

 need to be repeated everytime you change something
 in the software (e.g update of hardware_settings.h). 
 
 The poweresupply must be powered up during programming
 need to be repeated everytime you change something
 in the software (e.g update of hardware_settings.h). 
 
 The poweresupply must be powered up during programming

-but nothing should be connected to the output. Make
+but nothing should be connected on the output. Make

 sure that you do not accidently press any button
 sure that you do not accidently press any button

-during the programming (loading the software into the uC).
+during the programming (while loading the software into the uC).

 
 Compile under windows
 =====================
 
 Compile under windows
 =====================


@@ -47,17 +53,19 @@ Please use the provided Makefile.
 There are as well 3 batch files which you can use
 to run the makefile. To use them edit them and change
 the path as per your avr-gcc installation on your PC.
 There are as well 3 batch files which you can use
 to run the makefile. To use them edit them and change
 the path as per your avr-gcc installation on your PC.

-After that run them by double-clickin in the file manager
-on those batch files.
+After that run them by double-clicking on them in the 
+file manager.

 
  winmake.bat  -- comile, this is mandatory to use
 
 
  winmake.bat  -- comile, this is mandatory to use
 

+ winclean.bat -- delete all files generated during compilation
+

  winload.bat  -- load software using avrdude, may also use
                  some other means of loading the softare. In that
                  case you do not need to use this batch file.
 
  winload.bat  -- load software using avrdude, may also use
                  some other means of loading the softare. In that
                  case you do not need to use this batch file.
 

- winsetfuse.bat -- set fuse bytes using avrdude, may also use
-                   some other means of loading the softare. In that
+ winsetfuse.bat -- set fuse bytes using avrdude. You may as well use
+                   some other means of changing the fuse bytes. In that

                    case you do not need to use this batch file.
 
 Calibration
                    case you do not need to use this batch file.
 
 Calibration


@@ -76,16 +84,15 @@ A microncontroller controlled bench DC power supply unit.
 
 All of the control logic is implemented in software. This
 saves a lot of parts compared to conventional lab-power 
 
 All of the control logic is implemented in software. This
 saves a lot of parts compared to conventional lab-power 

-supplies. This means it is cheaper, easier to build and
+supplies and means it is cheaper, easier to build and

 offers more functionallity.
 
 Note however that this means also that the short circuit
 offers more functionallity.
 
 Note however that this means also that the short circuit

-protection is implemented in software. So be careful when
+protection is implemented in software. Be careful when

 you change something in the software. If the microcontroller 
 is not running properly due to a software fault then there
 might not be any short circuit protection.
 
 you change something in the software. If the microcontroller 
 is not running properly due to a software fault then there
 might not be any short circuit protection.
 

-

 The software is prepared for 2 versions:
 - 0-22V 0-2.5A
 - 0-30V 0-2A
 The software is prepared for 2 versions:
 - 0-22V 0-2.5A
 - 0-30V 0-2A


@@ -94,18 +101,20 @@ If you want to build a version that has a smaller output
 range than any of the two version then you can just
 modify the file hardware_settings.h.
 
 range than any of the two version then you can just
 modify the file hardware_settings.h.
 

+Remote control from your PC
+===========================

 The unit can be controlled remotely from a computer using
 a USB serial interface. An add-on card is available from
 http://shop.tuxgraphics.org which offers galvanic separation
 such that you can use this power supply relative to
 The unit can be controlled remotely from a computer using
 a USB serial interface. An add-on card is available from
 http://shop.tuxgraphics.org which offers galvanic separation
 such that you can use this power supply relative to

-any reference point (e.g build two power supply and use
+any reference point (e.g build two power supplies and use

 one as negative and one as positive power supply).
 
 Terminal settings for remote control via your computer
 ======================================================
 You can e.g use putty under windows
 http://www.chiark.greenend.org.uk/~sgtatham/putty/ 
 one as negative and one as positive power supply).
 
 Terminal settings for remote control via your computer
 ======================================================
 You can e.g use putty under windows
 http://www.chiark.greenend.org.uk/~sgtatham/putty/ 

-it supports as well serial connections. The other common
+Putty supports as serial connections. The other common

 option under windows is HyperTerminal but it is more complicated
 to use than putty.
 For Linux I can recommend picocom
 option under windows is HyperTerminal but it is more complicated
 to use than putty.
 For Linux I can recommend picocom


@@ -118,11 +127,14 @@ Serial port settings for the terminal:
 
 port       : Virtual com port (e.g /dev/ttyUSB1 or /dev/ttyUSB0
              or COM5 under windows or ... whatever port the
 
 port       : Virtual com port (e.g /dev/ttyUSB1 or /dev/ttyUSB0
              or COM5 under windows or ... whatever port the

-            virtual com-port maps to)
-            Under linux or Mac you can use the command dmesg
-            after you have plugged in the USB cable to see to 
-            which com-port/device the new virtual com port maps to.
-            
+             virtual com-port maps to)
+             Under linux or Mac you can use the command dmesg
+             after you have plugged in the USB cable to see to 
+             which com-port/device the new virtual com port maps to.
+             Under windows you look at Control Panel-&gt;Hardware-&gt;Devices
+             and click on FT232R USB UART-&gt;Hardware to see the COM
+             port.
+             

 baudrate   : 9600
 parity     : none
 flowcontrol: none
 baudrate   : 9600
 parity     : none
 flowcontrol: none


@@ -132,49 +144,72 @@ databits   : 8
 </pre>
 <br>
 <img src=screenshot-cmd-interface.gif>
 </pre>
 <br>
 <img src=screenshot-cmd-interface.gif>

-<br>
-<br>
-At shop.tuxgraphics.org you can get an optically insulated
-USB to serial interface add-on kit such that your computer
-is galvanically separated from the power supply but still able
-to give commands. This enables you as well to use two power supplies
-to provide positive and negative supply voltages for e.g. an operational amplifier.
-

 <br>
 <br>
 <pre>
 <br>
 <br>
 <pre>

+Controling the power supply with scriptable commands
+====================================================

 You can control the digital power supply by commands. A number 
 of commands are provided for this purpose. They are at the moment
 You can control the digital power supply by commands. A number 
 of commands are provided for this purpose. They are at the moment

-available for Linux and Mac:
+available for Linux, Mac and Windows:

 
 
 
 

-ddcp-script-ttyinit   - initialize the COM port
+ddcp-script-ttyinit   - initialize the COM port (run this once at
+                        at the beginning)

 ddcp-script-getval    - get current values (same as you see on the LCD)
 ddcp-script-setval    - send a command to the power supply
 
 ddcp-script-getval    - get current values (same as you see on the LCD)
 ddcp-script-setval    - send a command to the power supply
 

-ddcp-script-example.sh  - an example shell script showing how to use 
+ddcp-script-example.sh  - an example unix shell script showing how to use 

                           the above commands
 
                           the above commands
 

+To compile the ddcp-script commands under linux and on the mac
+use the command:
+
+make ddcp-script
+
+The windows versions of those commands are available in the
+sub-directory "ddcp-script-windows". The windows versions
+are compiled in that sub-directory with the command:
+
+make
+
+Pre-compiled binaries are available for winXP.
+

 -------------------------------------------------------------------
 -------------------------------------------------------------------

-Copyright: GPL V2
-Author: Guido Socher
+Software License:
+Copyright: GPL V2 (see http://www.gnu.org/licenses/old-licenses/gpl-2.0.html )
+Author: Guido Socher (guidosocher@gmail.com)

 Homepage: http://www.tuxgraphics.org/electronics/
 -------------------------------------------------------------------
 Change history:
 digitaldcpower-0.6.0 -- 2010-05-22 first version of the new power V3.
 Homepage: http://www.tuxgraphics.org/electronics/
 -------------------------------------------------------------------
 Change history:
 digitaldcpower-0.6.0 -- 2010-05-22 first version of the new power V3.

-                        This version is made for a new type of hardware
-                        and will not run on any previous hardware version.
+                         This version is made for a new type of hardware
+                         and will not run on any previous hardware version.

 
 digitaldcpower-0.6.1 -- 2010-06-06 Number conversion to display string
 
 digitaldcpower-0.6.1 -- 2010-06-06 Number conversion to display string

-                        improved.
-                     -- Basic uart interface prompt, no remote control yet
+                         improved.
+                         Basic uart interface prompt, no remote control yet

 
 digitaldcpower-0.6.2 -- 2010-06-26 Full UART command interface
 
 digitaldcpower-0.6.2 -- 2010-06-26 Full UART command interface

+

 digitaldcpower-0.6.3 -- 2010-07-03 Accelerate UART command polling to
 digitaldcpower-0.6.3 -- 2010-07-03 Accelerate UART command polling to

-                        not loose characters when copied/pasted at high speed.
-                       Line editing with backspace if terminal supports it.
-                       Set BOD (brown out detector enable) fuse.
-                       Script interface (ddcp-script)
-                        
+                         not loose characters when copied/pasted at high speed.
+                         Line editing with backspace if terminal supports it.
+                         Set BOD (brown out detector enable) fuse.
+                         Script interface (ddcp-script)
+digitaldcpower-0.6.4 -- 2010-07-11 added ddcp-script interface 
+                         commands for windows.
+digitaldcpower-0.6.5 -- 2012-04-14 There was a fault in the range setting
+                         for the PWM (ICR1L in dac.c). Thanks to Weitao Li (james)
+                         for reporting this. This fault reduced the precision
+                         a bit.
+                     -- 2012-04-14 some minor improvemnents in main.c and analog.c to 
+                        regulate the voltage drop over the current measuremtns shunts 
+                        faster.
+
+digitaldcpower-0.6.6 -- 2012-07-17 Adapt the code to compile clean with the latest
+                        avr-libc (http://www.nongnu.org/avr-libc/changes-1.8.html)
+                        prog_char is now depricated.

 -------------------------------------------------------------------
 -------------------------------------------------------------------

+ vim: set sw=8 ts=8 si et :

 </pre>
 </pre>