Hi,
I have sucesfully managed to compile the DrDaq Linux driver and can run the ddtest program. When I select option C to write continous data I get entries such as this:
I have been able to determine that the 3rd column is Sound and the 6th is Light as these values change when I make some noise or cover the light sensor. However, these values seem to be meaningless in their current form either as ADC counts or as scaled values.
Is there anyway to convert these to degrees C, dB, etc? Could you also tell which channel is connected to which sensor, as they don't seem to correspond with what is written in the DrDaq user manual (e.g. it says that light is channel)
Ultimatly I want to write my own C program to log sensor values into a database and possibly make the sensor readings available on the network.
Please can somebody help me? I've been pouring over the source code for a couple of days now and I still cant figure out how to get the driver to return meaningful values for the sensors.
E.g. According to the user manual the light sensors is supposed to return values between 0 and 100, but I'm getting values anywhere between -60 and 700 when ddtest is set to return measurement values and im getting values between 500 and 3000 when ddtest is set to return adc counts.
I have now finally managed to convert the ADC count readings for light, sound and temperature into real meaningful values by examaning the methods from drdaqscl.c and rewritting them into my own program.
I have written a simple C program that flashes the LED and then takes 40 readings once a second from the sensors. I have made this code available at http://www.uk-dave.com/files/drdaq.c for anyone else who has been struggeling like me.
Unfortunately we no longer actively support Linux. We have some old Linux drivers and files which can be used and we still supply these but we are unable to support them, update them or write new ones.
Unfortunately we are unable to help with Linux enquiries. The examples we provide were written on RedHat (version 6 I believe) but this is all I know I'm afraid. The person who wrote them is no longer with the company so we are unable to update them or provide support for them.