MOTM

> ----- Original Message -----
> From: Tony Karavidas <tony@...>
> Two big reasons I tend to want to put small knobs on my MOTM format
modules s:
> 1. I have thousands of them in stock.

That reason is 100% invalid from a customer perseptive.  The cost of knobs
wil not be a make or break price decision for customers buying such a niche
product.  What you have in stock is not even a consideration.  If you want
to reduce your stock, put them on e-bay at a reasonable price and they will
disappear.  Use the money to buy good knobs.  You are not John Simonton and
this is not PAiA.  Price is not the primary consideration.

> 2. They automatically differentiate a module as Encore in a sea of MOTM.

That reason is valid.  However, I can think of many ways to accomplish the
same thing without using only small knobs.

> I'm still considering some variations on the large knob small knob issue.
It turns out I could combine 1 large and 1 small knob on the Coarse/Fine
controls. When mounted that way, it "looks" like a vernier control, even
though they don't touch. (they are close)

Re-evaluation is good.  Now, why are you stuck on that grid layout?
Frankly, it is not user friendly.  Big knob on the same grid with all that
"blank" panels space will suck IMO.

> To address your issue with the schematics: To supply schematics outside of
a service manual is an invitation for trouble to be blunt.  If I were to
provide schematics I am basically giving the OK for people to mess around
with the design.

I see nothing wrong with people messing with the design if they choose to do
so.  Once they PAY you for it they can do exactly what they please.  No one
would expect you to honor a warranty on a modified product.  However, this
group is largely populated with DIY people and people who are getting a kick
from learning and re-learning.

> What if they Stoogify a panel within the first year? Should I pay anything
to repair it? I don't think so.

Certainly if someone modifies a product they accept they are voiding a
warranty.

> I have an internal policy about schematics and as long as I am actively
supporting a product, generally the schematics remain unavailable. When the
day comes that the UEG is no longer supported by me, I will release the
schematics, and the code in a single HEX file so someone with a device
programmer could replace and reprogram the microcontroller. That day hasn't
come yet.

I can accept that.  You owe your customers two things then.

1. A written policy about support.  What are the warranty terms?  Is there a
specific guarantee on turn around for repairs since you are the only game in
town with schematics?  If you do not release any service information,
customers need some assurance about service.  What are your service rates
for repair?

2.  A certificate delivered with the product good for a service pack
including the needed schematic and code for "when that day comes."  We never
know when the demands of your other income producing interest will take you
away for long periods.  I suspect UEG and FS are not primary means of
support. :-)

When you ask people to spend a lot of money on something, they need more
than faith.  I know I do.

> ----- Original Message -----
> From: Paul Schreiber <synth1@...>
> Roger doesn't publish schematics, but get Electronotes and you then have
them :)

There was a farmer had a dog and BINGO was his name-o.