PDF of registers: https://www.dropbox.com/s/0zg0e3z1m60gy24/ECU_Data_register_table.pdf
That is the document we used on development. The problem is that not all Nissan cars support all values, and there is only a limited amount of values that can be requested from the ECU. So in practise, RealDash needs to ask for the values, check for 0 responses, then replace the requests with another values and so on. So its not as straight forward as it may seem.
Interesting, How can I help with this? Test ECUs and/or Funding?
I am still looking to improve the Consult I support.
Currently we do not have plans to update Consult I support as we do not have enough information to do it. Last time we improved it we ended up improving it for some and breaking it for others. We can’t work on it blindly, its just waste of time.
In that case could we have a support option of manually defining addresses to suit our Consult applications?
That is a possible option, requires some extra work though. I will put this to the list, if we ever encounter some extra time.
Has any progress been made on allowing definition of our own addresses for Consult I? Still needing this. As I mentioned previously, I can supply funding for this feature if that helps get it completed faster.
I have not been keen on changing the Consult I implementation because last time I did it, it improved the situation for one user and pretty much destroyed the functionality for everyone else. Unfortunately I have to consider that there is very few RealDash Consult I connection users, and amount of time/risk of breaking it again is too big to make changes for that.
That is a bummer.