Thread: Production Double-Din VGA Touchscreen in the making!

Originally Posted by OldCarDriver

So Mrbmw99 , help me to understand. Should I wait until the new unit will be ready or should I go with the DL065A ? Can you present the advantages of the new unit compare to what you are selling now ?

No only do I think it would be much better to wait a few months for the new design, but, you'll find it difficult to get ahold of the current DL065A's. Stock will be very limited in the future, at least here in the US. There are several advantages over the DL065A. You'd be best flipping through the past thread and you'll see a lot of suggestions and specific features. A short list includes: Built-In Nano-ITX motherboard support, programmable backlit buttons on the face of the unit, non-motorized faceplate, CD/DVD drive, rotary knob, and an AM/FM/RDS tuner.

Originally Posted by andyhardy

You would lose a potential sale here if you didn't make it double DIN and potential future sales for reselling!

The whole point the CID650 was an attractive proposition was the fact that little to no modifying of the dashboard was required, especially important if installing into a customer's car.

Thanks,

Andy

Andy, we're going native double-din for this specific reason.

Originally Posted by FMode

okay...
here it goes:
(I am not Datalex/XTronic - the HQCT makers)

the HQCT consists of 3 main IC's - lets say they cost 15$/€ - do these guys now rip us off with HQCT ? I am sure not.
The casing needs design - and needs to be build - the PCB has to been builded somewhere...

Adding these 2-3 IC's to an existing PCB is more cheap than building an extra piece of hardware. So the integrated HQCT costs lets say 50$/€ ... (50 saves compared to the 99 from the HQCT)

So -> adding as many feature-IC's as possible will raise the price for it - BUT reduce the price of the complete car-pc system (!).... so going on with the GPS module: you will need a casing - you have to pay 150$ (U-Blox) - you need to solder... you will be "ripped off" by U-Blox because they don't want to sell you single units.

What about DAB (I would like to have it integrated!) and Sat Radio ? I feel that this would raise the price and in some parts of the world this hardware would be useless... So ... not a good idea...

But we all could use a analog TV diversity Tuner I guess ? The problem here: I would say this would raise the unit around 200-300$/€ (I wouldn't have a problem with it)... so... not a good idea...


Do you agree with me ?

TV Tuners will not be used - not popular enough for this application. Also, SAT radio receivers will not be included because 1) there are two different systems, and 2) they're too big to fit!

The Microtune AM/FM/RDS module is the SAME module that is used in the HQCT radio. That's what I'm looking to use. Datalex is not willing to sell the parts to their design (programmed chips etc), so it's either buy from them (expensive), or integrate the Microtune module ourselves. I'm going to attempt #2 and see how far it goes.

The GPS will be a module that is cheaper than the U-Blox stuff. I haven't picked one yet. I will design our board to interface with these directly. Since they all have a carrier board (and are not just IC's), they will not even be a physical part of our design, meaning that it's easy for someone to say YES i need one or NO i don't. Saves them money. Not everyone needs or wants GPS, and it's easy enough to make an option.

Originally Posted by Aaaron16

White LEDs please.

The buttons will have RGB LEDs so any color can be set. I'm also contemplating individually assignable RGB values for each button. This might make it nice to "highlight" the current button or action you're in. Of course that would all be up to the frontend programmers, but it just might work out!

- Brett

I had given up on a CarPC project until I read this. I'm watching very closely, keep up the good work.

The Microtune AM/FM/RDS module is the SAME module that is used in the HQCT radio. That's what I'm looking to use. Datalex is not willing to sell the parts to their design (programmed chips etc), so it's either buy from them (expensive), or integrate the Microtune module ourselves. I'm going to attempt #2 and see how far it goes.

The HQCT is with an additional PIC working as USB-to-I2C interface - you won't need that - so you need the Microtune Tuner and the TEF (Stereo+RDS Decoder). So you need both IC's - If you work (in any way) with Datalex you can order a larger amount of IC's (giving both of you cheaper IC's)...
(this would be a buying community then ?)

The GPS will be a module that is cheaper than the U-Blox stuff. I haven't picked one yet. I will design our board to interface with these directly. Since they all have a carrier board (and are not just IC's), they will not even be a physical part of our design, meaning that it's easy for someone to say YES i need one or NO i don't. Saves them money. Not everyone needs or wants GPS, and it's easy enough to make an option.

okay - agree with you now !
PLEASE (!) one pin from the back (ISO connector ?) of the unit to the GPS extension board connector (for a future speed signal).
This connector is only a 12V/5V provider and RS485 (RS232 with 5V) I guess... (connected to a cheap USB-2-serial IC)
I must say that I start to like this extension gps idea more and more....

The buttons will have RGB LEDs so any color can be set. I'm also contemplating individually assignable RGB values for each button. This might make it nice to "highlight" the current button or action you're in. Of course that would all be up to the frontend programmers, but it just might work out!

okay ! Why not !? Cool Idea ! Needs only some multiplexing IC's I guess...
If you do that - you may still have not recognized this:
New Product - Force Feedback (Haptic) Encoder
I was yesterday (as I saw it)

Bye Bye Infill !

Originally Posted by FMode

The HQCT is with an additional PIC working as USB-to-I2C interface - you won't need that - so you need the Microtune Tuner and the TEF (Stereo+RDS Decoder). So you need both IC's - If you work (in any way) with Datalex you can order a larger amount of IC's (giving both of you cheaper IC's)...
(this would be a buying community then ?)
Right, the Microtune and some other stuff. As I mentioned before, I have not out a tremendous amount of research on this aspect of the device. Do you have any information on TEF?

okay - agree with you now !
PLEASE (!) one pin from the back (ISO connector ?) of the unit to the GPS extension board connector (for a future speed signal).
This connector is only a 12V/5V provider and RS485 (RS232 with 5V) I guess... (connected to a cheap USB-2-serial IC)
I must say that I start to like this extension gps idea more and more....
Speed connector? How would this work? We're not going to use an ISO connector, we'll be using a Molex. There will be extra pins for future upgrades and modifications, so this should work.

okay ! Why not !? Cool Idea ! Needs only some multiplexing IC's I guess...
If you do that - you may still have not recognized this:
New Product - Force Feedback (Haptic) Encoder
I was yesterday (as I saw it)
I have seen the Haptic encoder, and I am looking intot that unit as well. I think it's going to be too big though. I don't think there is enough room for it with the DVD drive mounted behind/above the LCD panel. I'm trying to figure out a way though. I've been in contact with Imersion (who makes that unit).

Bye Bye Infill !

- Brett

Originally Posted by Mrbmw99

Speed connector? How would this work? We're not going to use an ISO connector, we'll be using a Molex. There will be extra pins for future upgrades and modifications, so this should work.

oh... I thought of the complete "un-pin-ed" ISO connector at the back of these other crap units

Originally Posted by Mrbmw99

I don't think there is enough room for it with the DVD drive mounted behind/above the LCD panel. I'm trying to figure out a way though. I've been in contact with Imersion (who makes that unit).

That was my main concern too....

I forgot something!
Remote control ! ... You don't need one but a TSOP 1736 which could receive RC5 commands from other remote controls (example: remote controls for steering wheels - VDO Dayton has one)


What are you using as TFT controller IC ? (I am asking because of 800x480 .... I get if I read the manual of these units and its not listed in the resolution list...)

I haven't started on the IR stuff yet, but I will look into the 1736. Thx for the info on that part number...

The rear wire connector for power, audio, and other stuff will not be the ISO. It will be a Molex Mini-Fit Jr. series assembly. I chose this because it's easier for people to buy in the future, instead of a custom ISO one.

This will be accessable from the rear of the unit:


This will be the other half of the plug.


Of course, there will be more pins. Probably 20 or so, that way there are a couple extra for hacks and upgrades.

- Brett

Excellent idea on the RGB LEDs. Giving the programmer the ability to set the backlight color is a huge plus for me.

Originally Posted by hammer32

Being able to use the steering wheel contorls on our Toyota FJ Cruiser is a must! Crutchfield sells a kit that will interface many car steering wheel buttons... if the buttons could be programmable like the front face buttons that would be even better.

oh sorry for the misunderstanding...
The VDO Dayton is a IR remote control which you can stick to your steering wheel powered by batteries. (sends RC5 just like any (home) remote control) (see WinLIRC project)


here is another one - Ampire LF100 (which learns other RC5 codes - the VDO is fixed)


Both solutions can be used in any car (but without MrBMW99 unit you will have to buy a an USB IR RC5 Receiver like the IGOR USB - and you have to fit it somewhere at your dash)

Specific steering wheel buttons can't be supported (IMHO) because of their different protocolls (CAN, analog, I2C, ... ?)