but the Si4701 has a USB bootloader and documented Firmware (!)...
this needs time and I don't have time at the moment for this... (sorry I only have one (small) brain and 2 hands)If your looking at the firmware may be you could have a look at the problem I mentioned... I'm almost into beg mode as there is nothing more I can do and I really want to use the advanced features of this dongle...
If (most of) the developers out there would not reinvent the wheel again and again they would easily have time for it (we all could have TMC, EON, "smartreceiving" with the help of a shared database, and much much more)
I have done all steps of the description, but in step 5 (see below) I had some problems. How should it look like?
5. Make sure you have in your skin in the menu.skin the following line
Thank you for your support.
Itís not a trick itís an Audi
Tried this today on my 500Mhz tablet and CPU spiked to 100% as soon as menu.skin loaded. Never came back down. So couldn't get to iceradio.skin.
HARDWARE: Fujitsu Stylistic ST5111w/WiFi and dock, internal Hitachi 500G HD, external 1TB HD, Sierra Wireless Aircard 550, DVD-RW, BoomzBox HD radio, XM Commander, Delorme GPS, Saitek X-52 Pro joystick, BluSoleil Bluetooth, TPMS, FB, Elm327
MEDIACAR menu. Skin
/, I, x, y, w, h, Code;INDICATORCODES
/, B, x, y, w, h, Command;COMMANDCODES, Tooltip
shared database for "smartreceiving" ( (c) by FMode ) means the radio (NOT the silabs, ANY radio) is recording his fieldstrength and GPS coordinates into a database - next time you are driving the same route it will switch sooner to the new stronger (AF) frequency. The frontend thinks there was an AF switch by the radio (means the frontend does not need to be adapted for this - and this is the point !). The radio(driver) thinks it is switched by the Frontend.
That is only one powerful idea to realize...
Here is a list for people you can ask to modify the Firmware:
(4x HQCT tuner implementation, RDS interpretation)
datalex for centrafuse
"in roadrunner" (who has done it?)
(ADS/Silabs tuner implementation, RDS interpretation)
"in roadrunner" (who has done it?)
then there are implementations for the Cinergy 600RDS and for Andre's radio.
these are only the ones I find quickly but I bet (and I know) there are more.
So finally we have 10 people interpreting the RDS - looking for RDS Group 3A taking bits x-to-y, looking into a table with chars.
While 1 (complete) implementation would be enough for all - resulsting in a lot of spare for all of them.
How to identify "complete" ? Easy ! I exposed all RDS attributes (Decoder identification , MS switch, ... which are part of the CENELEC standard) to my interface - there are not more !
If you think "Decoder identification" is useless to display then don't display it.
"But in Lichtenstein we have RDS pagingservice still in use and I want to display it in my Frontend !" Thats the reason why I am moving the raw RDS stream into the Frontends for their availabilty.
"I want to have USN and WAM to the fieldstrength from my HQCT - so your components are useless for me" - wrong ! USN and WAM from the HQCT (which is not offered by the Silabs) are offered per "late binding"
Code:Sub AnyEvent(byref AnyObject as Object) If Radio.Type="HQCT driver" then Dim HQCTsuperspecial as stHQCTsuperspecial Rem Cast Object (pointer to void) to HQCTstructure HQCTsuperspecial=CType(AnyObject, stHQCTsuperspecial) Print "WAM:" + HQCTsuperspecial.WAM Print "USN:" + HQCTsuperspecial.USN End If ... End Sub
Is there any update on using a different path than the C:\Progra..... Mine is on my D drive and I'd like to give this a try.
I got a question.
silabs lags by like 2 seconds (went to the drive in )
is there anyway to fix it with the dll or is the radio just slow???
thanks if you got any info.