Re: 2GiG recall

[mleuck <m.leuck@xxxxxxxxx>]

On Oct 26, 8:19=A0am, tourman <robercampb...@xxxxxxxxx> wrote:
> On Oct 24, 7:03=A0pm, Spellcheck Patrol <alarminst...@xxxxxxx> wrote:
>
>
>
>
>
>
>
>
>
> > I received an email announcing a recall on the 2GiG GSM today. Here it
> > is:
>
> > 2GIG Voluntary Recall
>
> > 2GIG Technologies, Inc. is voluntarily recalling the following GSM
> > radio modules ("GSM Modules") used with 2GIG's GO!Control security
> > panels. We have been working with 2GIG and Alarm.com to secure a list
> > of customers. We are developing a plan to replace these units as
> > quickly as possible and will communicate that plan to you as soon as I
> > have worked out all of the details. In the mean time, please review
> > the note below so you can check your existing inventory.
>
> > Model #
>
> > GSM Signal Carrier
>
> > 2GIG-GSM1
>
> > T-Mobile
>
> > 2GIG-GSM2
>
> > T-Mobile
>
> > 2GIG-GSM3
>
> > Rogers
>
> > 2GIG-GSM4
>
> > Rogers
>
> > 2GIG-GSM5
>
> > AT&T
>
> > 2GIG-GSM6
>
> > AT&T
>
> > Date Codes Affected: 201049, 201050, 201051, 201052, 201101, 201102,
> > 201103 and 201104. These date codes appear as the first six numbers of
> > the MDSN code of GSM Modules. This recall involves GSM Modules only
> > and not GO!Control panels.
>
> > We are recalling these GSM Modules because of the potential failure of
> > a voltage regulator integrated circuit located on the GSM Module board
> > that could, upon a reset or power off/on cycle, allow an overvoltage
> > condition causing tantalum capacitors located on the GSM Module board
> > to overheat and fail. This in turn could result in heat, smoke or fire
> > damage to the control panel and potentially to surrounding areas.
>
> > Your support and assistance is critical to ensuring that affected
> > inventory is not installed and that installed recalled GSM Modules are
> > replaced correctly and promptly. Exchanges of new GSM Modules for
> > recalled GSM Modules must be performed by qualified service
> > technicians.
>
> > 2GIG has, through its back-end service provider, blocked all currently
> > uninstalled recalled GSM Modules from being activated and authorized.
> > If a security dealer or technician attempts to install and authorize a
> > recalled GSM Module, the authorization will be denied by the back-end
> > service provider and a non- recalled GSM Module must be obtained to
> > continue the customer installation.
>
> > Instructions for Inspecting Inventory to Identify Recalled GSM Modules
>
> > To identify GSM Modules within the date code range applicable for this
> > recall, you will need to physically inspect all GSM Modules in your
> > inventory (whether in original packaging as a kit component, in
> > packaging as a separate component or otherwise). Only GSM Modules with
> > MDSN numbers that begin in the following range are being recalled:
>
> > Date Codes Affected: 201049, 201050, 201051, 201052, 201101, 201102,
> > 201103 and 201104.
>
> > (Note: The first four digits of the MDSN number are the year, the next
> > two are the week number of that year)
>
> > The MDSN number is found on the barcode label above the IMEI number,
> > which is used to register a customer=92s Alarm.com account. =A0This
> > barcode label can be found affixed directly to GSM Module itself, as
> > well as the box it comes in. =A0If the GSM Module is installed in a 2GI=
G
> > GO!Control panel, open the rear panel cover and locate the GSM Module.
>
> > This is an automated email notification from ASIS. Please do not reply
> > to this email.
>
> RHC: One could possibly make the argument that they rushed to market
> too quickly; however, at least they stepped up to the plate and
> acknowledged the problem....better than some other security parts
> suppliers in the past

Hey like Detection Systems eh? :)