[[UM S5] Camera feed stopping]

On 5/12/2020 at 4:13 AM, SandervG said:

 

Hello, that is more difficult to say because many factors can contribute (or undermine) a stable wifi connection outside of the Ultimaker. Like the amount of other devices connected to the same network can make the connection less stable. So if you have the option to select Ethernet, I would always recommend this for stabilities sake. 

 

 

My S5 has always had this spotty problem with nginx... (whether on ethernet or wifi) the device is pingable in both cases.. but nginx fails to serve requests timely.

 

I'll start poking at it and see if i can come up with a 'temporary' fix for it.

 

 

[[UM S5] Camera feed stopping]

On 5/10/2020 at 12:01 AM, jkcz said:

Also, where can I find a guide on how to do these changes? I'm new to these kinds of modifications but if it is straightforward I am willing to try.

 

no guides... this is just digging through the system and googling the source. mjpg-streamer is a common opensource app that is used in many many applications/DIY/projects.  I'm just googling and trying things since it was annoying to me (and everyone else here) that Ultimaker had yet to fix this issue with all the firmware updates they regularly post.

[[UM S5] Camera feed stopping]

3 hours ago, SandervG said:

But technically, we wouldn't recommend increasing resolution to the webcam, as the increased resolution could contribute to loosing the feed. Increasing the timer to 10 seconds we see no harm in this, and our developers also took note of it and will evaluate if it can be used to further improve your experience. 

 

 

 

 

Absolutely agree... the resolution increase was to just see how it will behave, it's not much better (cant really tell a difference).  you can set it lower though.

resolutions[] = {
	{ "QQVGA", 160, 120 },
	{ "QCIF", 176, 144 },
	{ "CGA", 320, 200 },
	{ "QVGA", 320, 240 },
	{ "CIF", 352, 288 },
	{ "PAL", 720, 576 },
	{ "VGA", 640, 480 },
	{ "SVGA", 800, 600 },
	{ "XGA", 1024, 768 },
	{ "HD", 1280, 720 },
	{ "SXGA", 1280, 1024 },
	{ "UXGA", 1600, 1200 },
	{ "FHD", 1920, 1280 },
	};

 

 

But the restart timer looks to be a way to improve performance... maybe longer than 10 sec will work better, i just passed 5 days with out a failure, but i had to restart the printer for other reasons (relocation).

 

the web page camera viewing is set to a smaller size (600 x 450) so really... if we wanted to optimize the best for the web page... we should force the res to VGA in the config file.  This would be the closest size, and theoretically be the lightest from a memory/utilization standpoint.

 

[[UM S5] Camera feed stopping]

day 4, still going strong here

[[UM S5] Camera feed stopping]

Just now, danieledge123 said:

How does this address the problem with the camera cutting out though?

 

 

I've been using the system like this for 3 days, and the camera has not failed once.  previously, it failed after a few hours if i was lucky to make it that long.

 

I think the problem is when it tries to restart with the default setting (3 sec) its not actually releasing the device fast enough for the new service to grab it.  the 10 sec seems to work really well for me.... ymmv

[[UM S5] Camera feed stopping]

Just now, danieledge123 said:

Thanks @Admehnistrator what does changing to SXGA do?

 

the resolution change is just to maximize what the camera is capable of on the S5.  If you try a resolution larger, mjpg-streamer will just force it to max allowed by the camera.

[Ultimaker S5 Camera Not Working]

5 minutes ago, jeffroe said:

 

What does this accomplish?  Does it prevent the service from stopping (or at least let it restart reliably)?  And are you changing the resolution to a higher value here?

 

 

yes, it allows the restart to be more reliable...  the resolution change is just to maximize what the camera is capable of on the S5.  If you try a resolution larger, mjpg-streamer will just force it to max allowed by the camera.

 

I've been using the system like this for 3 days, and the camera has not failed once.  previously, it failed after a few hours if i was lucky to make it that long.

 

I think the problem is when it tries to restart with the default setting (3 sec) its not actually releasing the device fast enough for the new service to grab it.  the 10 sec seems to work really well for me.... ymmv

[[UM S5] Camera feed stopping]

modify /lib/systemd/system/mjpg-streamer\@.service to the below:

 

enable Dev via the front touch panel.

 

 

SSH to the S5 as user root pass ultimaker

 

vi /lib/systemd/system/mjpg-streamer\@.service

 

 

========================================================

[Unit]
Description=mjpg-streamer, Webcam streaming for all on /dev/video%i
BindsTo=dev-video%i.device

[Service]
Type=simple
User=ultimaker
Environment=LD_LIBRARY_PATH=/usr/lib/mjpg-streamer
ExecStart=/usr/bin/mjpg-streamer -i "input_uvc.so -r SXGA -d /dev/video%i" -o "output_http.so -p 808%i"
Restart=always
RestartSec=10
TimeoutSec=1

========================================================

 

systemctl daemon-reload

systemctl restart mjpg-streamer@0

 

Disable Dev mode via the front touch panel.

[Ultimaker S5 Camera Not Working]

modify /lib/systemd/system/mjpg-streamer\@.service to the below:

 

enable Dev via the front touch panel.

 

 

SSH to the S5 as user root pass ultimaker

 

vi /lib/systemd/system/mjpg-streamer\@.service

 

 

========================================================

[Unit]
Description=mjpg-streamer, Webcam streaming for all on /dev/video%i
BindsTo=dev-video%i.device

[Service]
Type=simple
User=ultimaker
Environment=LD_LIBRARY_PATH=/usr/lib/mjpg-streamer
ExecStart=/usr/bin/mjpg-streamer -i "input_uvc.so -r SXGA -d /dev/video%i" -o "output_http.so -p 808%i"
Restart=always
RestartSec=10
TimeoutSec=1

========================================================

 

systemctl daemon-reload

systemctl restart mjpg-streamer@0

 

Disable Dev mode via the front touch panel.