Jump to content

AI meets Jeep technology


Recommended Posts

Posted

Well,

I asked AI about AI and this was it's response. :roflmao:

 

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.

 

 

cla1.png

cla2.png

cla3.png

cla4.png

Posted

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. 

Posted
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.  

Posted

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.

 

 

Posted

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.’

Posted
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. 

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...