I am trying to use a raspberry pi to send feature reports to a Vive tracker. However I've come across a bit of a problem when I connect both of them.
Whenever I boot up the pi with the vive connected the vive stops being tracked on SteamVR. However when I reboot the pi it tracks again despite the fact that the vive is connected via bluetooth to a pc running unity.
I've set up udev rules for the vive tracker and checked the output of /dev/hidraw0 which is empty on reboot but on boot constantly outputs, does that mean the pi is using the tracker? If so how can I find out what?
Is there a way to stop the pi from using the interfaces which I need to run my script and allow the tracker to track on SteamVR while plugged into the pi without having to reboot each time?
I've tried killing any process using the interface (through fuser) and printing logs of boot up processes and reboot processes but haven't found anything that would cause this
Related
My Node.js project utilizes CEC control and VLC where the app turns on the TV and chooses the HDMI port that the VLC video stream will be viewed on at a scheduled time.
Everything worked on Buster except that too many indeterminate crashes with segmentation faults occur with cec-client.
Since I am nearing a 'production' release, I thought it best to upgrade the OS to Bullseye and find a cec-client replacement. I found cec-ctl and made it asynchronous - ctl-cec works perfectly, everytime, no crashes. BUT, now VLC does not render anything, not even a black screen. Doing a 'ps' command during a time that a video should be playing, I can see that VLC is running.
What I tried: It turns out that changing the /boot/config.txt dtoverlay=vc4-fkms-v3d (Buster) to dtoverlay=vc4-kms-v3d (Bullseye) causes the problem. The Buster version of dtoverlay seems to be required for VLC to run, and The Bullseye version of dtoverlay is required for a /dev/cec0 to be created and used by ctl-cec.
All I can see from my inexperienced view is mutual exclusivity, but this doesn't feel like this is the final answer. Using both dtoverlay version (Buster/Bullseye) will brick the pi (speaking from the very recent experience of one not well-versed in dtoverlays).
I also tried: I Googled this problem to the extent of my search skills and have not been able to resolve this problem.
Any help is greatly appreciated!
Raspbian OS: Bullseye (Desktop)
Raspberry Pi 3 B+
App: Node.js based with ability to make config changes and set schedules via an external browser within the LAN.
The solution for my project, after days of Googling, turned out to be TOO simple (found here: https://www.reddit.com/r/archlinuxarm/comments/lg4z5u/no_hdmi_audio_via_alsa_on_raspberry_pi_400/):
sudo apt install pulseaudio
along with:
dtoverlay=vc4-kms-v3d
VLC and cec-ctl now work together perfectly on Raspberry Pi 3B+/Bullseye
I tried working with my RPi Pico today and my computer doesn't recognize the usb I triple checked the cable is power and data. And yes I'm holding the button
I've also had this annoying issue. Seems to happen even more often on the Pi Pico W.
Use my laptop USB-C port to connect via a USB-C to USB 3.0 hub and this happens every so often.
Bought a powered hub from Amazon: "UGREEN USB C Hub 4 Ports, USB C to USB Hub 3.0". It has a separate USB-C power input in addition to the laptop USB-C connection and it works fine when no other USB devices are connected to the hub. Seems to be an issue similar to what Foibled2 mentioned where the underlying issue may be power related.
I'm struggling with the same thing. Other than uninstalling in Device Manager and rebooting (sometimes several times) I can get it to recover.
There must be a better way.
I've seen references to Zadig, etc. But finally figured out the issue in my circumstance.
I disabled all of my other USB serial devices (Prolific USB for GPS tracker; and CH340 USB for Android Nano).
After that, I could plug / unplug my R Pi Pico between application and USB drive mode without rebooting.
Works now as advertised. Hope this helps short cut a few hours for someone else!
I am interested in game development, but my main computer is a raspberry pi 4B, and I won't be upgrading for a while. I am hoping to upgrade eventually, but for now I would like a solution for running Unity Engine on my Raspberry Pi 4B. performance is not my worry, I am overclocking to 2ghz and am using a lightweight desktop. I will only be doing 2d on my pi, but I want to use unity so that i don't have a massive learning curve when I hopefully upgrade and am able to do 3d.
Thanks!
In theory, it should be possible since Raspberry PI supports the Ubuntu Desktop operating system and so does Unity. Though, I haven't personally tested this out.
So that means that you would need to install Ubuntu on your Raspberry PI device and then install Unity Hub and then a version of the Unity editor.
Sources:
Operating systems supported by Raspberry PI
Linux distributions supported by Unity
I'm doing a project for my son where we're going to have a remote Pi Zero with a camera and various sensors and actuators, connected via wired Ethernet to a Pi 3 as a controller with a Scratch GUI.
Seems like I can get a local camera to send video to the background of the Scratch project, or I can get a remote camera to stream back to e.g. VLC Player using RTSP.
Being as how I want to teach my son how to build a scratch GUI on the Pi3 to remote control the sensors and actuators on the Pi Zero, I'd really like the rtsp video stream to show up as the Scratch project background so I don't have to have a separate VLC window open.
So... how to pick up an RTSP video stream and send it to the Scratch backdrop?
Anyone got any ideas as to where I could start? I have intermediate raspbian, python and Scratch skills.
Thanks in advance,
Ben
Just a wild suggestion. Maybe it is possible to access your USB camera on the remote pi zero as a local camera using remote USB (I admit I have never tried it).
This functionality is provided by the package usbip
https://packages.debian.org/jessie/usbip
You can install this package using the following command on both raspberry pi devices:
sudo apt-get install usbip
For more information about the setup enter the command:
man usbip.
i have installed wheezy on my raspberry pi and everything works fine except for the IDLE software where both versions IDLE and IDLE 3 won't open when double clicking them from the desktop or from the start like menu.
i try to open them but nothing happens?!
i don't know what does this have to do with this issue, but i used to connect to raspberry pi by putty and xming11 and at that case the IDLE software didn't open when trying to access it.
however by using tightvnc, this issue was solved!!!