Ok, that is curious. So, you can get data in the RaceCapture app such as RPM, TPS, and so on, but you instruments stop functioning.
The Lotuses of that year have an interesting hybrid system of legacy OBDII protocol support, but with also the CAN bus wires connected, which provides a feed of data from the ECU (going to the dashboard).
We talk about it quite a while ago here:
https://www.autosportlabs.com/pre-obd-i ... -can-data/
RaceCapture makes CAN bus requests to the legacy adapter, and then the legacy adapter translates it to legacy OBDII calls.
The CAN bus requests is also present on the CAN bus pins on the OBDII connector, and nearly all pre-CAN bus cars *do not* have these pins connected, so there's no issue.
It seems that the messages coming from RaceCapture might be conflicting with the data going to the instrument cluster.
We have a couple of options:
1) disconnect the CAN bus pins in your OBDII connector underneath the dash, so the CAN messages from RaceCapture cannot be seen by the ECU, which would prevent any conflicts.
2) Disable OBDII and only use the data provided by the ECU to the instrument cluster, as described in that blog post (above).
In the meantime, please try this:
connect the OBDII adapter, but turn off the OBDII feature under setup. Don't delete your channels, simply turn the switch to Off and then write the settings.
This should prevent CAN traffic from going to your car.
When you do this, let me know if your instrument cluster comes back to life, even if you're otherwise plugged in.