[147_Pat]

Hey team,
I've decided to go ahead with my speeduino install.
I've soldered up a V0.4 board, have a VR conditioner (yet to solder on) plus I have a raspberry PI with the Speedy Dash hat for data logging & Dash useage.
I'm new to this sort of project, and have only done simple electrical circuits on the car (wiring in a new relay and switch for a fan etc)

I'm planning on using a 3D printed enclosure with 26&34 pin AMP superseal connectors to run everything from the ECU.
Thinking of then running through the same connectors to get through the firewall again for ease of disconnection. Or is it better to just run it through the firewall and run smaller connectors on everything where needed?


I've drawn up a wiring diagram and was hoping to get some feedback on there; alongside a few questions.

Can I use the original fuel level sender?
Is fuel pressure necessary? I'm on the fence on this one.
Can I wire in the OEM steering sensor to measure steering angle for data logging?

Thank you, and looking forward to cracking on with this project!





Cheers,
Pat

[PSIG]

Congrats on your decision to move forward. I see a number of errors in your well-drawn wiring diagram. But before jumping that far, and with the large number of aux inputs you are anticipating; have you considered using a separate unit for the extra stuff, socrazy but the ECM is not swamped with IO?

Perhaps a GPIO, to collect and handle most of the extra IO? It might organize and simplify the extra stuff, and only suggesting so you know what path you will stay on, or options for later.

[dazq]

As psig says above , keeping aux inputs separately from the main ECU takes unnecessary load off the engine ECU . This is how most OEM do it these days too.
As you plan to run speedy dash then why not feed all the aux data direct to that? Then it only had to gather the engine data via serial3 from the speedy itself.

Just another option.

[147_Pat]

Congrats on your decision to move forward. I see a number of errors in your well-drawn wiring diagram. But before jumping that far, and with the large number of aux inputs you are anticipating; have you considered using a separate unit for the extra stuff, socrazy but the ECM is not swamped with IO?

No I haven't looked at this or even knew about it!
I'm assuming that you would run the non-essential aux inputs through a GPIO?
A lot of the aux inputs are mainly for logging and/or dash display. Ultimately one end goal of ours is to be able to do stream back telemetry to the pit. I'm guessing that maybe going further down the GPIO route would help enable this?

Otherwise as dazq mentioned, running them straight to the speedy? How would something like that look / function?


Hmm it seems that there is still lots to learn!
(also it seems I am getting a lot of broken image links on that wiki page, Is anyone else experiencing that?)

Thanks for the replies so far.

[dazq]

You have miss understood what I said.
I am said it is better NOT to run the aux data to the speeduino but DIRECT to the speedydash .
As OEM do they use multiple devices for specific tasks not feed everything into one !
An example of the gpio device psig mentions is the gpio I developed (see wiki) that was specifically made to work alongside speeduino or as a standalone device too. It was released at a time when speeduino had no aux io at all .

[147_Pat]

I may have written it in a way that didn't make sense, but I understood what you meant!
I can see how running it separately frees up space on the ECU.

Is it worth trying to run as many if not all of those aux sensors through the Speedy / separate GPIO?
Reading through the speedy website it seems that going this route it would need to be set up as CANBUS? Is that right or am I missing something.

Also I'm assuming that you can only have either the Speedy or a GPIO connected via serial 3 to the speeduino but not both?

[dazq]

I may have written it in a way that didn't make sense, but I understood what you meant!
I can see how running it separately frees up space on the ECU.

Is it worth trying to run as many if not all of those aux sensors through the Speedy / separate GPIO?
Reading through the speedy website it seems that going this route it would need to be set up as CANBUS? Is that right or am I missing something.

Also I'm assuming that you can only have either the Speedy or a GPIO connected via serial 3 to the speeduino but not both?

I think the confusion comes from us using the names speeduino and speedy interchanged .
The serial3 port can only have one device attached at a time to it.
The speedy dash I believe can support multiple inputs via serial (best check the dash docs for that )
You don't need to use/setup canbus to use the aux inputs on speeduino.

[147_Pat]

Ah Yep, I'll make sure to refer to the dash as the SDC.
Richard is great at replying to queries about the SDC, so if anyone is on the fence for that unit, I recommend it!

His reply was that going through the SDC has to be done via CANBUS; might be time to learn a little about how that whole side of things work.


"If you have external data to provide to SDC, the preferred way to add them is via canbus. You can't populate anything that speeduino populates already, even if the values in speeduino are empty, because the two sources will continuously overwrite each other. For example, if you sent a canbus message in to write to auxin0 (the first speeduino auxiliary input) and had nothing connected to that input in speeduino, then the speeduino value would overwrite your value (probably with zero) because it is always present on the speeduino message and I can't tell the difference between 'not being used' and 'present in the message', since speeduino does not provide that information.

So there are two ways to do it: Either via speeduino so that it appears in the serial message where possible, or via canbus inputs and a device that generates the right data. Personally I think the canbus approach is more flexible and future-proof. I am happy to extend the canbus side of things in SDC if there are specific needs not yet covered"

[147_Pat]

Without getting too far ahead of myself (I am planning on going down the CANBUS route for the speedy accessories, but would like to get the ECU up and running first)

What issues with the wiring diagram is apparent? To begin with the only AUX items will be oil pressure, oil temp and fuel level.

Thanks,

[dazq]

Without getting too far ahead of myself (I am planning on going down the CANBUS route for the speedy accessories, but would like to get the ECU up and running first)

What issues with the wiring diagram is apparent? To begin with the only AUX items will be oil pressure, oil temp and fuel level.

Thanks,

Whether you feed the additional signals into the speeduino or another MCU to send to the dash , you need suitable input circuitry. Mostly this is to protect the MCU but also if the sensor needs a bias resistance or level shifting.
You can copy the circuits used for these from what is used on the speeduino boards.

Also do not forget that if you are using a mega based speeduino then you do NOT have native canbus and need a coprocessor to convert the signals from serial3 to a suitable can stream. This was why it was suggested to feed the aux signals direct into that MCU rather than the speeduino as you need to have the coprocessor anyway to send to the dash.