I have never heard the phrase “runs on the edge”, and the article uses some form of it a half times.
My only results for “edge devices” refer to networking. Is that what they’re trying to say?
Submitted 1 day ago by cm0002@lemmy.world to 3dprinting@lemmy.world
I have never heard the phrase “runs on the edge”, and the article uses some form of it a half times.
My only results for “edge devices” refer to networking. Is that what they’re trying to say?
It’s referring to edge computing, and can be thought of as essentially saying “self hosting”.
It’s usually an IoT (Internet of Things) term that signifies that something runs on the end device. These are hardware constrained devices that would otherwise just send their data somewhere else to be processed, but in this case they’re doing the processing.
Article sounds AI written to me.
Devices like Intel MyriadX inside of a camera would be considered edge devices in this application.
github.com/luxonis/…/OAK-D-Pro_Datasheet.pdf
I’ve got an original OakD camera but haven’t tried to use it yet, was a gift at a convention a few years back. Pretty interesting device overall.
Yes. Kind of implying you’d be able to run it on a reverse proxy without undue security considerations.
Don’t have octoprint and not sure I’d be ready for it to abort my prints for me just yet. I use a security camera. Would be nice if it could just screengrab the feed from my desktop and send an email or sms alert if something looked off.
Klipper actually has this built in now - you can setup telegram notifications with snapshots when prints fail or even just at certain layer heights, no need for octoprint or other complex setups if your alredy running Klipper.
@Imgonnatrythis @cm0002 octoprint has a useful Telegram plug in so i can see my print updates on my phone. I'd recommend
I can already access that info via prusa app
Down anyone know of it works with belt printers? I had it, but it kept restarting some prints that were fine and never detected a failure :(
My suspicion would be that belt printers were not in the scope when writing it. Probably a good idea to open an issue in GitHub so that they can fix it.
fmstrat@lemmy.nowsci.com 7 hours ago
Since the article doesnt provide any useful links: github.com/oliverbravery/PrintGuard
I just aet up Obico self-hosted via Docker, so I may give this a go in Docker running alongside it. Can’t hurt to have two methods of failure detection.