[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Value of I2C_TRANSACTION_QUEUE_LEN

From: Felix Ruess
Subject: Re: [Paparazzi-devel] Value of I2C_TRANSACTION_QUEUE_LEN
Date: Sat, 8 Jan 2011 22:42:25 +0100

Hi Thomas,

I added a ifndef around the definition so now you can define it in your airframe file, e.g.
  <firmware name="rotorcraft">
<target name="ap" board="booz_1.0"/>
<define name="I2C_TRANSACTION_QUEUE_LEN" value="10"/>
Like you said we should probably set stuff like this (i2c timing and queue length) according to the number of defined mkk motors automatically...
Patches or pull requests are always welcome ;-)

Cheers, Felix

On Thu, Jan 6, 2011 at 3:35 PM, Thomas Wuensche <address@hidden> wrote:
Hi all,

In sw/airborne/mcu_periph/i2c.h I2C_TRANSACTION_QUEUE_LEN is set
to 8. With my octorotor I find that the last motor is not driven
with this setting, but works if I increase it to 10.

Based on the code I think that value has to be at least one slot
bigger than the number of simultaneously scheduled I2C commands.

Should we have that value configurable in the airframe definition?
Should we have some plausibility checks against number of motors?

Regards, Thomas
EMS Dr. Thomas Wuensche e.K.
Sonnenhang 3
85304 Ilmmuenster
HRA Neuburg a.d. Donau, HR-Nr. 70.106
Phone: +49-8441-490260
Fax  : +49-8441-81860

Paparazzi-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]