bsnively

These updates are fantastic. I have been wanting to do something like this (hook up OBDII in the navi unit), but haven't been able to do it. Great progress so far!

I can not believe some of you have not yet realized that the problem is not in the program or device, but how to connect that device to F900BT ... The only question is whether via USB, Bluetooth or maybe wireless

Could you enlighten me how it's not possible to use a ELM OBD2 to usb converter w/ the appropriate ce drivers/etc? I must be missing something.

Thanks,

Ben

This is the link I got it from - source zip file is at the bottom

http://www.qcontinuum.org/obdgauge/

Thx,

Ben

I know it requires the .net compact framework (has the source with it as well as the binaries)

thx,

Ben

I guess this means no body has attempted to install the 2.0 compact framework.

Another question - what type of project (using visual studios .net) would I want to create to play around w/ creating some custom applications? Every one I create seems to need the .net framework?

Thanks,

Ben

I am looking at migrating a tool that is written for windows ce, but it relies on the .net compact framework.

Has anybody tried to load the compact framework onto the avic f-series

Would like to hear about any success or failed stories.

Thanks,

Ben

I installed mine in a Cayman which has a very similar setup (this doesn't help w/ diagnosing, but no issues w/ mine)

What option do you have w/ the car: Base, Sound Package Plus, Bose (hopefully not since it uses the MOST fiber system to send signals/etc)?

Thanks,

Ben

I am considering getting an elm chip/cable from the usb to try this.

I understand if the answer is no, but would you be willing to loan out the source to me w/ the understanding that the source is the rights to you and any changes I make, you will own?

(much like some of the open source licenses that allow you to use, but have to submit edits back...)

Thanks,

Ben

Wow, that looks really great. Good job!!

~Ben

any chance of getting this hosted someplace - rapidshare is very, very slow and other link is down due to ISP issues.

Thanks,

Ben

Very Impressive!

Great work!

~Ben

The other cruise that you are using is one that uses a different screen/state rather than being a layer in the navigate 800_480 ui file (which IDT is using).

 

Then - if you have it as a layer - you can set the z value for transparency/etc...

 

Thanks,

Ben

 

\

I set the z to 500 and I got the foreground transparent but the backgroud is still there. Do I need to remove the BMP file? What should I set the z value to?

Thanks,

Bryan

Did you try to set the z value for the image (or if you don't want the image there at all - removing it)?

Thx,

Ben

The other cruise that you are using is one that uses a different screen/state rather than being a layer in the navigate 800_480 ui file (which IDT is using).

Then - if you have it as a layer - you can set the z value for transparency/etc...

Thanks,

Ben

As always - great looking Mod - Wondering job IDT.

.VPR files.

Newbie question - where are the VPR files? I've tried searching both the base gurjon files, the backup flash I have, and the internal data.zip.

Thanks,

Ben

Looks great.

Really looks a lot better than what I had so far - great work. I may simply grab what you've done so far.

Thanks!!

Ben

Now it just seems like I'm trying to get post counts up, but... here's a pic.

need a lot of work - I know...

Alright - this is how you get it to show up.

In the state area (say speedometer.ini in the common folder) or wherever you are putting it.

You need this line in the uselayer section:

Then you need to have the init script put it where you want it:

the ui_Route.y moves it to a variable position - the variable being d_slrouteDS_y. The last thing that needs to be done is in the 800_480 file - need to define where the y location is for that variable.

So - in my example the Speedomter_800_480.ui has:

Which places the bar at the y location of 352.

Worked pretty well for me. the ported speedometer extension now has the route bar on it..

Here are the two complete files so far - need A LOT of work:

;--visota






;-- Tekuschaja ulica









;-- skrosti	








;--Znak zapretnyx povorotov

;

;-- Ukazateli povorotov--
;-- "Pvoroti" button 


;AK	;-- blizaisij pavorot







;-- vijezd iz kolca



;-- Compass	
























;--gurjon Speed kamera 

;-- Speedcam add




;-- gurjon znaciok kamery --

;




;-- gurjon distancija / sredniaja skorast --















;-- gurjon knopka vykliucenija zvuka kamery --


;--cifry


;--Time to turn 








;-- gurjon knopka perekliuchateli waipoint --




;--gurjon -- flazki






;--gurjon Adress navigaciji
;;	







;--gurjon -- vremia pribitija v cel 






;--gurjon -- rastojanie do celi















;-- speed limit












;-- proidenoe rastojanie






;-- AVG speed










;-- "Trip" button 




;-- "Previous State" button 


;;

I wanted to find this out too. On the Gurjon Speedomter extension, the only other iconmodel that I see is the

But this doesn't seem right from the name of it...plus the x/y coordinates are off for where it was on the screen.

Wonder if it's not using an iconmodel to draw that? Anybody have any suggestions...?

(elegant bump I suppose......)

EDIT:

Maybe something to do w/ this in the script: ui_Route.y d_slrouteDS_y - moving the ui_Route to the y coordinate to be seen??

I'll play around w/ it a little too...

No problem at all - I should have done a better job highlighting the point that this is a part of Gurjon that was pulled out.

EDIT: To confusing - see post below that describes how...

Thanks

Ben

"Just like the trip computer screen, this screen requires people to move over two ui files. One inside the 800_480/ui directory and the other in the common/ui directory"

 

What 2 files do I move, and where do I move them?

 

********

 

"Obviously the destinationdial.ui goes in the common/ui path and the destinationdial_800_480.ui goes in the 800_480/ui directory"

 

Where is destinationdial.ui coming from and how do I get it?

 

********

 

"These new ui files need to be included in the main.ui file in the 800_480/ui/ directory as well. Just follow the convention/grouping you notice"

 

Convention/grouping? I don't even know where I'm supposed to be looking!

 

********

 

I've got the Gurjon skin working, do I have to stop using it? If not, won't overwriting the data.zip make it stop working? This data.zip is 3 mb smaller than my gurjon data.zip.

 

Thank you in advance to anyone who is brave enough to try straightening this out for me!

 

icps - is there any way someone could post the needed files for this mod?

Like NSEW said. This is for people who don't have the Gurjon skin and want that screen. You don't need t do any of this with the Gurjon Skin. While I really like that skin, i decided to revert back and really liked this screen from it.

you can get the destinationdial ui files from my data.zip that I posted. What you do is unzip it and look at where they need to go in yours and it's already done in the posted version. For example the destinationdial_800_480.ui is located in the posted data.zip/ui_pioneer/800_480/ui directory.

if you open the main.ui file. You see a set of imports. You will notice that the 800_480 imports are in one main group and the common or the other. This just means type in the line "import ..." to essentially include the different ui files in the running system.

All the files needed if you don't have the gurjon skin are posted in the data.zip file. Again - if you are using the Gurjon skin, you don't need any of this. That's where most of the work came from (I just pulled it out and put it in it's own state transition...

Thanks,

Ben

You probably already did this, but just to make sure - grab the speedometer.ini and speedometer_range.ini out of the 800_480 directory.

Nice catch on the template line, must have forgotten that one step on the previous post...

Also, the Speedometer ui files are for a different view I'm working on. it's the digital speedometer screen that looks like this:

Thanks,

Ben

..

That worked great. Thanks IDT.

Speedometer is now working/etc... I was missing the speedometer range attachment...

Uploaded new data.zip to main page and altered instructions.

Thanks,

Ben

I was missing some. I just had this part:

ATTACH_SPEEDOMETER sprSpeedometerPointer "speedometer.ini"

bummer - thanks - I'll give that a try...

~Ben