You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good to have cwipc running on a Raspberry Pi 4 or later. Earlier is pointless, see below.
This is (I think) specifically to allow using the RPi as a dedicated "camera server" with a RealSense camera attached.
I'm targeting the RealSense at the moment, because people have gotten it working on the RPi (unlike the Kinect).
I'm specifically saying RPi4 or later because earlier models don't have USB3, and USB3 is needed to (1) get decent throughput to the camera, and (2) get decent Ethernet throughput.
I'm going to start with investigating whether we can build librealsense2 for the RPi4, and see whether its performance is good enough to continue this line of work. It may be that it is, in which case we continue. It may be that we have to wait for the RPi5.
The text was updated successfully, but these errors were encountered:
The Python interfaces still don't work (this version of protobuf is incompatible with 3.11). Also tried v24.0 (which apparently has a newer naming scheme?), but I couldn't build that with the given instructions.
Continuing with the instructions (skipping OpenCV, which was a suggestion I saw somewhere else).
Am now at the point of trying to build librealsense.
It would be good to have cwipc running on a Raspberry Pi 4 or later. Earlier is pointless, see below.
This is (I think) specifically to allow using the RPi as a dedicated "camera server" with a RealSense camera attached.
I'm targeting the RealSense at the moment, because people have gotten it working on the RPi (unlike the Kinect).
I'm specifically saying RPi4 or later because earlier models don't have USB3, and USB3 is needed to (1) get decent throughput to the camera, and (2) get decent Ethernet throughput.
I'm going to start with investigating whether we can build librealsense2 for the RPi4, and see whether its performance is good enough to continue this line of work. It may be that it is, in which case we continue. It may be that we have to wait for the RPi5.
The text was updated successfully, but these errors were encountered: