Hi!
these days I downloaded cockpit, and started to set it up, to use it instead of Qground.
Everything went well, until using the joystick.
Every time i arm the rov the verticals start to spin on their own.
I did different tests to rule out both joystick and rov firmware problems.
I downloaded another version of cockpit but nothing changed, i downgraded the rov firmware, but nothing changed, i tried to set up the joystick using windows and even then nothing changed.
I changed the joystick using another one, and as soon as I insert the usb into the computer with rov armed the verticals start to spin.
I also got another laptop, I’ ve installed everything from zero and get the same problem too.
I tried other programs besides qground control and joysticks always work perfectly, the problem is only and exclusively on cockpit, when is using a wired controller. Has anyone had the same problem?
Hi @Framau -
We’e not encountered the issue your facing! It sounds like your game controller could be at fault. What position do the joysticks indicate they are in when you navigate to the Cockpit joystick setup menu? Can you share a screenshot?
I suspect the joystick you’re using is sending the command to dive - you could either disable the axis in favor of another one, or use a different controller. Can you share what model joystick you’re using?
Ciao Tony,
thanks for your reply, definitely is a software problem, I’ve tried 3 different wire joysticks, one is a home made hand control ( but I’m using since 2 years without issues), second is a logitech, third one is a trust one.
In cockpit (joystick page), no input from joysticks… Also if I use xbox bt one, but wired have the same issue…
On qground no problems, even without calibration, on cockpit all joysticks tried get me same issue.
I downloaded 1.3/1.31 cockpit to check if it it’s different version can be fix the problem… also rollback firmware on Br.
Try also to download specific firmware for all joysticks.
Finally doesn’t work only on cockpit.
Francesco Maurizio
| Tony White Applications Engineer
October 19 |
- | - |
Hi @Framau -
We’e not encountered the issue your facing! It sounds like your game controller could be at fault. What position do the joysticks indicate they are in when you navigate to the Cockpit joystick setup menu? Can you share a screenshot?
I suspect the joystick you’re using is sending the command to dive - you could either disable the axis in favor of another one, or use a different controller. Can you share what model joystick you’re using?
Hi @Framau
Can you show us what you see on the HTML5 Gamepad Test when plugging in each of your joysticks?
Also are you running cockpit as a BlueOS extension? if so, what browser are you using?
Ciao,
no I’m running the last version of the cockpit’s app, installed on Pc.
Now I’m mobilizing two rov for an offshore project, as I on again I will do it.
Hello,
Indeed, I encounter exactly the same problem with our joystick (it is a joystick based on a Bodnar card). It works perfectly on Qground.
On Cockpit, as soon as the vertical motors start and the joystick settings page does not show any faults!
I tried everything, even other wired joysticks, same problem… they don’t work with cockpit…
Hi @FlyingManta and @Framau
As I’m written, joystic work good, also with others applications, this issue happens when I connect a wire joystic to cockpit, doesn’t matter, if is a custom one, or a logitech/trust etc…
On Qground works fine, can be calibrate (but no need to fly, the stick working perfect only to calibrate deadbands and button’s assigment), on cockpit just when I’m inserted the joy’s usb, all 4 vertical ( heavy config.), start to spin for it self, all at same rpm, all at same direction. Dosen’t matter if I arm or note the rov, if I try to change something (manual mod-stabilize etc). Also if I don’t disarm the rov before close app, also with app closed, trusths still spinning…
Hi @Framau -
To confirm, you are not keeping QGC open at the same time you are using Cockpit??
Otherwise it looks like the joystick axis are not sending a full dive / ascend signal to the vehicle. I wonder if the center-stick-zero-throttle parameter needs to be enabled…
No, just using Cockpit …
@FlyingManta could we schedule a meeting to take a look at the problem?
There are some known bugs in the joystick configuration menus that we are already aware of and are scheduled to be fixed in the next weeks, but this one regarding the motors auto-spinning is not one of them.
I am experiencing the exact same issue. We have a custom joystick with 6-axis. When armed, in Manual Mode, the vertical thrusters spin. To add to that, sequential, arm/disarm steps, causes the thrusters to spin faster and faster.
I’m running the latest BlueOS, Ardusub and Cockpit. Heavy BlueROV2. On Standard BlueROV2 the problem doesn’t happen, but all 6-axis are visible in Cockpit (settings)…5-axis work. Although pitch cannot be reversed using the Cockpit joystick variables. (-1000 etc)
On the Heavy BlueROV2 I have tried disabling the S & T axis, still see issue.
Also tried altering the variables from -1000 & + etc…again still see issue with thrusters.
@rafael.lehmkuhl need your help here. G. Torres suggested I poll you.
Further tests with MS Edge as opposed to Chrome, showed same issue.
What specific logs are needed from me ?
@UnderseaROV if you can get Cockpit logs, they can help. You can download them from the main-menu > dev.
But @tony-white was able to reproduce the issue already, having possibly find the root cause. We are now investigating and expect to have a fix in the following week.
Cockpit (Nov 27, 2024 - 10꞉31꞉41 GMT+11).log (257.8 KB)
I renamed the file to .log as .syslog wasn’t permitted.
Is this the right file ? I enabled and disabled the ROV three times, I believe.
Each time the thrusters spun faster, as described.
It is great if this has already been identified.
Will take a look! Thanks @UnderseaROV!
Hi Rafael, I realised my Cockpit was version 1.3.2
I installed the local Windows version topside…version 1.4.1
Same issue. As soon as vehicle is enabled in Manual mode, the vertical thrusters start to spin. Faster and faster with each enable/disable sequence.
Was the log I attached last time, the correct one ? Do I need to enable lower level debug/log anywhere ?
@UnderseaROV I couldn’t find anything suspicious in your log. I’m going to include extra debug information in the logs of the next release, but while we don’t have that, do you mind doing a test for me? It will probably answer most of our questions:
- Open Cockpit
- Connect a controller (click on a button or move an axis so Cockpit can fetch it)
- Open the mavlink2rest page (http://your-blueos-address:6040)
- Scroll to the end of the page and click on the link to the
MANUAL_CONTROL
messages that are being sent from Cockpit - Take a screenshot of this page and post here
What you see there is the last MANUAL_CONTROL
message that was sent by Cockpit when you clicked the link. It will tell us what Cockpit is sending, so we know what is incorrect.
As an example, mine, with a PS5 DualSense controller connected to Cockpit (desktop version, on macOS), looks like this:
What we expect to see is X, Y, R, S and T all around zero and Z around 500.