Re: [Paparazzi-devel] Xbee 868 uplink

[Jeremy MICHEL]

I had the problem of the 10% duty cycle which stops the transmission 
after 5,40 minutes at 57600bps.
I solved that by resetting the Xbee every 5 minutes before the problem 
appears. And it work very well.
I have connected the Xbee reset pin to the Tiny P0.14 pin with some 
modification in the main_ap.c in order to control this pin periodically.
I lost only 18ms of transmission every 5 minutes…


I tried to reduce the amount of data sent using the minimal.xml file but 
it had no effect.
The Xbee bandwidth isn’t fully used by the telemetry (Data every 100ms).

Next step : try to reduce the bandwidth but let me doubt about this.

Jeremy


Gareth Roberts a écrit :
> I bought one, but the device is apparently designed for burst, not 
> streaming. It only has a 10% duty cycle, so after about 5 min it just 
> stops working for me. I switched back to 2.4ghzs until I work around it...
>
> ----- Original message -----
>
> There is an example of such low-bandwidth telemetry file available in
>
> telemetry/minimal.xml
>
> --Pascal
>
> Gautier Hattenberger wrote:
>
> > Hi,
>
> > The bandwidth of a 868MHz modem is much smaller than the one of a
>
> > 2.4GHz. If you use the same telemetry file, the result can be an
>
> > overloading of the downlink that will prevent the uplink to work very
>
> > well. Removing some of the messages or at least increasing their
>
> > sending period could solve your problem. I should be able to test this
>
> > new modem next week I hope.
>
> >
>
> > Gautier
>
> >
>
> > Jeremy MICHEL a écrit :
>
> >> Hello,
>
> >>
>
> >> I am trying to use the new Xbee pro 868 MHz.
>
> >> Downlink works well however I couldn't get the Uplink working reliably.
>
> >> Sometimes I succeed in live changing aircraft's settings by multiple
>
> >> fast double-clicks... Not user friendly...
>
> >>
>
> >> Datalink is configured in transparent mode which worked well with
>
> >> Aerocomm modems.
>
> >>
>
> >> The code I used in "my_airframe".xml in order to configure the 
> datalink:
>
> >> ...
>
> >> <section name="DATALINK" prefix="DATALINK_">
>
> >>    <define name="DEVICE_TYPE" value="PPRZ"/>
>
> >>    <define name="DEVICE_ADDRESS" value="...."/>
>
> >> </section>
>
> >> ...
>
> >> ...
>
> >> ap.CFLAGS += -DDOWNLINK -DUSE_UART0
>
> >> -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart0
>
> >> -DDOWNLINK_AP_DEVICE=Uart0 -DPPRZ_UART=Uart0 -DDATALINK=PPRZ
>
> >> -DUART0_BAUD=B57600
>
> >> ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c
>
> >> ...
>
> >>
>
> >> Any help is welcome,
>
> >>
>
> >> Jeremy
>
> >>
>
> >>
>
> >>
>
> >> _______________________________________________
>
> >> Paparazzi-devel mailing list
>
> >> address@hidden <mailto:address@hidden>
>
> >> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
> >
>
> >
>
> > _______________________________________________
>
> > Paparazzi-devel mailing list
>
> > address@hidden <mailto:address@hidden>
>
> > http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
> _______________________________________________
>
> Paparazzi-devel mailing list
>
> address@hidden <mailto:address@hidden>
>
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>