Re: [Paparazzi-devel] Trouble with digi 900Xtend

Type this into terminal to doublecheck what group the device belongs to.

ls -l /dev/ttyUSB*

Also you have set the RF mode of your transmitters to polling.

I would just set them as transparent.

To do that set the value of MD to 0.

regards

rijesh

On Sun, May 22, 2016 at 11:28 AM, Amir Ashrafizadeh <address@hidden> wrote:

Yes I get the same error. When I run paparazzi with sudo I dont get the error anymore but I still get a black screen. I have checked and my user is part if the plugdev group.
Any thoughts?

Sent from my iPhone
On May 22, 2016, at 1:13 PM, Rijesh Augustine <address@hidden> wrote:
The original error you were experiencing was due to not being able to access the modem.
Failure("Error opening modem serial device : fd < 0 (/dev/paparazzi/xbee)").

If you open paparazzi and set the session to flight usb serial 57600 do you still get an error?

rijesh

Are you
On May 22, 2016 10:51 AM, "Amir Ashrafizadeh" <address@hidden> wrote:
Hello Rijesh,
I have installed cutecom and when I connect everything I cant see any messages coming through.
Below is the result from dmesg | grep tty:
[ 3.367633] usb 1-7.1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 640.999741] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 654.401136] usb 1-7.1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 1964.658438] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 3109.174349] usb 1-7.2: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3115.571068] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 3119.914835] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0
[ 4598.582395] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 4601.181283] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0
[ 4764.726582] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 4766.942348] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0
[ 5315.973579] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 6784.882060] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0
[ 6830.494952] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 7511.153229] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0
[ 8495.194322] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 8516.175337] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0

Have you checked the settings of my modems in XCTU? did they seem wrong to you?
Once again thanks for your time and help.

Regards,
Amir
On Sun, May 22, 2016 at 2:46 AM, Rijesh Augustine <address@hidden> wrote:
Cutecom is a barebones serial monitor.
https://help.ubuntu.com/community/Cutecom

Maybe paste the output from dmesg? Did it verify that the serial port is /dev/ttyUSB0?

Open cutecom by typing in cutecom in the terminal. If it's not installed then you can do a quick Google search to see how you can install it for your specific os.

In cutecom try opening the serial port and see if there is any incoming data.

Rijesh.
Thank you for your response. What is cutecom? Like I mentioned in my initial email, I keep getting an error message so I know for a fact that the modem is not communicating properly. When I run dmesg I can see that the modem is connected.

Regards,
Amir
On May 22, 2016, at 2:25 AM, Rijesh Augustine <address@hidden> wrote:
Hi Amir.

I have never messed with the udev rules or made a symbolic link to serial telemetry modules. I don't think it should be necessary. It is necessary to add your user to the plugdev rules unless you want to run via sudo.

When you plug in the device are you sure you are getting the correct name.
You can check what the device's name is by monitoring the /dev folder before and after plugging in the device. You can also check by running dmesg in terminal right after you plug in the device and seeing what the last device is.

After making sure you know the device name I would try connecting with cutecom and see if you can read messages coming from the autopilot.

I have always used FLIGHT USB-serial @57600.

regards
rijesh
On Sun, May 22, 2016 at 12:14 AM, Amir Ashrafizadeh <address@hidden> wrote:
Can anyone help me get my modem working?

Thanks in advance.

Amir
On May 21, 2016, at 12:17 AM, Amir Ashrafizadeh <address@hidden> wrote:
Hi all,

I am trying to connect my digi 900Xtend to an apogee board and I keep getting the following error:

RUN '/home/amir/paparazzi/sw/ground_segment/tmtc/link -d /dev/paparazzi/xbee -transport xbee -s 57600'
RUN '/home/amir/paparazzi/sw/ground_segment/tmtc/server '
RUN '/home/amir/paparazzi/sw/ground_segment/cockpit/gcs '
Failure("Error opening modem serial device : fd < 0 (/dev/paparazzi/xbee)")
Read Socket : Connection reset by peer
Broadcasting on network 127.255.255.255, port 2010

FAILED '/home/amir/paparazzi/sw/ground_segment/tmtc/link' with code 1

Broadcasting on network 127.255.255.255, port 2010

DONE '/home/amir/paparazzi/sw/ground_segment/cockpit/gcs'

I found an old email from 2011 where Felix has recommended a few fixes for the issue and I have tried them all but they dont seem to work. I have tried the following things:
1- changed the command line for the data link to -d /dev/ttyUSB0 instead of -d /dev/paparazzi/xbee (which I think is the equivalent of FLIGHT USB-serial @57600 in the session drop down)
2- added my user to the dialout group
3- modified my dev rules (/etc/udev/rules.d/50-paparazzi.rules) which I have added below:

ACTION!="add|change", GOTO="paparazzi_rules_end"

# your own XBee ground modem with FTDI USB adapter (adapt serial number and uncomment line below)
#SUBSYSTEM=="tty", ATTRS{product}=="FT232R USB UART", ATTRS{serial}=="A80081ej", SYMLINK+="paparazzi/xbee", GROUP="plugdev", GOTO="tty_FTDI232_end"
SUBSYSTEM=="tty", ATTRS{product}=="TTL232R", ATTRS{serial}=="FTHAR3LK", SYMLINK+="paparazzi/xbee", GROUP="plugdev", GOTO="tty_FTDI232_end"

# FLOSS-JTAG serial cable
SUBSYSTEM=="tty", ATTRS{interface}=="FLOSS-JTAG", SYMLINK+="jtag%n"
SUBSYSTEM=="tty", ATTRS{interface}=="FLOSS-JTAG", ATTRS{bInterfaceNumber}=="01", SYMLINK+="jtag-serial"

# Black Magic Probe
SUBSYSTEM=="tty", ATTRS{interface}=="Black Magic GDB Server", SYMLINK+="bmp-gdb"
SUBSYSTEM=="tty", ATTRS{interface}=="Black Magic UART Port", SYMLINK+="bmp-serial"

# FTDI 3.3V serial cable
SUBSYSTEM=="tty", ATTRS{interface}=="TTL232R-3V3", SYMLINK+="ftdi-serial"

# other bare FT232R FTDI chip without EEPROM
SUBSYSTEM=="tty", ATTRS{product}=="FT232R USB UART", SYMLINK+="ftdi-serial", GROUP="plugdev"

# Paparazzi STM32 Autopilot board USB CDC serial device
SUBSYSTEM=="tty", ATTRS{manufacturer}=="Paparazzi UAV", ATTRS{product}=="CDC Serial STM32", SYMLINK+="paparazzi/stm32-usb-serial"

# MaxStream xbee pro box
SUBSYSTEM=="tty", ATTRS{product}=="MaxStream PKG-U", SYMLINK+="paparazzi/xbee", GROUP="plugdev"

# Navstik Xbee port
SUBSYSTEMS=="usb", ENV{.LOCAL_ifNum}="$attr{bInterfaceNumber}"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6011", ATTRS{product}=="Quad RS232-HS", ENV{.LOCAL_ifNum}=="02", SYMLINK+="paparazzi/xbee", GROUP="plugdev"

# Recent Digi XBee pro modems (XBP24-PKC-001-UA)
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{product}=="USB <-> Serial", SYMLINK+="paparazzi/xbee", GROUP="plugdev"

LABEL="tty_FTDI232_end"

SUBSYSTEM!="usb", GOTO="paparazzi_rules_end"
ENV{DEVTYPE}!="usb_device", GOTO="paparazzi_rules_end"

ATTR{product}=="Lisa/M *(Upgrade)*", GROUP="plugdev"

#SUBSYSTEMS=="usb", ATTRS{serial}=="*_fbw", NAME="test_fbw", SYMLINK+="paparazzi/%s{serial}", MODE="0666"

# FTDI 2232 parallel converter / Amontec JTAG-Tiny (access through libftdi)
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="cff8", GROUP="plugdev"

# FTDI 2232 based jtag for Lisa/L and usb upload
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="0666", GROUP="plugdev"

# FTDI 2232 based jtag for Navstik
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6011", MODE="0666", GROUP="plugdev"

# dfu devices
ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", MODE="0666", GROUP="plugdev"

# all (fake VID 0x7070) LPCUSB devices (access through libusb)
ATTRS{idVendor}=="7070", GROUP="plugdev"

# make joysticks/gamepads readable on event interface (writeable for force feedback), see input_event.sh
KERNEL=="event*", IMPORT{program}="input_event.sh %p", NAME="input/%k", GROUP="plugdev", MODE="0640" ENV{FF_DEVICE}=="1", MODE="0660"

# FTDI with uBlox direct on USB
ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a5", KERNEL=="ttyACM*", SYMLINK+="paparazzi/acm", GROUP="plugdev"

LABEL="paparazzi_rules_end"

and this is the result of
udevadm info --query=all --attribute-walk --name=/dev/ttyUSB0:

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/ttyUSB0/tty/ttyUSB0':
    KERNEL=="ttyUSB0"
    SUBSYSTEM=="tty"
    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/ttyUSB0':
    KERNELS=="ttyUSB0"
    SUBSYSTEMS=="usb-serial"
    DRIVERS=="ftdi_sio"
    ATTRS{latency_timer}=="1"
    ATTRS{port_number}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0':
    KERNELS=="1-3:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="ftdi_sio"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bInterfaceClass}=="ff"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bInterfaceProtocol}=="ff"
    ATTRS{bInterfaceSubClass}=="ff"
    ATTRS{bNumEndpoints}=="02"
    ATTRS{interface}=="TTL232R"
    ATTRS{supports_autosuspend}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1/1-3':
    KERNELS=="1-3"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{bMaxPower}=="90mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bcdDevice}=="0600"
    ATTRS{bmAttributes}=="80"
    ATTRS{busnum}=="1"
    ATTRS{configuration}==""
    ATTRS{devnum}=="9"
    ATTRS{devpath}=="3"
    ATTRS{idProduct}=="6001"
    ATTRS{idVendor}=="0403"
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="FTDI"
    ATTRS{maxchild}=="0"
    ATTRS{product}=="TTL232R"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="unknown"
    ATTRS{serial}=="FTHAR3LK"
    ATTRS{speed}=="12"
    ATTRS{urbnum}=="15"
    ATTRS{version}==" 2.00"

  looking at parent device '/devices/pci0000:00/0000:00:14.0/usb1':
    KERNELS=="usb1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{authorized_default}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="0mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bcdDevice}=="0402"
    ATTRS{bmAttributes}=="e0"
    ATTRS{busnum}=="1"
    ATTRS{configuration}==""
    ATTRS{devnum}=="1"
    ATTRS{devpath}=="0"
    ATTRS{idProduct}=="0002"
    ATTRS{idVendor}=="1d6b"
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="Linux 4.2.0-34-generic xhci-hcd"
    ATTRS{maxchild}=="16"
    ATTRS{product}=="xHCI Host Controller"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="unknown"
    ATTRS{serial}=="0000:00:14.0"
    ATTRS{speed}=="480"
    ATTRS{urbnum}=="90"
    ATTRS{version}==" 2.00"

  looking at parent device '/devices/pci0000:00/0000:00:14.0':
    KERNELS=="0000:00:14.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="xhci_hcd"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x0c0330"
    ATTRS{consistent_dma_mask_bits}=="64"
    ATTRS{d3cold_allowed}=="1"
    ATTRS{device}=="0xa12f"
    ATTRS{dma_mask_bits}=="64"
    ATTRS{driver_override}=="(null)"
    ATTRS{enable}=="1"
    ATTRS{irq}=="121"
    ATTRS{local_cpulist}=="0-7"
    ATTRS{local_cpus}=="ff"
    ATTRS{msi_bus}=="1"
    ATTRS{numa_node}=="-1"
    ATTRS{subsystem_device}=="0x8694"
I have also attached screenshots of my modem configurations in XCTU. 
Any help would be greatly appreciated.
Regards,
Amir
<Air Modem.jpg><Ground Station.jpg>
_______________________________________________
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

From:	Rijesh Augustine
Subject:	Re: [Paparazzi-devel] Trouble with digi 900Xtend
Date:	Sun, 22 May 2016 11:38:56 -0600