Re: [Paparazzi-devel] digi 868 modem

Hi,

When using an example airframe file and default telemetry for fixedwing, one would get the NAVIGATION message from two sources, which would load the downlink more than necessary.

To avoid confusion for new users I suggest it would be sensible to have <define name="PERIOD_NAVIGATION_0" /> in the example airframe files, to suppress the message that comes from main_ap.c, line 462.

Thanks,

Helge.

2013/7/31 Refik Sever <address@hidden>

Hello,

We have added <define name="PERIOD_NAVIGATION_0" /> to the airframe file and now it can send continuously for hours.

We may update the wiki:

XBee Pro 868 MHZ

Getting Them Working

Even with the xbee868.xml telemetry file, XBee868s will not last over 6 minutes. There is a special 868 build flag (in slayer1.xml), and matching option for the datalink but I could not get this to work. Eventually, I got them to work for about 20 minutes, which happily is the flight endurance of a heavily overloaded GWS Formosa.

Best regards,
Refik

>
>

From: Refik Sever

Subject: Re: [Paparazzi-devel] digi 868 modem

Date: Sun, 28 Jul 2013 18:34:06 +0000
>Dear all,
>
>We decreased the power of 868 modem to 25mw, and now it does not block our 433MHz RC receiver.
>
>I decreased all the telemetry messages to overcome the 10% duty cycle constraint. Although I decreased >the Navigation message period to 24sec, it comes continuously with a period of around 1 sec. Therefore, >the xbee 868 modem stops sending data at 12:50.
>
How can I decrease the Navigation message rate? In navigation.c file, I saw that there are two commands:

Line 314:
DOWNLINK_SEND_WP_MOVED_ENU(DefaultChannel, DefaultDevice, &wp_id, &(new_pos->x), &(new_pos->y), &(new_pos->z));

Line 335:
RunOnceEvery(10,DOWNLINK_SEND_WP_MOVED_ENU(DefaultChannel, DefaultDevice, &wp, &(waypoints[wp].x), &(waypoints[wp].y), &(waypoints[wp].z)));

Do I need to change something here?

I am sending my telemetry file below.

Best regards,
Refik

<?xml version="1.0"?>
<!DOCTYPE telemetry SYSTEM "telemetry.dtd">
<telemetry>
<process name="Ap">
    <mode name="default">
      <message name="AIRSPEED"            period="24."/>
      <message name="ALIVE"               period="16."/>
      <message name="GPS"                 period="16."/>
      <message name="NAVIGATION"          period="24."/>
      <message name="ATTITUDE"            period="24."/>
      <message name="ESTIMATOR"           period="24."/>
    
      <message name="WP_MOVED"            period="24."/>

      <message name="CIRCLE"              period="24."/>
      <message name="DESIRED"             period="24."/>
      <message name="BAT"                 period="24."/>


      <message name="SEGMENT"             period="24."/>
      <message name="CALIBRATION"         period="16."/>
      <message name="NAVIGATION_REF"      period="16."/>
      <message name="PPRZ_MODE"           period="24."/>
      <message name="SETTINGS"            period="16."/>
   

     <message name="DOWNLINK"            period="16."/>

    <message name="DL_VALUE"            period="24."/>
    
      <message name="SURVEY"              period="24."/>
      <message name="GPS_SOL"             period="16."/>
    

    </mode>

>

>Re: [Paparazzi-devel] digi 868 modem

From: Refik Sever

Subject: Re: [Paparazzi-devel] digi 868 modem

Date: Thu, 25 Jul 2013 22:48:28 +0000
>Hello,
>
When we use 868.xml file, then the buttons in the GCS are not activated and also the settings tab is absent. When we choose default_imu_9k6.xml file, everything is OK. We are using paparazzi version: v4.9_devel-812-g8f341f0-dirty.

Do we forget something?

Best regards,
Refik

From: Refik Sever

Subject: [Paparazzi-devel] digi 868 modem

Date: Thu, 25 Jul 2013 22:41:39 +0000
>Dear all,
>
We get digi 868 oem modems. Today, we tried them for the first time. Our RC 
transmitter is at 433MHz. After take-off, we couln't use RC transmitter. The 
power of 868 modem was 100mW. 

It also corrupted our ublox GPS module. When we pushed the launch and take-off 
buttons, take-off is written in the GCS. At that moment, GPS gave a pos. acc. 
of 3.6m. However, the autopilot did not give any throttle in auto2. We removed 
the modem, and connected serial cable, then it gave throttle. In some tests, it 
also immediately jumped from takeoff to standby, although we did not take off. 

1. I think that 100mW power was too large. What power level do you recommend 
for communicating within 5km range?
2. Do you recommend to use a filter for RC_receiver and modem? Do I need to 
change RC frequency to 2.4GHz?
3. Do you think that the take off problem was due to GPS error or EMI-EMC 
problem at the autopilot?
4. Is there a tool which calculates the duty cycle of modem depending on the 
telemetry xml file?

>Best regards,
>Refik
>
>
_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

From:	Helge Walle
Subject:	Re: [Paparazzi-devel] digi 868 modem
Date:	Wed, 31 Jul 2013 19:25:12 +0200

From:	Refik Sever
Subject:	Re: [Paparazzi-devel] digi 868 modem
Date:	Sun, 28 Jul 2013 18:34:06 +0000