Recent submissions

Comment · 1 year ago
Comment · 2 years ago
> When my AoA sensor fails, then what?

crickets, let's just randomise which sensor we use during boot, that ought to do it!

Comment · 3 years ago
Strange. I haven't changed a thing. Just to confirm, the problem yesterday was that the website would be stuck, not that you couldn't move down further by scrolling in an unnatural way, right?
Comment · 3 years ago
Comment · 3 years ago
PPS input/output is off to the side, look for the "User Interface Connector" paragraph on the website.

> What do you mean? Do you have your own DSP stack to deal with that while user receiving/transmitting? If there is, do you provide any control over it?

You can quickly pause whatever is running on the LA9310, push the NXP NLM stack, correct local frequency errors by synching to a cell network tower and then resume normal operation. It's going to cause a glitch, but if you want to maintain frequency accuracy it's a small cost you need to pay. Once you have absolute deviation and drift it should track quite well.

My understanding is that SRS and the like all require beefy desktop-class processors to run in?

Comment · 3 years ago
Is this with an older Firefox version maybe? I've tried with a relatively recent one and couldn't reproduce, but I'll look at the logs and try to fix this now that the HN storm has passed :-)
Comment · 3 years ago
It would need to be a different design entirely.
Comment · 3 years ago
Comment · 3 years ago
The schematics will be released publicly when the product is shipping, but it won't be OSHW. I don't want to end up like the HackRF, where one small company is burdened with supporting an ecosystem of what is mostly clones. The HackRF designer himself said he wouldn't do it again.
Comment · 3 years ago
You'd probably want something way more sensitive than that, right? Something that goes well into the micro/nanovolts rather than millivolts. But it should be reasonably simple to do. Also the RTL board when designed with a good frontend should be a viable option.
Comment · 3 years ago
8x ADCs and 2x ADCs @ 153 MSPS -> 4x RX I/Q pairs and 1x TX I/Q pair. The way the math works, you can sample a 153 MHz signal at 153 MSPS using I/Q, or you can use each ADC line to sample at nyquist, and in that case you get 8x RF channels, each sampling 80 MHz at most. All untested, of course.
Comment · 3 years ago
We need volumes, so the best I can hope for is people join the waitlist and pre-order when we show a functioning prototype. We already placed sizeable orders with the manufacturers and have the first batch planned for September, but further batches are probably going to be delayed into 2024 (we can't start asking for preorders before the product is tested, which is going to take time, so we can't preorder those chips early like we did for the first batch).

Feature wishlist: please! Do send them our way. Especially if it's hardware, this is the right time!

Comment · 3 years ago
Here is a fast render of what the enclosure might look like (work in progress): https://i.imgur.com/AEYgLxU.png

The idea is however you get shielding and cooling, sit it on the desk upside down and have all the RFNM boards accessible from the top.

Comment · 3 years ago
A few practical use cases that are not easily covered by similar platforms:

1) Direction finding thanks to the 8x 153 MSPS ADCs and coherent clocks.

2) Mixed domain analyzer: have one daughterboard act as a RF receiver, and at the same time sample an analogue voltage with the other one. This is a capability reserved to the most expensive of test equipment and lets you analyze how a RF switch is behaving (or do side channel attacks?).

3) Sample almost 600 MHz of bandwidth in real time, use the powerful DSP core to run FFTs on it and send the results over to a browser that implements a RTSA display. This lets you have a real-time view of the spectrum around you for just a few watts. Thanks to the double-PPLs on the Granita board, you can also sweep the spectrum very fast.

4) There is enough processing power onboard to enable RFNM as a 5G RedCap node. We are working with NXP to add an eSIM, so with the right software, this can become a fully-functional 5G UE and connect to the normal cell network. Don't care about 5G? You can write your own standard and deploy it on the same hardware (the limitation here is having access to NXP's DSP development tools, which might limit the processing to the beefy i.MX 8M Plus, but some cores will be available as binaries).

5) Technically, anything requiring an insane amount of ADCs and DACs. You can implement your own board, as the heavy lifting (the motherboard) is already done for you. You could prototype something easily with the development board that's on the website and turn it into a real design within weeks.

Comment · 3 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton