dei 507m problem

Having just installed the 507M, I'm now trying to verify correct operation -- relative, that is, to your mentioned  false triggers.  Except for when the vehicle is being driven, I'm keeping the alarms armed (including overnight in my garage).  Nothing unexpected has happened yet and so I'm wondering if there's any pointers or insights you could share with me.  If there's a problem, I'd prefer to identify it sonner than later.

Thanks -- Trevor

Wow, install it and it fires just sitting there -- ouch!  Thanks for the run down, it's interesting, all the things that can go wrong :(.  Just a thought, there is one thing probably a little unusual about my install (longitudinal) -- the 1990 Eclipse ETAC Security Controller doesn't provide a "Ground With Arm" (GWA), so I created one using an open collector transistor to yank on the Orange wire when the system is armed.

That's something I'm wondering about.  The install instructions say to use a "True" ignition line if no GWA is available, however, of course, it needs to go to ground when the Ignition is OFF.  I just started modding my 2008 Scion xB OE Security and like the Eclipse, I see no sign of a deliberate ground on any of the ignition wires -- they appear to be either HOT or not.  It strikes me as a question mark whether an OFF Ignition Switch output satisfactorily grounds the DEI 507M Orange wire.

For the Eclipse, I'd previously synthesized an Armed Status signal (not provided by the ETAC), and so it was fairly straightforward to generate a GWA.  With the xB, I'm back to square one (no identified Armed Status)., though I could detect the OE Security flasher (Eclipse didn't have one -- does now :)) and synthesize an approximate Arm Status and hence OC GWA.

How do people in the business handle the Orange wire connection?  I'm beginning to wonder if it might be a crap shoot.  The quality of that ground during Arm might be a factor in 507M performance (just a thought of course -- I'm new to alarm systems).

Thanks Howie :)!

With the Eclipse, I tried to use whatever the OE Security Controller (ETAC) made available to get a clean "factory-like" result.  It took a lot of head scratching and a couple false starts to develop a clean interface between it and my aftermarket Keyless Entry Controller.  After which, further adjustment was needed to support aftermarket sensors.  From what I've read, people generally just replace the ETAC with an aftermarket model :(!

With the Scion xB2, I'm again trying to leverage off the OE Security Controller.  Keyless Entry is already provided, so it's a much simpler problem than the Eclipse, but I still want to achieve as clean as practical an interface with the aftermarket sensors.  However, as you pointed out, one can't afford to do R&D with vehicles when your livelihood depends on turning the jobs around.  Fortunately for me, these are my personal vehicles and I can pretty much take whatever time I need to get the result I'm looking for.  Still, once again, from reading, people generally install an aftermarket Security Controller in the xB2 :(!

Guess I just hate the idea of replacing a perfectly good OE Security Controller, even if it is somewhat limited :)!

FWIW -- The 506T is working great!  I've also installed a DEI 504D Shock Sensor which also seems good, just needs a spot of "glue" for the horn warning (working on it :)) .  I considered the Proximity Sensor, but was recommended against it due to apparent issues.  Since parking lots invite people to get especially near adjacent cars, I can quite believe they could be a hassle.  Between the Shock and Glass-Break, I think the interior is covered.  The Tilt covers jacking and towing, so I'm thinking it's sufficient.

PS. The 507M defaults to quick arm and one degree sensitivity -- no falses yet.  I'll be watching these guys' for misbehavior, but initial impressions are good.