Venomancer

I used ethanol as its the first parameter in the list.  It is just being used to generate a constant, since we are multiplying it by zero then adding an offset it will always output a constant no matter what the actual %ethanol is reading.  
 
They are not meant to turn off, the assist level controls the flow rate of the hydraulic fluid through the system.
 
Yes, that is the intent, you can put whatever axes you like on there.  Typically wheelspeed Vs a multipostion adjustment knob on the dash.

Ok, give this a try.  Assist level is varied with GP PWM 1,  0% in this table gives minimum assist level (CAN speed = 6000), 100% DC gives maximum assist level (zero speed).  For testing I have set up this table to be controlled by TPS so you can just press the throttle to see if the assist level changes.  
3000gt Volvo EPAS CAN.pclx

This is easier for me to understand than the Lua code originally quoted above.  
It looks like they actually wait to receive an "im awake" message from the steering? (0x1B200002) before sending the speed and counter messages.  That might be a bit tricky to do in the Link user streams.  That may not be needed though, especially since its only being transmitted at 2Hz you would think the steering ecu should be booted up by then.  So we can give it a try without waiting for the Im awake message.  The counter is quite easy, it is just 0x00,0x40, 0x80, 0xC0, which is really just 0/1/2/3 in the 2 most significant bits.  
@Venomancer Can you attach a copy of your tune and tell me what CAN port the steering is wired to and I will set up a couple of streams.  
  

Can't do 2104136 at ~71.4hz and 1ae0092c at ~2.38hz, closest you can get on that with custom CAN would be 50Hz and 2Hz.
1ae0092c is a hex number and is '450890028' in decimal format, this will be an extended Id
I assume 2104136 is also a hex number based on the above code, this will be '34619702' in decimal format and will also be an extended CAN Id.
To get the fixed values in the streams use any runtime and give it a multiplier of 0 and an offset that matches the fixed offset as shown below for the 0x1ae0092c ID:
local data_0x1ae0092c = { 0x00, 0x00, 0x22, 0xe0, 0x41, 0x90, 0x00, 0x00 }

Note that I've done it as 2 16bit numbers instead of 4 8 bit numbers, 0x22, 0xe0 = 0x22e0 = 8298.

The following code says that the 2nd byte (assuming 0 list indexing in the above code) in the 0x1ae0092c id message changes each sent message.
slowRoll = (slowRoll + 1) & 3
data_0x1ae0092c[1] = slowRollTable[slowRoll + 1]
The first message will have '((0 + 1) &(bitwise AND) 3) + 1 = 1+1 = 2' in that byte
The second will have '((1 + 1) & 3) + 1 = 2+1 = 3'
The third will have '((2 + 1) & 3) + 1 = 3+1 = 4'
The fourth will have '((3 + 1) & 3) + 1 = 0+1 = 1'
The fifth will have '((0 + 1) & 3) + 1 = 1+1 = 2' which means the cycle has repeated.
The best way I can think of to replicate this given that you can't do a specific message counter in custom CAN is to use a timer with a max time that won't run out in any drive, the max value of 16,000,000 wouldn't be a bad choice, set the activation to always on and polarity to reset when inactive. Then use a math block setup as below:

Note I haven't tested this setup but the thinking behind it is multiply time by 2 so that you are effectively incrementing every half second (this matches the 2Hz message transmit rate), the '%4' is a modulus operation which should give values of 0, 1, 2, 3 and then adding one will make this value move between 1,2,3 and 4 every half second, then add the math block to byte 1 of the 0x1ae0092c message.
Note: I'm pretty sure the modulus operation isn't working in the current release firmware so you might need to wait for the next firmware release for that bit to work.
 
For the 0x2104136 use the same trick as above for the fixed values (data_0x02104136 = { 0xbb, 0x00, 0x3f, 0xff, 0x06, 0xe0, 0x00, 0x00 }).
and then just put a CAN Aux duty cycle in bytes 7 and 8 (width of 16, Least Significant (LS) byte first and control that CAN Aux duty using a gp pwm output.
 

It will likely be possible.  I will take a look when I have a spare half hour but I mostly look after the forum in my own time and im reasonably busy with other stuff right now. You can bump the thread to remind me if I haven't replied here within say about a week.  

From what I can tell, based purely on what I've looked into, the pump will "default" to 70% with no CAN input.
The keepalive is a heart beat signal from the ecu, so effectively turning on the PWM of the pump itself, enabling it to be controlled 0-100%. 
If the keep alive signal is not there, it will default to 70%.

Once the keep alive is active, the PWM can be changed. 
It "might" be as simple as giving the keep alive the rpm parameter, so as long as the engine is running, it has that keep alive signal, but then it might not and might be expecting a certain counter.. You just need to know what bytes within that frame need to change. I'm very novice on code and not quite making out the C++ of the Arduino code but should be pretty easy for a coder to say what bytes need changing etc from that code example. 

Hey! I haven't had time to tinker with this. I copied the ChromedECU ignition degrees without reducing them, but I don't really go much into boost anyway, because I've put my solenoid at 0. I will install a knock-block that I purchased from Link and monitor the knock with headphones to see how the engine works with that timing once I have the time. Then I will set the threshold and call it a day. I will update once I figure everything out.

Have you sorted this @Venomancer? The only help I can offer is to use the timing from the ChromedECU ROM and reduce a few degrees off the boost areas. Datalog with those and note the knock threshold numbers. That should give you a safe threshold curve to start with. Unfortunately my stealth is not near me, otherwise I would offer to do a few pulls and datalog the spark timing I get from it. I could try to look for some old logs and get a histogram going if you haven't figured this out yet.

Awesome to see a 3000GT getting a Link. Do you have a thread on 3si or here about the install? I would like to checkout your progress and outcome.

Does your car have the 2 speed fuel pump on pin 21?
 
Your accel enrichment cold correction table is zeroed out.  The smallest value in there should be 1. 
 
You need to change the wiring to suit the ecu, this is why it is sold as an Evo3 ecu and not a 3000GT ecu.  

A number of pin functions can be changed through software, but not Injectors and Ignition drivers that are being used for Injection and Ignition. So, Injectors must be pinned to Injector 1-X outputs, and Ignition must be pinned to Ignition 1-X outputs, and you can't skip over any (i.e. you can't use Ignition 1-3, then 5-7, you must use Ignition 1-6)
 
Whenever you use a vehicle specific ECU in a different vehicle, it's your responsibility to match the car's wiring to the ECU. 

I vote for CAN connectivity.  

Yes, you can connect it via CAN bus (most accurate) or using an analog input such as pin 56.  

The stock O2 sensors are narrowband so not much use to you unless you have a catalytic converter and have some emissions regulations to meet.  But if you want to use them then you can connect the 2nd one to any spare analog input.  If you want dual bank closed loop then I would suggest 2 CAN based wideband lambda devices.