Skip to content

GitLab

Commit b4c323cb authored by thomas.forbriger's avatar thomas.forbriger Committed by thomas.forbriger
Browse files

base any2matlab revision on repository revision of 2010-07-17 

This is a legacy commit from before 2015-03-01.
It may be incomplete as well as inconsistent.
See COPYING.legacy and README.history for details.
this is the date when libraries were created and suppied to Daniel


SVN Path:     http://gpitrsvn.gpi.uni-karlsruhe.de/repos/TFSoftware/branches/any2matlab0.1
SVN Revision: 3103
SVN UUID:     67feda4a-a26e-11df-9d6e-31afc202ad0c
parents 852fac51 a768864f
Expand all Hide whitespace changes
Inline Side-by-side
src/COPYING.legacy 0 → 100644
View file @ b4c323cb
This is a legacy version of the repository. It may be incomplete as well as
inconsistent. See README.history for details. For the old stock of the
repository copyright and licence conditions apply as specified for versions
commited after 2015-03-01. Use recent versions as a base for new development.
The legacy version is only stored to keep a record of history.
src/GPLphrase 0 → 100644
View file @ b4c323cb
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
src/LICENSE.GPL 0 → 100644
View file @ b4c323cb
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
src/README.1st 0 → 100644
View file @ b4c323cb
this is <README.1st>
============================================================================
General guide for published packages
------------------------------------
$Id: README.1st,v 1.2 2007-11-23 09:15:27 tforb Exp $
============================================================================
The packages you obtain from my site are not full-featured, coming with
configure scripts or similar tools to support installation. The packages are
snapshots from my CVS repository. They are snapshots of the code I'm currently
using myself. Please feel free to use this code and compile the programs and
libraries. But you have to do it yourself. I will give you some guidance and
please feel free to get into contact with me if you have additional questions.
Apart from this file you usually will find the following in the packages:
Makefile: The Makefile conatains all rules you need to compile the code.
Information about the purpose of the package, special
coniderations during installation and dependencies to other
packages are placed in the preamble of the Makefile.
README.compile:
This text is the same for all packages (published at the same
date). Here you find general information about utilities and
environment settings that are usually expected by the Makefile.
In some packages you may find a README. In most cases this is not a general
information about installing and using this package (please have a look at
Makefile for this). In particular in C++ library packages the README file is
part of the doxygen documentation.
If you experience any problem, please contact me:
--
| Dr. Thomas Forbriger e-mail: Thomas.Forbriger@gpi.uni-karlsruhe.de |
| Observatorium Schiltach (BFO), Heubach 206, D-77709 Wolfach, Germany, |
| Tel.: ++49 (0)7836/2151, Fax.: ++49 (0)7836/7650 |
| http://www-gpi.physik.uni-karlsruhe.de/pub/forbriger |
----- END OF README.1st -----
src/README.compile 0 → 100644
View file @ b4c323cb
this is <README.compile>
============================================================================
How to compile the source code
------------------------------
$Id: README.compile,v 1.13 2010-07-16 09:10:53 tforb Exp $
============================================================================
Here you will find some notes to help you in the process of compiling software
provided by me (Thomas Forbriger). My programs usually make use of several
different software libraries.
With the beginning of 2006 I provide software packages (main code) separately
from the libraries, which makes life easier for me (but harder for you).
Please read the notes below to compensate for that.
From November 2007 on, I will port my programs to a 64-bit Linux system. Until
this is finished, you may find some of the packages in a transitional stage.
See also specific notes on Fortran code below (section Compilers).
Make
----
In many cases you will need gmake (GNU make) to use the provided Makefiles.
Environment variables in Makefiles
----------------------------------
The bevahiour of the Makefiles is controlled by environment variables. It is
most suitable to set their values in $HOME/.profile or $HOME/.bashrc
Here I give a description of these variables together with their typical
values:
export LOCBINDIR=$HOME/bin
Compiled and linked binaries will be copied to this directory. If you
include this directory in the setting of your PATH variable, you will have
easy access to the binary from any working directory.
export LOCLIBDIR=$HOME/lib
Libraries will be copied to this directory. An Makefiles will pass this
directory to the linker in order to link against these libraries.
export LOCINCLUDEDIR=$HOME/include
Links to header files will be installed in this directory. The Makefiles
pass this directory to the preprocessor to look for header files.
SERVERLIBDIR
If libraries that are needed by this code (like PGPLOT) are installed in
an uncommon system directory, you can use this variable to pass the
location to the linker.
SERVERINCLUDEDIR
If header files that are needed by this code (like cpgplot.h) are installed
in an uncommon system directory, you can use this variable to pass the
location to the linker.
LD_LIBRARY_PATH
If you install external libraries (e.g. PGPLOT) in an uncommon place, you
might have to set LD_LIBRARY_PATH to pass the location of the dynamic
library (e.g. libpgplot.so) to the dynamic linker.
export WWWBASEDIR=$HOME/doxydoc
C++ libraries usually are distributed together with a set of documentation
files that are automatically created by doxygen from the source code. The
resulting HTML files or man-pages wil be installed in this place by the
Makefile. The Makefiles create subdiretories to distinguish between
different packages.
export TF_BROWSER=firefox
The Makefile support the display of doxygen documentation with your html
browser. Use this variable to pass the name of the browser to the
Makefile.
export TF_LIBREGEXX=yes
If this variable is set, the Makefiles will expect libregexx to be
installed. Since libregexx is discontinued since several years and does
not easily compile on 64-bit systems, my code will be ported to use the
regular expression module in the boost library. This will be the default
in the future. If you do not have the boost library installed, but
libregexx, you should use this variable.
This feature may disappear somewhere in the future.
export TF_LINK_REGEXX=-lregexx
Defines the linker option to link against regexx functionality. This can
either be libregexx or libboost_regex. This variable and TF_LIBREGEXX must
be set coherently.
export TF_FALLBACK=yes
During porting of the software to 64-bit systems, the default method of
compiling Fortran code will be changed from f2c and gcc to g77. After this
transition some Makefiles might no longer support f2c at all. At least the
convetion for library file name will change. Until the porting procedure
is finished for all packages, this variable can be used to use the old
rules (f2c is default) as a fallback solution. Since filenames will be
different in this solution you should use different settings for LOCBINDIR
and LOCLIBDIR too, when using the fallback setting.
export TF_LINK_FORTRAN=-lgfortran
Define the linker option when doing interlanguage linking (i.e. link a C++
main program against Fortran code from a library). Is you use g77, you
will have to link against libg2c.a here.
export TF_LINK_PGPLOT=-lpng -lX11 -L/usr/X11/lib64
This variable is passed to the linker in cases where binaries have to be
linked against PGPLOT. Use this variable to pass the location of your X11
libraries as well as the names of additional libraries that might be
needed for the PGPLOT drivers in your installation (like libpng.a in this
example).
export TF_f2c_PGPLOT=f2cpgplot
Use this variable to pass the name of the PGPLOT library that was compiled
with f2c and gcc (libf2cpgplot.a in this example).
export TF_g77_PGPLOT=pgplot
Use this variable to pass the name of the PGPLOT library that was compiled
with gfortran (or g77, see below) (libpgplot.a or libpgplot.so in this
example).
The following variables will be used in Makefiles:
CXX name of C++ compiler command
CC name of C compiler command
FC name of Fortran compiler command
CPP name of C preprocessor command
To the following variables local values may be appended in Makefiles:
FLAGS general flags (will be appended to other flag variables)
CFLAGS flags to C compiler
FFLAGS flags to Fortran compiler
CPPFLAGS flags to preprocessor
CXXFLAGS flags to C++ compiler
LDFLAGS flags to linker
Libraries
---------
The library packages depend on each other. If you start compiling from
scratch, you should install them in the following order:
libaff: base library, depends only on common system libraries
libtime: base library, depends only on common system libraries and
tfmacros.h (but includes tfmacros.h in the package)
libtfxx: base library, depends only on common system libraries and
STL (standard template library)
libgsexx: base library, depends only on common system libraries
libsffxx: depends on libgsexx, libaff, and libtime
libdatreadxx: depends on libaff, libtfxx, libgsexx, libtime, libsffxx
tfmacros.h
----------
The file tfmacros.h is available in package thofdevel########.tar.gz.
It is used by several packages. Download and unpack this package and call
/bin/cp -vpd tfmacros.h $LOCINCLUDEDIR
Comments in header files
------------------------
Some Makefiles contain rules to strip comments from C++ and C header files.
They use the program remcmmnt by Jari Laaksonen (see below). If this is not
available to you, look for the variable REMCMMNT and set it to
REMCMMNT=cat
Compilers
---------
With the transition to 64-bit systems, the default method to compile Fortran
files will be gfortran (Fortran compiler in the GNU compiler collection).
Most code will still compile with g77 if used consistently for all libraries
too. Please use the FC environment variable to select your preferred Fortran
cpmpiler. Notice that most code must be compiled with the -ff2c option set,
to ensure proper interlanguage linking.
Since I experience problems with return values from libf2c-functions on
64-bit systems (see below), the support for f2c may be discontinued entirely
in the future. Some libraries that provide features for inter-language
linking (like libtime.a) may still require f2c to create a C-version of the
Fortran source code.
Fortran code traditionally was compiled by f2c (netlib, see below) and gcc
(GNU C compiler). For packages not yet ported to 64-bit, you may use the
TF_FALLBACK environment variable to use the f2c rules in Makefiles (see
above).
Other Fortran compilers are not guaranteed to work properly with code
provided here.
C and C++ code usually is prepared to compile with the GNU C and C++
compiler.
I will not support the creation of 32-bit binaries on 64-bit platforms
(which would be possible by using the -m32 option).
f2c
---
The standard integer type for f2c compilation is "long int". The f2c-version
I obtained together with openSuSE 10.2 provides a f2c.h that defines the
Fortran integer type to be simple "int". That is reasonable since this keeps
integer variables 4 byte long, which is necessary to keep binary i/o
compatible for data files written on 32bit systems. However, the libf2c.a
that is provided with this package apparently is compiled with integer being
long int (8 byte on 64bit systems). Since f2c originally was designed to use
long int integer types, it is very likely that this confusion may reappear
elsewhere on 64bit systems, when using f2c. Since Fortran is supported by
the GNU compiler collection I no longer see a reason to support f2c
compilation.
Shell scripts
-------------
Some make rules may still contain calls to shell scripts called newprog or
newlib. A rule
newprog $@
can safely replaced by
/bin/cp -vp $@ $(LOCBINDIR)
Replace
newlib $@
by
/bin/cp -vp $@ $(LOCLIBDIR)
Calls to newinclude, incdep or others are replaced as easily. Look for
package thofdevel########.tar.gz, which contains those tools. You will find
a copy of remcmmnt there too.
The shell-script setsandbox is used to set the environment variable (see
above) to independent values, when preparing a package. You will not need
this shell-script, since you will not use the make rules for package
creation.
Fortran plot programs
---------------------
Plot programs usually link against PGPLOT (see below).
References
----------
doxygen: www.doxygen.org
PGPLOT: www.astro.caltech.edu/~tjp/pgplot/
remcmmnt: Jari Laaksonen, http://cpp.snippets.org/ C++ collection
A copy is placed in thofdevel########.tar.gz
f2c: Netlib, http://www.netlib.org/f2c/
If you experience any problem, when compiling the code, please contact me:
--
| Dr. Thomas Forbriger e-mail: Thomas.Forbriger@gpi.uni-karlsruhe.de |
| Observatorium Schiltach (BFO), Heubach 206, D-77709 Wolfach, Germany, |
| Tel.: ++49 (0)7836/2151, Fax.: ++49 (0)7836/7650 |
| http://www-gpi.physik.uni-karlsruhe.de/pub/forbriger |
----- END OF README.compile -----
src/conv/COPYING.legacy 0 → 100644
View file @ b4c323cb
This is a legacy version of the repository. It may be incomplete as well as
inconsistent. See README.history for details. For the old stock of the
repository copyright and licence conditions apply as specified for versions
commited after 2015-03-01. Use recent versions as a base for new development.
The legacy version is only stored to keep a record of history.
src/conv/ThiesDL1/COPYING.legacy 0 → 100644
View file @ b4c323cb
This is a legacy version of the repository. It may be incomplete as well as
inconsistent. See README.history for details. For the old stock of the
repository copyright and licence conditions apply as specified for versions
commited after 2015-03-01. Use recent versions as a base for new development.
The legacy version is only stored to keep a record of history.
src/conv/ThiesDL1/DL1direct.cc 0 → 100644
View file @ b4c323cb
/*! \file DL1direct.cc
* \brief directly send command to DL1 and receive the response
*
* ----------------------------------------------------------------------------
*
* $Id: DL1direct.cc,v 1.8 2009-01-16 22:30:38 tforb Exp $
* \author Thomas Forbriger
* \date 24/11/2008
*
* directly send command to DL1 and receive the response
*
* Copyright (c) 2008 by Thomas Forbriger (BFO Schiltach)
*
* ----
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by