<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Human Interface Computer (HIC) White Paper and Requirements</title>
	<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/</link>
	<description>SSM - the Home of the Open Source Green Vehicle (OSGV) Project</description>
	<pubDate>Thu, 09 Sep 2010 14:16:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: David Lee</title>
		<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-6</link>
		<author>David Lee</author>
		<pubDate>Tue, 12 Jun 2007 05:56:48 +0000</pubDate>
		<guid>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-6</guid>
					<description>I am hoping that somebody will take the ownership of the item and develop the idea further. The interface (mechanical and electrical) should be straight forward enough for a rather independent group.

I know there are plenty of Car PCs out there - but we need to identify a cheaper solution - instead of costing $1000+, it has to be built for $300 or so...

Some people on Mp3Car.com have some homebrew double-DIN chassis with mini-ITX PC in it. Pretty cool. I think we could adapt it to fit.

Anyway, please note that the requirements are written such it is not platform-specific. So, other solutions might work as well.

Good luck.</description>
		<content:encoded><![CDATA[<p>I am hoping that somebody will take the ownership of the item and develop the idea further. The interface (mechanical and electrical) should be straight forward enough for a rather independent group.</p>
<p>I know there are plenty of Car PCs out there - but we need to identify a cheaper solution - instead of costing $1000+, it has to be built for $300 or so&#8230;</p>
<p>Some people on Mp3Car.com have some homebrew double-DIN chassis with mini-ITX PC in it. Pretty cool. I think we could adapt it to fit.</p>
<p>Anyway, please note that the requirements are written such it is not platform-specific. So, other solutions might work as well.</p>
<p>Good luck.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Lee</title>
		<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-7</link>
		<author>David Lee</author>
		<pubDate>Tue, 12 Jun 2007 06:02:56 +0000</pubDate>
		<guid>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-7</guid>
					<description>In addition, the requirements above will be turned into a source control specification - according to our open design license. 

Please provide links to possible vendors (if any).</description>
		<content:encoded><![CDATA[<p>In addition, the requirements above will be turned into a source control specification - according to our open design license. </p>
<p>Please provide links to possible vendors (if any).</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: motosaurus</title>
		<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-8</link>
		<author>motosaurus</author>
		<pubDate>Tue, 12 Jun 2007 18:05:08 +0000</pubDate>
		<guid>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-8</guid>
					<description>Very complete David, good job.
Since the vehicle is pretty much certain to have large electric motor(s) and therefore some heavy current flow ( DIY BEVs run 500 amps at 144V as a matter of course), perhaps there should be a placeholder for magnetic/RF shielding beyond the usual consumer/gas-auto level? (I have no idea what level of RF a BEV controller puts out, but I'll ask)

John</description>
		<content:encoded><![CDATA[<p>Very complete David, good job.<br />
Since the vehicle is pretty much certain to have large electric motor(s) and therefore some heavy current flow ( DIY BEVs run 500 amps at 144V as a matter of course), perhaps there should be a placeholder for magnetic/RF shielding beyond the usual consumer/gas-auto level? (I have no idea what level of RF a BEV controller puts out, but I&#8217;ll ask)</p>
<p>John</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Lee</title>
		<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-9</link>
		<author>David Lee</author>
		<pubDate>Tue, 12 Jun 2007 20:23:52 +0000</pubDate>
		<guid>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-9</guid>
					<description>The vehicle will max out at 400A at 450V. The 450V power rail is separated from the 12V utility power rail with a DC-DC converter. Switching frequency is no less than 2kHz so it should be fairly stable. EMI is currently unknown as it is highly dependent on the type of high-power components we use.

But the idea is to isolate the conducted and radiated EMI at the source (so you don't have to shield everything else - which might increase cost). e.g. the motor will have ground shielding and inline EMI filters on the power lines.

Very good point indeed. I will add that to the requirements.</description>
		<content:encoded><![CDATA[<p>The vehicle will max out at 400A at 450V. The 450V power rail is separated from the 12V utility power rail with a DC-DC converter. Switching frequency is no less than 2kHz so it should be fairly stable. EMI is currently unknown as it is highly dependent on the type of high-power components we use.</p>
<p>But the idea is to isolate the conducted and radiated EMI at the source (so you don&#8217;t have to shield everything else - which might increase cost). e.g. the motor will have ground shielding and inline EMI filters on the power lines.</p>
<p>Very good point indeed. I will add that to the requirements.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Lee</title>
		<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-10</link>
		<author>David Lee</author>
		<pubDate>Tue, 12 Jun 2007 20:26:42 +0000</pubDate>
		<guid>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-10</guid>
					<description>FYI, this site seems to have a list of these in-dash computers... 
http://www.carputers.org/
Hope this helps.</description>
		<content:encoded><![CDATA[<p>FYI, this site seems to have a list of these in-dash computers&#8230;<br />
<a href="http://www.carputers.org/" rel="nofollow">http://www.carputers.org/</a><br />
Hope this helps.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: JeffreyBeauchamp</title>
		<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-17</link>
		<author>JeffreyBeauchamp</author>
		<pubDate>Sun, 19 Aug 2007 13:33:44 +0000</pubDate>
		<guid>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-17</guid>
					<description>The requirement that all user-functionality of the HIC shall be touch-screen enabled poses a safety hazard. The driver would have to scan the screen to locate a command button, which would take attention away from the task of driving. I would propose standard media commands (Stop, Play/Pause, Forward, Back, Eject) be implemented via front panel controls with relief patterns on buttons so their functions could be recognized by touch. I realize the requirements state that mechanical switches and buttons may be used to supplement the touch screen; however, if it flashes on the screen, that's where the driver is likely to look first. I have read in various postings that drivers have been distracted by the Toyota Prius power flow readout; making the touch screen mandatory just sounds dangerous. There will also be a need to switch between active devices (phone, MP3, CD, etc.). I would propose that this also be implemented via a front panel control. Some diagnostic information (such as remaining battery power) should likely be considered a requirement for the instrument panel, so the driver would not be required to direct attention to the HIC while driving.</description>
		<content:encoded><![CDATA[<p>The requirement that all user-functionality of the HIC shall be touch-screen enabled poses a safety hazard. The driver would have to scan the screen to locate a command button, which would take attention away from the task of driving. I would propose standard media commands (Stop, Play/Pause, Forward, Back, Eject) be implemented via front panel controls with relief patterns on buttons so their functions could be recognized by touch. I realize the requirements state that mechanical switches and buttons may be used to supplement the touch screen; however, if it flashes on the screen, that&#8217;s where the driver is likely to look first. I have read in various postings that drivers have been distracted by the Toyota Prius power flow readout; making the touch screen mandatory just sounds dangerous. There will also be a need to switch between active devices (phone, MP3, CD, etc.). I would propose that this also be implemented via a front panel control. Some diagnostic information (such as remaining battery power) should likely be considered a requirement for the instrument panel, so the driver would not be required to direct attention to the HIC while driving.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Lee</title>
		<link>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-19</link>
		<author>David Lee</author>
		<pubDate>Tue, 04 Sep 2007 05:47:08 +0000</pubDate>
		<guid>http://www.osgv.org/2007/06/11/human-interface-computer-hic-white-paper-and-requirements/#comment-19</guid>
					<description>We've moved our discussions here:

http://www.osgv.org/nfphpbb/viewtopic.php?p=677#677</description>
		<content:encoded><![CDATA[<p>We&#8217;ve moved our discussions here:</p>
<p><a href="http://www.osgv.org/nfphpbb/viewtopic.php?p=677#677" rel="nofollow">http://www.osgv.org/nfphpbb/viewtopic.php?p=677#677</a></p>
]]></content:encoded>
				</item>
</channel>
</rss>
