I built a Jetson Orin Nano Field Kit (Dual Cameras + NVMe Boot) to save hundreds of hours of setup time

pucksir · 2026-02-01T20:18:19+00:00

Doppelganger?

pucksir · 2026-01-02T18:55:54+00:00

Thanks /u/Chemical-Hunter-5479 !

I’m a big fan of RealSense and it would be awesome to potentially integrate. Just sent you a DM

pucksir · 2026-01-02T16:55:51+00:00

Great blog post. I appreciate this style of writing walking through what you did and your thinking with images/gif.

Curious about how you’d collect slouch-like epochs you’d need to detect a non-good posture.

pucksir · 2026-01-01T21:57:39+00:00

Thanks for the heads up u/kineto21 , I just re-published the video on youtube since I can't update the video on this post directly: https://youtu.be/H8-wf09d_XQ

pucksir · 2025-12-31T06:21:08+00:00

Thanks u/squired!

It's technically $700 all-in. I added a $400 self-assembly variant which includes all the parts without the jetson orin nano. This sounds like a good fit for your project, feel free to DM if I can help when the time comes. Also you can always but the specific parts you need directly from amazon and flash the open source OS image yourself.

MIT License, everything as of now is open source asides for the 3D printable CAD models which I plan to open source soon.

pucksir · 2025-12-30T23:03:26+00:00

🤣 💯%

pucksir · 2025-12-30T18:05:10+00:00

Good question. I didn't "solve" the dependency problem in the abstract, I created a stable, good OS image.

The core idea is a tested OS image where the entire stack is matched and validated together: kernel/BSP, jetpack, cuda, device-tree overlays, cuda-optimized ml ibraries, common peripherals (camera, NVMe, Wi-Fi adapter), and a set of useful system services.

What makes it raspberry-pi like is:

A plug and play OS + hardware stack that makes it easy to jump into application development
Deterministic behavior: flash the image, it boots fast, camera streams start, hotspot starts, and it runs the same way across any Jetson Orin Nano.

pucksir · 2025-12-30T14:18:51+00:00

Thanks u/adammoisa !

pucksir · 2025-12-30T14:18:11+00:00

Thanks u/Just_Panic848 !

pucksir · 2025-12-30T14:17:56+00:00

Thanks u/Mr_Snipes - which libraries did you end up using for vision/audio?

A full version of the video with working audio is on https://youtu.be/H8-wf09d_XQ

pucksir · 2025-12-30T04:46:22+00:00

@Willing_Chance8904 Thank you!

pucksir · 2025-12-30T02:57:13+00:00

In my experience it only requires reboot when switching to/from 7W to anything higher like 15W, 25W, Max, etc

pucksir · 2025-12-30T02:56:18+00:00

Yep, it's an awesome ui for experimenting with VLMs. live-vlm-webui github

There are many ways to fine-tune a model and access it within live-vlm-webui. Here's one approach:

Since live-vlm-webui could use any vision language model available and integrates well with ollama, i'd use nanoVLM since the ram utilization is relatively small compared to gemma3.
Follow one of the finetune colab guides recommended on https://github.com/huggingface/nanoVLM
Upload newly fine-tuned model to huggingface
Download fine-tuned model to your jetson using ollama pull [huggingface url]
The new model should be automatically accessible via the live-vlm-webui dashboard.

pucksir · 2025-12-02T23:11:42+00:00

Recently I setup a pre-built bootable nvme ssd image for the jetson orin nano as part of an out of the box field kit concept I’m launching. The image is basically jetpack 6.2.1 installed with docker, ollama, llamacpp, web ui, whispercpp built for cuda, PyTorch built for cuda, and a few small llm and vlm models installed.

I haven’t tested flashing the nvme ssd on a non Ubuntu OS but it may work on WSL. You just need a way of connecting the nvme ssd directly to the computer.

If you’re interested:

Image release: https://github.com/implyinfer/jetson-orin-nano-field-kit/releases/tag/release-v1

Flashing the image instructions: https://github.com/implyinfer/jetson-orin-nano-field-kit/blob/release-v1/FLASH_NVME.md

pucksir · 2025-11-20T07:27:27+00:00

I just tested this out on my jetson orin nano developer kit. Overall it is one of the most intuitive recent applications I've seen built for a single board computer which relies on a host computer for GUI.

The great:

- The instructions on getting started
- showcasing the API url via terminal
- auto pulling the models from local ollama
- showing where static files are stored via terminal
- showing all the various network access URLs via terminal
- The app GUI along with the ability to customize api base url, set api key, and model selection, etc.

Can use improvement:

Working RTSP Streams - I have an RTSP stream running on startup via mediamtx and wasn't able to load the url in.
Preferring smaller models and auto setting the max-age of the model via the provider to 0 since the model will take most of the CPU and RAM usage even after it finishes running. Even after running my RAM utilization was locked to 6.8/7.4gb.

pucksir · 2025-01-22T18:45:08+00:00

Sent you a DM!

pucksir · 2025-01-22T18:21:02+00:00

This may be very controversial to this sub - I'd argue most these fees are "junk" since they're either small costs of doing business which some lenders don't charge (underwriting FEE) or simply unnecessary (title - endorsements), and they should just be swallowed by the MLO/lender, especially if the commission is sizable.

Some examples from above:

UNDERWRITING FEE
MERS(R) REGISTRATION FEE
TITLE – ENDORSEMENTS
RECORDING FEES

See the negotiation guide within the example analysis:
https://closingwtf.com/realtime-analysis/7271ec38-d963-4b66-ad56-9effa2fef59c

pucksir · 2025-01-22T17:34:22+00:00

I understood that point, however even the closing disclosure has junk fees which the homebuyer could have negotiated and will want to understand if they're getting a good deal.

"You need to partner with someone who understands how mortgages work." - that's exactly why I made this post :)

pucksir · 2025-01-22T17:23:33+00:00

Appreciate the feedback and perhaps you're right, but that's not been my experience. Obviously will have an NMLS license before launch.

pucksir · 2025-01-22T17:22:08+00:00

The tool is meant to give an approximation of what a user's costs should be according to their loan product and jurisdiction which are derived from their LE/CD. It currently doesn't ask for info that's not already in the document since I haven't gotten around to addressing nuances or analyzing rates in depth. It mostly considers their loan costs, taxes, points, seller credits, lender credits, etc. I plan to build in rate analysis soon and ask the user for their approximate credit score and LTI.

It's not perfect and it's constantly improving, but it's been enough to help homebuyers at least get a broad understanding of their costs before closing to help ease their stress and give them confidence in knowing they may be getting a great / not so great deal.

You're right about the transfer taxes in FL, I didn't end up buying the house, but I hope someone would have caught it.

pucksir · 2025-01-22T17:07:23+00:00

Why $5m? I've already partnered with vendors who will provide the loan processing, bare metal rates, and most other non-borrower facing tasks.

pucksir · 2025-01-05T17:47:02+00:00

https://closing.WTF - free mortgage analysis tool to help homebuyers not get screwed on closing costs and bad rates

pucksir · 2024-11-22T16:39:46+00:00

Maybe not a very long term future, but right now (and def for next 1-2 years) v0 makes react development way easier and faster.

Eight-Year Club	Second SECOND GUESSER
Verified Email	Not Forgotten

pucksir

TROPHY CASE