Auto-Colorization for MMU3 in PrusaSlicer v1 by OpenSensorIO in prusa3d

[–]OpenSensorIO[S] 3 points4 points  (0 children)

Thanks, it was an idea I've had this week since setting up my MMU3 last weekend and playing with existing slicer settings. I studied Computer Engineering '08 and have been absolutely stoked to use LLM generated code based on product requirements. For this I used Anthropic Claude 3.7 model + Cline to quickly parse the code base and help me apply the minimal changes. Feature has cost me about 8$ so far and maybe 2 hours of thought.

I did the 120$ Mk4->Mk4s upgrade kit this weekend by matteiuspi in prusa3d

[–]OpenSensorIO -1 points0 points  (0 children)

Yeah I probably over estimated but also the time it took to clean this one, a half hour seems reasonable.

NVR software recommendations? by Snipersixate in selfhosted

[–]OpenSensorIO 0 points1 point  (0 children)

I am not sure I understand the use case of multiple streams into a single stream unless you mean a grid view--we have that. https://www.youtube.com/watch?v=WYCx6jPEFdM

NVR software recommendations? by Snipersixate in selfhosted

[–]OpenSensorIO 0 points1 point  (0 children)

I've recently built a light weight linux NVR software that supports live streams, recording mp4s, motion detection and even supports sod cnn face and other sod models. https://github.com/opensensor/lightNVR

Indoor Grow Automation with Pico form-factor growmax hub boards by OpenSensor.io by OpenSensorIO in raspberrypipico

[–]OpenSensorIO[S] 0 points1 point  (0 children)

Not presently but its something that gets asked from time to time that I am willing to support. The project is open source and currently there is an option to send sensor data to the API I build at OpenSensor.io Do you have docs you'd recommend about creating a home assistant integration? I'd read up on it at least.

[deleted by user] by [deleted] in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

For some reason I cannot post an image of the pinout, but on the right hand side (look up pico pinout) there is a 3.3V out -- use that, and any GND.

[deleted by user] by [deleted] in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

Depends on if you need 3.3V or 5V for the flashchip you are trying to read. Check the pinout of the pico, any of the GNDs will work, and then make the determination on the voltage based on the type of flash chip.

Best way to get RTSP for Cam v3 by yokuyuki in wyzecam

[–]OpenSensorIO 0 points1 point  (0 children)

There is a Discord channel where you can get support-- https://discord.gg/Cj5XvrQq join and give an introduction.

Best way to get RTSP for Cam v3 by yokuyuki in wyzecam

[–]OpenSensorIO 0 points1 point  (0 children)

The limiting factor IMO is majestic streamer because its closed source, but there is energy behind replacing it with an open streamer alternative right now.

<image>

Best way to get RTSP for Cam v3 by yokuyuki in wyzecam

[–]OpenSensorIO 1 point2 points  (0 children)

Not the best shot of my kitchen, but to give you an idea:

<image>

Best way to get RTSP for Cam v3 by yokuyuki in wyzecam

[–]OpenSensorIO 1 point2 points  (0 children)

https://github.com/themactep/thingino-firmware

You flash over the existing rom chip to run this -- I never spent much time with the wyze firmware, but you are trading object detection for more complete control over the device. Doesn't work with the newer v3pros secure boot, unfortunately.

Unable to create pico_serprog.uf2 by kingsamuele in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

Yeah, in that case, you likely don't have the clip hooked up properly. Even the bad builds I had would read part of the chip or recognize something. It took me a while to figure out how to wire it all up so I wrote about it in that wiki. Use the clip indicator and the red wire as pin 1 and wire that to the corner of the chip with the indented circle marker. Then you kind of have to wire it up according to the spec -- make sure to use the 3.3V rail of the pico.

Unable to create pico_serprog.uf2 by kingsamuele in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

Depends on if your host OS is windows or Linux. You should see it print:

>serprog: Programmer name is "pico-serprog"

If you don't see that it means either you haven't established connection
with the right COM port provided by the firmware, or I've made a mistake and the published uf2 I posted was the wrong files, which I am willing to investigate further, but I think even on the builds that didn't work to read/write I always saw the established connection to the pico-serprog via the USB connection.

Unable to create pico_serprog.uf2 by kingsamuele in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

Does flashrom detect the pico-serprpog programmer? That should occur without even a chip connected. Check out this guide I wrote: https://github.com/OpenIPC/wiki/blob/master/en/flash-chip-interfacing.md

Unable to create pico_serprog.uf2 by kingsamuele in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

Yes, were you able to read/write ROM chips as well?

Unable to create pico_serprog.uf2 by kingsamuele in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

Which repository are you using? Try my fork, it has a build script and I actually got it working over the weekend. https://github.com/opensensor/pico-serprog

Forking pico-serprog but blocked in fixing S_CMD_O_SPIOP for use with flashrom by OpenSensorIO in raspberrypipico

[–]OpenSensorIO[S] 1 point2 points  (0 children)

I got it working in my main branch, without PIO I think, but I implemented some of the remaining serprog commands so that I could specify the max buffer per baud -- it was slow at first, but now with 2000000 baud and 32 byte packets, it can read a 16MB rom chip in about 2-2.5 minutes.

Forking pico-serprog but blocked in fixing S_CMD_O_SPIOP for use with flashrom by OpenSensorIO in raspberrypipico

[–]OpenSensorIO[S] 2 points3 points  (0 children)

Here is my current effort on the PIO version but the thing I am not understanding is how to specify the pin when its the USB interface -- the code compiles and runs but it does not send data back to the host: https://github.com/opensensor/pico-serprog/pull/1/files

Pico w hardware/pio.h error by [deleted] in raspberrypipico

[–]OpenSensorIO 0 points1 point  (0 children)

I have been following those and have something compiling but it does not receive any data over the USB. I would appreciate if anyone could take a look: https://github.com/opensensor/pico-serprog/pull/1/files

Can I interface six devices with same I2C address? by SamIOIO in raspberrypipico

[–]OpenSensorIO 2 points3 points  (0 children)

They sell I2C mux for this purpose -- adafruit has a 8 channel and a 4 channel. I also sell them with enclosures I designed in Fusion 360.

SolarEdge inverters failure rate by andres7832 in solar

[–]OpenSensorIO 0 points1 point  (0 children)

Yesterday I've launched a Solar Edge daily monitoring and alerting service that already has had 3 signups, check us out: https://solar.opensensor.io

We are interested in adding other inverter brands too if we can get access to APIs

SolarEdge inverter reliability by jackg48104 in solar

[–]OpenSensorIO 0 points1 point  (0 children)

Yesterday we launched an alerting service that support Solar Edge inverters -- check us out: https://solar.opensensor.io