Re: [Paparazzi-devel] Eagle Tree airspeed sensor startup testers needed

[Eduardo lavratti]

this is exctly the same behavior i have with original code.

> Date: Fri, 5 Oct 2012 14:31:44 -0600
> From: address@hidden
> To: address@hidden
> Subject: Re: [Paparazzi-devel] Eagle Tree airspeed sensor startup testers needed
>
> Hello,
>
> I tried this out, and it was only working after a luftboot upload, not
> after a regular bootup sequence. It was on a Lisa/M v2.0, nothing else
> connected but UART2, on the Bixler example airframe, with the sensor
> connected to I2C2. When it was working, it wasn't overly reliable,
> with a considerable number of NACKed bytes in the transactions. The
> same results occurred with a delay of 2sec or 8sec.
>
> Perhaps someone else could also test?
>
> I also tried the ETS sensor in master, and that worked much better,
> but there was still a 10-20% transaction failure rate (NACKed bytes).
>
> Thanks,
> -Stephen Dwyer
>
> P.S. I used the following in the airframe file:
> In Firmware section:
>
> <define name="USE_I2C2"/>
>
> In Modules:
> <modules>
> <load name="sys_mon.xml"/>
> <load name="airspeed_ets.xml">
> <define name="AIRSPEED_ETS_START_DELAY" value="2"/>
> <define name="AIRSPEED_ETS_I2C_DEV" value="i2c2"/>
> <define name="SENSOR_SYNC_SEND"/>
> </load>
> </modules>
>
>
> On Fri, Oct 5, 2012 at 11:50 AM, Felix Ruess <address@hidden> wrote:
> > Hi,
> >
> > could someone with this sensor please test the airspeed_ets_delay branch in
> > my github repo?
> >
> > E.g. for a delay of 2 seconds:
> > <modules>
> > <load name="airspeed_ets.xml"/>
> > <define name="AIRSPEED_ETS_START_DELAY" value="2"/>
> > </load>
> > </modules>
> >
> > Cheers, Felix
> >
> > On Fri, Sep 21, 2012 at 2:37 PM, Eduardo lavratti <address@hidden>
> > wrote:
> >>
> >> Felix, i dont put this code on me gitr because my code is ridiculous.
> >> i am tried the same code used on actuator delay but it not worked then i
> >> do a for next loop inside airspeed_ets driver initialization.
> >>
> >> ________________________________
> >> Date: Thu, 20 Sep 2012 12:57:28 +0200
> >> From: address@hidden
> >>
> >> To: address@hidden
> >> Subject: Re: [Paparazzi-devel] Test flight results (Lisa/M, ETS,
> >> Pitch-loop, GPS)
> >>
> >> Hi Eduardo,
> >>
> >> it would be great if you could make a pull request with that!
> >>
> >> Cheers, Felix
> >>
> >> On Thu, Sep 20, 2012 at 12:51 PM, Eduardo lavratti <address@hidden>
> >> wrote:
> >>
> >> Some time ago my AirSpeed ETS only show constant values and i put a delay
> >> in start sequence then this problem are solved.
> >>
> >>
> >> > Date: Thu, 20 Sep 2012 09:50:45 +0100
> >> > From: address@hidden
> >> > To: address@hidden
> >> > Subject: Re: [Paparazzi-devel] Test flight results (Lisa/M, ETS,
> >> > Pitch-loop, GPS)
> >>
> >> >
> >> > On 19/09/12 23:00, Marc Schwarzbach wrote:
> >> > > Hi Tilman,
> >> > >
> >> > > the only difference seems to be the I2C Port..
> >> > > Can you quickly change to port 2 for a test?
> >> > Doh! Sorry, I just had a facepalm moment.
> >> >
> >> > I thought the port numbers where 0 indexed. I had it on I2C2 actually.
> >> >
> >> > What a fail. Sorry to bother you.
> >> > >
> >> > > Regarding going through luftboot just to check, my timing is: Attach
> >> > > programming wire, power on (luftbook blink sequence running), load firmwire,
> >> > > while that is happening unplug programming wire, system is running...
> >> > >
> >> > > Power off, power on, ETS shows static value...
> >> > >
> >> > > Another thing Felix told me to try some days ago was to insert an
> >> > > initialisation delay to the ETS code like already implemented in the mkk
> >> > > controllers (sw/airborne/firmwares/rotorcraft/actuators/actuators_mkk.c),
> >> > > since the problem looked similar. I will not be able to test in the next
> >> > > time, prbably you can?
> >> > Probably.
> >> >
> >> > _______________________________________________
> >> > Paparazzi-devel mailing list
> >> > address@hidden
> >> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> >>
> >> _______________________________________________
> >> Paparazzi-devel mailing list
> >> address@hidden
> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> >>
> >>
> >>
> >> _______________________________________________ Paparazzi-devel mailing
> >> list address@hidden
> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> >>
> >> _______________________________________________
> >> Paparazzi-devel mailing list
> >> address@hidden
> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> >>
> >
> >
> > _______________________________________________
> > Paparazzi-devel mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> >
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel