Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Function Brokenfocus never gets called #232

Closed
Obagunceiro opened this issue Jan 14, 2024 · 1 comment
Closed

Function Brokenfocus never gets called #232

Obagunceiro opened this issue Jan 14, 2024 · 1 comment
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@Obagunceiro
Copy link

What happened

The brokenfocus function that should be executed to define the absolute focus is never called, when I look at the LOG, the following never appears: WARN: Detected 'brokenfocus' device. and then this function is not executed and my focus is always set to the webcam default, which in my case is 160, I can set the value for focus_absolute easily via SSH with the command: v4l2-ctl --set-ctrl=focus_absolute=200
. The problem is that whenever the crownest service is restarted, my webcam goes to default focus

What did you expect to happen

I would expect the following message to appear: WARN: Detected 'brokenfocus' device, and for my absolute focus to be set to that of crownest.cfg

How to reproduce

Configure v4l2 in crownest.cfg with the parameters focus_continuous_absolute=0 and focus_absolute=X
Using ustreamer (camera-streamer also doesn't set my focus)
Start the crownest service

Additional information

crowsnest.log
Screenshot_2

@mryel00
Copy link
Member

mryel00 commented Jan 14, 2024

The brokenfocus function that should be executed to define the absolute focus is never called

The brokenfocus function only executes, if it detecs that the settings are wrong after it got already set, as some devices got problems with settings it too early.
But this is a duplicate of the other issue you wrote in. Please don't do such things.

@mryel00 mryel00 added the duplicate This issue or pull request already exists label Jan 14, 2024
@mryel00 mryel00 closed this as completed Jan 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants