Hello,
in one very old post I found that user: decipha was able to convert some tune for SCT to .bin format.
Please, will anybody be able to convert .frg (it should be format for DIABLO SPORT) to SCT format (it is .cef) ????
Thank you very much
Moderators: cgrey8, EDS50, Jon 94GT, 2Shaker
-
- Gear Head
- Posts: 1
- Joined: Tue Feb 20, 2024 10:09 pm
Re: Convert .frg to .cef (SCT)
Also came here for this. User appears to not be part of this group now.
- cgrey8
- Administrator
- Posts: 11268
- Joined: Fri Jun 24, 2005 5:54 am
- Location: Acworth, Ga (Metro Atlanta)
- Contact:
Re: Convert .frg to .cef (SCT)
I don't know of some programmatic way of converting SCT tunes to bins, however I have heard that SCT chips were readable by Moates chip-readers and that's how they were "converting" SCT tunes to bins by simply reading the tune out.
As for Diablo frg formats, unless those chips are also readable via the chip-readers, I'm not sure how that's done. I do recall there was some company, maybe Diablo, that designed their chips specifically to NOT be easy to read just to make it a little more annoying to extract the tune. To read them requires the reading software periodically update the ROM's SPC (Slave Program Counter) like the EEC would at runtime. I don't know how sophisticated the anti-extraction algorithm is, but it may even require breaking the memory up into logical blocks of 50-100 bytes, and randomly reading each block out, then putting the pieces back together into a contiguous format. If that's all they did, I believe that would be a fairly trivial thing to do, but I don't know of any reading software that was ever modified to actually do that.
Now if their anti-read protection logic is more sophisticated than just putting a counter on how many bytes have been read without an SPC update, then extracting the bin successfully may be more problematic. Although my guess is they just lock up the chip and/or return garbage if you read more than about 500-1000 bytes without sending an update. That's a fairly unlikely thing for the EEC to ever do at runtime hence how the protection logic doesn't affect the EEC's ability to read the chip. Any "real logic" is not going to consume the instructions and data contiguously for that many bytes without hitting a branch/jump of some kind, which would update the SPC.
As for Diablo frg formats, unless those chips are also readable via the chip-readers, I'm not sure how that's done. I do recall there was some company, maybe Diablo, that designed their chips specifically to NOT be easy to read just to make it a little more annoying to extract the tune. To read them requires the reading software periodically update the ROM's SPC (Slave Program Counter) like the EEC would at runtime. I don't know how sophisticated the anti-extraction algorithm is, but it may even require breaking the memory up into logical blocks of 50-100 bytes, and randomly reading each block out, then putting the pieces back together into a contiguous format. If that's all they did, I believe that would be a fairly trivial thing to do, but I don't know of any reading software that was ever modified to actually do that.
Now if their anti-read protection logic is more sophisticated than just putting a counter on how many bytes have been read without an SPC update, then extracting the bin successfully may be more problematic. Although my guess is they just lock up the chip and/or return garbage if you read more than about 500-1000 bytes without sending an update. That's a fairly unlikely thing for the EEC to ever do at runtime hence how the protection logic doesn't affect the EEC's ability to read the chip. Any "real logic" is not going to consume the instructions and data contiguously for that many bytes without hitting a branch/jump of some kind, which would update the SPC.
...Always Somethin'
89 Ranger Supercab, 331 w/GT40p heads, ported Explorer lower, Crane Powermax 2020 cam, FMS Explorer (GT40p) headers, aftermarket T5 'Z-Spec', GUFB, Moates QuarterHorse tuned using BE&EA
Member V8-Ranger.com
89 Ranger Supercab, 331 w/GT40p heads, ported Explorer lower, Crane Powermax 2020 cam, FMS Explorer (GT40p) headers, aftermarket T5 'Z-Spec', GUFB, Moates QuarterHorse tuned using BE&EA
Member V8-Ranger.com
Re: Convert .frg to .cef (SCT)
There are 2 SCT formats.
CEF - email format. Cannot be edited. Can only be loaded to handheld using SCT Device Updater.
MTF - the Advantage III software uses for tuning. Can only be loaded to the handheld with Advantage III software.
Advantage exports the tune in CEF format to email tune to customer.
CEF - email format. Cannot be edited. Can only be loaded to handheld using SCT Device Updater.
MTF - the Advantage III software uses for tuning. Can only be loaded to the handheld with Advantage III software.
Advantage exports the tune in CEF format to email tune to customer.
91 GT, A9P, systemax II, 75mm tb, AFP, 75mm Pro M, 42#, Vortech S trim, GT40 crate 5.0, BBK catted X, flows, Tremec 3550, Pro 5.0, 3.27 gears. Tweecer RT, TunerPro.
Who is online
Users browsing this forum: No registered users and 55 guests