#just got a raspi 5, setting up crowsnest
59 messages · Page 1 of 1 (latest)
Ahoi @agile crest!
It looks like you did not provide all the necessary information we need to help you.
Please upload your logfiles and a detailed description of your problem.
For further information see: https://docs.mainsail.xyz/faq/getting-help/discord#provide-information
Note: We only accept .log and .txt files as log files.
This is an automated message
I was having a similar problem. I ended up having to look to see how the camera was listed in /dev . For me the cam i was wanting was listed as /dev/video1 .
It's listed in the log, that's why we got that bot to ask for logs automatically, as a log would help here and in most other cases too
mine is dev video10
idk how to pull the log
as, this is crownsnest stand alone, nothing else on the pi
sftp client
run as sudo sftp client??
can i ssh into via that, or do i need to pull the sd card?
just google what winscp or a sftp client is and the question should answer itself
ok which specific logs do you need?
Please look at your log and tell me again, which device it should be
video 0?? honestly no clue..
The answer would be actually, "Don't use Crowsnest"
You only got a libcamera
That won't work with ustreamer and on the Pi5 you only got ustreamer with Crowsnest
Therefore you should install Spyglass instead: https://github.com/mryel00/spyglass
was just testing with a csi camera, but im going to be using usb cameras, are usb cameras also lib??
no, they are not
It's hard to help you, if you give me a log, with a setup that you don't even want to use. I won't go through the whole log, just to find the point where you had the correct setup
ok, ill connect reconfigure with usb setup, and if it doesnt work, use spyglass. didnt know csi wouldnt work, as on the pi4 it did work with csi
Yes, but as you can read in the log/on my screenshot, we don't support it on the Pi5 yet
Overall I don't recommend to use a Pi5 for any webcam tasks
yeah, thats where i was getting confused
Are you only using it for cams right now?
yeah, the pi is a secondary pi just for cameras, thats it
having usb cameras on my other pi causes usb bus overload which causes failed prints due to mcu connection issues
Then you should swap out the Pis. The Pi5 is the worst Pi for cams.
damn.... XD just replaced the rpi3 for the 5 due to horrible fps on the 3 lol
FPS are nearly always network related. The Pi5 does not have better network.
The Pi3 can use webrtc, which will use less bandwidth and therefore most likely result in higher fps
thats what i was thinking, tested the speeds and was getting like 5mbps down, 1.4up, got a tplink, got it to 17 down, 7 up. fps still sucked
I recommend to use the by-id path, that the path won't change after reboots, or plugging in multiple cams
ok ill research what by by-id path is. never had issues with video paths changing on pi 4, this unit will have 2 cameras plugged in, maybe 3 if i decide on doing a nozzle camera.
your talking about video 0 and video 2 kinda thing or?
That's the path that can change, yes
That's the portion of the log
First the by-id path, then the corresponding /dev/video path
ahh, so lookign at it online, it locks the serial for the cameras to the specific video path? so as in maybe if the camera gets unplugged plugged into wrong usb it locks it?
Yes, the by-id path, won't change
ahhh makes sense,... yeah that would be a good idear
You can switch usb ports, plug the cams back in in different order and so on. The by-id path is always the same
as you can tell im very linux illiterate
Like 95% of the people that use Klipper ^^
For basic linux stuff, it's really good. For klipper stuff, it's pretty bad
helped me with small things klipper, but yeah rest was github and discord