u/Relevant_Tax_6814

Been spending the last few months learning more about low-level C++ and Windows APIs, and this project slowly turned into a full storage analysis utility.

The main thing I wanted was a system tool that:

• stays responsive while scanning
• visually shows what’s taking space
• doesn’t feel overloaded or ancient

Current features:

• visual disk usage mapping
• large file detection
• cleanup utilities
• ImGui-based interface
• optional memory cleanup tools

A lot of the work went into multithreading, UI responsiveness, and trying to make the experience feel smoother than the usual system utilities on Windows.

Still early in development, but finally at a point where it feels usable enough to share.

Would love feedback from people into:

• C++
• Windows internals
• ImGui
• optimization
• UI/UX

https://preview.redd.it/cblgrkft064h1.png?width=1920&format=png&auto=webp&s=749a30ce148c163a2f9b026aa34ea5848d4b4ab6

GitHub: https://github.com/Gurates/ByteMap

Hey everyone,

I’m working with my FRC team and we’re thinking about using custom PCBs for cleaner wiring, especially for CAN line distribution and signal routing.

I’m not very sure how common custom PCBs are in FRC or what rules/restrictions we should follow.

So I wanted to ask:

• Are custom PCBs commonly used in FRC?
• Any rules we should be aware of?
• What are the main risks for CAN/signal boards?
• Any best practices for reliability?

We’re not trying to replace official components, just reduce wiring complexity and improve robustness.

Any advice or examples would be really helpful

Thanks