Camera Stops Working.... Solved! #531
Replies: 19 comments 24 replies
-
|
Interesting, thanks for sharing. |
Beta Was this translation helpful? Give feedback.
-
|
This unfortunately did not resolve my issue and I think that is because the issue manifests in different ways. In my case the cam_app service terminates and will not restart unless I reboot the system. |
Beta Was this translation helpful? Give feedback.
-
|
My Camera went down on the K1C aswell, reboot fixed, on generic machines I just restart Crowsnest, not sure what we can do on the K1 series? |
Beta Was this translation helpful? Give feedback.
-
|
Mine doesn't stop working, it just starts to flicker after a while. Can I just use 127.0.0.1 as the IP address in case the IP address of the printer changes? |
Beta Was this translation helpful? Give feedback.
-
|
I think it should work. Flickering is indicative of a service restarting, so I would be curious to see your system logs. Can you run dmesg on the terminal and share the output when you observe the flickering? The services on the K1 are not very easy to trace but what I managed to figure out so far is that the AI service seems to be like a master service that then shares the stream with mjpeg- streamer. I tried to get mjpeg-streamer to stream the camera directly but the formats are not standard webcam, and information on the camera is quite sparse, so I have not been able to get it working directly yet. |
Beta Was this translation helpful? Give feedback.
-
|
127.0.0.1 doesn't work I had to enter the IP address of the printer. I think it might be better described as looking like the image isn't always fully loading, like when you only get the top part of a JPEG. |
Beta Was this translation helpful? Give feedback.
-
|
Localhost might also work
Joel M. Gabel
"Any sufficiently advanced technology is indistinguishable from magic." -
Arthur C. Clarke
…On Sat, May 4, 2024 at 07:59 Mark ***@***.***> wrote:
127.0.0.1 doesn't work I had to enter the IP address of the printer.
I think it might be better described as looking like the image isn't
always fully loading, like when you only get the top part of a JPEG.
—
Reply to this email directly, view it on GitHub
<#531 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHT66CQ2HJQJRU4AFETQ67DZATLUZAVCNFSM6AAAAABGY4ASTGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGMJTGY4TK>
.
You are receiving this because you authored the thread.Message ID:
<Guilouz/Creality-Helper-Script-Wiki/repo-discussions/531/comments/9313695
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I don't think it will as it seems to use that URL in the page, so it would point to localhost on the computer where the page is open. |
Beta Was this translation helpful? Give feedback.
-
|
Mine is working great with the IP for over a week now. Have 2 rooted K1Max
printers running that config.
Joel M. Gabel
"Any sufficiently advanced technology is indistinguishable from magic." -
Arthur C. Clarke
…On Sun, May 5, 2024 at 04:35 Mark ***@***.***> wrote:
I don't think it will as it seems to use that URL in the page, so it would
point to localhost on the computer where the page is open.
When I start to get the flickering of the webcam is also when the previews
stop appearing on the display and I get a white square instead.
—
Reply to this email directly, view it on GitHub
<#531 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHT66CXYOPNKWJKKHJIJF3DZAX4NHAVCNFSM6AAAAABGY4ASTGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGMJYHA3DM>
.
You are receiving this because you authored the thread.Message ID:
<Guilouz/Creality-Helper-Script-Wiki/repo-discussions/531/comments/9318866
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Looks like I missed the camera restart macro, I initially disable all from the web GUI as there was way to many, so all good for me, mine still occasionaly goes down but the restart macro fixes it up. Still cant get the camera to put out a descent frame rate though. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah the framerate is garbage on both of mine (Seems to be a newer lens or
camera on my 12/23 production date vs my 2/23 printer)
…On Fri, May 17, 2024 at 3:31 AM NexGen-3D ***@***.***> wrote:
Looks like I missed the camera restart macro, I initially disable all from
the web GUI as there was way to many, so all good for me, mine still
occasionaly goes down but the restart macro fixes it up.
Still cant get the camera to put out a descent frame rate though.
—
Reply to this email directly, view it on GitHub
<#531 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHT66CX3GOFNYP72DK23NOTZCW545AVCNFSM6AAAAABGY4ASTGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINRXGU3DA>
.
You are receiving this because you authored the thread.Message ID:
<Guilouz/Creality-Helper-Script-Wiki/repo-discussions/531/comments/9467560
@github.com>
--
Joel M. Gabel
"Any sufficiently advanced technology is indistinguishable from magic." -
Arthur C. Clarke
|
Beta Was this translation helpful? Give feedback.
-
|
Have you looked at this discussion here? #508 I've been working on the camera issues for months now with little success. We should join forces! haha I had to stop testing for now because I found a defect in my K1C heater core (the mount flanges sheer off way too easily) and am awaiting warranty replacement parts shipping from Creality. |
Beta Was this translation helpful? Give feedback.
-
|
Oh that’s a whole new set of issues. Mine was completely fluidd based.
Joel M. Gabel
"Any sufficiently advanced technology is indistinguishable from magic." -
Arthur C. Clarke
…On Fri, May 17, 2024 at 10:09 TheWebMachine ***@***.***> wrote:
Have you looked at this discussion here? #508
<#508>
I've been working on the camera issues for months now with little success.
We should join forces! haha
I had to stop testing for now because I found a defect in my K1C heater
core (the mount flanges sheer off *way* too easily) and am awaiting
warranty replacement parts shipping from Creality.
—
Reply to this email directly, view it on GitHub
<#531 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHT66CU2HTBLFXNUNYQ7WWDZCYMSNAVCNFSM6AAAAABGY4ASTGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINZSGA2TK>
.
You are receiving this because you authored the thread.Message ID:
<Guilouz/Creality-Helper-Script-Wiki/repo-discussions/531/comments/9472055
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I managed to get to the bottom of my issues and it manifested in a completely different way. I saw these laser messages in the device manager log and I noticed their timing coincides consistently with the USB disconnect message in the system dmesg logs. ==> /usr/data/creality/userdata/log/device_manager.log <== ==> dmesg_2.log <== As an experiment I disconnected the lidar sensor and the problem went away, like in no more camera failure. So it seems the lidar connecting disconnecting eventually results in the camera_app terminating and resulting in the camera stream going dead and the only recovery from that is a complete system reboot. I am getting a new LIDAR under warranty. |
Beta Was this translation helpful? Give feedback.
-
|
Keep an eye on it and report back, for sure. In my thermal tests, I was getting USB disconnects in dmesg too, but I have the K1C with no lidar at all. It may be an issue, in general, with the USB controller or kernel module for it, if both lidar and camera were experiencing issues at the same time. While I can't speak for the OG K1, I'm pretty sure the K1C and K1 Max are using the same mainboard. |
Beta Was this translation helpful? Give feedback.
-
|
I think the camera_app controls both lidar and webcams and if you look at the bottom of the lidar unit there is actually another camera in there too. The mjpeg-streamer doesnt get a direct camara feed, it looks at a file system provided by camera_app, so if you kill camera_app you should in theory be able to run mjpeg-steamer independently without the need of camera_app, but then if you interrogate the camera with v4l2, you dont get a normal usb camera and this is where I got stuck, I cannot figure out how to get mjpeg-streamer to run the video stream directly without the intermediate camera_app. Maybe you found something I could not figure out so far, if so please share your insights and let's dump it in a wiki. |
Beta Was this translation helpful? Give feedback.
-
|
Wow! That worked. The camera was failing < 3 mins in. Now I am over 1 hr in and it is still working. Thanks for the efforts. |
Beta Was this translation helpful? Give feedback.
-
|
So another case of LIDAR malfunction manifesting camera failure? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting as the first thing I did was remove the lidar assembly from
both my K1Max’s…. Good catch on your diagnosis!
Joel M. Gabel
"Any sufficiently advanced technology is indistinguishable from magic." -
Arthur C. Clarke
…On Fri, May 17, 2024 at 12:06 jattie-ire ***@***.***> wrote:
I managed to get to the bottom of my issues and it manifested in a
completely different way.
I saw these laser messages in the device manager log and I noticed their
timing coincides consistently with the USB disconnect message in the system
dmesg logs.
==> /usr/data/creality/userdata/log/device_manager.log <==
[2024/05/05-17:14:07:241303]-[INFO]-device_manager.c <http://494>
laser_set_state: ubus_notify: {"laser_plugged":0}
[2024/05/05-17:14:07:777128]-[INFO]-device_manager.c <http://494>
laser_set_state: ubus_notify: {"laser_plugged":1}
==> dmesg_2.log <==
2024-05-05T17:14:07,326819+01:00 usb 1-1.1: USB disconnect, device number
35
2024-05-05T17:14:07,533828+01:00 usb 1-1.1: new full-speed USB device
number 36 using dwc2
2024-05-05T17:14:07,633578+01:00 usb 1-1.1: New USB device found,
idVendor=1a86, idProduct=55d3
2024-05-05T17:14:07,641104+01:00 usb 1-1.1: New USB device strings: Mfr=0,
Product=2, SerialNumber=3
2024-05-05T17:14:07,649475+01:00 usb 1-1.1: Product: USB Single Serial
2024-05-05T17:14:07,654369+01:00 usb 1-1.1: SerialNumber: 5719024095
2024-05-05T17:14:07,660514+01:00 cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
As an experiment I disconnected the lidar sensor and the problem went
away, like in no more camera failure.
So it seems the lidar connecting disconnecting eventually results in the
camera_app terminating and resulting in the camera stream going dead and
the only recovery from that is a complete system reboot.
I am getting a new LIDAR under warranty.
—
Reply to this email directly, view it on GitHub
<#531 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHT66CVUQZ3GFBFM3MPKF6DZCY2LFAVCNFSM6AAAAABGY4ASTGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINZTGMZDE>
.
You are receiving this because you authored the thread.Message ID:
<Guilouz/Creality-Helper-Script-Wiki/repo-discussions/531/comments/9473322
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Took me a few weeks of diligent slog work. The flavour of Linux on the K1 is quite strange and non standard, but I managed to get a decent way into figuring it our, but the camera part is still a bit of a mystery. |
Beta Was this translation helpful? Give feedback.
-
I think this is totaly my issue with K1C, I only print ABS, and I have it fully enclosed with almost no way for heat to escape, chamber will get over 60C after a few hours and the camera always craps itself in the middle of long prints, I will look at a thermal solution for it. I have had many issues with cameras dying from heat, all of my nozzle cams die quite quickly, I have collection going, and a number of RPI cameras all dead, these all came out of my machines with active heated chambers. Ill test mine and report back if I see any improvments. |
Beta Was this translation helpful? Give feedback.
-
|
Also, I still occasionally get a camera fail on super long prints, but the frequency has dropped substantially. Unfortunately, with the positioning in the enclosure, there is not an easy way to add more cooling to it beyond the basic heatsink and cover cut out without heavy modifications to the mount, the enclosure, or both. |
Beta Was this translation helpful? Give feedback.
-
|
(I started mocking up a new camera enclosure with 1/8" water cooling loop and then snapped back to reality. 🤣) |
Beta Was this translation helpful? Give feedback.
-
I was not aware of a nozzle cam. It's this something you retrofitted or do I have one and just don't know about it? |
Beta Was this translation helpful? Give feedback.
-
It's only on the K1 Max as part of the lidar assembly. Not the K1C, if you have that one. |
Beta Was this translation helpful? Give feedback.
-
|
I have a K1 max too. So can I view the nozzle cam or is it used by lidar and AI features only? |
Beta Was this translation helpful? Give feedback.
-
|
Let me see if I can design something, I think the angle on the camera is also garbage, so I may as will make a new enclosure with some adjustment. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, something adjustable that might allow room for something like a little 20mm fan back there - like these that could maybe even be powered from the cam's own 5v line: https://a.co/d/iU9QUZR I couldn't find any reliable source for 15mm fans, which would be a better fit; they just aren't commodity enough at 15mm to be readily available. However, keep in mind the reach of the gantry. The cam is already SUPER close to the extruder at the far end of the X axis. Creality also screwed the pooch with clearances of the rear corner steppers cuz you can totally run into them with the extruder and shift the known position if you aren't careful with super large prints, but I digress. My design skills begin to wane the smaller the parts, so you'll certainly come up with something way better than I could. haha |
Beta Was this translation helpful? Give feedback.
-
|
Im pretty clever with things like this, I'll use a 20x6 mini blower from GDStime, I use these on my custom JetStream cooler for Nema14 rounds. |
Beta Was this translation helpful? Give feedback.
-
|
Nice! |
Beta Was this translation helpful? Give feedback.
-
|
This should do the trick, Ill run the fan from auxillery blower output, as I have removed that from my machine and it now runs an active filter, this little blower can run at the same time as I print with the filter running at all times.
|
Beta Was this translation helpful? Give feedback.
-
|
Good job on the design, looks great. Two thoughts:
|
Beta Was this translation helpful? Give feedback.
-
|
So, since the lidar is part of another camera assembly on the Max, perhaps it is that camera that is dying and killing the connection for the lidar, as well. These cameras have an SoC that is rather impressive for its size. dual-core MIPS 1.2Ghz, 1 or 2GB of DDR2 RAM, separate image co-processors, USB controller, etc. That's a lot for such a small package to not be cooled in any way. At idle, open chamber, not printing, just feeding video, outside of its own enclosure, the SoC in the chamber camera gets to about 60°C! In its own enclosure, it climbs even higher than that...then you start printing with a build plate sitting right underneath it, let alone enclosing it for things ABS. I suspect the problem is exponentially worse on the hotend lidar/camera assembly.
And what happens when a CPU/APU/SoC gets too hot? PC Overclock enthusiasts will know that that is when things get glitchy. As best I can tell so far, once the SoC gets above a certain internal temp, everything starts glitching. Frame rates drop first, as the SoC attempts to down-clock, but this still isn't enough. So, it just hits a ceiling and eventually the USB controller glitches and resets (I think), killing the connection. Part of the issue may be that the software side of things doesn't handle this reset gracefully, preventing the cam[s and lidar] from recovering until reboot. So, yes, the handling of the issue is likely flawed in software (typical Creality), but the issue seems to begin with thermal overload glitching out the hardware first. It also explains why the lidar/camera assembly has needed replaced so many times for some Max users; repeated extreme thermal stress is going to eventually complete kill the SoC[s] permanently. |
Beta Was this translation helpful? Give feedback.
-
|
The "moral" of this story is, I think: 3D printing needs a new camera design methodology to account for the thermal shortcomings of most of the current "off-the-shelf" camera modules out there. Even standard CMOS-based camera image sensors are going to degrade from the heat over time, which surely accounts for some camera failures people experience. |
Beta Was this translation helpful? Give feedback.
-
|
Ive just ordered in a new 5v 2006 blower from GDSTime as I cant find the one I had kicking about, It will be a week or so before I can test it.
|
Beta Was this translation helpful? Give feedback.
-
|
Nice! 😯 |
Beta Was this translation helpful? Give feedback.
-
|
Okay, sorry for the long wait, I had multiple nozzle blockage's which turned into a completely destroyed hotend, not a fan of the heater setup and the full length Nozzle, mostly pointless as it flows no better than a standard V6, I tried everything to eliminate nozzle seizing inside the heater, thermal paste, anti-seize, Copper based anti-seize and now I'm using high temp brake calliper slide grease, such a stupid design, well I digress. Here is the camera mod, and it works, no more lockups, even when printing PC-CF: Printables: K1C Camera Mod YouTube: K1C Camera Mod |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Thanks for the work on this. I'll get one printed and a fan ordered and see how it goes for me. I'm gonna see about powering the fan off the camera's 5v USB rail for a cleaner install. Since the fan is only rated 100mA, it shouldn't be an issue since the T31 chip is also rated at less than 100mA; the rest of the camera components surely aren't gonna pull another 300mA to overload the 0.5A of the USB2 port. My only concern is potential noise on the VCC, but I doubt it will be an issue. 🤞 In your experience with these fans, how's their lifespan? I'm hoping to find a source other than AliEx (I have the worst luck with them.), but if I can't I'm just curious how many I should order to have spares. 😎 |
Beta Was this translation helpful? Give feedback.
-
|
Im running it off the camera power now, the fan is 5v, no issues so far, Camera hasn't stop at all, its been 100% stable, normally 15mins and its dead every print. Second black wire in on the plug is ground, red is 5v. GDSTime fans are awesome, its all I use now, I was using Sunon Maglev, but they dont make them in a wide range, the dual ball bearing ones from GDStime are 99% as good as Sunon Maglev and are rated for long term use. |
Beta Was this translation helpful? Give feedback.
-
|
i installed creality helper recently and noticed this camera issues also , i only print with pla. and have one additional cam installed. its working but after a while it disconnects. the only thing to get them back is to run /etc/init.d/S50usb_camera restart on my k1. 10 seconds after that the cameras are back online. |
Beta Was this translation helpful? Give feedback.
-
|
Since installing the cooling fan, I have never seen the camera fail, not even once, it was definately heat related for me, I print ABS and Polycarbonate constantly in mine, so high chamber temps, my camera use to fail withing minutes every single time, even restarting the camera would result in it failing rapidly straight after. |
Beta Was this translation helpful? Give feedback.
-
Camera suddenly stop working in Fluidd
Settings > Camera > Click your camera and change the following values
Camera Url Stream: /webcam?action=stream
Camera Url Snapshot: /webcam?action=snapshot
Use the full URI structure!
Please be sure to replace the ip address with the IP of your printer!
Camera Url Stream: http://XXX.XXX.XXX.XXX:4409/webcam/?action=stream
Camera Url Snapshot: http://XXX.XXX.XXX.XXX:4409/webcam/?action=snapshot
Credit to: morriscode (https://www.reddit.com/user/morriscode/)
Beta Was this translation helpful? Give feedback.
All reactions