Search results

The undercut is to clear the surface mount components on the other side of the sensorboard. Yes it's a tad harder to print because of this, but not sure what the alternative would be.

This is the "denoising" that is eating all the grain in the shadows. I've turned some of it off, the frame to frame denoising, but not the spatial denoise. The alternative lens helps a big, but here is not control for this.

As I don't have a Type D, I don't know what they have changed. On all three previous models the LCD buffer was at 0x81821180. This is used in hist.c (in the repo.) uint8_t *LCD = (uint8_t *)0x81821180; // All types The size of the LCD buffer is 480x864 (vertical), and is 8-bit palette mapped...

All my code changes additions are between 338f28 - 340008. However these are dozens of changes in the rest of the firmware to branch the old code to run the new additions. You will need to diff the stock type C with v7.7 Type C, to see all these changes and do the equivalent. But this will be...

This is base version (type D) that has creates code space by resizing and removing one of the JPEGs in the firmware. Can you confirm it still works and shows a changed boot screen? Things have move around a lot in Type D. This is no other chances, so only for @videodoctor

I'm away for this weekend, so take the UITRON.BIN and decompress if with ntktool (from dashcamtalk). You can then compare with the .rbn files from each previous model. You can install any version to test. Rename you saved UITRON.BIN back to FWV280.BIN to restore if necessary.

No updates for type D, yet D2825 units are not type D, I have one that runs Type B firmware. As we have imaged all known models, you can proceed with the firmware update (as all are reversible, including D2825 units.)

Seems like one of the cables is not restored correctly. The main power LED is only white. You could see if you have console output. When you plug the USB port the COM port is created. In Device Manger see which port is added (Reels unit doesn't power at this point, the COM port is ported...

I modified @Deano 's new lens cover to be more FFF printer friendly, and fit the larger mounting lens offset bracket I'm using. While not as pretty as your MSLA output, it is nice enhancement to the unit's look.

Here are two example of mounting on the inside of the unit. Last one was mount on the right rear side so the cable was well clear of the motors. The hole was made using a soldering iron and exacto knife. The Arduino board is mounted to the case using Sugru, silicon moldable rubber glue...

I always zoom in to the maximum, that way the LCD resolution is not an issue.

Just short RST to GND, and TX on the main board goes to TX1 on the Nano, same for RX to RX0 and GND to GND.

Great post. I have stopped using the 3mm F-stop change, while it does make focusing easier (not required), and it does add some vignetting. Without FOV correct, the shading is almost flat for the 12mm lens. With the 3mm aperture correction, the vignette start to show with the darker corners.

It is probably okay. I didn't follow the guide exactly, and used whatever I had around.

The existing USB port has a different function, it is not connecting to the debug interface that's on the main board. I just added serial ports using an Arduino nano with USB-C to two units yesterday, helping a friend do it. This is what I used https://a.co/d/5uqn1jQ

Thank you. I have attempted to get an H2825 model from eBay, but many sellers will not respond to enquires about serial number (even ask for only the first 5 characters.)

If you can add the serial port, then you can dump the firmware, this must be before any update attempts (if you want exactly what your firmware contains.) A serial port is extremely helpful for any development you want to try. We do know there are type D units out there, and it seems that only...

Yes, that would appear to be type D. Through which seller do you buy this?

Anyone want to sell me their H2825 unit?

Now for the weirdness of D2825 units. This is different firmware (then I have seen, doesn't match any of @Mac84 originals), but it only so slightly different, as it seems to have a small code patch to Type B, yet Type B firmware works as is. It has 8 bytes more code at 0x1042C8. Just: There...