[sdiy] Discrete OTA

[Neil Johnson]

cheater00 wrote:
> Another good tool for that is to have a blog and progress reports
> online. Inevitably coming up with a new module will take months or
> years. So if you do *public* progress reports on a project every
> couple of months, once you've released, there will be blog posts there
> that have existed for a year, maybe more. That is a believable time
> scale for a project like this. Nothing much needs to be said on the
> blog post, other than: "here's an update on my VCO project. I'm using
> the following chips as the base: SSM2164, TL072 (list here the
> important chips on the board). It sort of works, but it's got the
> following problems currently: temperature tracking, amplitude
> variations (list any other issues). I'm still working on that. Below
> is a demo of some oscillator waveforms (add some soundcloud links or
> youtube links)." All in all 15 minutes of work, and the benefits are:
> lack of ambiguity of whose work it is, and more importantly, great
> marketing for you. You don't need to talk about secret technology,
> such as the circuit topology, the schematic, etc.

In a DIY context then yes that can work.  But from a business
perspective you would be folly to reveal too much to your competitors.
Not every one out there is nice and fluffy.  To someone skilled in the
art it wouldn't take long to work out enough details to understand
what you're doing.  And while you could argue that once your latest
product is on the market your competitor can reverse-engineer it, why
make life easy for them, or give them a headstart?

Definitely don't post schematics that you care about, no matter what
wording you put on them.

Neil
--
http://www.njohnson.co.uk