Is breathalyzer source code fair game?
  • 4 Comments
by Doug Aamoth on January 15, 2009

CMI

Kentucky-based CMI has come under fire on more than one occasion for not turning over the source code used in the breathalyzers that it sells to various law enforcement agencies, citing trade secrets as the reason for keeping the code under wraps. Well that hasn’t sat too well with people who have been pulled over and cited with DUIs, as some of them have claimed that the machines aren’t registering blood alcohol levels accurately.

Just this week, 100 cases were thrown out of a Bradenton, Florida court after defense attorneys demanded to have the source code for CMI’s Intoxilyzer 5000 examined by breathalyzer experts. Kentucky-based CMI refused to turn over the code and software used with its machines, despite threats of more than $2 million in fines.

Bradenton Judge Doug Henderson eventually ruled that “the refusal was a violation of due process,” saying that “The defendant’s right to a fair trial outweighed the manufacturer’s claim of a trade secret.” As such, breathalyzer evidence for the pending cases was deemed inadmissible – and some of those cases had dragged on for over three years.

A similar case involving CMI happened in Minnesota not too long ago when a defendant asked to see the source code for the same model of breathalyzer mentioned above. The Minnesota Supreme Court found that “under the contract between the state and CMI, the state owned the source code for the Intoxilyzer 5000EN.”

So is all this source code hoopla just a stalling tactic or are these legitimate claims?

“What’s frightening is that the 5000EN is apparently based on the ancient Z-80 processor, which powered the Radio Shack TRS-80 desktop computer … which went on sale in 1977. CMI has also been accused of making uncertified changes to the machines, and had to issue a recall due to faulty software.”

That, according to an article on Switched.com about the Minnesota case back in 2007. Also, please reference the above image for a look at the actual machine.

The bigger issue here, however, isn’t about faulty software, hardware, or source code, it’s that a publicly-funded entity like your local police department buys technology from the private sector and then has no access to information about how the technology works. When that technology is used as evidence in a trial, should it be open to scrutiny by the defense? Your thoughts?

[via Slashdot]

Comments rss icon

  • Third-party software for such devices (including radar gun, dashboard cameras and even stunguns) should not even be allowed. Any software that will be involved in taking away someone’s freedom should be soley developed out in the open by the governments and should be freely, completely and constantly available to public scrutiny – including all revisions and the reasons for them. Have someone build the machines under contract bid, but the code must be -if you will – of the people, by the people and for the people.

  • Here in Canada new legislation has now made the Intoxilyzer Judge, Jury and Executioner! It scares me that our present government has put so much faith in a peace of equipment that has been proven to be inaccurate by many experts. Even one of the guys who designed the Intoxilyzer stated that it was never meant to be used on its own as evidence. In Fact he did go on to say that for a legal limit of 0.08, that a reading of 0.11 should be used to be fair the a defendant because of a 3% inherent error involved in process that the machine uses to estimate alcohol in the system.

    As a Footnote to the legislature in Canada….it was MADD Canada’s Lawyers that wrote the law then the governments Lawyers reviewed and revised it to escape any Charter of Rights issues. Glorious and Free we are!!!?

  • i got myself a breathalyzer from http://www.alcometers.com and it has a +/- of .02% so if it reads .08, i make sure to wait for it to read .05 just to be extra safe before getting behind the wheel.

Leave Comment

Commenting Options

Enter your personal information to the left, or sign in with your Facebook account by clicking the button below.

Alternatively, you can create an avatar that will appear whenever you leave a comment on a Gravatar-enabled blog.

Trackback URL
bugbugbug