Okay, I placed the tripcomputer UI file in my datazip and it doesn't boot past the start up screen. I did change the file name to 800_480 and commented out the trip computer I created just to be sure they didn't conflict with each other.

 

I would think there should be 2 files:

tripcomputer.ui <- goes into COMMON folder

tripcomputer_800_480.ui <- goes into 800_480 folder.

 

That should get it father along...

 

Neither the Gurjon or kiker zips had common tripcomputer ui's. I found another on that did have both. Installed both and can't get past the start up screen.

 

Do you want me to PM the two files to you or post them here?

Whatever is easier.

I've also found where I keep NavNGo's original trip computer files. If Gurjon's skin does not make any changes to the common's tripcompouter.ui then it would not be included into his skin, and iGO will use one from default DATA.ZIP.

The skin that has both might use some custom codes that need the rest of the screen... I could take a look at it...

I have nothing further to report on this. Other than kerosene. there doesn't seem to be much interest for me to spend hours on end with this project.

With Boris' assistance I tried importing trip computers from the I-GO8 forum. The unit just hanges when booting and I can't figure it out. It's beyond my abilities.

If anyone else can get one going with a memory function, let me know. Otherwise I'll make do with what's on the first page.

N-S-E-W, nice work messing with this trip computer stuff. I have not been on here much lately since first my unit died, and then once I had it fixed I just made some small changes to my interface and then got busy with the holidays and work. I have always been interested in a trip computer with nice info like average speed and all the other stuff you made. I hope to have time in the near future to add some of these things to my setup at some point. I do remember a few months ago reading a post that mentioned how to save info for later but I think that had to do with remembering the state of a setting - i.e. voice mute on or off - and it had to be done with scripts. Have you done anything else with the trip computer?

N-S-E-W, nice work messing with this trip computer stuff. I have not been on here much lately since first my unit died, and then once I had it fixed I just made some small changes to my interface and then got busy with the holidays and work. I have always been interested in a trip computer with nice info like average speed and all the other stuff you made. I hope to have time in the near future to add some of these things to my setup at some point. I do remember a few months ago reading a post that mentioned how to save info for later but I think that had to do with remembering the state of a setting - i.e. voice mute on or off - and it had to be done with scripts. Have you done anything else with the trip computer?

Welcome back. I saw you took a little heat when you had to replace your last unit. Some of the members were blaming you because you were modding the unit and thought that's why it failed. I guess that's the chance we all take when we mess with it. Glad you got it replaced under warranty.

I haven't done anything else with it. The script stuff is over my head. I just don't understand how to put it all together. Now that I've rearranged everything, I think I'm going to keep it. I sorta like the look although I might try to shrink the mute and end route buttons to be about the size of the sat button and put them on the far right side of the top bar. I also got rid of my over sized ugly compass and am using the smaller linear compass.

I also got rid of my over sized ugly compass and am using the smaller linear compass.

Can you tell me which one you're using? Thanks

I also got rid of my over sized ugly compass and am using the smaller linear compass.

 

Can you tell me which one you're using? Thanks

Not sure who created it, but I believe it was in a zip lava had posted. A picture of what I'm using now is in this thread. http://avic411.com/forum/viewtopic.php?t=21076

N-S-E-W,

That heat I took from my head unit dying was total BS and pissed me off. I know I hardly did anything to my unit other than so cosmetic changes which I know is MUCH less than what other members have done here. Anyways, I ran into a small roadblock on this trip computer thingy. What code did you use to get the time based info? I'm trying to get time_total, time_driving, & time_stopped to work but nothing shows up in the area I setup. I got speed and distance stuff working though. I plan on setting up a new layer that I can turn on and off for this trip computer stuff.

N-S-E-W,

 

That heat I took from my head unit dying was total BS and pissed me off. I know I hardly did anything to my unit other than so cosmetic changes which I know is MUCH less than what other members have done here. Anyways, I ran into a small roadblock on this trip computer thingy. What code did you use to get the time based info? I'm trying to get time_total, time_driving, & time_stopped to work but nothing shows up in the area I setup. I got speed and distance stuff working though. I plan on setting up a new layer that I can turn on and off for this trip computer stuff.

Vorian - I didn't mean to imply the mods caused your other unit to brick. I doubt it did. I'm actually surprised I haven't bricked mine yet. My crash file is about 1/2 the size of my navigate800 file already. It'll only post info in the crash file if it loops over and over, no entries are made when the system hangs at the start up screen. If it did I probably would have filled out the available space on the drive with just the crash file.

Try these for time:

textmodel_timespan="other.tripcomputer.time_total"

textmodel_timespan="other.tripcomputer.time_driving"

textmodel_timespan="other.tripcomputer.time_stopped"

I didn't try out the stopped textmodel as I only created room for six entries. I figured if I really wanted to know stopped time I could deduct the moving time from total time.

Let me know how you do. I'm at a standstill for now, but that's okay I can reset, pause and resume anytime I want. But if I reboot I loose all previous data.

Vorian - I didn't mean to imply the mods caused your other unit to brick. I doubt it did. I'm actually surprised I haven't bricked mine yet. My crash file is about 1/2 the size of my navigate800 file already. It'll only post info in the crash file if it loops over and over, no entries are made when the system hangs at the start up screen. If it did I probably would have filled out the available space on the drive with just the crash file.

 

Try these for time:

 

textmodel_timespan="other.tripcomputer.time_total"

textmodel_timespan="other.tripcomputer.time_driving"

textmodel_timespan="other.tripcomputer.time_stopped"

 

I didn't try out the stopped textmodel as I only created room for six entries. I figured if I really wanted to know stopped time I could deduct the moving time from total time.

 

Let me know how you do. I'm at a standstill for now, but that's okay I can reset, pause and resume anytime I want. But if I reboot I loose all previous data.

Ok... I see what I did wrong. I had .full_text and the end of the string... oppsie. Once I get this all working right I plan on putting this all in a seperate layer that I can call up with a hidden button somewhere so it does not take up much more screen space. I do not have much interest in keeping trip info between reboots so I do not think I will bother trying to figure out how to make it keep that data. If things change and I find a need for that function then I will try to figure that out.

Anyways, I was not annoyed with you. I was annoyed at the posters that gave me heat because they did imply that I killed the unit with my small mods. None of the cosmetic changes that we do could possibly cause a unit to die the way mine did.

For those of us who haven't figured out the scripts yet, any chance you would have time to post them? These look VERY useful for those of us who drive for a living!! If you can, thanks and nice work!!

Anyways, I was not annoyed with you. I was annoyed at the posters that gave me heat because they did imply that I killed the unit with my small mods. None of the cosmetic changes that we do could possibly cause a unit to die the way mine did.

Hey Vorian, fuck em mate, your kit is your kit: to do with as you please. And I agree that what we do here isn't going to make these units completely die, it aint unheard of for modern electronics to give up the ghost without any tinkering. So I reckon you should keep on doing your mods etc., just like the rest of us

Anyways, I was not annoyed with you. I was annoyed at the posters that gave me heat because they did imply that I killed the unit with my small mods. None of the cosmetic changes that we do could possibly cause a unit to die the way mine did.

Hey Vorian, fuck em mate, your kit is your kit: to do with as you please. And I agree that what we do here isn't going to make these units completely die, it aint unheard of for modern electronics to give up the ghost without any tinkering. So I reckon you should keep on doing your mods etc., just like the rest of us

Trip computer info in this thread: viewtopic.php?f=34&t=24580&start=30

You can now have a trip computer within it's own user interface (see page 3), or just download the whole zip in the first post of that thread and use as is.