currently the booz board isn't mounted into the airframe. I wanted to get the avionics working completely before mounting it, so currently I can't start the Motors. I wanted to start the investigation by taking something, that was working before. So I took old repository for my Funjet and tried it with the old one. I attached the airframe file. I just changed some things needed to get it compiled (attitude->ahrs and ublox_lea5h->ublox). Everything else was the same. In the old version I get (in this case) the BARO_ETS Messagge and the I2C works, in the new one not.
This morning I also tried something else: I took a plane containing a Tiny13 and ppzuav IMU (also I2C) and it was working -> so I'm suspecting it to be my fault in the configuration somewhere, but I don't know where.
Can you start the motors ? Can you send your airframe file (or use
pastebin or alike) so we can see the what is your exact
configuration. Thanks
Gautier
On 16/07/2012 23:23, Christoph Niemann wrote:
Dear Community,
some weeks ago, I wrote a mail about my problem, using the old
booz IMU with the HMC5843 or HMC5883L with the lpc based booz ap.
Investigating this further, I found that for me, using the pretty
current 3.9 branch (v3.9.2_testing-3-g38ebd01-dirty), the I2C for
LPC doesn't seem to work at all.
I tried both the hmc5843 and hmc5883l on the booz board. It didn't
work. Next I tried those boards using a TWOG, it did't work. I
suspected there is an issue with the hmc driver, so I tried an ETS
Baro, it didn't work either. So I tried the code from about a year
ago (95a65a7-dirty). The baro was working.
What could be the Problem? I used a logic anaylzer, to investigate
it further. in the working version, there was data going through
the bus. In the new version both lines where high.
Every help would be appreciated.