ROB-80E

Well, I can honestly say that I'm a very happy boy at the moment. 
I dusted off my old Nexus 7 tablet (running Android 4.4.4) and got RealDash installed and hooked up to my G4+ with no issues at all. Getting the data I wanted (eg ethanol content) was where I started to come unstuck. Did all the reading through this thread, saw the issues with the data stream for lambda and didn't see anything with setting up Ethanol% output.
Long story short, I found in PClink help what is supported over OBDII...I had always planned to connect via OBD as I used to use racechrono etc with my factory ECU. But RealDash over OBDII using my old cheap ELM327 has achieved an awesome result. The data has probably .5 second lag for the fasted refresh rate data, but for me, I'm not using this as "dash". I just wanted to monitor. So it's perfect. 
 
Anyway, I already have some AEM gauges for AFR, Boost and Oil Press, so I got drawing and created my background and dials for my "dash". I also threw in some "lights" for good luck. So what went from wanting a solution for ethanol%, i definitely got carried away. 
 

IMO nothing can compare to what the stock ECU is capable of doing.  Not MDC, Emtron, link or anything else that doesn't use the same level of inputs and calculations.
The MAJOR drawback with the factory ECU is the ability to log (easily).  It can be done using EvoScan, but it can't be done internally.   This is the major bonus of the Motec or Emtron (or possibly even Link...i haven't had any experience here) is that you can accurately log the Center Diff control parameters just as easy as everything else in the engine ECU.
Now don't get me wrong, you can certainly achieve great results with an aftermarket ACD solution, and the ability to find someone to tune them is probably easier too....but yeah I've been doing the factory ecu setup for over 10 years now and see no reason to change.
The attachment is a simplified control diagram of the factory ECU.

IMO nothing can compare to what the stock ECU is capable of doing.  Not MDC, Emtron, link or anything else that doesn't use the same level of inputs and calculations.
The MAJOR drawback with the factory ECU is the ability to log (easily).  It can be done using EvoScan, but it can't be done internally.   This is the major bonus of the Motec or Emtron (or possibly even Link...i haven't had any experience here) is that you can accurately log the Center Diff control parameters just as easy as everything else in the engine ECU.
Now don't get me wrong, you can certainly achieve great results with an aftermarket ACD solution, and the ability to find someone to tune them is probably easier too....but yeah I've been doing the factory ecu setup for over 10 years now and see no reason to change.
The attachment is a simplified control diagram of the factory ECU.

Just setup the Link ECU in connections.  You don't need to have connected to the ECU, just have a "connection" setup. 
Mine works fine using the Lambda 1 channel in realdash.   Mine is a similar setup where I'm using the analogue output from an AEM guage.  It's calibrated within the ECU and set as lambda.  But yeah, no issues over serial.
I've also got a connection setup to a ELM dongle and I have lambda target via OBD.

IMO nothing can compare to what the stock ECU is capable of doing.  Not MDC, Emtron, link or anything else that doesn't use the same level of inputs and calculations.
The MAJOR drawback with the factory ECU is the ability to log (easily).  It can be done using EvoScan, but it can't be done internally.   This is the major bonus of the Motec or Emtron (or possibly even Link...i haven't had any experience here) is that you can accurately log the Center Diff control parameters just as easy as everything else in the engine ECU.
Now don't get me wrong, you can certainly achieve great results with an aftermarket ACD solution, and the ability to find someone to tune them is probably easier too....but yeah I've been doing the factory ecu setup for over 10 years now and see no reason to change.
The attachment is a simplified control diagram of the factory ECU.

Well, I can honestly say that I'm a very happy boy at the moment. 
I dusted off my old Nexus 7 tablet (running Android 4.4.4) and got RealDash installed and hooked up to my G4+ with no issues at all. Getting the data I wanted (eg ethanol content) was where I started to come unstuck. Did all the reading through this thread, saw the issues with the data stream for lambda and didn't see anything with setting up Ethanol% output.
Long story short, I found in PClink help what is supported over OBDII...I had always planned to connect via OBD as I used to use racechrono etc with my factory ECU. But RealDash over OBDII using my old cheap ELM327 has achieved an awesome result. The data has probably .5 second lag for the fasted refresh rate data, but for me, I'm not using this as "dash". I just wanted to monitor. So it's perfect. 
 
Anyway, I already have some AEM gauges for AFR, Boost and Oil Press, so I got drawing and created my background and dials for my "dash". I also threw in some "lights" for good luck. So what went from wanting a solution for ethanol%, i definitely got carried away. 
 

The best option I can come up with is below.
Forget about the IC spray function, we will instead use a GP timer to achieve the same thing.  So set up VA 1, 2 & 8 like below, your Inj 7, Ign 8 & DI2/DI7 setup will all remain the same as they are above.
The "Timer 1 >" setting on VA2 is the "on time", the "timer 1>" setting on VA8 is the "period".  So examplle below has 3 second period and 50%DC (1.5sec).

The IC spray status will just show "on" all the time that the activation conditions have been met, the on/off duty cycle actually gets applied to the output afterwards.  So it will work if Inj 7 is set to IC spray, but is not going to work with a virtual aux status.   

Sorry I read that wrong, I missed the 1.8 part on the bottom board, yes 1.8 on the bottom board is EThrottle

The V number on the base map file refers to the bottom board revision, so for your V1.8 board you should be using the Base map "Mitsubishi EVO 9 PCB V1.6+ G4+ Xtreme Plugin".  

It is