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

Camera feed not monitored by cockpit #235

Closed
BrianAdams opened this Issue Jun 2, 2014 · 2 comments

Comments

Projects
None yet
1 participant
@BrianAdams
Collaborator

BrianAdams commented Jun 2, 2014

The current cockpit software does start the mjpeg streaming process, but it does not monitor it. Dues to instability in the USB on the beaglebone (DMA not on), and potential restarts in the cockpit software itself, the system needs to check the status of the mjpeg streamer service and restart it in the case it dies. The system should also be smarter when cockpit restarts and no error out if the mjpeg streamer process is already running.

@BrianAdams BrianAdams added the bug label Jun 2, 2014

@BrianAdams

This comment has been minimized.

Collaborator

BrianAdams commented Aug 26, 2014

Design:

The camera should be decoupled from the cockpit software. The contract should be the URL of the feed from the camera for video. There should also be a contract for setting the parameters for the video such as fps and resolution.

Assuming we are still using mjpegstreamer, that implies standing up a service with a messaging API that listens for changes events and can then cycle the mjpegstreamer service. This service will also need to manage the mjpegstreamer process for failures and auto-restart the service.

@BrianAdams BrianAdams added this to the vNext milestone Sep 12, 2014

@BrianAdams BrianAdams modified the milestones: 2.5.2, 2.5.1 Nov 13, 2014

codewithpassion added a commit to codewithpassion/openrov-software that referenced this issue Mar 4, 2015

@BrianAdams

This comment has been minimized.

Collaborator

BrianAdams commented Aug 11, 2016

This has been resolved in 30.1+ cameras are now run by supervisor processes

@BrianAdams BrianAdams closed this Aug 11, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment