Eagle Posted Wednesday at 05:50 PM Posted Wednesday at 05:50 PM If Claude can do this to the '94s, I wonder if it can also do the Renix computers ...
Chico Posted Thursday at 03:06 AM Posted Thursday at 03:06 AM Well, I asked AI about AI and this was it's response. Honestly though, I am technologically incompetent so a lot of that was an unrecognizable forein language to me but, damn isn't that all amazing? Thanks for the link E. Below is the answer to you question according to Google.
scguy Posted Thursday at 10:00 PM Posted Thursday at 10:00 PM I checked out when the guy said "OBD2 sensor". It seems like he's trying to vibe code his way around proper diagnostics. While it's a cool idea, and I'd love for there to be a HO version of the REM, I just am whelmed.
Eagle_SX4 Posted Thursday at 11:26 PM Posted Thursday at 11:26 PM I think it is awesome someone is finally digging into the H.O. computers. This is a very good first step. Next would be to get a unit like the REM built for it.
pizzaman09 Posted Friday at 12:28 AM Posted Friday at 12:28 AM 2 hours ago, scguy said: I checked out when the guy said "OBD2 sensor". It seems like he's trying to vibe code his way around proper diagnostics. While it's a cool idea, and I'd love for there to be a HO version of the REM, I just am whelmed. One of the reasons I seeked out an 89 or 90 MJ was because of the REM.
Eagle_SX4 Posted Friday at 01:14 AM Posted Friday at 01:14 AM The REM is a great resource but it does have its limitations. Like when you need to chase spark issues that are not the CPS. Any fault in the ignition system brings up the CPS fault code. Even just having the coil wire off the distributor will pull a CPS error. I might try and replicate what the video did with the HO computer in my Eagle when I get the stroker in there and see if I can piggy back off the ECU and adjust fuel and ignition accordingly.
Gojira94 Posted 8 hours ago Posted 8 hours ago If AI had a raw hexadecimal dump of a Renix ROM, it could probably sus out the parameters for tables, flags, scalars and constants with some human help. Someone with some EFI tuning experience would be able to recognize where one parameter ends and another starts, though it takes some time and patience. Then give the AI feedback on what tables are what (like spark tables, VE {fueling} tables, lookup tables for AE and DE routines). Then ask the AI to write a definition file in XDF file format, which it should be aware of. A human can do this by getting a hex dump of a ROM and converting to integers. Flags (yes/no, true/false, on/off) are the tricky ones to spot, as they’re just hexadecimal for 0 or 1. You spot them because they don’t fit in with values that precede or follow them in the code. Given an editable calibration in XDF or other human-readable definition format, all you’d need would be emulator hardware similar to Ostrich or QuarterHorse that alters calibration values on the fly to effect alteration of the ‘tune.’
eaglescout526 Posted 7 hours ago Posted 7 hours ago 41 minutes ago, Gojira94 said: AI had a raw hexadecimal dump of a Renix ROM Hell if we had that we could easily be making ROMs for performance and making our own performance ECUs or economy ECUs. We could have some genuine fun with Renix if we understood the ROM.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now