boscha

I also had problems with brickv crashing on my MacBook (MacOS X v.10.8.2; brickv/brickd from the .dmg files - no GIT ). Also for me 1.1.17 works without problems. Just FYI.

Ah, thanks. I thought about trying the 2.0 beta, but I didn't expect it to be the master of the regular trunk (I used the GIT code in combination with the .deb of brickd). I have looked for version information in the code and only found the API version information in imu_create, which was set to 1.0.1 (afterwards I was just assuming that it would be related to the version of brickd/brickv). Same version information is also in the "old" code that you pointed me to, maybe it would be nice to have some kind of "general" version match/check/information. Thanks for the fast help, now it works like a charm, Boris

First of all, hello everybody! I am new to this board and hope my question hasn't been asked a hundred times already (I did search). I have a problem with a newly arrived IMU brick. Simply: Brickv shows the data, but if I try to use the C example, I don't get any data. More specifically, after turning on the return codes (imu_set_response_expected_all), I seem to know that I get timeouts. Any ideas what could be wrong? (I already flashed a new firmware, etc.) Bests Boris Code: // Enable debugging, i.e. turn on return codes imu_set_response_expected_all(&imu, true); // Set period for quaternion callback to 1s ret = imu_set_quaternion_period(&imu, 10); if (ret != E_OK) { fprintf(stderr,"Error: imu_set_quaternion_period (%d)\n",ret); exit(ret); } Returns: Error: imu_set_quaternion_period (-1)