[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: DSC GSM Communicator
This is a multi-part message in MIME format.
------=_NextPart_000_24A8_01C79995.7420EC40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I don't understand why everyone except Uplink has had at least one =
recall on GSM products, I had a box of beta units I recently sent back =
and am still waiting for release versions, I guess I now know why I =
don't have em yet
"Just Looking" <nospam@xxxxxxxxxx> wrote in message =
news:464e32d3$0$19420$4c368faf@xxxxxxxxxxxxxxxxx
Why should this be a surprise? It's DSC after all. I am still waiting =
for a replacement 1832 from that first batch of bad units. They always =
BETA test everything at the dealer level, they just don't tell you. Ask =
to speak to the product manager for GSM communicator if you need the =
ULC/UL questions answered.=20
"George Siegle" <gsiegle@xxxxxxxxxxxxx> wrote in message =
news:vp13i.33977$Xh3.17911@xxxxxxxxxxx
Speaking with DSC and Tri-ed today I learned that the units shipped =
out have a problem.
If the unit looses communication or is unable to communicate, it =
requires the installer to go out to the site to cycle power to the unit.
Tri-ed informed me they have stopped shipping waiting for new units =
with new software to fix the power cycle problem. They hope to have =
them next week.
Does anyone know about ULC/UL? If the first unit out had ULC/UL =
approval, with a software change as it was explained to me is all that =
is needed, will this new version have to go back to ULC/UL for =
approval?
And if you put a battery across the phone line and cut the phone =
line it does not send unless you tie back into an input on the radio =
Tri-ed explained to me.
What happens with the unit if doing it's own power cycling, if an =
alarm event takes place, is the event lost? I asked this of DSC tech =
support, still waiting for a call back from Harry Schultz.
If you have used any, you may want to contact your local distributor =
or DSC. I have looked on the DSC web site for any kind of Tech Bulletin =
or notice, as of now they have posted nothing.
------=_NextPart_000_24A8_01C79995.7420EC40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I don't understand why everyone except Uplink has =
had at least=20
one recall on GSM products, I had a box of beta units I recently sent =
back and=20
am still waiting for release versions, I guess I now know why I don't =
have em=20
yet</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Just Looking" <<A=20
href=3D"mailto:nospam@xxxxxxxxxx";>nospam@xxxxxxxxxx</A>> wrote in =
message <A=20
=
href=3D"news:464e32d3$0$19420$4c368faf@xxxxxxxxxxxxxx";>news:464e32d3$0$19=
420$4c368faf@xxxxxxxxxxxxxx</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Why should this be a surprise? It's =
DSC after=20
all. I am still waiting for a replacement 1832 from that first batch =
of bad=20
units. They always BETA test everything at the dealer level, they just =
don't=20
tell you. Ask to speak to the product manager for <FONT =
size=3D2>GSM=20
communicator </FONT>if you need the ULC/UL questions answered. =
</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"George Siegle" <<A=20
href=3D"mailto:gsiegle@xxxxxxxxxxxxx";>gsiegle@xxxxxxxxxxxxx</A>> =
wrote in=20
message <A=20
=
href=3D"vp13i.33977$Xh3.17911@edtnps90"">news:vp13i.33977$Xh3.17911@edtnps90";>news:vp13i.33977$Xh3.17911@e=
dtnps90</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Speaking with <STRONG><FONT =
color=3D#0000ff>DSC=20
</FONT></STRONG>and <STRONG>T</STRONG>ri-ed today I learned that the =
units=20
shipped out have a problem.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If the unit looses communication or =
is unable=20
to communicate, it requires the installer to go out to the site to =
cycle=20
power to the unit.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Tri-ed informed me they have =
stopped shipping=20
waiting for new units with new software to fix the power cycle=20
problem. They hope to have them next week.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Does anyone know about =
ULC/UL? If the=20
first unit out had ULC/UL approval, with a software change as it was =
explained to me is all that is needed, will this new version =
have to=20
go back to ULC/UL for approval?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>And if you put a battery across the =
phone line=20
and cut the phone line it does not send unless you tie back into an =
input on=20
the radio Tri-ed explained to me.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>What happens with the unit if doing =
it's own=20
power cycling, if an alarm event takes place, is the event=20
lost? I asked this of DSC tech support, still waiting =
for a call=20
back from Harry Schultz.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If you have used any, you may want =
to contact=20
your local distributor or DSC. I have looked on the DSC web =
site for=20
any kind of Tech Bulletin or notice, as of now they have posted=20
nothing.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial=20
size=3D2></FONT> </DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_24A8_01C79995.7420EC40--
alt.security.alarms Main Index |
alt.security.alarms Thread Index |
alt.security.alarms Home |
Archives Home