General MMCd-Go

[T2Small]

Since my son picked up a relatively stock 1992.5 Laser, I thought I'd finally resurrect and port the old palm pilot mmcd to Windows, Linux and Mac. I finally have it connected and creating logs. So far it has been tested from my macbook using a cable I built myself.

Please consider this a beta release. I will keep fixing it up over the next few weeks and would be happy to have Windows and Linux users to give some feedback. I normally use Linux, but my laptop mainboard won't boot right now (will fix soon).

So where can you find this goodness?:

GitHub - kevin-buckham/MMCd-Go: Cross-platform ECU datalogger for 1G DSM (1990–1994 Eclipse/Talon/Laser) — real-time sensor dashboard, scrollable graphs, DTC diagnostics, and log replay. Go + Wails + Svelte desktop GUI & CLI.

Cross-platform ECU datalogger for 1G DSM (1990–1994 Eclipse/Talon/Laser) — real-time sensor dashboard, scrollable graphs, DTC diagnostics, and log replay. Go + Wails + Svelte desktop GUI & CLI....

github.com

Binaries here:

Releases · kevin-buckham/MMCd-Go

Cross-platform ECU datalogger for 1G DSM (1990–1994 Eclipse/Talon/Laser) — real-time sensor dashboard, scrollable graphs, DTC diagnostics, and log replay. Go + Wails + Svelte desktop GUI & CLI....

github.com

Since the mac binaries are not signed, they will not work on your machine. Feel free to download and build yourself if you are using a mac. I do actually have a personal app signing key so I can sign these if there is enough request for it.

I am not responsible if the cable you build from these docs burns your car down, fries your ECU, or makes your significant other leave you. Same for the software (especially the software!). You have been warned! (It did work for me, from one mac to one DSM.)

This app has some interesting (maybe good?) features:

• can read old Palm mmc logs
• has a rudimentary graph system to show your sensor values on a graph
• logs to csv format by default so you can import to your favourite spreasheet
• has both a GUI and headless mode
• the less data items you select in settings the faster you get data updated. This selection is remembered across runs.

Since the original was GPL licensed, so is this. While the code initially wasn't "stolen", I did have the AI inspect the old C code to make sure we are close as possible in terms of error handling, edge cases and conversion functions. It is now close enough I consider this a derivative forcing me to the same license. If anyone has a problem with the naming, let me know and I'll change it. Bonus points for a good new name.

If I get enough time, I'll get this running on a RPi2w and have an Android and iPhone app to connect to it. That was the original reason for the headless mode.

Dirty details:

• I haven't validated that any of the values I see on screen in fact match reality (they *seem* reasonable, and I do know his front O2 sensor is not working)
• perhaps the log files are complete garbage
• I am unsure if the DTC read works at all (anyone have a car they know has DTCs that can test this?). I suspect this car should, but I trust nothing about this DSM.
• I am unsure if the Test (like disabling fuel injectors and activating other ECU outputs even work). Test this very carefully. Let me know if it works.

Once I believe these are all working plus some testing on Windows and Linux, I'll move the project to a 1.0.0 version. I do think it is very close.

Definitely a huge thanks to the original MMCd developer, Dmitry Yurtaev!

You must be logged in to view this image or video.

 

[CrackedDSM]

Bro this is spectacular. There is absolutely a need for this because there's more than a few guys who just bought cars and are working up to ECMLink but would still like to log.

If I had a 1G, I'd absolutely be doing this. Probably still download it and keep it for a rainy day.

Thank you for doing this! Truly.

 

[T2Small]

No problem at all! It will remain on github so no worries about it disappearing any time soon.

ECMLink is definitely in the works for my son's car, but he's still saving some pennies.

 

[rdeis]

Awesome! This task has been on my todo list forever but I was never able to get to it.

Having it ready for iphone would be amazing.

I'll make good use of it on my non-dsmlink car for sure.

 

[T2Small]

BTW, I did get this updated and validates some signals from my son's car. I haven't yet proven if the fault read works or the tests. Will update to 1.0 when I confirm those.

I don't have an iphone, plus cable support is a problem. Easiest option would be to run a Pi or similar locally and then have the IOS app connect via a REST API to the linux device actually running mmcd-go in a headless setup.

 

[steve]

Looks interesting. While I do know C and have modified and build the MMCd Palm code in the past as well as helped disassemble the 1G ECU assembly code I don't know Go, Wails, or Svelte.

If there are things your not sure about I might be able to answer them. Assuming I can remember them.

 

[deexeq]

Greetings! Thank you for creating such a wonderful program and providing the opportunity to test it.I have a few questions regarding the correct connection to the car's ECU. My car is a 1993 Mitsubishi Sigma with a 6G72 DOHC engine. I built the adapter according to the schematic and bought a USB-to-TTL programmer based on the CH340 chip.When I try to connect (using the "Live ECU" button), the TX/RX (transmit/receive) LEDs on the adapter start flashing, but nothing is displayed in the program itself. An error appears in the connection log.How can I fix this error?

You must be logged in to view this image or video.

 

[steve]

It would hep if you posted a clear/sharp picture of your cable. The important end is where you assembled the interface between the USB cable and the OBD1 cable. We need to see the if the correct leads are used and the direction of the diode.

You also mentioned that you based your cable on a CH340 chip, do you know if it supports the 1953 bit rate and what voltage is it's signaling?

 

[deexeq]

Thank you for such a quick reply.
I assembled the cable according to the diagram, using a 1N5817 diode (the direction is correct) and a 10 kOhm resistor.In Device Manager, the baud rate can only be set to 1800 or 2400 (I left it at 2400), while the software itself is set to 1920. I configured the remaining parameters according to the instructions. I am attaching a photo of the adapter.

You must be logged in to view this image or video.

 

[deexeq]

Hi everyone! I managed to get the machine working with the program. I had to replace the adapter with a different one featuring the original FT232RNL chip and slightly modify the wiring diagram. Once again, a huge thank you to the author for finally allowing me to communicate with the machine via my laptop.