digital interface/protocols?

I'm new to the CAN scene. I was a proffesional mobile technician for ~10 years up until ~1995. I would now consider my self a semi-professional, since I've been away from the industry for so long. Back then, it was pretty much all analog(w2w). However, I would like some knowledge about the interface/protocols that are being used by the aftermarket alarm manufacturers, for communication between their products and others. What are the different interface/protocols being used and what are their names? What are their compatibilties with other manufacturers interface/protocols and any issues? I've tried to do as much specific research on my own(2 weeks) but, there isn't much that I've found. If you want to be either very technical or completely vague, I'm ok with that. I know some techs hold onto their knowledge like a patent and won't license it.  I never did that. My brief encounter here in the forums lends me to believe the vast majority of techs here don't either. Otherwise, why would they be here. If you just want to point me to links, I'm fine with that too. I've probably already read them though.  Give it a shot anyway. if you feel the need.

Within the next couple of days to week, I'm going to install(R/S K/E) either a Viper 5301 or 5501 into my 2002 Honda CRV, that is originally equipped with keyless entry and an immobilizer. I going to do this as inexpensively as possible and will not sacrifice security(no key and digital). I've seen at least 2 different interface/prototcols, if I'm not mistaken. I believe one is called D2D/DBI that is used by DEI. I'm not sure if this and the others are proprietary or some CAN derivative. I like what I've seen though, as far as the capabilities of these aftermarket modules and their vehicle integrations. Based on my specific vehicle though, there isn't much integration.  However, it's old so I understand. Of the applications I've seen, I found 3 modules that I'm leaning towards(Honda SL3, TBSL-HA, and PKH34). My understanding is only one(PKH34) of these provides a more secure installation(disables analog communication) when using the D2D port. It may also be the only one compatible with DEI products, hence my reason for the topic of this thread. I believe it could be made even more secure, if there was some sort of unique(un-cloanable) encrypted communication as well? Of course, if you see any errors in my ways, please feel free to correct me.

Basically, helping to answer the first paragraph would give me the information I need to understand the architectures used today and the confidence that my products, whatever they may finally be, will work properly together with my given knowledge.

TIA for your time. -LR

What are the different interface/protocols being used and what are their names? What are their compatibilties with other manufacturers interface/protocols and any issues?

there are many out there. try to grab any of the following bypasses.

Fortin, Bypasskits, iDataLink. for the 02 i dont think you will need a canbus unit since most wires would be at the ignition, driver/pass kick and maybe door. i havent had any real issues with digital interfaces but had issues with the honda-sl3 programming, but i realised i missed one wire. also the tach wire output on the units reallly suck. i wrote something awhile back about this issue. most units will now have d2d or datacontrolled wire(saves time) but i still prefer to hardwire all outputs to bypass interface to prevent ant faults through data wire. im sorry if i confused you. if you got more q's feel free to ask.

Thank for the reply. 

The thread was not how integrate or install modules into a vehicle, nor how to integrate or install RS/alarms into a vehicle. I very competent at this exercise, knowledgeable about the wiring for vehicles, and understand what is available on the buses the in different vehicles. This thread was mainly to get knowledge of the various interface/protocols used to integrate the various products together, that are offered by aftermarket accessory and alarm manufacturers.

Thanks for your reply. I really appreciate your input djfearny2, as well as yours tedmond. Everyone can gleen some information from almost any reply. I hope neither of you took/take any offense to my replies.

I may be new to the CAN scene but, I'm completely competent about the CAN concept. I'm not an expert mind you but, any information I need on CAN is available, as it's a industry standard. I am professionally knowledgable about vehicle wiring, whether it be analog or digital. I know what is available for integration into vehicles and how it is integrated into those vehicles. I used my scenario in my opening post as a way of explaining where a past mobile electronics technician who may be coming into the industry again is left, in regards to knowledge about the aftermarket alarm and alarm accessories industries internal integration. There really seems to be no source of information about this, even from the vendors themselves. I guess I need to clarify this thread more. It's not about integration into the vehicle.

This thread is mainly about the proprietary interface/protocols created and used by the aftermarket alarm and alarm accessories manufacturers, to integrate their products together and their cross-compatibility with others. Specifically, their naming schemes, their compatibility with other manufacturers, and any issues that may arise when integrated together. Current mobile electronics technicians themselves must come across this scenario daily.

Note: I wish there was an edit feature in these forums!