joystick.service error

Question

joystick.service error

LittleBookboy12138 opened this issue 4 years ago · comments

LittleBookboy12138 commented 4 years ago

Both joystick.service and robot.service are active, but an error occurred while connecting the PS4 to the Pupper.

The specific questions are as follows:

pi@raspberrypi(rw):~$ sudo systemctl status joystick.service
● joystick.service - Pupper Joystick service
Loaded: loaded (/boot/appliance/home/pi/PupperCommand/joystick.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2019-02-14 10:17:57 GMT; 78ms ago
Process: 1173 ExecStart=/usr/bin/python3 /home/pi/PupperCommand/joystick.py (code=exited, status=1/FAILURE)
Main PID: 1173 (code=exited, status=1/FAILURE)

Thank you!

JueDongli · Answer 1 · Tue Dec 29 2020 22:03:23 GMT+0800 (China Standard Time)

https://github.com/stanfordroboticsclub/UDPComms
DEFAULT_IP = "10.0.0.255"

ip By default UDPComms sends to the 10.0.0.X subnet, but can be changed to a different ip using this argument.
Set to localhost (127.0.0.1) for development on the same computer.

marx · Answer 2 · Sat Mar 19 2022 11:41:21 GMT+0800 (China Standard Time)

i have the same question ,still unsolved

Michal · Answer 3 · Sat Mar 19 2022 19:11:12 GMT+0800 (China Standard Time)

try running python3 /home/pi/PupperCommand/joystick.py to run the joystick program without systemd. What does it output?

marx · Answer 4 · Sat Mar 19 2022 19:40:24 GMT+0800 (China Standard Time)

try running python3 /home/pi/PupperCommand/joystick.py to run the joystick program without systemd. What does it output?

pi@pi(rw):~/PupperCommand$ sudo python3 joystick.py
Can't get device info: No such device
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/ds4drv/backends/bluetooth.py", line 89, in setup
subprocess.check_output(["hcitool", "clock"],
File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['hcitool', 'clock']' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/pi/PupperCommand/joystick.py", line 14, in
joystick = Joystick()
File "/usr/local/lib/python3.9/dist-packages/PS4Joystick.py", line 85, in init
backend.setup()
File "/usr/local/lib/python3.9/dist-packages/ds4drv/backends/bluetooth.py", line 92, in setup
raise BackendError("'hcitool clock' returned error. Make sure "
ds4drv.exceptions.BackendError: 'hcitool clock' returned error. Make sure your bluetooth device is powered up with 'hciconfig hciX up'.

Michal · Answer 5 · Sat Mar 19 2022 19:48:16 GMT+0800 (China Standard Time)

have you tired running hciconfig hciX up before running that command? Its a bit weird because I think joystick.py should run that on its own but I want to make sure

marx · Answer 6 · Sat Mar 19 2022 19:55:41 GMT+0800 (China Standard Time)

sudo hciconfig hciX up
Can't get device info: No such device

marx · Answer 7 · Sat Mar 19 2022 20:00:24 GMT+0800 (China Standard Time)

To start with,I didnt use offical img ,instead i used version _2021 bulleyes( 2021-10-30-raspios-bullseye),and followed the offical document to install the software

Michal · Answer 8 · Sat Mar 19 2022 20:01:07 GMT+0800 (China Standard Time)

It seems like the pi's bluetooth module is not showing up at all. What version of Pi are you using? What's the output of hcitool dev?

marx · Answer 9 · Sat Mar 19 2022 20:03:49 GMT+0800 (China Standard Time)

raspberry 4b ,pi@pi(rw):~/PupperCommand$ hcitool dev
Devices:
device is blank

Michal · Answer 10 · Sat Mar 19 2022 20:08:02 GMT+0800 (China Standard Time)

It's possible something changed between raspios versions. A quick googling brings this up which suggests early bullseye versions had something wrong with bluetooth. I would recommend updating raspios (it should be possible to do in place without reinstalling) and seeing if that fixes things

marx · Answer 11 · Sat Mar 19 2022 20:18:28 GMT+0800 (China Standard Time)

pi@pi(rw):$ sudo nano /etc/apt/sources.list.d/raspi.list
pi@pi(rw):$ sudo apt-get update
Hit:1 http://mirrors.tuna.tsinghua.edu.cn/raspbian/raspbian bullseye InRelease
Hit:2 http://mirrors.tuna.tsinghua.edu.cn/raspberrypi bullseye InRelease
Reading package lists... Done
pi@pi(rw):$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@pi(rw):$ sudo hcitool dev
Devices:
still blank
i think maybe i need to reinstall it to the newest version

marx · Answer 12 · Sat Mar 19 2022 20:26:23 GMT+0800 (China Standard Time)

It's possible something changed between raspios versions. A quick googling brings this up which suggests early bullseye versions had something wrong with bluetooth. I would recommend updating raspios (it should be possible to do in place without reinstalling) and seeing if that fixes things

thanks for your advice

Alfred Moore · Answer 13 · Thu Jun 01 2023 14:43:15 GMT+0800 (China Standard Time)

pi@pi(rw):~~$ sudo nano /etc/apt/sources.list.d/raspi.list pi@pi(rw):~~$ sudo apt-get update Hit:1 http://mirrors.tuna.tsinghua.edu.cn/raspbian/raspbian bullseye InRelease Hit:2 http://mirrors.tuna.tsinghua.edu.cn/raspberrypi bullseye InRelease Reading package lists... Done pi@pi(rw):$ sudo apt-get upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. pi@pi(rw):$ sudo hcitool dev Devices: still blank i think maybe i need to reinstall it to the newest version

Did you solve it ? Totally same problem, though I am in the Debian 10.