[Tesseract]

Originally Posted by skooler

...
At the moment the CEL is an advisory, ABS light a failure, Traction control light is a failure and power steering light is a failure.

I was thinking more along the lines of stopping the ECU from reporting the errors...

Unless you are an excellent mechanic - at least for the RX-8 - then your chances are slim-to-none, as we Yanks say, of either solving why the CEL is lit or reprogramming the ECU to not register those particular errors.

The throttle is reduced by the ABS and traction control modules when either system is active in some cars, so that may be the source of the warnings for those two. The power steering warning is probably because the OEM crankshaft sender isn't connected.

Do you have the factory wiring diagram for the car? Alldata has reasonable prices on that sort of thing.

[skooler]

Originally Posted by Tesseract

Unless you are an excellent mechanic - at least for the RX-8 - then your chances are slim-to-none, as we Yanks say, of either solving why the CEL is lit or reprogramming the ECU to not register those particular errors.

The throttle is reduced by the ABS and traction control modules when either system is active in some cars, so that may be the source of the warnings for those two. The power steering warning is probably because the OEM crankshaft sender isn't connected.

Do you have the factory wiring diagram for the car? Alldata has reasonable prices on that sort of thing.

Thats kinda what I thought. Its probably a lot of work and wont provide anything else extra like plan b.

Interrupting the CANbus signals it is then! At least that way I can use the other lights for various errors reported

I'll probably work with the chap who built me my power steering controller to develop it.

Jeffrey,

Does the Soliton logging protocol transmit the errors in a form that is easy to manipulate (a code?) or is it plain text such as in the logfiles?

I'm thinking that a magic box can sit between the soliton's ethernet port and the dash CANbus input...

Yes I have the factory manual. there's a link to it a few pages back.

Cheers,

Mike

[Tesseract]

Originally Posted by skooler

...
Jeffrey,

Does the Soliton logging protocol transmit the errors in a form that is easy to manipulate (a code?) or is it plain text such as in the logfiles?

I'm thinking that a magic box can sit between the soliton's ethernet port and the dash CANbus input.....

That's more Qer's domain than mine; I just designed the hardware. The logging data is in UDP format, so not plain text. The logger program we supply basically just converts the UDP data from the ethernet port to a tab delimited text file (for easy importation into a spreadsheet program). That is the sum total of my knowledge of that part of the controller.

[skooler]

Originally Posted by Tesseract

That's more Qer's domain than mine; I just designed the hardware. The logging data is in UDP format, so not plain text. The logger program we supply basically just converts the UDP data from the ethernet port to a tab delimited text file (for easy importation into a spreadsheet program). That is the sum total of my knowledge of that part of the controller.

Thanks Jeffrey,

I was hoping it was something like that should be relatively easy to get something to work

Looks as though I have an interesting mini project coming up!

Cheers,

Mike

[Tesseract]

Originally Posted by skooler

...
Looks as though I have an interesting mini project coming up!
...

We encourage this sort of thing - it's why we provide the source code for logger, for example - but just be aware that we have - and will again - change the logging data format as well as the content (ie - the numerical and verbose error codes, etc...).

[Ace_bridger]

Mike,

If you just want to get around the light problem for the MOT couldn't you just knock up a little timer circuit which has the lamp coming on when the ignition is switch on and then stays on for a few secs before switching off?

The discussion above clearly give you more functionality and info about the state of the controller but...

[skooler]

Originally Posted by Ace_bridger

Mike,

If you just want to get around the light problem for the MOT couldn't you just knock up a little timer circuit which has the lamp coming on when the ignition is switch on and then stays on for a few secs before switching off?

The discussion above clearly give you more functionality and info about the state of the controller but...

Could do but that would mean chopping up the dash...

Its over £200 for a new one!

And rather than create a circuit I could just tap into the airbag light which does exactly what i want the others to do...

I'll see if I can get it through the MOT as is. Like I say, the ABS actually works! it just the light Just needs a tester that will use common sense rather than go exactly to the book.

[kakheath]

Originally Posted by skooler

It spoofs the signals that would normally be supplied from the ECU to the EPS controller via canbus. The lack of the engine speed (eccentric/crankshaft sensor) causes the EPS to shut off as it isnt recieving the correct signals.

Mine arrived today so I'll let you know how I get on

Got PS yet?

[kakheath]

Could you mount the eccentric crankshaft sensor so that it picks up the front motor shaft rotation? Would that get it going again?

I'm gonna have to pull the ICE harness this weekend and start playing with all those missing sensors. My dash is too colorful right now. The only thing that works is the speedo and odometer.

[skooler]

Not working yet...

I'm on holiday atm so haven't had chance to have a propper look.

I have installed my controller but think I'm having the common issues with this the original wiring.

http://www.rx8club.com/trouble-shoot...-107481/page1/

I will have another look when I get back. The plan will be to completely rebuild the harness between the ps controller and the torque sensor. Right now it has some iffy resistance values.

Cheers,

Mike