HQCT Module (new thread following HU RDS/RDBS)

**TheLlama** · 03-18-2006, 11:37 AM

Ok, Curve ball:

Racemier and Diogenes, I've been looking at the code some more, and I think it would be a heck of alot easier to just build my driver from the specifications instead of based on someone else's code. I understand the basics of the transactions. 32 byte packets containing either control sequences or a status report. Are the more detailed software specifications available yet? If not, can you point me toward the right region in the source?

I just wanted to mention, to any Linux users, that I am writing a driver that runs as a kernel module and is exposed to the user environment as a character device. So you can just pipe stuff to and from /dev/radio for example.

Thanks guys, great work!

**emumanXM** · 03-18-2006, 09:00 PM

Lets stop acting like children and a$$holes. The radios will be ready when they are ready and a price will be determined when a price will be determined and thats that. For all you who are pooping your pants about the software, I have something that will save your drawers. I have the philips control software which will control the TEF6892 and the Microtune tuner containing the TEA6849. You need to build a 74LS05 parallel port I2C interface to interface the I2C port to your parallel port. The software tunes and aligns the tuner, configures the audio processor, and decodes all RDS/RBDS data and has a radio text display. A pic of the software in action is at the bottom of page 4. A link is also there too. If anyone wants to host it, please let me know if the link is dead. Please don't ask me for support, as I am not in the position to give any because I know very little. The TEA6849 and TEF6892 datasheets should answer all your questions.

Jonathan

**TheLlama** · 03-18-2006, 10:08 PM

Originally Posted by emumanXM

I have the philips control software which will control the TEF6892 and the Microtune tuner containing the TEA6849. You need to build a 74LS05 parallel port I2C interface to interface the I2C port to your parallel port. The software tunes and aligns the tuner, configures the audio processor, and decodes all RDS/RBDS data....

Why do we want to do that if they have a usb pic controlling the thing already?

**Diogenes** · 03-19-2006, 04:10 AM

Right,

besides, we supply the unit WITH software that does work, software WITH source code so it can be modified to anybodys particular taste.

Diogenes

**camsgs3** · 03-19-2006, 08:04 AM

Originally Posted by emumanXM

Lets stop acting like children and a$$holes. The radios will be ready when they are ready and a price will be determined when a price will be determined and thats that. For all you who are pooping your pants about the software, I have something that will save your drawers. I have the philips control software which will control the TEF6892 and the Microtune tuner containing the TEA6849. You need to build a 74LS05 parallel port I2C interface to interface the I2C port to your parallel port. The software tunes and aligns the tuner, configures the audio processor, and decodes all RDS/RBDS data and has a radio text display. A pic of the software in action is at the bottom of page 4. A link is also there too. If anyone wants to host it, please let me know if the link is dead. Please don't ask me for support, as I am not in the position to give any because I know very little. The TEA6849 and TEF6892 datasheets should answer all your questions.

Jonathan

please tell me how is that carPC friendly?? + alot of people on this forum will have no idea how to set that up(what u descibed above)myself included

Ther are alot of peps, like myself that cant develope ****, like what u mentioned above sounds like all starwars **** to me, i would have no idea where to begin...and if im paying money for the hardware i would like a plug and play device that would let me load up any frontend and start working

**TheLlama** · 03-19-2006, 10:37 AM

Originally Posted by Diogenes

Right,

besides, we supply the unit WITH software that does work, software WITH source code so it can be modified to anybodys particular taste.

Diogenes

Yup. Things a difficult now because the software appears to still be in its first draft and the damned module hasn't even been released yet. How can we complain about software support for something that cannot be purchased?

**Diogenes** · 03-19-2006, 10:47 AM

Hi,

camsgs3 should not only write posts but also read what is written by others, if you can copy an exe file to your carPC and if you can make that exe run you have all you need to use the HQCT. You also need to know how to hook up power to it, an antenna is needed and the audio output must be connected to some kind of amplifier...

Diogenes

**TheLlama** · 03-19-2006, 11:39 AM

Originally Posted by Diogenes

Hi,

camsgs3 should not only write posts but also read what is written by others, if you can copy an exe file to your carPC and if you can make that exe run you have all you need to use the HQCT. You also need to know how to hook up power to it, an antenna is needed and the audio output must be connected to some kind of amplifier...

Diogenes

I think he was referring to the idea of interfacing i2c over the parallel port, etc..

**ccsnet** · 03-19-2006, 03:09 PM

Guys - found this... not sure if its any use but allows NMEA / TMC output...

CTRM-03 FM RECEIVER MODULE WITH RDS/TMC

The CTRM-03 is a small and sensitive FM digital receiver module that
decodes RDS and TMC information with stereo sound output.
It can be easy integrated into devices for mobile navigation suchs as
PDA’s, PNA’s etc. The SMD PCB can be soldered directly onto
another PCB.

Main Features
- Digital FM-PLL Synthesized high sensitivity receiver
- Frequency FM 87,5 MHz – 108MHz. high quality stereo output.
- Integrated RDS/TMC decoder, with TTL output
- Universal Open TMC protocol and NMEA protocol.
- Power save function and low power consumption
- Spacing for USA and EU possible
- RDS (EU) and RBDS (USA-Japan) decoding
- Sensitivity 3uV or better
- Small SMD single side component pcb of only 16 x 32 x 2,7mm

Terran