<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o = "urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>There are other issues regarding publishing bad
experience with our (limited) suppliers. When one invests in pattern equipment
(regardless of glow or E) we hope the stuff will perform as expected and will be
warranted if it doesn't. The problem comes when equipment is defective and there
are problems with the warranty service. Most of us can't afford to ditch the
equipment and get something else (sometimes there aren't any options), so we're
stuck with working through the warranty. Should we publish the bad experiences?
Probably - but will it wake up the provider or make them vindictive the next
time we need service?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Fortunately, most pattern suppliers provide
excellent and outstanding service. Most recognize pattern competitors as being
skilled and serious about their equipment. Most accept pattern folks as
reasonably credible technicians able to evaluate and describe a problem.
However, there's likely to be a lack of this "skill recognition" for pattern
types by some E suppliers. They've built their business dealing with some of the
most unskilled folks in modeling. Now we come along and buy their high end
products, expecting to be treated as we've become accustomed - may not
happen.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>So - do we blast the supplier in open forum, or
take businesslike steps to resolve the problem and hope for better service the
next time? I recently endured a very frustrating / aggravating experience with a
supplier and chose the latter. I was close to burning my bridges and
going public - but that was my vindictive side. I was also very close to
purchasing airline tickets for a visit to this outfit with a local attorney
- but again this would have meant doing further business offshore for a
basically excellent product. Fortunately the situation was resolved and,
hopefully, won't be repeated. Suppliers that don't learn will go away and we
should help them do that by withholding our bucks - but let's not slay a
supplier for an occasional lapse in service.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The information on this list regarding E is
probably the best that anyone has. Remember that sponsored folks are often using
prototype items and failures result in better end products. There are only a few
folks really into E pattern that have the background to accurately gather and
report data regarding performance - most are doing that openly and freely. Good
information backed by data will always trump opinions / fears / and
innuendo.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Earl</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=bob@toprudder.com href="mailto:bob@toprudder.com">Bob Richards</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=nsrca-discussion@lists.nsrca.org
href="mailto:nsrca-discussion@lists.nsrca.org">NSRCA Mailing List</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, March 27, 2006 8:33
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [NSRCA-discussion] Changing
list behavior.</DIV>
<DIV><BR></DIV>
<DIV>Eric,</DIV>
<DIV> </DIV>
<DIV>Now that you mention that, I have to say that if I hear of someone that
has blown a rod, then my first thought is that the engine had a defect.
However, if I hear of someone losing a battery, blowing an ESC, or burning up
a motor, my first thought is that the user was doing something wrong.</DIV>
<DIV> </DIV>
<DIV>But, you know what, I think most of the time my first thought is usually
(but not always) correct.</DIV>
<DIV> </DIV>
<DIV>You mentioned that most people are open about their problems with IC
engines, and not so open about problems with electrics. I don't know if that
is true, but if it is, then perhaps it is due to the public's perception being
what it is.</DIV>
<DIV> </DIV>
<DIV>How many times have you heard "I was doing xxx with my electric, and the
yyy fried" and someone else says "Gee, didn't you know you should never do xxx
to the yyy!!!". I would be less open about my experiences if I felt !
everytime I said something I would be chastised online. But, I think that is
the state of electrics in pattern right now, a lot of second
guessing. But, hey, that is a normal learning process.</DIV>
<DIV> </DIV>
<DIV>Bob R.</DIV>
<DIV><BR><BR><B><I>Grow Pattern <pattern4u@comcast.net></I></B>
wrote:</DIV>
<BLOCKQUOTE class=replbq
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"></o:SmartTagType>
<STYLE> st1\:*{behavior:url(#default#ieooui) } </STYLE>
<STYLE> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited,
span.MsoHyperlinkFollowed {color:blue; text-decoration:underline;} p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} p {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman";} pre {margin:0in; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New";} span.EmailStyle19 {mso-style-type:personal-reply; font-family:Arial; color:navy;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {page:Section1;} --> </STYLE>
<DIV><FONT face=Arial size=2>Jim,</FONT></DIV>
<DIV><FONT face=Arial size=2> I'm not
anti-electric. But if I reported that I had blown a rod on a YS DZ
I perceive that I would get a different reaction than if I
report a problem with an electric motor or its set-! up. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BLOCKQUOTE><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>NSRCA-discussion
mailing
list<BR>NSRCA-discussion@lists.nsrca.org<BR>http://lists.nsrca.org/mailman/listinfo/nsrca-discussion</BLOCKQUOTE></BODY></HTML>