By the way, you guys should watch these videos about HTML5...
It explains a lot and you will not have any questions about its capabilities...
Pretty awesome videos explaining why it is the best choice... Oh and apparently you don't need a browser...
on android/iphone it's integrated into the os, you just don't see the addressbar and control buttons, under the hood an engine like webkit/blink is working which is the base of every browser.
Originally Posted by redheadedrod
lets keep call it browser, cause it uses the same engine ;) correct me if i'm wrong
Yep, it's a browser. Or an interpreter if you prefer. At the end of the day, there has to be an engine of some kind that reads the html and converts it into something you interact with. This also explains why no web interface will ever be as responsive as native controls. The additional processing and API layers just add a lot of overhead to each button click.
Personally, I think trying to build a "universal" carPC platform is a little bit na´ve. Everyone has different priorities, and no system, regardless of hardware or software will be capable of meeting them all. I think that's kinda why everyone got into carPCs in the first place, and why there are so many different visions of what carPC hardware and software looks like.
Still, never hurts to try something new. Keeps things moving, and that's a good thing.
"We want the parts used to be widely available and provide detailed instructions so that anyone with the desire can integrate a computer into their car."
I for one would be thrilled with a standard platform that even I can understand. (Yes, meant to be derogatory to me...) If you have seen my work log, you'll see that my aptitude is more towards the hardware, audio, wiring and designing/ building of physical pieces for a project, I suck at the software side. I would not think twice about hacking into my HVAC system on my truck and connecting to it if I was confident that the computer being connected to it would function as intended. The sad reality is I know I'm not capable of writing or debugging the software for it.
But the sad reality is I have no programming skills and can't seem to get my head around it, I would have to take a full on course to get it; hacking away at home gets me no where close to the skills I see used here or what I would require to undertake a project like this.
On the other hand, my interest in it and desire to be able to install something more advanced like this is very high!
If you anyone needs a test mule willing to connect stuff to a fairly current vehicle, my truck and myself are both willing and the automotive wiring side of it is no issue for me, I understand it pretty well.
Heck if someone offered an ISO image of a FE fully functioning with voice control etc. that could be loaded onto any PC hard drive and work with just updating drivers for the hardware, I'd pay for that.
We are not all blessed with the 1010101010101010 gift but I'm sure I'm not alone. It doesn't make me love this hobby any less!
It's an ambitious goal, but we are going to do our best to make it a reality.
Originally Posted by PhilG
We'll keep you updated, and would love to use your guinea pig!
Too bad QNX isn't willing to release its CarQNX package... That sucker is what all of the OEM packages are setup for from the big manufacturers...
And it uses HTML5 technology. If you look at the videos they are using a lowly ARM processor in the videos. I don't know about anyone else but that thing is as fast as any native application I have seen.
I hope your project succeeds, and in the end it brings lots of great new and easy to use improvements to the hobby. I wish I had something to contribute, but I'm just another Average Joe. My hobby skill sets are Corel Draw, and hardware integration.
i would suggest more than one brains. Tesla model S, has a separate brain for each monitor. (and i suppose a main brain to send info to both?? ). in my car i have created a digital dashboard using arduino and a 7 inch LCD. (but my car did not had any OBD or ECU at all)
having more than one brains, could make both maintenance, and installation easier, since you would have to do it part-part. only problem is, how they communicate one another!
that is part of the plan. Each Node can provide different services. How all this stuff gets configured and discovered by the system has to be figured out, but i think we find a solution for that.
Originally Posted by settra
One Masterbrain may do the configuration, to check which devices and services are available, to provide those informations to the Frontend and share it with the nodes, so they can use each other to use their services. (for ex. media node should know there is a OBD Node which can provide speeddata of the car to control the volume settings)
one other part, is what cars will it be meant for.... cars have different communication protocols (of the OBD), some provide more info than others, and some control more things from the ECU than others (etc the windows). what you sed bennY is good. one node could be used to understand all the stuff the car can provide, and then "tell" the other nodes what they should or shouldn't do. but it would require great programing from some one , to understand a wide variety of cars... woulden't it?