[info] Prometheus - NEW compact ECU shield!

[darxfame]

Work in progress=)

[darxfame]

It will be look like as photo

[kb1gtt]

You have allot of patience in soldering those wires. It looks like the final package will be very small and tidy. Keep us posted, looks like a cool project.

[darxfame]

Of course) i will send you a final result) i had no found box for ECU like andreika's box and i get for 3$ ECU Bosch Motronic from lada 2112 with 55pin connector.

[darxfame]

It works) But I seem to have killed hc-06 when soldered on the other side of the tpic (hip)

[kb1gtt]

HC-06 wifi in a metal enclosure will likely not work. I'm assuming you mean that with no metal around, it still does not work. You will need the metal more than a couple inches or a like 50cm or more away for this to work. Once you know it works with metal around, you can then start to place metal closer to it and see how and when it starts to work. Also I've read that some of the boards sourced from lower cost suppliers have issues, and are dead players out of the box. It might simply be broken.

Looks tidy when in the enclosure. Very nice.

[darxfame]

It worked, while I did not solder the tpic from the back side

[andreika]

I'm glad to inform that the second stage of the Prometheus board testing is complete!

Tested on a real car, 12 days of hours-long driving, over 4500 km distance traveled, 8 countries, including complicated weather conditions, mountains etc.
No significant hardware issues detected!
And rusEFI firmware was also stable and reliable!

P.S. There was no backup ECU on board! If something happened to the board, it would be some big trouble far away from home...

[AndreyB]

P.S. There was no backup ECU on board! If something happened to the board, it would be some big trouble far away from home...

https://en.wikipedia.org/wiki/Russian_roulette

[kb1gtt]

Sweet, 8 countries. Any chance it's a amphibious car? Perhaps you could do a trip around the world on rusEFI.
https://en.wikipedia.org/wiki/Amphicar

Good works, and good news it is working well.

[kb1gtt]

I haven't heard much about this board lately. I'm curious how is this board going?

[andreika]

I haven't heard much about this board lately. I'm curious how is this board going?

There're 3 boards at the moment. Mine is seemingly fine, but the car isn't used currently (I'm quite busy with long-term rear axle upgrade), so I can't tell for sure.
Another one is already assembled and is waiting for the first run - on darxfame's car (harness mess-up etc.). I hope he starts his own topic here soon!
And the third board is at the early stage of gathering components, I haven't heard of any progress recently...

[darxfame]

Maked new wires

Отправлено с моего PRO 6 через Tapatalk

[kb1gtt]

Very good to see. Keep up the good work.

[puff]

hey, where exactly in the moscow region?

[andreika]

Updated Prometheus files for Revision 0.2 (2018-01-30)!

What's new:
+ resistor R13 (near CJ125) connected to pin 22 of U2, not to the ground
+ transistor Q1 (oxygen sensor heater) changed from VND5 to VND14
+ resistor R3 (heater MOSFET gate) reduced to 220 Ohm
+ removed resistor R5 (changed to jumper wire) and capacitor C6
+ more wide traces for Wideband O2S heater power supply (near P2 connector)
+ power lines V12 and WV12 (WideBand) now separated
+ removed erroneous connection of CKPS2+ and R152 to the ground
+ increased clearance between capacitors C42 and C43
+ more wide power supply traces for MAX9926
+ added +5V TVS-diode for supply of MAX9926 (D30)
+ increased clearances for internal ign.coil ground planes, ign_gnd output moved away
+ removed connection traces of ign.ground and power ground inside PCB
+ additional pull-up resistor added for tachometer transistor to +5V (R165)

All links to schematic & gerber files - on the first page of the topic.

[andreika]

Do my eyes deceive me, do I see prometheus uses 2 STM32's. It looks like the CJ125 is on the second chip, and that's not the same chip on our discovery board.

Yes, the board has a double footprint to choose between STM32F469 and STM32F405:

double-footprint.JPG

And CJ125 support is available for both chips!

your can mount either a smaller more available chip and get limited functionality, or get a larger chip less available chip and get everything.

The functionality of the smaller chip is almost literally the same as of the larger one. All 64 pins used and routed!
The only absent pin in STM32F405 is a debug-test pin used as an output of RPM stimulator.

[puff]

I've forgotten if I'v asked it, do you have vehicle speed sensor on that board and what's the circuit for it? What does INA denote on your schematics?
Am I right, this is the way the board knows that ignition is on? To the left is from ignition key on, the upper line to AGND is basically the mcu adc pin, and that's enough?

Снимок экрана 2018-03-19 в 2.29.38.png

[andreika]

do you have vehicle speed sensor on that board and what's the circuit for it?

VSS can be connected in two ways:
a) via secondary trigger input (if no cam sensor) - this method is being used by @darxfame, and it works;
b) via digital In1/In2 inputs - but not supported in firmware yet.

What does INA denote on your schematics?

INA stands for "Input analog" and is used to connect an additional analog sensor (like throttle pedal etc.).

Am I right, this is the way the board knows that ignition is on? To the left is from ignition key on, the upper line to AGND is basically the mcu adc pin, and that's enough?

Yes, it's ignition voltage sensing input. A resistive voltage divider, TVS-protection and ADC pin, right.
It detects both ignition (for board power management option) and battery voltage (there shouldn't be much voltage drop across the operational ignition key in most cases)...

[puff]

why didn't you use an opamp for that VIGN input? is that okay? In case I am using it (for fuel level calculations), do I have to add an opamp to that circuit?

speaking of vss, am I right, it is powering from 12V rail and uses some sort of pull-up? (in stock, usually, to 12V rail). If so, what's the way this signal is translated to 3.3v? the same resistive divider plus TVS-protection?

[andreika]

why didn't you use an opamp for that VIGN input? is that okay? In case I am using it (for fuel level calculations), do I have to add an opamp to that circuit?

When we're measuring the battery voltage, we don't need opamp, because source resistance is low. But we do need it when a high-impedance sensor is connected (including resistive ones like tps and thermistors). So if you connect some kind of voltage (power) source to VIGN, it's ok (adjust voltage divider to correct values).

speaking of vss, am I right, it is powering from 12V rail and uses some sort of pull-up? (in stock, usually, to 12V rail). If so, what's the way this signal is translated to 3.3v? the same resistive divider plus TVS-protection?

If VSS is connected to the secondary trigger input (ckps2+), there're lots of pull-up/pull-down configurations possible:

ckps2-config.PNG

If your VSS already has built-in pull-up to 12V or 5V, you don't need pullups on cpks2+ (R161,R163). And if it doesn't, just populate 5V pullup (R161) on Prometheus. All level translation is done by MAX9926. You can also use additional R157 to pullup ckps2- (negative) to 5V - it may give a better threshold to MAX9926 for sensing 12V signals...

[puff]

I see. Now, the question is what's the impedance of fuel meter (300ohm pullup to 12V rail + 0 to ∞ pulldown) - I mean, whether I need to use opamp for that part or not.

[andreika]

the question is what's the impedance of fuel meter (300ohm pullup to 12V rail + 0 to ∞ pulldown)

Without opamp (i.e. VIGN) the readings will be somewhat inaccurate. You may try increasing the resistance of the divider from 2k/10k to 20k/100k - perhaps it would be enough, idk...

[puff]

got it. no sense in not using opamp then..

[Rhinoman]

When we're measuring the battery voltage, we don't need opamp, because source resistance is low. But we do need it when a high-impedance sensor is connected (including resistive ones like tps and thermistors).

You don't need an op-amp for TPS or thermistors, OEM ECUs don't use them.

[puff]

probably, they implement software filtering? (Kaman filtering?)

[masrodjie]

Nice board! Is there any source for schematic?

[andreika]

Nice board! Is there any source for schematic?

The full schematic is currently available only in PDF format here.

[masrodjie]

Nice board! Is there any source for schematic?

The full schematic is currently available only in PDF format here.

Is there any EAGLE source?

[andreika]

Is there any EAGLE source?

No, I'm afraid not, sorry... But I can export it into PCADv16-ASCII format, and you may try to import it in EAGLE if you want.
Don't know if it works though... Anyway, here's the attach:

prometheus-schem-pcad-v16-ascii.zip