Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request failed. Check mavros log #538

Closed
TonderaiZR opened this issue May 2, 2016 · 17 comments
Closed

Request failed. Check mavros log #538

TonderaiZR opened this issue May 2, 2016 · 17 comments
Labels

Comments

@TonderaiZR
Copy link

After running: roslaunch mavros amp2.launch and successfully connected.

I have tried arming the apm with : rosrun mavros mavsafety arm.

Result is: Request failed. Check mavros logs

Hope you can help.

@vooon vooon added the question label May 2, 2016
@vooon
Copy link
Member

vooon commented May 2, 2016

Please copy all text output (log) of console where you run roslaunch (a), then show diagnostics (b):

rostopic echo -n1 /diagnostics | tee /tmp/diag.yml

Also what wersion of ROS and Mavros?

FYI: use triple ` for code block.

@TonderaiZR
Copy link
Author

Hello Voon

I am using ros indigo. I will send text output when I run roslaunch. What will:
rostopic echo -n1 /diagnostics | tee /tmp/diag.yml Do ?

@vooon
Copy link
Member

vooon commented May 4, 2016

rostopic echo prints all data from topic; tee.

@vooon vooon closed this as completed Jun 23, 2016
@TonderaiZR
Copy link
Author

TonderaiZR commented Jul 16, 2016

Hello

After running this command:
rostopic echo -n1 /diagnostics | tee /tmp/diag.yml

This message appears:

header: 
  seq: 2725
  stamp: 
    secs: 1468703221
    nsecs: 436976838
  frame_id: ''
status: 
  - 
    level: 1
    name: mavros: FCU connection
    message: not connected
    hardware_id: /dev/ttyUSB0:115200
    values: 
      - 
        key: Received packets:
        value: 0
      - 
        key: Dropped packets:
        value: 0
      - 
        key: Buffer overruns:
        value: 0
      - 
        key: Parse errors:
        value: 0
      - 
        key: Rx sequence number:
        value: 0
      - 
        key: Tx sequence number:
        value: 138
      - 
        key: Rx total bytes:
        value: 0
      - 
        key: Tx total bytes:
        value: 1024105
      - 
        key: Rx speed:
        value: 0.000000
      - 
        key: Tx speed:
        value: 277.000000
  - 
    level: 2
    name: mavros: GPS
    message: No satellites
    hardware_id: /dev/ttyUSB0:115200
    values: 
      - 
        key: Satellites visible
        value: 0
      - 
        key: Fix type
        value: 0
      - 
        key: EPH (m)
        value: Unknown
      - 
        key: EPV (m)
        value: Unknown
  - 
    level: 2
    name: mavros: Heartbeat
    message: No events recorded.
    hardware_id: /dev/ttyUSB0:115200
    values: 
      - 
        key: Heartbeats since startup
        value: 0
      - 
        key: Frequency (Hz)
        value: 0.000000
      - 
        key: Vehicle type
        value: Generic
      - 
        key: Autopilot type
        value: Generic
      - 
        key: Mode
        value: ''
      - 
        key: System status
        value: Uninit
  - 
    level: 0
    name: mavros: System
    message: Normal
    hardware_id: /dev/ttyUSB0:115200
    values: 
      - 
        key: Sensor present
        value: 0x00000000
      - 
        key: Sensor enabled
        value: 0x00000000
      - 
        key: Sensor helth
        value: 0x00000000
      - 
        key: CPU Load (%)
        value: 0.0
      - 
        key: Drop rate (%)
        value: 0.0
      - 
        key: Errors comm
        value: 0
      - 
        key: Errors count #1
        value: 0
      - 
        key: Errors count #2
        value: 0
      - 
        key: Errors count #3
        value: 0
      - 
        key: Errors count #4
        value: 0
  - 
    level: 2
    name: mavros: Battery
    message: No data
    hardware_id: /dev/ttyUSB0:115200
    values: 
      - 
        key: Voltage
        value: -1.00
      - 
        key: Current
        value: 0.0
      - 
        key: Remaining
        value: 0.0
  - 
    level: 2
    name: mavros: Time Sync
    message: No events recorded.
    hardware_id: /dev/ttyUSB0:115200
    values: 
      - 
        key: Timesyncs since startup
        value: 0
      - 
        key: Frequency (Hz)
        value: 0.000000
      - 
        key: Last dt (ms)
        value: 0.000000
      - 
        key: Mean dt (ms)
        value: 0.000000
      - 
        key: Last system time (s)
        value: 0.000000000
      - 
        key: Time offset (s)
        value: 0.000000000

@TonderaiZR
Copy link
Author

So

I run : roslaunch mavros px4.launch

then tried : rosrun mavros mavsafety arm

This become error : request failed. Check mavros logs.

I tried setting all pre arming check off.

@vooon
Copy link
Member

vooon commented Jul 17, 2016

Did you see "level: 1 name: mavros: FCU connection message: not connected"?
What should ARM?

@TonderaiZR
Copy link
Author

So the pixhawk board should ARM.

@TonderaiZR
Copy link
Author

From Diagnostics command.

level: 1 name: mavros: FCU connection message: not connected hardware_id: /dev/ttyUSB0:115200 values:

@vooon
Copy link
Member

vooon commented Jul 17, 2016

And how it may ARM if there is no connection?

@TonderaiZR
Copy link
Author

So I have a usb serial connecting to the pixhawk telem2 pins with rx tx and ground.

@TonderaiZR
Copy link
Author

Hello

How can I Debug connection. Whats the correct way to guarantee a connection ? Or a link to a usb serial to pixhawk connection.

Kind regards.

Tondy

@vooon
Copy link
Member

vooon commented Aug 7, 2016

There are several tools for that. E.g. wireshark.

// Are you on Mars? Such delays…

@TonderaiZR
Copy link
Author

Hello

Not yet on Mars. Only get to work on drone once in a while . I more of a coder. Will use wireshark
first debug that connection issue. Also if you have a helpful link please post.

Kind regards.

Tondy

@vooon
Copy link
Member

vooon commented Aug 7, 2016

Try USB first. It should be /dev/ttyACM%d device. Check dmesg after plug. minicom may help to check tty communication.

APM as i know start mavlink by default, while PX4 give nsh shell. If it works then check params that set baud rate on TELEMn ports (check configuration manual, use MissionPlanner or QGC). Baud rate should match on both sides.

If params are ok: check your cable (connect Rx-Tx and use console), check that wire give correct cross: Rx1-Tx2, Tx1-Rx2, GND1-GND2.

@TonderaiZR
Copy link
Author

Ok . Thank you very much.

@noble-8
Copy link

noble-8 commented May 21, 2017

hey everyone I am getting the same error, but my diagnostics are showing that everything else is fine can somebody help?

@khancyr
Copy link
Contributor

khancyr commented May 22, 2017

@Count-Darth Please open another issue with your information and log. If it failed to arm, it either you aren't correctly connected or you miss an arming check. Look at the message send back to see where the error is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants