[BC] That EAS Handbook

[Broadcast List USER]

OBDII is for monitoring.  It gives a common interface for knowing what  
is going on.  The standard doesn't tell auto manufacturers how to make  
the car go.  The lack of those standards allows for innovation.  The  
computers in the cars and that software are not standard, and the  
manufacturers can do what they want.  The car just has to report out  
to the scan tool in a basic standard format, though the manufacturers  
can even add onto and enhance that reporting.  It just has to work  
with the basic tool.

The same is pretty much the same for EAS.  What goes in and out are  
standard, but how the manufacturer does it inside the box is up to  
them.  Again, that allows for innovation, as well as some pretty awful  
products, but that is how it should work.

--chip

On Feb 16, 2010, at 3:14 PM, broadcast-request at radiolists.net wrote:

> Message: 29
> From: Kevin Raper <kj4hyd at gmail.com>
>
> Barry Mishkind wrote:
>> Given the differences between the EAS receivers, I"m sure the
>> FCC handbook does not plan to cover all possibilities.
>
> Shouldn't the FED require ALL EAS systems operate the same and use the
> same software? They did that to the car makers with OBDII, so why  
> not do
> it to EAS?
> -- 
>
> 73,
> Kevin Raper
> KJ4HYD
> CE WCKI WQIZ