Well that is excellent news, The device I am working with is the NVSRAM module being sold on moates site specificlly for the 1227730/1227727 ECU's Let me know if there is anything i can do to help you along with this.
thx
Printable View
Well that is excellent news, The device I am working with is the NVSRAM module being sold on moates site specificlly for the 1227730/1227727 ECU's Let me know if there is anything i can do to help you along with this.
thx
I would need the hardware itself to test as well as the documentation on how to communicate with this thing
The Turbo Buick community seems to be gathering interest with this...
I expect more of a demand to develop the T31 .adx
It takes 2 seconds to convert the ADS file there to ADX: http://www.tunerpro.net/downloadBinDefs.htm. Not sure if that ADS file is right to begin with tho, but I guess some people in the Turbo Buick community already tried ? I would think people want to tune these things and already have an ADX file... maybe ?! :thumbsup:
Oh, I see. Do people that use scanmaster get more data ? Because the data stream of the ECU wouldn't change, so I would assume they would get about the same info. That ADS file is pretty complete. It's just that these 160 baud ECUs don't have much info in their datastream (and are slow as hell :D)
Hello 34Blazer. Some of the Turbo Buick guys have related the same concern to me about the lack of parameters in the adx file. I worked on it today and they seem happy with the initial outcome. The adx file was set up for a 10K resistor to be across terminals A and B. This changes the last 5 bytes in the message. I changed the file to work without the 10K installed. This makes available the knock retard parameter that is incredibly important to the Turbo Buick community. I also add more of the bit parameters. All of the error codes are in this adx. I think before there were about 5 or 6. The ranges for the analog values are also set up. This makes the gauges work correctly in ALDLDroid. Let me know if you have any comments. Moderators, feel free to move the attached adx to the reference pages if you like!
John
That makes sense now, awesome work John!
I'm thinking the app needs more ADX files already bundled in it but I'm not sure how to display it so that it makes sense. For some people, seeing just the code mask doesn't help and sometime there is a lot of applications for an ADX file so it's hard to list them all. I also have to rely on users to tell me if an ADX file is good or not as I don't have all the setup possible on my bench test (obviously). I will have to think about this some more :D I'm surprised nobody came up with a proper ADX files database yet, the TunerPro website is the best thing I have seen and it's not all that great :|
3400tZ clear out your PMs please..
Now I have a question
I am using a in dash unit and there are a bunch of people working on custom ROMs for it one of them added a button to the navigation bar but that button will not detect the app.. I inquired about how his code detects apps.. here is the post
http://forum.xda-developers.com/show...postcount=4771
Is this something you can add? it is not a major thing if you cannot, just thought it would be nice
Oh yeah another thought, I will be using my tablet on a couple different cars, the display dash is different any thoughts on being able to have 'multiple' dash boards or one store with the adx (sort of like TunerPro)?
Sorry, I've just cleared my PM, my inbox keep filling up. I have deleted almost everything now, should be good for some time :happy: I'm also still not receiving email notification for this thread, this forum hates me :laugh:
Can you please give a bit more context about that button you're talking about ? Where would it be and what would it do ? I'm not sure what the nav bar is and I'm not sure what the button should do and I would rather not have to read that 480 pages thread if I can :laugh:
The dashboard are stored outside the ADX in a main.json file in a dashboard folder so having different dashboards across devices using the same ADX file should be no problem. The reason the dashboard aren't saved back in the ADX file is that desktop and mobile are just too different and most of the stuff in the ADX dashboard makes no sense on mobile so I created my own thing. I wanted to talk about Mark about possibly making the ADX format more flexible in that section but I think he hates me as much as this forum for some reason :laugh:
3400tZ,
the button is on the navbar, which is the lower bar on most devices that has return, home, apps on it. In this case it is custom. When it is pressed it looks for apps that have this (Intent.CATEGORY_CAR_MODE) it then will pop up the Icon for the app. I think that is it, I can get some pictures next time I am in the car
OK, Different dash boards across devices will be nice, but what about different dashboards on the SAME device?
I think I understand for the car mode thing in the nav bar. I could try something but as far as I know, I don't really have any way to test, right ?
On the same device, you can already swipe across dashboard pages and add indicators and stuff... Is that what you mean ? Or I'm missing something ? :D
I can test it
No what I mean is having the dash board pages set up for my $8EA, then being able to load a completely different one for another BIN (Like $8D) as there might be some variables that are different or not in one or the other ADX
Ha, sorry, got it now... Yeah, I think the right way to implement that is with a "car profile" thing that would allow you to change car profile on the same device. Profile could contains ADX, XDF, BIN, dashboards, etc...
Problem right now is that I do take note of things to do but the list just keep growing and I don't have time to do much... Moving in the house I just bought in exactly 1 month, etc etc... Yes I know excuses, excuses :laugh:
I hope to have time for more in a near future tho, time will tell :)
I might be able to come up with something for your car mode thing soonish tho, I will let you know.