EEC V file conversion
-
- Posts: 246
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
Also....I added the bank start sym commands to help find the start of the banks easier for me, But is there a way to put something grander ( not even sure that is a word) in the dir file to make the start of banks even easier to see while quickly scrolling through the code? I know the addresses are prefixed with bank numbers, but something the stop at while quickly scrolling would be nice to have. Beginner problems, right?!?!? LOL
-
- Posts: 285
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
I'll have a look at building the jump comments for omae.BOOSTEDEVERYTHING wrote: ↑2024 Mar 28, 08:47Yes, Very useful.. I wish I could build them as fast as you can. I still have trouble spotting the loops in the code most times. I also still have issues following along with exactly where the code goes and where exactly it comes back to. But I am getting the hang of it. I wish it would have exact addresses (or line numbers) listed for where to go next so it was easier to go back and forth to follow along.Yeah, not so much as a comparison source for OMAE, just asking if it were useful for RZASA alone.
Use the one I just posted. Your old one has too many gemlins introduced. Paste stuff into the new in small blocks, run it too prove it, repeat.I will check out the new DIR file today and compare and see how I can improve upon my other DIR file. Do most of the addresses I found for the SYM commands in the old DIR file still hold true, or do I need to start from scratch with those?
Mostly from the strategy documents. Sometimes from other disasseblies.BOOSTEDEVERYTHING wrote: ↑2024 Mar 28, 08:54Another question I have is, Where exactly are the function names, table names, etc, that everyone uses as standard coming from? Do they come from the eec documents or a specific code that was disassembled in the past?sym 12364 "uuwFn072A_Perload>Row" # Row Scaler
FUN 12364 1237F :UW V32768 :UW V16
East Coast, UTC+10.My other question is a bit off topic, It says Australia in your bio but doesn't say where? I was wondering what time zone you are in? Just curious I guess.
As per the new dir I posted, use it, add to it.Also, I have tried adding a sym for table names or subroutines names but it gives me duplicate command errors at times. Is there a certain format to which I need to stick to when doing separate entries for these? And do I keep the SYM with the Func command or in the SYM list?
Thanks again for all the help.
The examples in the new dir show the required format.
Payload, scalars functions and tables end in different locations in a definition file, so it pays to organise the dir accordingly. I keep the associated sym and fun together.
How about flashing neon lights, lol.BOOSTEDEVERYTHING wrote: ↑2024 Mar 28, 13:30 Also....I added the bank start sym commands to help find the start of the banks easier for me, But is there a way to put something grander ( not even sure that is a word) in the dir file to make the start of banks even easier to see while quickly scrolling through the code? I know the addresses are prefixed with bank numbers, but something the stop at while quickly scrolling would be nice to have. Beginner problems, right?!?!? LOL
Use the comment file to add some ascii art.
Code: Select all
###### ###
# # ## # # # # # #
# # # # ## # # # # #
###### # # # # # #### # #
# # ###### # # # # # # #
# # # # # ## # # # #
###### # # # # # # ###
-
- Posts: 246
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
Perfect!!! Thank you very much. I’ll be on this this weekend for sure. I’ll post up when I have some progress made.
I would really like to name the subroutines and add comments for what they are actually doing but some of them are a bit confusing for me. There seems to be a ton of them related just to the p0420 code. I didn’t realize that it took so many subroutines to test for one fault. There really is a ton going on in the background.
I would really like to name the subroutines and add comments for what they are actually doing but some of them are a bit confusing for me. There seems to be a ton of them related just to the p0420 code. I didn’t realize that it took so many subroutines to test for one fault. There really is a ton going on in the background.
-
- Posts: 246
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
I would really love to see what the engineers saw when they were tuning these vehicles new. Before the program was run through the assembler to build the bin file.
-
- Posts: 285
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
Branch comment file;
-
- Posts: 246
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
I have no idea how you can do that so quickly. Thank you very much for your help!!!! Also, I added some things to the new DIR file and to my comparison spreadsheet. I made new sheet to compare OMAE2 and RZASA for simplicity. Maybe I can work on a combined sheet in the future once I can get a grip on building a good spreadsheet. I think I want to get the actual functions of the functions, tables, and subroutines and use that as my first column and put the actual addresses after that in columns thereafter. So I guess I will need to do a bunch of investigating before I can do that.
Anyways. Here is the updates!!!! Thanks Again!!!
Anyways. Here is the updates!!!! Thanks Again!!!
- Attachments
-
- OMAE2_NEW.zip
- (231.82 KiB) Downloaded 36 times
-
- Posts: 285
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
Thanks.
It's an ugly spreadsheet that does the jump comments, sometimes it works ok'ish other times it fights all the way. For omae2 it wanted to do +E0 scientific notation math for any address with e followed by numbers in it instead of text. Ended up doing a pile of manual fixes.
Comparison spreadsheets can be handy for guiding SAD development.
It's an ugly spreadsheet that does the jump comments, sometimes it works ok'ish other times it fights all the way. For omae2 it wanted to do +E0 scientific notation math for any address with e followed by numbers in it instead of text. Ended up doing a pile of manual fixes.
Comparison spreadsheets can be handy for guiding SAD development.
-
- Posts: 246
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
Comparison spreadsheets can be handy for guiding SAD development.
Very true. But I think I am picking up disassembly much faster than spreadsheets. lol. While do my comparison spreadsheets I did notice the scientific math a ton while copying addresses over. I had to change the cells to text format. For some reason, sometimes it will change it back and I don’t catch it and I’ll come back to a weird address. Like 5800000. lol.
-
- Posts: 246
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
JSA.....If you could help me with a completely unrelated spreadsheet problem I am having, I would appreciate it? I am trying to make a build sheet for some transmissions I am building for people in excel. I would like to have a menu option or the snap ring and pressure plate choices that I have so I can select a thickness and it displays the part number and thickness of the plate or ring in the sheet, instead of having all of them listed and checking the one I use. I can figure out how to make a menu for thickness or part number, but I would like to select the thickness and have it display thickness and the corresponding part number for that thickness plate or ring. I can post what I have if you think you can help? I have several dropdowns I would like to have on the sheet for different clutch packs. Also I am having problems putting all of the data on one or two pages, I cant seem to find any videos on that. I want to be able to print it out and give it to the person I built it for. Also I have 3 options for build types that I would like to have a drop down for with descriptions of each build displayed on the printout, only the build selected would print on the sheet. I also can not figure out how to do that. Am I using the incorrect software for something like this? Should I be using something else? Thanks again for the assistance if you can help, if not, thanks anyways, LOL.
-
- Posts: 285
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
Sounds like a combination of lookups, named ranges and drop lists would cover it. The build type print out would need formulas to display the required output for the selection choice.
No I'm not inclined to get involved with it.
No I'm not inclined to get involved with it.