Down camera issues on OpenPnP restart (settings not reloaded to cam)

116 views
Skip to first unread message

vespaman

unread,
Jul 25, 2022, 4:19:17 AM7/25/22
to OpenPnP
So, I'm not sure if this has always been an issue for me, or if I just did not notice it before, but eveytime I restart OpenPnP, the settings of the down cam seems to go back to defaults.

The settings looks correct in the camera setting tab, but the camera has not actually got them reloaded after start. If I nudge each setting the camera will be good again. In my setup, the most irritating one is the exposure time, which will be brought to  around 20 (defualt of 165 is way too long).

I realize this could be a camera issue, a driver issue, or OpenPnP. (Linux computer)

I get these messages in the console, which looks related...

[DBG ] FOURCC = MJPG
[ERR ] setAutoProperty (ID=5) failed on VIDIOC_S_CTRL (errno 22)
[ERR ] getAutoProperty (ID=5) failed on VIDIOC_G_CTRL (errno 22)
[ERR ] getAutoProperty (ID=5) failed on VIDIOC_G_CTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getProperty (ID=3) failed on VIDIOC_G_CTRL (errno 22)
2022-07-25 10:10:31.255 AbstractBroadcastingCamera TRACE: Camera Down Locking thread 35 started.
[DBG ] FOURCC = MJPG
[ERR ] getPropertyLimits (ID=2) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getAutoProperty (ID=2) failed on VIDIOC_G_CTRL (errno 22)
[ERR ] getPropertyLimits (ID=2) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=2) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=2) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getProperty (ID=2) failed on VIDIOC_G_CTRL (errno 22)
[ERR ] getAutoProperty (ID=2) failed on VIDIOC_G_CTRL (errno 22)
[ERR ] setAutoProperty (ID=5) failed on VIDIOC_S_CTRL (errno 22)
[ERR ] getAutoProperty (ID=5) failed on VIDIOC_G_CTRL (errno 22)
[ERR ] getAutoProperty (ID=5) failed on VIDIOC_G_CTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getPropertyLimits (ID=3) failed on VIDIOC_QUERYCTRL (errno 22)
[ERR ] getProperty (ID=3) failed on VIDIOC_G_CTRL (errno 22)
2022-07-25 10:10:31.343 AbstractBroadcastingCamera TRACE: Camera Up Locking thread 37 started.


I don't see any issue with my up camera, but that maybe because it is close enough to the defaults, so it isn't really visible (and doesn't really matter).


Not a huge thing, but a bit annoying, and I suppose it would be good to know if this is only in my setup, or not. Or maybe well known issue?

Cheers,
  - Micael

mark maker

unread,
Jul 27, 2022, 6:24:10 AM7/27/22
to ope...@googlegroups.com

Just wanted to say that I can't help there. Someone else?

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/3442a8d3-5b9d-4578-af40-4a5a88e0fce9n%40googlegroups.com.

Łukasz

unread,
Jul 27, 2022, 7:17:34 AM7/27/22
to OpenPnP
AMD motherboard with B series chipset?

Litterio Andrea Guainella

unread,
Jul 27, 2022, 7:25:48 AM7/27/22
to OpenPnP
Hi Michael,
try to follow this thread. Seems Javier has solved with same error. Maybe useful

LAG

vespaman

unread,
Jul 27, 2022, 11:01:00 AM7/27/22
to OpenPnP
Hi all,

So this is an intel box, old i7, so not AMD, and while Javier had the same error, his cameras did not seem to work at all, whereas mine always work only that if I restart, the settings are not transferred to the cameras without me nudging the settings on the camera. If I reboot the computer, I have no issues at all, and same on cold start - no issues.

But :- I do have Ubuntu on this box and probably v18, similar to Javier, so..  I am anyway about to move to a more modern box, with Manjaro instead and if I am alone seeing these errors, then there's hope in that. Not that it is the end of the world, just a bit tedious.


Thanks,
 Micael
Reply all
Reply to author
Forward
0 new messages