It's spring, convertibles are coming out to play (maintaining proper social distancing of course). I volunteer my testing-services for this board. When will it be available for sale?
Re: microRusEfi pnp Miata MX5 NA
Posted: Fri Mar 27, 2020 7:25 pm
by Crazy Striker
Yes perfect Miata time.
I'm tidying up the routing on the board (a few days), there is approx 12-14 days from ordering to delivery, add the dropshipping time to that and you have it. I will update design status as often as possible.
Yes perfect Miata time.
I'm tidying up the routing on the board (a few days), there is approx 12-14 days from ordering to delivery, add the dropshipping time to that and you have it. I will update design status as often as possible.
Gwendal
Sounds great!
Re: microRusEfi pnp Miata MX5 NA
Posted: Sat Mar 28, 2020 10:24 pm
by AndreyB
Schematics added to first post, still with missing LED resistors...
Re: microRusEfi pnp Miata MX5 NA
Posted: Mon Mar 30, 2020 2:02 pm
by Crazy Striker
For 3D view lovers
pnp48_isometric.jpg (155.06 KiB) Viewed 24013 times
Cheers
Gwendal
Re: microRusEfi48adapter pnp Miata MX5 NA
Posted: Sat Apr 11, 2020 2:27 am
by stefanst
First batch of 10 boards ordered. Now let's see if shipments from China still make it here.
The suspension is palpable.
Re: microRusEfi48adapter pnp Miata MX5 NA
Posted: Sat Apr 11, 2020 2:56 am
by stefanst
I just realized that U2 and U3 won't be populated. I can order some with my next order from Digikey.
Re: microRusEfi48adapter pnp Miata MX5 NA
Posted: Mon Apr 13, 2020 11:36 pm
by stefanst
Just looking through the schematic, trying to figure this thing out. I have a few questions:
- On the injectors: How are the schottkys in series with the LEDs suposed to work. Seems to me like we'll send 12V straight to the LEDs and blow them up as soon as an injector output goes low. Should the diodes be reistors?
- On the High level outputs we got a similar picture: Schottkys in line with LEDs hooked straight to 12V. Not sure what that's for. But it looks like when the high-out is turned off, whatever is hooked up to the output will be pulled high by the LED and Schottky, assuming the output does not pull low when turned off.
- On the left "174917" connector we have 1V and 2A both hooked up to 22. To make up for it 48 is not connected. What's the purpose of this?
Also: Which connector is the one coming from MicroRusefi? Both big connectors are labeled 174917 which would be the standard 48 pin Miata connector. It looks like the MRE connector is kind of scattered all over the schematic.
Re: microRusEfi48adapter pnp Miata MX5 NA
Posted: Tue Apr 21, 2020 2:04 am
by AndreyB
Boards come in boring green, at least we can install used RED connectors from Honda ABS units. Plug compatibility confirmed.
Re: microRusEfi48adapter pnp Miata MX5 NA
Posted: Thu Apr 23, 2020 5:18 pm
by stefanst
Funny you should be talking about exciting red connectors.
1st assembled.jpg (337.27 KiB) Viewed 23781 times
Board is assembled and being tested on the engine simulator. We are dropping sync a lot. See below:
020-04-23_13_13_10_646: EngineState: error: synchronizationPoint @ index 12 expected 4/8/0 got 4/9/0
2020-04-23_13_13_10_646: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_10_745: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_10_746: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_10_846: EngineState: time=616 index=0: gap=0.229 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_10_847: EngineState: time=616 index=0: gap=5.587 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_10_856: EngineState: time=616 index=0: gap=0.781 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_10_956: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_10_956: EngineState: error: synchronizationPoint @ index 24 expected 4/8/0 got 9/16/0
2020-04-23_13_13_10_966: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_056: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_057: EngineState: error: synchronizationPoint @ index 12 expected 4/8/0 got 4/9/0
2020-04-23_13_13_11_057: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_147: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_148: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_249: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_249: EngineState: error: synchronizationPoint @ index 12 expected 4/8/0 got 4/9/0
2020-04-23_13_13_11_258: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_350: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_350: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_449: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_449: EngineState: error: synchronizationPoint @ index 12 expected 4/8/0 got 5/8/0
2020-04-23_13_13_11_459: EngineState: time=616 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_551: EngineState: time=616 index=0: gap=1.507 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_551: EngineState: error: synchronizationPoint @ index 12 expected 4/8/0 got 4/9/0
2020-04-23_13_13_11_561: EngineState: time=616 index=0: gap=0.663 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_563: EngineState: time=616 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_565: EngineState: time=616 index=0: gap=0.033 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_651: EngineState: time=617 index=0: gap=18.652 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_652: EngineState: time=617 index=0: gap=1.589 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_664: EngineState: error: synchronizationPoint @ index 13 expected 4/8/0 got 5/9/0
2020-04-23_13_13_11_755: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_756: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_853: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_853: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_954: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_954: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_11_954: EngineState: error: synchronizationPoint @ index 12 expected 4/8/0 got 4/9/0
2020-04-23_13_13_12_056: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_056: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_157: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_157: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_171: EngineState: error: synchronizationPoint @ index 12 expected 4/8/0 got 4/9/0
2020-04-23_13_13_12_174: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_254: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_254: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_358: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_358: EngineState: time=617 index=0: gap=0.662 expected from 0.895 to 1.940 error=Yes
2020-04-23_13_13_12_457: EngineState: time=617 index=0: gap=1.508 expected from 0.895 to 1.940 error=Yes
dropped sync 2.png (81.66 KiB) Viewed 23781 times
dropped sync 3.png (79.11 KiB) Viewed 23781 times
dropped sync 4.png (80.15 KiB) Viewed 23781 times
Re: microRusEfi48adapter pnp Miata MX5 NA
Posted: Thu Apr 23, 2020 5:30 pm
by stefanst
Trigger log attached.
Re: microRusEfi48adapter pnp Miata MX5 NA
Posted: Thu Apr 23, 2020 11:33 pm
by AndreyB
You have an older microRusEfi running with a harness adapter, have you ever put that older on the the stim? it would be interesting to compare notes. In case of differences I would double-check that Hall divider and pull-up values.
in latest firmware TLE8888 dialog now has "mode" dropdown. So far we've tried "default" and "manual" mode (NB2 likes "manual" mode of TLE8888). Let's try "hall" mode now?
Not sure how far we're off, but the connector should be in the exact center between the front mounting holes (PCB to case, approx 120mm apart). That would mean approx 17.5mm from each PCB mounting hole.
Re: MREAdapter48 pnp Miata MX5 NA
Posted: Sat May 09, 2020 10:18 pm
by AndreyB
Maybe some SD card shield to get SD card via SPI? Please not SD-card socket on the board or at least I would prefer not to be soldering those, those are tricky to solder in my experience
I have a bunch of "Mini Data Logger Logging Shield Module Board For Arduino For Raspberry Pi Recorder Shield SD Card 3.3V Regululator"
We have a working proof of concept. MRE on 48 pin board works with a cheap ($1.20) microSD adapter board from Amazon. As soon as the ECU fires up, it starts logging.
rusefi with spi microSD.jpg (133.6 KiB) Viewed 22855 times
Bribes. At this point it's unclear whom to bribe and in what amount.
Interesting relevant fact that both Proteus 0.3 and microRusEFI all use stm32f427 instead of stm32f407 - that gives us a bit of extra RAM and USB hardware on the chip is a bit more powerful with more "endpoints" whatever it means. We just need one developer to dive into this and we should have USB composite device and USB Mass Storage Device... Maybe. There are probably multiple ways to get there.
Re: MREAdapter48 pnp Miata MX5 NA
Posted: Fri May 15, 2020 12:56 am
by AndreyB
@stefanst reports the following SD cards working with rusEFI SPI code, all the way up to 64Gb!
Rumors are that MREAdapter48 0.2 is a major success but only @stefanst knows for sure.
Re: MREAdapter48 pnp Miata MX5 NA
Posted: Fri Jul 03, 2020 11:44 pm
by stefanst
The board seems to be a success indeed. I went for several longer rides without any issues. We have a working tune using MAP and a somewhat working tune (needs a better spark table) for running MAF. Idle compensation (closed loop idle) seems to begin working as well. The engine hasn't self-stalled in a while.
