New FM USB module, maybe good for our carputers?

Printable View

Show 40 post(s) from this thread on one page

11-16-2006, 09:35 AM
W3bMa5t3r

1 Attachment(s)

I saw the HID device yesterday too after looking around. Here's what I got with USB Mon...

Vendor: 0x06e1 (ads technologies, inc.)
product id: 0xa155
manufacturer: 0x0409: ads tech

I attached a few seconds of the radio connected and then playing with the instantradio software, to the log file of the data package capture with usb mon. captured just the HID portion. hope this helps... cuz I have no clue about any of this. :) cheers...

Here's the full subtree copy/paste for the device :)

Code:

USB Root Hub Port1: USB Composite Device Hub Power: Self Power Number of Ports: 2 Power switching: None Compound device: No Over-current Protection: Individual Device Descriptor USB Version: 1.1 Device Class: (0) Reserved (defined in Interface Descriptor) Device Subclass: 0 Device Protocol: 0 Max Packet Size: 0x40 (64) bytes Vendor: 0x06e1 (ADS Technologies, Inc.) Product ID: 0xa155 Product Version: 0x0100 Manufacturer: 1 0x0409: ADS TECH Product: 2 0x0409: ADS InstantFM Music SerialNumber: 0 Number of Configurations: 1 Connection Status: Device Connected Current Configuration: 1 Device Bus Speed: Full Device Address: 0x02 Number of Open Pipes: 2 Configuration Descriptor (1) Total Length: 145 bytes Number of Interfaces: 3 Configuration Value: 1 Configuration: 0 Attributes: 0x80 Bus Powered Max Power: 0x32 (100 Ma) Interface Descriptor (0) Interface Number: 0 Alternate Setting: 0x00 Number of Endpoints: 0x00 Interface Class: (1) Audio (Audio) Interface Subclass: 1 (Audio Control) Interface Protocol: 0 Interface: 0 Interface Descriptor (1) Interface Number: 1 Alternate Setting: 0x00 Number of Endpoints: 0x00 Interface Class: (1) Audio (Audio) Interface Subclass: 2 (Audio Streaming) Interface Protocol: 0 Interface: 0 Interface Descriptor (1) Interface Number: 1 Alternate Setting: 0x01 Number of Endpoints: 0x01 Interface Class: (1) Audio (Audio) Interface Subclass: 2 (Audio Streaming) Interface Protocol: 0 Interface: 0 Endpoint Descriptor (Addr: 0x83) Endpoint Address: 0x83, Input Transfer Type: Isochronous Max Packet Size: 0x0200 (512) bytes Interval: 0x0001 Sync Address: 0x00 Interface Descriptor (2) Interface Number: 2 Alternate Setting: 0x00 Number of Endpoints: 0x02 Interface Class: (3) Human Interface (HID) Interface Subclass: 0 Interface Protocol: 0 Interface: 0 HID Descriptor HID Version: 0x0111 Country Code: 0x00 (0) Number of Descriptors: 1 Type: 0x22, Length: 0x00cb bytes Endpoint Descriptor (Addr: 0x81) Endpoint Address: 0x81, Input Transfer Type: Interrupt Max Packet Size: 0x0040 (64) bytes Interval: 0x0a Endpoint Descriptor (Addr: 0x02) Endpoint Address: 0x02, Output Transfer Type: Interrupt Max Packet Size: 0x0040 (64) bytes Interval: 0x01
11-16-2006, 11:42 AM
afterdigital

this may be the choice of radio! thanks W3bMa5t3r!
11-17-2006, 02:26 PM
jbolter

alright, i tried my instantFM in the car on the way to work this morning. it worked pretty well with the included retractable antenna. under a tunnel it cut out and my head unit fm worked fine. i think if i can adapt the connection to use my car's antenna i can get some better performance. i'm going to try to work on that this weekend. anyone have any luck getting the SDK yet so we can get this working in a front end?
11-21-2006, 04:57 PM
jbolter

i just received the sdk from ads. i'm not a very experienced coder but i'm going to look through it all tonight. what would we need to do to make this work with RR or CF?
12-07-2006, 12:46 PM
FMode

sorry I lost this thread....

I remember as my amazon order (I just ordered because I was just curiously) with the ADSTech arrived...

I opened it and it is a 99% copy of the Silabs PCB :eek: !

So If you like to waste your time go ahead and code a driver.
;)

Or just contact the Silabs driver guys...

and:
Why not just coding a driver for every frontend ?
12-08-2006, 01:31 PM
jbolter

Quote:

Originally Posted by FMode

sorry I lost this thread....

I remember as my amazon order (I just ordered because I was just curiously) with the ADSTech arrived...

I opened it and it is a 99% copy of the Silabs PCB :eek: !

So If you like to waste your time go ahead and code a driver.
;)

Or just contact the Silabs driver guys...

and:
Why not just coding a driver for every frontend ?

obviously nobody likes to waste their time. who are the "silabs driver guys" that i should contact? and by getting their driver, how should i use it in a front end? could you provide more information?
12-11-2006, 06:16 AM
FMode

Quote:

Originally Posted by jbolter

obviously nobody likes to waste their time.

hmm.... I don't think so ;) if I see what is done sometimes in the carpc community !

Quote:

Originally Posted by jbolter

who are the "silabs driver guys" that i should contact?

search for "Silabs" in this forum...

Quote:

Originally Posted by jbolter

and by getting their driver, how should i use it in a front end? could you provide more information?

You get the "point" of my software (FMRadioHAL) !
This is crapped in nearly all Frontends expect Centrafuse and here the radio driver interface is somewhat under development and nearly 20% (IMHO) finished.

(and this is certainly also caused by the users of the Frontends asking can "car-xyz support my ding-ding-radio" instead of looking at MS Office realizing that it uses drivers to access printers and then "kicking" for the developer (expect RR) - "use a driver to access the radio!"
and see where we are discussing... :nutz: )
12-11-2006, 12:25 PM
jbolter

Quote:

Originally Posted by FMode

hmm.... I don't think so ;) if I see what is done sometimes in the carpc community !

search for "Silabs" in this forum...

You get the "point" of my software (FMRadioHAL) !
This is crapped in nearly all Frontends expect Centrafuse and here the radio driver interface is somewhat under development and nearly 20% (IMHO) finished.

(and this is certainly also caused by the users of the Frontends asking can "car-xyz support my ding-ding-radio" instead of looking at MS Office realizing that it uses drivers to access printers and then "kicking" for the developer (expect RR) - "use a driver to access the radio!"
and see where we are discussing... :nutz: )

so is the goal for me to get the "point" of your software? because i get the point, but i'm still not sure how that helps me get my ADS radio working in a front end...
12-11-2006, 02:20 PM
mrWRX

The radio software that came with ADS uses a customizable skin. You can edit this skin using Active Skin 4.x. I think this software has been discontinued, so it was hard to get it, but I eventually got the shareware version.

I was also able to embed the radio app in RR using Skinbedder .

Now, all I have to do is to create a skin that goes along with my RR skin. This way, you get the RDS information(song title/artist/station id, etc) as well that Radiator does not support.

I didn't notice anything when I attached it to my laptop, but when I connected it to a 2.1 setup , I noticed a lot of popping noise from the radio not constantly, but from time to time.
12-12-2006, 02:34 AM
FMode

Quote:

Originally Posted by jbolter

so is the goal for me to get the "point" of your software? because i get the point, but i'm still not sure how that helps me get my ADS radio working in a front end...

Where is my posting ???

okay again:
Ask the Silabs developers if they can move the vendor and product id from "hardcoded constant" to a file/registry (which is loaded at startup).

Get their work and change Vendor to 0x06e1 and Product ID to 0xa155 and start...

I can also have a quick look at the sources (VB6 and .NET only) if I got them...
I have a HQCT, Silabs and a ADSTech...
(sorry for no more help but HQCT is first)

Show 40 post(s) from this thread on one page