We are pretty new to the Blueboat and still testing its functions. At our first test in the water, we encountered a very problematic issue.
We followed the software setup guide and configured in QGroundControl under Windows 11 the recommended XBOX controller as described. There are 4 joystick control modes listed that can indeed be selected.
The big issue occurs with Windows screen lock: For the 3 modes that involve the L stick, if the BlueBoat is Armed and you lock the screen, if you so much as touch the L stick, no further inputs are accepted (no more disarming), and the BlueBoat reverses full throttle, leading to potentially catastrophic consequences. It can only be stopped by unlocking the PC or, using the cell modem and ZeroTier going into Blueos and manually disarming.
This happens in manual mode. No matter if the XBOX controller is connected via USB or bluetooth. Changing various failsafe settings does not change this behavior. The Base Station is connected directly to the PC via USB. We have not changed any parameters other than SERVO#_TRIM and trying various failsafe configurations (the latter only after we encountered the issue).
Our current workaround is to completely disable screen locking in Windows power settings (awkward if you want to do long missions and use manual control for getting to shore at the end) and/or to use the one Joystick mode that uses only the R stick. With that mode we can lock and unlock the screen as we please, does not affect manual control at all.
So, there seems to be some fundamental issue. I suspect it’s somewhere in the communication between QGC, Windows, and the controller.
Can anyone replicate this problem?
Could it be a QGC issue and therefore could using another control software solve the problem?
This does sound like a windows / QGC problem - it does seem unusual to expect to maintain control while your computer is locked! It seems bizarre that QGC can receive commands and process / change it’s output when the system is locked…
If you’re trying to save power with your laptop, disconnecting the controller and turning it off after starting your auto mission, and managing the vehicle from your phone connected via ZeroTier / QGC may be a good alternative? You could also install a sbus compatible radio receiver, and use a traditional RC controller for control with no computer / zerotier involvement….
I wouldn’t mind if there was no control input possible with the laptop screen off (most accurately, it is locked, as you would get by pressing WIN+L). But actually, regular inputs are possible with the right stick and the buttons, while the left stick gives us the described problematic behavior.
We do indeed have a modem installed and ZeroTier active. What is the best way to disarm the boat from the phone? I am going into blueOS and then into the PWM testing window, where I can disarm but that’s rather slow and awkward. Or, maybe better, is there a way to put the boat into hold or manual from the BlueOS web interface?
I am also interested in installing an sbus compatible radio receiver could you please point me in the direction of what to buy and how to do it?
We’re surprised it’s possible for input to make it into a locked computer at all! Definitely seems like a fundamental Windows problem…
I would recommend installing QGround Control on your phone, there are both Android and iOS versions that work when connected via zerotier. You can control the vehicle normally then - disarm, set waypoints, plan missions, even drive via on-screen joysticks or a controller paired to the phone!
Hold mode simply disarms the motors - maybe you meant loiter mode?
The BlueBoat does not have anything plugged into Serial1 by default. Serial 3 & 4 are still available for serial connections, or a USB to Serial adapter can be used. One can certainly come up with situations where that Serial1 interference causes a conflict, but that shouldn’t be the case in most situations - are you using Serial1 currently?
You may need to cut a trace depending on the type of SBUS the receiver is using…
