Webcam stops working after connecting to printer

Get Help Webcams
1

Camera model
Logitech C510

What is the problem?
When only the webcam is connected, the stream works great. As soon as I connect the printer in the GUI, the webcam stops (as the led on the Webcam) and then even if I disconnect the printer the camera wouldn't start, I have to reboot to make it work again.

What did you already try to solve it?
I covered the 5V pin on the USB cable to the printer, I also tried using a powered USB hub to make sure that there is enough power

Logs (/var/log/webcamd.log, syslog, dmesg, ... no logs, no support)
pi@octopi:~ $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:081d Logitech, Inc. HD Webcam C510
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Additional information about your setup (OctoPrint version, OctoPi version, ...)
I got the Raspberry 4B 2Gb with the official 15W power supply, and the latest OS.

2

Hi @Waza_Boy!

You may try this: Put tape on the 5V pin - Why and how

3

They already did :wink:

@Waza_Boy Any undervoltage warnings in the octoprint.log?

1 Like
4

I should read more carefully... :pensive:

5

So I powered my printer, connected the Pi and again the webcam stops working when the connection is estblished.
Here are the logs :

2019-11-20 16:14:23,169 - octoprint.server.util.sockjs - INFO - User user logged in on the socket from client ::ffff:10.8.0.3
2019-11-20 16:15:07,495 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial port"
2019-11-20 16:15:07,548 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial port" to "Opening serial port"
2019-11-20 16:15:07,551 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Detecting baudrate"
2019-11-20 16:15:08,560 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:20,587 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:21,594 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:22,601 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:23,604 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:24,616 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:24,628 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting baudrate" to "Operational"
2019-11-20 16:15:24,634 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:24,656 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin 1.1.9 (Github)"
2019-11-20 16:15:24,665 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2019-11-20 16:15:41,415 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline"
2019-11-20 16:15:44,606 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial port"
2019-11-20 16:15:44,611 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2019-11-20 16:15:44,620 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:44,623 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:44,632 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Operational"
2019-11-20 16:15:44,635 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:15:44,650 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin 1.1.9 (Github)"
2019-11-20 16:15:44,654 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2019-11-20 16:17:45,975 - octoprint.filemanager.analysis - INFO - Starting analysis of local:Pi_Zero_Arm.gcode
2019-11-20 16:17:45,980 - octoprint.filemanager.analysis - INFO - Invoking analysis command: /home/pi/oprint/bin/python2 -m octoprint analysis gcode --speed-x=6000 --speed-y=6000 --max-t=10 --throttle=0.0 --throttle-lines=100 /home/pi/.octoprint/uploads/Pi_Zero_Arm.gcode
2019-11-20 16:17:50,104 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: Pi_Zero_Arm.gcode, owner: user, user: user
2019-11-20 16:17:50,112 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2019-11-20 16:17:50,116 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Pi_Zero_Arm.gcode, owner: user, user: user
2019-11-20 16:17:50,122 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-11-20 16:17:50,127 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2019-11-20 16:17:52,168 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2019-11-20 16:18:20,755 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2019-11-20 16:22:19,952 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2019-11-20 16:26:21,008 - octoprint.server.util.flask - INFO - Passively logging in user user from ::ffff:10.8.0.3
2019-11-20 16:26:21,881 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:10.8.0.3
2019-11-20 16:26:21,999 - octoprint.server.util.flask - INFO - Passively logging in user user from ::ffff:10.8.0.3
2019-11-20 16:26:22,663 - octoprint.plugins.webcamstreamer - INFO - Checking stream status.
2019-11-20 16:26:22,675 - octoprint.plugins.webcamstreamer - INFO - stream is inactive 
2019-11-20 16:26:23,050 - octoprint.server.util.sockjs - INFO - User user logged in on the socket from client ::ffff:10.8.0.3
2019-11-20 16:26:36,848 - octoprint.plugins.errortracking - INFO - Initialized error tracking
2019-11-20 16:26:49,350 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:10.8.0.3
2019-11-20 16:26:49,451 - octoprint.server.util.flask - INFO - Passively logging in user user from ::ffff:10.8.0.3
2019-11-20 16:26:49,491 - octoprint.server.util.sockjs - INFO - User user logged in on the socket from client ::ffff:10.8.0.3
6

If it were me, I would move either the webcam or the printer's serial cable to/from the other style of USB connection: if it's already in the 2.0 type then move it to 3.0 or vice versa. But I'm guessing that perhaps both the webcam and the printer's serial cable are in the blue 3.0 style connectors.

7

Actually the printer is in the V2, and for the camera I tried in the V2 and V3, didn't change a thing

8

As requested, are there any undervoltage indications in the octoprint.log?

9

I showed the octoprint.log, there is none.

10

Okay so for anyone wandering, I need to have a camera to watch my printer so I used another raspberry (Pi Zero W) just to stream.
But if you think you have a solution to the problem I'll gladly try it on my main Rpi4.

Thanks to everyone

1 Like
12

I have developed the same problem using a PI 3B+. The problem started when I replace the stock Melzi board with an SKR1.3. Have you found a solution?

P.S. I also taped over the 5v pin.

1 Like