# Button inputs crazy **URL:** \ **Category:** Cockpit\ **Created:** [June 22, 2026, 12:09am UTC](https://discuss.bluerobotics.com/t/button-inputs-crazy/23210 "2026-06-22T00:09:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Mauro](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Mauro](https://discuss.bluerobotics.com/u/Mauro)\ **Post date:** [June 22, 2026, 12:09am UTC](https://discuss.bluerobotics.com/t/button-inputs-crazy/23210/1 "2026-06-22T00:09:20Z")
Hi everyone, I’m having trouble mapping the buttons on my controller because my son completely messed up the settings. The worst part is that when I access the joystick configuration in Cockpit, the computer disconnects and everything goes haywire. Is there any way to do a clean install of Cockpit or reset the joystick settings? Thanks… ---
**Author:** ![rafael.lehmkuhl](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/rafael.lehmkuhl/32/6630_2.png) [@rafael.lehmkuhl](https://discuss.bluerobotics.com/u/rafael.lehmkuhl)\ **Post date:** [June 22, 2026, 5:17pm UTC](https://discuss.bluerobotics.com/t/button-inputs-crazy/23210/2 "2026-06-22T17:17:18Z")
Hey @Mauro! Yes, there are ways to reset it to a clean state, but first I would like to take a look at the logs to see what’s causing this behavior when you access the joystick configuration, and make sure on how to deal with it. Following are the steps on how to catch a good log for that: 1. Go to `/menu/settings/dev` and make sure you have “Enable system logging” on. If it’s not, switch it on. 2. Still on `/menu/settings/dev` take note on the name/date-time of the current logging being written (red dot in the left). 3. Now make it so the bug happens (from what I understood you just need to open `/menu/settings/joystick` for it to happen?) 4. Now that Cockpit crashed, start it again and go to `/menu/settings/dev` 5. Click to download the log from the previous session, where the bug happened (remember the name/date-time we got in step 2) 6. Send us this log ---
**Author:** ![Mauro](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Mauro](https://discuss.bluerobotics.com/u/Mauro)\ **Post date:** [June 22, 2026, 6:23pm UTC](https://discuss.bluerobotics.com/t/button-inputs-crazy/23210/3 "2026-06-22T18:23:09Z")
Hi there Rafa, thanks in advance… [Cockpit (Jun 22, 2026 - 14꞉04꞉13 GMT-4).syslog](https://discuss.bluerobotics.com/uploads/short-url/fMndizUKms0fzWrbEXzIfTtdJ3P.syslog) (1.6 MB) ---
**Author:** ![Mauro](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Mauro](https://discuss.bluerobotics.com/u/Mauro)\ **Post date:** [June 23, 2026, 10:27pm UTC](https://discuss.bluerobotics.com/t/button-inputs-crazy/23210/4 "2026-06-23T22:27:26Z")
Hi there, I have an update. I changed the PC, the joystick, and the ROV, and everything was OK. But when I tried the old ROV in the new setup, the behavior returned. The parameters were reset to 0 from the BlueOS configuration, a clean joystick mapping configuration was loaded, but it still has the same problems. When trying to access the cockpit configuration, it loses communication and displays the “Heartbit…” warning. I seriously suspect the Pixhawk board in the unit since the symptom is generally related to servo control. What do you think? ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [June 24, 2026, 2:13am UTC](https://discuss.bluerobotics.com/t/button-inputs-crazy/23210/5 "2026-06-24T02:13:10Z")
Hi @Mauro - What output servo devices are you controlling? Could one of them be causing an electrical issue for the Pi or Pixhawk? Do you notice the lights change when you lose connection to the vehicle? Can you provide a clear description of the sequence of events, or maybe record a video of the issue? ---
**Author:** ![rafael.lehmkuhl](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/rafael.lehmkuhl/32/6630_2.png) [@rafael.lehmkuhl](https://discuss.bluerobotics.com/u/rafael.lehmkuhl)\ **Post date:** [June 24, 2026, 3:03pm UTC](https://discuss.bluerobotics.com/t/button-inputs-crazy/23210/6 "2026-06-24T15:03:30Z")
@Mauro I can see in the logs that the Pixhawk is rebooting every couple minutes, but I could not find a correlation between any Cockpit action and the reboots (not saying that Cockpit is not causing that, as it may not be logging something that could explain us the reason). To better understand: in the first computer, the problems started as soon as you opened the joystick configuration menu? It was a clear correlation between opening the menu and the problems starting?