added skeleton test routines w/ expected return values and parameters to interface HAL and API layers
added test routines for DUT methods
dummy implementation to HAL/API interface routines
*very* early API call implementation with HAL interaction and loop expansion for distinguishing between pixel/roc/module HAL calls
moves issue #3 forward
added wiki link to README
dummy routines return data now
fleshed out expandloop routine; to be tested
used parameter to simulate dac range
renamed debug routine accordingly to avoid highjacking of methods
further implementation of the api routines; work in progress: compiles but does not yet work as intended.
Move DUT implementation in its own file.
Merge branch 'master' of github.com:psi46/pxar

Conflicts:
	core/api/api.cc
Re-add lost function from moving DUT into its own implementation file and merging upstream.
DUT: use status() function to check availability instead of the _initialized flag.
API CHANGE: "flags" parameter for test functions now defaults to 0. Makes the calls in most cases shorter.
Adding dacConfig struct to allow storage of ID, MIN, MAX values for range checks.
API CHANGE: new parameters for API constructor, default to * (any USB ID for attached board) and logging level "WARNING"
API CHANGE: only allow 16bit flags for API calls. This allows us to use the upper 16bit for internal flags to be passed to the HAL functions.
Add logging mechanism. Allows to start API with different log levels:
	QUIET / SUMMARY: only give necessary information or shut up completely
	ERROR / WARNING / INFO: give the respective information.
	DEBUG / DEBUGAPI / DEBUGHAL / DEBUGRPC / DEBUGUSB: give detailed debug output
                for the mentioned library parts, including all levels above.
The logging mechanism is the same as used in CMSPixelDecoder and a more detailed docu
can be found here: https://github.com/simonspa/CMSPixelDecoder/blob/master/README.md
Also log function name and line number in API