# Resetting ssh password

Source: https://forum.modalai.com/topic/1166/resetting-ssh-password
Category: Development Drones (https://forum.modalai.com/category/44/development-drones)
Tags: m500
Posted: 2022-07-28 13:34:20 UTC by Dean Hart
Replies: 7 · Views: 1324

## Dean Hart · 2022-07-28 13:34:20 UTC

I purchased the VOXL M500 over a year ago. I set it up initially but due to other projects I’m just getting back to it. Unable to ssh in using root/oelinux123 so worried I may have changed the password. How do I go about resetting it?

## Reply by Guest · 2022-07-28 17:29:21 UTC

Hi,

If you're just getting back to it after a while anyways i'd recommend reflashing the board with our latest software stack from downloads.modalai.com . You'll find it under voxl1 platform releases and then platform 3.8.0-0.7. This will both reset the voxl's environment and get you up to date with our latest stuff.

## Reply by Dean Hart · 2022-07-28 20:19:06 UTC (in reply to Guest)

Thanks @Alex-Gardner . I reflashed the board. Went through all the setup instructions but I'm stuck at https://docs.modalai.com/voxl-m500-user-guide-px4/#connect-m500-to-qgroundcontrol. 

QGC can see the drone, I can see telemetry streaming, but when trying to access vehicle settings I encounter the message `Vehicle settings and info will display after connecting your vehicle.`

When attempting to arm I encounter the error `Vehicle did not respond to command: MAV_CMD_COMPONENT_ARM_DISARM`.

This is what's running on the drone:

```
root@apq8096:~# voxl-inspect-services  --version
 Service Name         |  Version  |  Enabled  |   Running   |  CPU Usage
---------------------------------------------------------------------------
 docker-autorun       |    1.2.4  | Disabled  | Not Running |
 docker-daemon        |    1.2.4  | Disabled  | Not Running |
 modallink-relink     |   0.15.1  | Disabled  | Not Running |
 voxl-camera-server   |    0.9.1  |  Enabled  |   Running   |     2.0
 voxl-cpu-monitor     |    0.2.5  |  Enabled  |   Running   |     0.0
 voxl-dfs-server      |    0.2.6  | Disabled  | Not Running |
 voxl-imu-server      |    1.0.1  |  Enabled  |   Running   |     0.0
 voxl-mavlink-server  |    0.1.1  |  Enabled  |   Running   |     0.0
 voxl-modem           |   0.15.1  | Disabled  | Not Running |
 voxl-portal          |    0.2.6  |  Enabled  |   Running   |     0.0
 voxl-qvio-server     |    0.4.6  |  Enabled  |   Running   |    10.1
 voxl-streamer        |    0.3.1  | Disabled  | Not Running |
 voxl-tag-detector    |    0.0.4  | Disabled  | Not Running |
 voxl-tflite-server   |    0.2.3  | Disabled  | Not Running |
 voxl-time-sync       |    1.1.1  | Disabled  | Not Running |
 voxl-vision-px4      |    1.0.5  |  Enabled  |   Running   |     0.0
 voxl-wait-for-fs     |    1.1.1  |  Enabled  |  Completed  |
```

Any ideas?

## Reply by James Strawson (ModalAI staff) · 2022-07-28 21:05:37 UTC

Sounds like QGC is in the state where it failed to load all of the PX4 params and appears connected but not fully. When connecting to QGC does the green progress bar at the top of the QGC window completely go from left to right or does it get stuck halfway and throw a warning that it failed to load params?

## Reply by Dean Hart · 2022-07-28 21:26:02 UTC (in reply to James Strawson)

@James-Strawson Just restarted  QGC to test. Correct. Green line stops just over 1/3 of the way and error `Vehicle 1 did not respond to request for parameters. This will cause QGroundControl to be unable to display its full user interface` is displayed.

## Reply by James Strawson (ModalAI staff) · 2022-07-28 22:18:56 UTC

Are you trying to connect over Wifi? I generally see this when trying to get QGC to connect over a really slow data link instead of wifi. QGC is particularly sensitive to dropped packets during that initial param load phase.

## Reply by Dean Hart · 2022-07-28 22:19:47 UTC (in reply to James Strawson)

@James-Strawson Yes wifi (softAP mode).

## Reply by Dean Hart · 2022-07-29 15:51:55 UTC

Seems to be an issue with QGC itself. The latest v4.2.3 I’m running is where it’s failing. If I revert back to the latest 4.1.* (4.1.7) it works.