ESP32Cam -- Software and lighting options
Got an ESP32Cam for my Core One and am currently printing Rainer's very nice custom enclosure for it. While the printer is busy, I am wondering about the best software option:
- Integration with PrusaLink would have been my preference, but that is apparently not supported. I wonder why? Integrating a video stream from a separate web server (the ESP32) into the PrusaLink HTML page should be straightforward for the developers, and it would not cause any CPU load or data traffic on the xBuddy CPU. Has there been any discussion about a future PrusaLink implementation, or any hack that makes this possible?
- PrusaConnect integration is what Prusa supports officially. Does it mean the same limited frame rate (one image every 10 seconds) which we get from Prusa's Buddy3D camera?
- I could just use a separate web browser window to monitor the camera feed. Does the Prusa camera firmware support this mode, or should I use a different firmware on the camera in this scenario?
Also, how do you provide illumination for the exposures? Via the camera's built-in LED? (Does it survive continuous operation?) Or via the Core One's LED strip -- presumably after setting it to always-on, no-dimming mode?
Thanks for your advice!
RE: ESP32Cam -- Software and lighting options
I use the ESP Cam32 in Prusa Connect.
With Prusa, I also have no concerns about the cloud.
Yes, even with the ESP Cam it is only with single images.
However, a live mode has also been announced for the Buddycam, but I guess it's not a high priority.
To be honest, it's enough for me. Every now and then a picture to check if it prints and everything on the plate is ok.
The Prusa software for the cam also has a live stream but I don't really use it.
I use the LED as a flash for the lighting. It's enough for pictures only.
But it's not made for continuous operation.
When I want to watch the printer, I sit in front of it 😍
RE:
https://github.com/prusa3d/Prusa-Firmware-ESP32-Cam
has some good information on the various flavours and some of the issues with the camera.
The camera integrates okay with Prusa connect. I find the website more reliable than the app for some reason when it comes to the camera.
You can go onto the camera directly from inside your network prusa-esp32cam.local should work. You can setup most of the settings and even 'live' stream from it.
I've not used the integrated LED but reports on the github that it doesn't use a current limiting resistor and can cause problems. There are various solutions to the problem (basically wire up an external LED of some sort).
Personally I've found it to be a bit flakey. I'm not sure on the problem (i should stick an SD card in it and get some logs) but either it is overheating or the wifi drops out sporadically. I've not had a chance to investigate.
I've ordered some parts to experiment with. A wider FOV camera with a longer cable, an external wifi antenna and a couple of small servo motors. One option I am considering is moving the ESP32 outside the enclosure and having the camera be the only thing inside and having the camera directly attached to an actual heatsink. I would also like the esp32 to be the brains for a servo controller for the vent. In theory you could add code to the esp32 to read the material from PrusaLink and then close/open the vent as required. Again it is also in a good place to control some addressable LED's.
RE: ESP32Cam -- Software and lighting options
Thank you both! I have installed my ESP32Cam now, programmed with Prusa's firmware. The HTML-based setup pages for the camera look quite professional and comprehensive. While the video stream (viewed in a separate browser tab) works fine, I am concerned about overheating of the camera, so I might switch to PrusaConnect.
For lighting, the camera's built-in single LED seems too wimpy to give usable images. The printer's LEDs are bright enough, but it looks like I will have to disable the auto-dimming. Or can operation via Prusa Connect turn them on briefly for each exposure of the camera?
RE: ESP32Cam -- Software and lighting options
I don't think there exists an ability to control the LED brightness on the printer remotely, however if you are wanting to check on the print then the LED's would need to be on and depending on the frequency of imaging this could be quite distracting (imagine the lights on your printer pulsing for 200ms to full power every 5-10 seconds)
Thank you both! I have installed my ESP32Cam now, programmed with Prusa's firmware. The HTML-based setup pages for the camera look quite professional and comprehensive. While the video stream (viewed in a separate browser tab) works fine, I am concerned about overheating of the camera, so I might switch to PrusaConnect.
For lighting, the camera's built-in single LED seems too wimpy to give usable images. The printer's LEDs are bright enough, but it looks like I will have to disable the auto-dimming. Or can operation via Prusa Connect turn them on briefly for each exposure of the camera?
RE: ESP32Cam -- Software and lighting options
Personally I've found it to be a bit flakey. I'm not sure on the problem (i should stick an SD card in it and get some logs) but either it is overheating or the wifi drops out sporadically. I've not had a chance to investigate.
This has been my experience too, so I'd be interested to see what your experiments bring. I've tried a couple of different brands of ESP32 camera, but I find that I can get them set up and working initially but after a short while they just stop working. On one of them I changed the solder link on the ESP32 antenna so as to be able to attach an external wifi antenna, but it made little difference. And in any case my printer is only a short distance from the mesh wifi node, so wifi signal strength shouldn't be an issue, even inside the printer and with a couple of other Prusa enclosures in between. I've also made sure to use the supplied heatsinks, but my testing was all with a cool printer, so if the problem is heat related then it will surely struggle when printing ABS/ASA.
I've now switched to a Tapo C110 for which I've made a magnetic corner mount similar to the buddy cam mount. It works fine inside the printer enclosure, even in high temperatures, and provides streaming video via the Tapo app on my phone. I'm planning to experiment with the mount though, so that I can manually adjust the pointing angle. It's just a shame that the Tapo needs a separate 9V supply via a barrel jack, rather than the USB-C cable that I've already routed.
RE:
I find that I can get them set up and working initially but after a short while they just stop working. [...]
I've also made sure to use the supplied heatsinks, but my testing was all with a cool printer, so if the problem is heat related then it will surely struggle when printing ABS/ASA.
Temperature is certainly an issue I am nervous about. The ESP32 Wifi module on its own is quite a power hog and its radiation shield does not seem to be designed with heat dissipation in mind. And the little camera runs quite hot too, already after a short runtime.
Combined with the elevated chamber temperatures, this may well make the ESP32Cam unsuitable for use in an enclosed 3D printer. I will try my luck with a slow frame rate and see how that goes.
An ideal design would have both, the ESP32 and the camera chip, thermally coupled to the printer's frame profile. (Directly or via a metal base plate.) But the standard board layout of the ESP32Cam does not lend itself to that, I'm afraid. Are there compatible camera modules with slightly longer flex cables?
RE:
Aliexpress has a large range. If you search for esp32 cam you'll find plenty of them or if you search for ov2640.
The longest I've seen is 75mm for the cable which should be long enough to get the camera inside and the esp32 outside.
Oh and some of the camera modules have the ir filter removed. This presents an elegant solution for imagin without the printer constantly glowing like Vegas as you could use an IR led to illuminate the printer whixh you couldn't see, but the camera will.
Another idea I'm trying with is to remove the radiation shield completely and attach a heatsink to it, pending what is actually causing it to fail.
The esp32 has an operating range up to 105C apparently (might exceed that when running in a 50C environment) however the ov2640 is up to 70C and given it is noted to get hot in ambient conditions, stuck in an enclosure that is already at 35-50C could easily cause it stability issues.
I'm kind of looking forward to troubleshooting it tbh. Just need to get some logs and do more printing.
RE: ESP32Cam -- Software and lighting options
I have also printed ASA several times with a chamber temperature of 55 degrees without any problems.
I was also worried about it getting too hot at first but I think 85 degrees was the highest I've seen.
RE: ESP32Cam -- Software and lighting options
Which esp32 variant did you use?
RE: ESP32Cam -- Software and lighting options
I wonder whether the temperature issue is the real reason why the Buddy3D camera can only operate at 0.1 fps? It might have a better heatsink inside, but it's still in a passively cooled plastic housing -- so they can't work any power dissipation magic when streaming video continuously.
RE: ESP32Cam -- Software and lighting options
I don't think that's the reason. The normal Buddy camera also has this limitation.
I think it's more because of the cloud and the associated traffic.
But at the beginning I think a local live mode was announced.
Unfortunately it always takes a little longer with Prusa. I didn't see any added value in the buddy cam.
That's enough for me with the ESP32.
From time to time it stops responding, but that's independent of the temperature.
I've been following the project from the very beginning, when there was no official Prusa version. Since then the reliability has improved a lot.
For timelapses or similar, I would prefer a high-quality camera anyway.
I wonder whether the temperature issue is the real reason why the Buddy3D camera can only operate at 0.1 fps? It might have a better heatsink inside, but it's still in a passively cooled plastic housing -- so they can't work any power dissipation magic when streaming video continuously.
RE: ESP32Cam -- Software and lighting options
I don't think that's the reason. The normal Buddy camera also has this limitation.
I think it's more because of the cloud and the associated traffic.
But at the beginning I think a local live mode was announced.
Unfortunately it always takes a little longer with Prusa. I didn't see any added value in the buddy cam.
That's enough for me with the ESP32.
From time to time it stops responding, but that's independent of the temperature.
I've been following the project from the very beginning, when there was no official Prusa version. Since then the reliability has improved a lot.
For timelapses or similar, I would prefer a high-quality camera anyway.
I wonder whether the temperature issue is the real reason why the Buddy3D camera can only operate at 0.1 fps? It might have a better heatsink inside, but it's still in a passively cooled plastic housing -- so they can't work any power dissipation magic when streaming video continuously.
I am in the same boat. I just want to be able to check my print. I do not need 4k quality. It is good to get understanding from someone who has more experience of it.
From my side i am happy with the esp32 cam. My prusa mini will be getting used for pla parts by my wife for boardgames so I have ordered another for her.
RE: ESP32Cam -- Software and lighting options
So I got a 160 degree camera to upgrade the default and it provides a much better view over stock. Perhaps even a little too wide. This one is IR sensitive and should see 850nm light. I just need to have a root around my bits box and see if I have any IR LED's to test it with.
RE: ESP32Cam -- Software and lighting options
i buy this stripes and connect togehter to the prusa powersupply ... but check, not to much power 🙂
RE: ESP32Cam -- Software and lighting options
I'm going to rescind my previous comments about the camera being flakey. I think it's prusa connects integration with webcam thst is the issue. Ive just been going to the cameras local site and it works perfectly, seemingly 100% of the time.