I just read that the Data logger demo must be treated as beta-q ok. Another of their bugs:
At low frequencies (< 1 Hz) doesn't work properly. LED blinks as expected but empty .csv files are created after ending the recording. It happens with short (few minutes) and long (several hours) times. In my case I checked this with the environmental and luminosity sensors working together. It's not a problem of the flashing because increasing the frequencies values in the logger the .csv of the new records are created properly.
0 (0 Stimmen)
Data logger fail to cretae files at low recording frequency
Antwort
24.09.15 22:21 als Antwort auf Jorge Mir Bel.
Hi Jorgemirbel,

welcome to the XDK community and thanks for your question.

Unfortunately I don't quite get what you are trying to ask. 
Could you might try to describe your problem again and maybe in greater detail?

Thanks,
Florian
0 (0 Stimmen)
Data logger fail to cretae files at low recording frequency
Antwort
28.09.15 07:37 als Antwort auf Florian Harr.
Ok.
The problem appears by changing the logger file.
If the frequencies of recording is set in that file to a rate lower than 1 Hz the .csv files are created with no data.

 
0 (0 Stimmen)
Data logger fail to cretae files at low recording frequency
Antwort
11.12.15 13:03 als Antwort auf Jorge Mir Bel.
I have seen the same behaviour with my xdk.
At 1 Hz, the logging still works but if you go low, say to 0.1 Hz, the csv file on the SD card will be empty.
0 (0 Stimmen)
Data logger fail to cretae files at low recording frequency
Antwort
12.12.15 12:48 als Antwort auf Niclas Mueller.
Hi Jorge and Niclas,

I saw the same results and I think I also found the reason for this behavior:

uint32_t bma280_enabled;
uint32_t bma280_sampling_rate_timer_ticks;
uint32_t bma280_range;
uint32_t bma280_bandwidth;
uint32_t bma280_sampling_rate_remaining_ticks;
uint32_t bma280_sampling_rate;

uint32_t bmg160_enabled;
uint32_t bmg160_sampling_rate_timer_ticks;
uint32_t bmg160_bandwidth;
uint32_t bmg160_sampling_rate_remaining_ticks;
uint32_t bmg160_sampling_rate;
...


The configuration values seem to be stored as integers.
You can also see that the timer ticks are set to 0 in the console output.
I will report this bug to the demo developers. Until then, you will have to stick with integer rates or fix the code yourself.

Kind regards,
Manuel
0 (0 Stimmen)