All kit PCBs come pre-programmed and verified. No firmware upload required right after soldering. Actually your microRusEFI would
communicate via USB if you solder just USB connector or feed USB via 48 pin connector.
Re: microRusEFI
Posted: Sat May 30, 2020 5:39 pm
by AndreyB
WARNING: AT THIS PRICE POINT YOU BUY ONLY HARDWARE. No TUNING or even SETUP support is included - please read rusEFI wiki and please post all your questions on rusEFI forum
Re: tight connector area and traces on PnP boards and talk of smaller drill size:
Random JLC support quote, interesting stuff: "for the size of 1.1mm in the original file, they will become 1.25mm after making compensation, then the spacing between holes to lines will be only 0.108mm, our limit is 0.2mm" I assume 1.1 becoming 1.25mm is drill sizes.
Re: microRusEFI
Posted: Mon Jun 08, 2020 9:51 pm
by Joey120373
I've been playing around with my MRE for about a week now off and on, just on the bench.
Have to say I really like the RusEFI environment, this board is just cool, small and versatile.
Ive been adding a few wires to the main connector to eventually hook it up to a simulator to fiddle with some knobs.
One issue i had, and this is completely on me, I seem to have used the wrong connector. I had a couple of that 48 pin connector lying around from other cases i bought ( plastic ones from alli-express ) . The crimp connectors and plug are not all the same. The crimp connectors that came with the MRE case I ordered are
square, and the crimp connectors that fit the connector I soldered on are round.
Not sure if anyone else has run across this issue but sure had me banging my head for awhile.
Re: microRusEFI
Posted: Sat Jun 13, 2020 6:47 pm
by AndreyB
An exercise in panelization is currently taking place, mostly for fun really.
Re: microRusEFI
Posted: Sun Jun 14, 2020 11:59 pm
by AndreyB
PSA: Fully assembled microRusEFI price will go up next Friday or after next four units sold, whatever happens first. There is also a good chance that kits would now longer be offered or maybe similar price bump. https://www.ebay.com/itm/333532119947
microRusEFI was a major success and I've learned a lot with it. Next phase would be to adjust with all the knowledge we've gained with MRE and Proteus.
Re: microRusEFI
Posted: Thu Jul 02, 2020 2:37 pm
by AndreyB
A very special framed edition
Re: microRusEFI
Posted: Thu Jul 16, 2020 11:54 am
by fluxin
Quick question,
Is there a way to add a second VR input? We've got a WRL/Champcar miata and possibly wanted to bring in the Speedo (switched to NB style VR)
Re: microRusEFI
Posted: Thu Jul 16, 2020 3:08 pm
by AndreyB
You would have to buy a VR board on eBay if you really need two VR.
I believe you do not need any VR. NA and NB miata both use Hall signals, please note that my primary test mule is NB and somehow it runs on microRusEFI as is, in hall configuration.
Quick question,
Is there a way to add a second VR input? We've got a WRL/Champcar miata and possibly wanted to bring in the Speedo (switched to NB style VR)
To the best of my knowledge, the VSS signal fed into the ECU on NB Miatas is a TTL-level square wave generated by the speedometer electronics. You don't need VR for that.
Re: microRusEFI
Posted: Thu Sep 17, 2020 10:16 pm
by fluxin
Sorry for the severely delayed response! We have no dashboard left in the car. We only have a Autosport Labs Racecapture for data logging and currently a Microsquirt, which we will be replacing with a microRusEfi pretty soon! We need to monitor the speedo sensor directly,
Re: microRusEFI
Posted: Tue Nov 03, 2020 11:55 pm
by Gepro
Hello,
on the schematic, I see that GP1,2,3,4 can be LOW-SIDE or HIGH-SIDE.
I can't find how to change it, is it possible to change 2 of them to HIGH-SIDE ?
on the schematic, I see that GP1,2,3,4 can be LOW-SIDE or HIGH-SIDE.
I can't find how to change it, is it possible to change 2 of them to HIGH-SIDE ?
Thanks,
They can (in theory) be switched in software. Right now, they're locked to something (maybe lowside only?). Eventually™ you'll be able to pick the function per-pin, once we pester @dron_gus to implement it (which he has been making progress on).
I see there is flashmemory on the MRE, I also see that it can be accessible by the rusefi plugin, but how can we activate the logs, is it automatic ? Can we choose what to log ?
And what happen when the memory is full ?
Thanks,
Re: microRusEFI
Posted: Wed Nov 11, 2020 5:30 pm
by Gepro
Hello,
I have an other question, I believe that I am right but not sure.
Does an AT input can detect ground contact ?
My clutch pedal goes to the ground, I just want to be sure if there is no risks. (maybe, must I plug a resistor before ? )
I have an other question, I believe that I am right but not sure.
Does an AT input can detect ground contact ?
My clutch pedal goes to the ground, I just want to be sure if there is no risks. (maybe, must I plug a resistor before ? )
Thanks,
All the analog inputs are safe to connect to any voltage from -12 to +12 volts. Totally fine to short the pin to ground via a switch.
Re: microRusEFI
Posted: Thu Nov 12, 2020 7:50 pm
by azm
Hi everyone,
I am digging through HW schematics, checking the code (mainly focusing firmware at the moment). I have to say, all contributors did a very very good job.
As someone working in automotive industry I can say, that you could be an example to many engineers working full time in automotive.
Regards
Re: microRusEFI
Posted: Sat Nov 28, 2020 12:12 pm
by Gepro
Hello !
I just received my microRusEFI, I am really happy because it is a 0.5.3, with 2 VNLD5090 on it.
But I am really confuse about it... I don't know how to use it. I take a look at the 0.5.2 schematics and it looks like AV8 and AV9 can be use for them ? I find the R86 unpopulated, look to be for AV6, I don't understand.
So, if I tune them for input, it is an input, and if I tune them for injectors, it is an injector output ?!?
Maybe I miss the wiki !?!
And I have a question about ignition out. At the back of the board, I have 4 unpopulated resistor and it looks to go to ign1 to 4. It is R20 R33 R80 R81.
It is to solder if I want to use the TLE instead of 4427 ?!?
Thanks,
Re: microRusEFI
Posted: Sat Nov 28, 2020 1:28 pm
by Gepro
I take a look to the 0.5.3 corrected PNG, and it looks like every thing is populated on the top side, except R86, so I can use AV6 for one injector, through TLE_OUT12_PRE in tuner studio. Am I right ?
Do I need to remove R84 from the PCB if I want to use AV8 for another injector ? Or is it OK ?
Thanks,
Re: microRusEFI
Posted: Sun Nov 29, 2020 8:49 am
by Simon@FutureProof
Your looking to run a 6 cylinder right?
At this time the only proven way to run a 6 cylinder on an MRE is wasted spark and batch injection using the standard 4 Inj and Ign outputs.
The VNLD5090 is pretty untested as far as I am aware, they were added on 0.5.2 and I believe have not been used for anything yet.
Which would make you a bit of a test pilot for them.
Schematic wise 0.5.3 is identical to 0.5.2
They are connected to AV 6, 7, 8 and 10.
We have noticed the fault detection of the TLE is putting 3.3v onto the analogue channels, this should be getting switched off in the firmware but if you want to disable it full time then you can cut the traces going to the VNLD chips as again it is not currently used and prevents the analogue inputs working as analogue inputs.
Maybe not a problem in your case as you want to use them as outputs.
Re: microRusEFI
Posted: Sun Nov 29, 2020 10:22 am
by Gepro
That's right !
Absolutely no problem for sequential COP on 6 cylinders on microrusefi, I don't want wasted spark, it is more stress for coils, and they are limited for my use.
But I will try full sequential for injectors, I can't test the outputs for now, but I don't know why it will be wrong at low power. And I will test it with picoscope later, before making power. I think that a picoscope can see the difference of lag between the two, maybe I am wrong
Actually, I don't know if the tune is fine, the TLE have to send push-pull signal to VNLD5090, but for the 1-4 injectors, I believe it sends lowside ?! And I can't tune it by injectors.
I removed the R84, just in case, but I have a little concern about PC10 attribued to "console TX" ? And I need it for SPI1 from TLE.
I believe that I have to go with MRE firmware and tune the ".ini" for crank input on AV2.
Re: microRusEFI
Posted: Fri Dec 04, 2020 12:27 am
by Simon@FutureProof
Just as a confirmation, I tested the AUX lowsides on AV 6, 8, 9 and 10 tonight and I can confirm that all but AV6 will work as a lowside out of the box.
AV6 needs a zero ohm resistor added to make that one work but it also functions.
So if the AUX AV reuse pins are selected then they 100% work.
What we do have a bit of an issue with at the moment is the analogue on those pins, it is being affected by the TLEs fault detection, and this is something that we hope to fix in software in the near future.
So if you see a weird 3.3v on those pins then don't panic, it's 'normal' and will be made to go away soon.
Anyone have practical experience with MRE and electronic throttle body driven by wire?
My prefered scenario looks realistic?
Says I want to have very fast TB with time of open or close below 0.1s by direct shaft bldc motor
Then instead of accelerometer pedal it would bel used correct signal of autopilot (any analog or digital)
Anyone have practical experience with MRE and electronic throttle body driven by wire?
My prefered scenario looks realistic?
Says I want to have very fast TB with time of open or close below 0.1s by direct shaft bldc motor
Then instead of accelerometer pedal it would bel used correct signal of autopilot (any analog or digital)
ETB moving from 0 to 100% in under 0.1 second is pretty realistic.
I bought 4 MRE from Dmitry Korostelev as well as 4 "Speeduino Blitzbox" for test use
"considering shielding the community from you" - SOUND VERY RUDE. I dont deserve this...