K Pro V4 and AIM MXS config
Posted: Sat Jan 07, 2017 6:44 pm
Hi guys
This is more a post directed to Hondata, but if you have experienced a similar issue then please post!
I have a K pro V4 running with a Aim MXS Strada digital display. It is all working very well with a couple of minor things I want to resolve!
1.
I have an ethanol content sensor wired into the K pro and it is fully functionable, I have both ethanol content and fuel temp reading while datalogging on K manager. however, on the Aim MXS I only have a reading for ethanol content, fuel temperature is 0. I have been in contact with Aim and they have 'tested' virtually that it transmits though CAN and they say it is, but to get in contact with Hondata to make sure it is included in the CAN stream from the ECU? Can someone from Hondata please confirm. Im using the Motec protocol.
2.
So I also have a Bosch oil temp sensor wired into AN1 input with the appropriate resistor and it is working well and I there is data in the datalogging on K manager). Through my research I have seen this thread which also applies to the Aim MXS:
http://www.s2ki.com/forums/s2000-racing ... l-1153580/
So as I understand, this guy from S2ki has worked with you guys (hondata) to get this working. The only issue is when Aim coded the data to display on the dash they set it as Celsius even though it is actually Fahrenheit. So the data displayed on the Aim is Fahrenheit even though it says Celsius. This serves a problem as the number is obviously not celsius. I have asked about Aim doing a modified version of the firmware so that it's celsius (with the option to change it to fahrenheit) but they say that isn't an option.
This was their solution:
"The solution I see is that you code the ECU with the Farenheit scaling, this information is transmitted to the MXS according to the existing protocol, then in your MXS setup you can choose to display whatever measure unit you want on it, because we do the conversion starting from the "raw" data we receive (Farenheit in this case)."
Is this something you guys can help with?
It's working really well and i', am stoked with it, I just want to resolve these small things!!
Thanks in advance.
This is more a post directed to Hondata, but if you have experienced a similar issue then please post!
I have a K pro V4 running with a Aim MXS Strada digital display. It is all working very well with a couple of minor things I want to resolve!
1.
I have an ethanol content sensor wired into the K pro and it is fully functionable, I have both ethanol content and fuel temp reading while datalogging on K manager. however, on the Aim MXS I only have a reading for ethanol content, fuel temperature is 0. I have been in contact with Aim and they have 'tested' virtually that it transmits though CAN and they say it is, but to get in contact with Hondata to make sure it is included in the CAN stream from the ECU? Can someone from Hondata please confirm. Im using the Motec protocol.
2.
So I also have a Bosch oil temp sensor wired into AN1 input with the appropriate resistor and it is working well and I there is data in the datalogging on K manager). Through my research I have seen this thread which also applies to the Aim MXS:
http://www.s2ki.com/forums/s2000-racing ... l-1153580/
So as I understand, this guy from S2ki has worked with you guys (hondata) to get this working. The only issue is when Aim coded the data to display on the dash they set it as Celsius even though it is actually Fahrenheit. So the data displayed on the Aim is Fahrenheit even though it says Celsius. This serves a problem as the number is obviously not celsius. I have asked about Aim doing a modified version of the firmware so that it's celsius (with the option to change it to fahrenheit) but they say that isn't an option.
This was their solution:
"The solution I see is that you code the ECU with the Farenheit scaling, this information is transmitted to the MXS according to the existing protocol, then in your MXS setup you can choose to display whatever measure unit you want on it, because we do the conversion starting from the "raw" data we receive (Farenheit in this case)."
Is this something you guys can help with?
It's working really well and i', am stoked with it, I just want to resolve these small things!!
Thanks in advance.