News for hackers. Stuff that matters.
Re:Tinkering with electronics by jjoonathan on Sunday February 25, 2018 @07:18PM (#16462069)
Anything, so long as it interacts with the outside world exclusively through a screen, speakers, or API :)
Re:Tinkering with electronics by vvanders on Sunday February 25, 2018 @08:56PM (#16462446)
Right? Why didn't someone tell me that these newfangled SDRs worked purely through the magic of softrware.
Re:Tinkering with electronics by jacquesm on Monday February 26, 2018 @02:35AM (#16463771)
Missing a /s ? If not, what did you think the 'S' stood for?
Re:Tinkering with electronics by vvanders on Monday February 26, 2018 @10:33AM (#16465945)
Well Software, duh ;).

The point I was sarcastically making was that even in SDRs you still have a downconversion via either Direct Converting or SuperHet to baseband so your signals are in the right frequency reference that you don't completely saturate your DSP/FPGA/CPU.

I love software as much as anyone else but just saying that you can do everything in SW is a bit disingenuous.

Re:Tinkering with electronics by jacquesm on Monday February 26, 2018 @11:35AM (#16466543)
But nobody said that.

I wrote "So now anything that I do that has to have an effect in the real world is put together with the absolute minimum in interface hardware and the remainder is software." and the other person wrote "virtually".

Re:Tinkering with electronics by vvanders on Monday February 26, 2018 @12:28PM (#16467039)
I was replying to the second, just adding a "virtually" doesn't absolve you of real-world hardware concerns. If your SDR is getting overloaded because of bad pass-band filtering then no amount of software is going to save you.
Re:Tinkering with electronics by TeMPOraL on Monday February 26, 2018 @06:02AM (#16464489)
There's plenty of hardware tinkering around SDRs though.
Re:Tinkering with electronics by jacobolus on Sunday February 25, 2018 @09:09PM (#16462515)
A way of rephrasing the previous comments would be: “I only use hardware devices when I need special-purpose I/O (including direct physical measurements and physical effects). All signal processing and logic can be more cheaply, quickly, and effectively done in software.”
Re:Tinkering with electronics by vvanders on Monday February 26, 2018 @01:13AM (#16463501)
> cheaply, quickly, and effectively done in software

Hardly.

Power usage in SW(or FPGA) vs ASIC is easily an order of magnitude difference. For most battery based solutions software based signal processing is right out.

Latency is another, your CPU is going to introduce both jitter and long latency compared to a discrete software solution.

Software also can't handle raw speeds involved in a lot of things. There's not a single CPU out there that can natively handle 5GHz wifi off of the wire. That's why even direction conversion SDRs use a frequency mixer to lower the data rate down to something a DSP can handle.

Re:Tinkering with electronics by jacobolus on Monday February 26, 2018 @01:33AM (#16463570)
By cheap, quick, and effective, I’m talking about human labor, not cost of silicon doodads for a commercial-scale product.

If you imagine we’re talking about someone’s hobby prototype projects, designing all of those things you mentioned takes skill, experimentation, time, parts, assembly, likely a team collaboration, etc. The combinations of parts get conceptually complicated and the feedback loops during the development process get slower and slower.

Obviously there are reasons to use custom-designed hardware if you are a corporation and you are building a million identical devices, or if you have extreme bandwidth or latency needs that a modern CPU literally can’t keep up with, etc.

But that’s a very different context than what the people several posts up are talking about.

P.S. if you pile your posts with abbreviations your readers have a harder time figuring out what you are talking about.

Re:Tinkering with electronics by vvanders on Monday February 26, 2018 @12:31PM (#16467087)
> Obviously there are reasons to use custom-designed hardware if you are a corporation and you are building a million identical devices, or if you have extreme bandwidth or latency needs that a modern CPU literally can’t keep up with, etc.

Or power, plenty of battery powered things in the hobby space where using discrete hardware optimized for low power usage is necessary. Discrete hardware doesn't have to be an ASIC, it's still possible to string together a opamps and other SMD parts pretty easily these days.

Re:Tinkering with electronics by twtw on Monday February 26, 2018 @02:07AM (#16463677)
Loads of people do FPGA development for hobby projects, which isn't "software." FPGAs can dramatically improve problems with latency, jitter, power over software implementations, yet are still quite accessible.
Re:Tinkering with electronics by icebraining on Monday February 26, 2018 @03:47AM (#16464015)
Isn't it software? What is it, then?
Re:Tinkering with electronics by meuk on Monday February 26, 2018 @06:03AM (#16464491)
I think it is more commonly referred to as hardware design (or simply 'digital design'). I think it's also reasonable to call it software - but I think that even the 'real' hardware development (of ASICs) is starts with a VHDL design.
Re:Tinkering with electronics by vvanders on Monday February 26, 2018 @10:35AM (#16465963)
It's more like a million jumper switches(called LUT in FPGA parlance) that you can configure.

It doesn't share much, if anything with serial software and you use the same tools(VHDL/Verilog/etc) as ASIC design.