Hi everyone, I recently build a custom version of mission planner (changed button aspect, made an autonomous joystick detection, and a new window that opens a ssh session). To share it to other computers, I made a .msi and shared the net461 folder from the release bin.
4 computers were able to make it work normally, using different methods :
deleting regular mission planner and downloading new version from .msi
downloading regular mission planner, and replace the C:\Program Files (x86)\Mission Planner folder by the bin build.
For them everything works properly and it’s great !
But the one last computer doesn’t work. We tried both ways and the app launches but stop at some point just after the hud appeared. Splash doesn’t close and the app never start completly. So we tried disabling the firewall, and updating the driver of graphic card.
Here’s the log in the command prompt of the app that doesn’t load.
Disable your changes and re enable them one by one to find out what is causing the issue. then you can debug focused on the area.
Some detailled logging could help as well.
Mission Planner log is in the ProgramData/Mission Planner folder. You can check what is the last message you got.
But you should add some logging around the modifications you did (starting, finishing etc.) to see where is the hangup.
I would suspect the changes in the joystick detection to the SSH session..
It is definitely something with the computer setup, which is not handled by the changed code.
Okey well I’m quite sure it is not the ssh session, since it is started with a button in flightdata. It could be the joystick, but the joystick detection starts at the end of the flightdata load and this part is cleary not reached since it stops before showing anything but the hud. Also, it works on the other computers…
Here’s the last log, as it seems to stop after the airports… Don’t know what to do with this…
If you don’t have any clue, I’ll try to put message when I start any of my change for debugging tomorrow.
Thank you for your help !
EDIT : Here’s a new log where I put log.info to debug, and we can see that joystick detection is started but not ssh and the code stops once again at airport MissionPlanner.log (466.7 KB)
It is a multi threaded application, so it think it is not stopping at the airport, that is the mainloop running.
I\m afraid you have to debug it on the actual machine to see what is happening.
I found the issue, you were right I had to wait a mavlink connexion for the joystick to know which joystick configuration load. Now everything works has expected