eriks4

One likely cause is that the transmit from the PC to the ECU is not working. In that cause the ECU outputs the chatter that only contains the data you mention. To get more data, it needs to be provided with a mode 1 request. If that is correctly received it will output a much larger datastream that contains the other info.

I watched the video and was surprised by the suggestion to directly connect the transmit and receive lines of the FTDI chip. In other schematics that use a TTL Tx and Rx, a diode (e.g. 1N4148) and resistor (1K) are used between Tx and Rx and the connection to the ALDL line is the point between the diode and the resistor.

Some more info on BLM cells 16 to 19 in addition to the above: What I can see when using my hardware Esprit emulator, they are only used with TPS=0 (hence the label below the column) and 16 is for RPM below approx 1800. For higher RPM cell number 17 is selected (in the learn mode). A better explanation would follow from an analysis of the actual ECM code, Sailorbob will know the details. I think 18 is for airco on and 19 is still for airco off but to me an unknown combination of RPM/MAP/??

Thanks Derek, and the current version would not have had the automatic identification of the correct memory for the BLM cells for the SE if you and fjmuurling hadn't participated on the testing and the discussion we had.

just put an updated version of Espritmon (V6.3) on: https://tudl0493.home.xs4all.nl/ and https://lotusesprit.eu/ Manual has also been updated. Enjoy

In the BRAKE STATUS byte that the ABS computer transmits, bit 0 represents the state of the brake switch: 0 = OFF, 1 = ON. When set the light will be blue. Bit 4 represents the following (according to the specification): BIT 4 : 0 = NO BRAKE SWITCH ON THIS IGNITION CYCLE 1 = BRAKE SWITCH ON THIS IGNITION CYCLE In case bit 4 is set, the light changes to red. This is just to provide information about the status of that bit, I have no more detailed info. I plan to release a better manual soon, together with an update of Espritmon that uses virtual buttons on the display instead of the key commands. Will put it on the same download location. Erik

Seems like a fun idea to add a virtual dash mode to Espritmon. Will look into this. Erik

Hi Bob, I will recheck, but from what I remember there is always a byte between the stored BLM values, so the 0x0018 was intentional, not a typo. I first need to find my original source of information. Erik

In later versions of Espritmon I have added the capability to save the first 1 KB of RAM to disk in the file espritram.bin. This is done when you press the v key. In this file the whole table is available. The contents of BLM cell 0 is at location 0x0016, cell 1 at 0x0018 etc. Good luck, Erik

Hi Robin, I can upload some files that I recorded with my S4. Just send me a PM with an email address and I will upload them using wetransfer. Kind regards, Erik

RLTC = Rich Lean Transition Counter The numeric value at the top of the RPM plot indicator is the (computed) ratio of RPM/speed with speed in km/h. This ratio is used to estimate the gear. Enjoy, Erik

Paul, A 1228708 was used for many different cars. Are you certain you got one with an Esprit EPROM and MEMCAL? If so, are you running the same version of the software as in your other ECU or a different one? Erik

Vince, I hope with the info about the timing you get your software to work. Please not that the Arduino Due I used does not use any of the standard AVR processors but an ARM processor. I think that if I would write the software directly in AVR assembly language it would run fast enough. However, I wrote it in the Arduino environment and when running it on an Arduino with an AVR processor (the Arduino Mega) I was loosing data. The Due is faster and works ok. So the binary is only for the Arduino Due, it will not run on other Arduinos. You mention that you made an ECU simulator. For the testing of new versions of Espritmon, but also for the datarecorder, I use a spare ECU. I bought one in the US that is the same type used in the Esprit and replaced the Eprom with an Esprit version. Next I built a small circuit that simulates most of the loads/inputs on the ECU terminals and a block-wave (frequency controllable) to simulate that the engine is running. As a result the ECU thinks it is in a real Esprit and the data output on the ALDL is the real thing - i.e.not simulated. I really recommend such a setup as it prevents the issue you describe - having something working on your desk with the simulator but not when connected to a real Esprit. Here are two older pictures of my setup: The module on top of the ECU generates the inputs, the white box in the second picture is the ALDL to serial box, connected to the laptop running a version of Espritmon. Enjoy, Erik

This is an overview of the components needed to build the logger. In my Esprit I have a D15 female to ALDL connector, hence the 15 pin male in the proto. The green LED blinks each time mode1 data is transferred, the green one for any ALDL data. This helps to verify whether communication is ok and whether actual mode1 data is received. The RTC module is used to obtain time and date (for the logfile name). The software for the Arduino DUE is in the logger.bin file. For the DIY people, this is all you need to build one yourself. Enjoy! logger.bin

Just for fun I recently used an Arduino Due to create a solid state mode 1 ALDL recorder. It interogates the ECM like Espritmon, Freescan and the Tech 1 tool do and it stores the data as a .CSV file on an SD card. The data can be read and plotted using Espritmon. Building the recorder yourself is not very difficult and in fact easier than an ALDL-serial interface since the Arduino already has TTL level instead of the +-12V. Hardware comprises Arduino DUE, real-time clock module, SD card shield, one resistor and 1 diode. Will post more info soon.