[rusEfi] Miata NA 1990, 1.6L stock #21
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Nokia 2GB card also works always
SanDisk 1GB card worked once and does not work anymore, WAT?
unmarked 2GB card does not work - formatted FAT
SAMSUNG 1GB works
same SAMSUNG 1GB works just formatted it FAT32 and it still works! Good news FAT32 is supported I did not know that.
Kingston 8GB FAT32 card works
another SanDisk 1GB worked couple of times already
another SanDisk 2GB worked once and now it does not work any more.
I've just wasted 2 hours of my life on unreliable SD cards
Technically my collection is too small for a good analysis but all cards which worked on a PC but not reliable on rusEfi are either unmarked or SanDisk.
update: unmarked 32GB FAT32 works on my Rev D card Frankenstein board
sony 8gb does not work
SanDisk 1GB card worked once and does not work anymore, WAT?
unmarked 2GB card does not work - formatted FAT
SAMSUNG 1GB works
same SAMSUNG 1GB works just formatted it FAT32 and it still works! Good news FAT32 is supported I did not know that.
Kingston 8GB FAT32 card works
another SanDisk 1GB worked couple of times already
another SanDisk 2GB worked once and now it does not work any more.
I've just wasted 2 hours of my life on unreliable SD cards
Technically my collection is too small for a good analysis but all cards which worked on a PC but not reliable on rusEfi are either unmarked or SanDisk.
update: unmarked 32GB FAT32 works on my Rev D card Frankenstein board
sony 8gb does not work
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
I'm using a Kingston 16GB card formatted FAT32 on the Frankenso powered from the car 12v. I'll try a small card to see if it makes a difference.russian wrote: Are you using same board same SD card in both cases?
Last edited by tomiata on Thu Feb 09, 2017 4:52 am, edited 2 times in total.
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Interesting, even relatively large lot of used small 2GB cards - http://www.ebay.com/itm/222401344036 - still above $2 per card.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
RevC Discovery on Frankenso in car, 1G Kingston FAT formattomiata wrote:I'm using a Kingston 16GB card formatted FAT32 on the Frankenso powered from the car 12v. I'll try a small card to see if it makes a difference.russian wrote: Are you using same board same SD card in both cases?
2017-02-08 22_27: EngineState: confirmation_ls /:4
2017-02-08 22_27: EngineState: ls_result
2017-02-08 22_27: EngineState: logfile36948:rus1.msl
2017-02-08 22_27: EngineState: confirmation_sdinfo:6
2017-02-08 22_27: EngineState: MMC CS PD4
2017-02-08 22_27: EngineState: SD enabled: Yes [rus1.msl]
2017-02-08 22_27: EngineState: fs_ready=Yes totalLoggedBytes=40476
RevD Discovery on Frankenso in car, 1G Kingston FAT format
2017-02-08 22_33: EngineState: confirmation_ls /:4
2017-02-08 22_33: EngineState: Error: No File system is mounted
2017-02-08 22_33: EngineState: confirmation_sdinfo:6
2017-02-08 22_33: EngineState: MMC CS PD4
2017-02-08 22_33: EngineState: SD enabled: Yes []
2017-02-08 22_33: EngineState: fs_ready=No totalLoggedBytes=0
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Did you mention you have more than one Rev D board? Do you have more than two boards total?
With my testing today I am convinced Rev D SD works at least sometimes.
With my testing today I am convinced Rev D SD works at least sometimes.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
Yes, I have 2 RevD boards and 1 RevC, not counting a RevC board that I killed with 12v applied to the 5v input.
Re: Miata NA 1990, 1.6L stock #21
Some items to keep an eye out for include SD card vs MMC, as well there are special SD cards which are commonly used on PLC's which have special extra security features. Do you expect the SD cards are all generic camera SD cards? Do they all have the same pin out as noted below.
Also lets not forget the read / write switch position.
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Pictured are sd cards, our boards take microSD - too small for a key
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
RevC & RevD refers to stm board, right? Frankenso (or whatever it is) is the same? So, probably, something inside discovery is broken? Have you checked errata?
Re: Miata NA 1990, 1.6L stock #21
one more note on cheap cards with large capacity sold on ebay. often they are not as large as they may seem. e.g. the descriptor might show that it is 2GB card, while the actual available capacity is 256MB or less. And nobody knows what happens when you try to write down data in the addresses higher than those 256MB. There are utilities on the net that help identify the actuall capacity of the card.
Re: Miata NA 1990, 1.6L stock #21
Is the software expecting SD or MMC? We have SD, but could there be a software compatibility issue with MMC? Sorry just a wild ass guess.
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Each SD is an MMC I believe? See http://www.diffen.com/difference/MMC_vs_SD_Card
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Why analogInputDividerCoefficient = 2.5? That's a big question since this affects pretty much all calibrations and everything.tomiata wrote:Attached is current tune
injector_flow = 215 why not 230 as on http://miataturbo.wikidot.com/fuel-injectors and http://www.miataturbo.net/useful-saved-posts-8/diy-faq-all-your-answers-one-big-post-10821/#post513134 ? that's a much smaller question.
globalTriggerAngleOffset = 16 tell me when it would be a good day for me to change firmware so those 16 are part of trigger and you do not need to have any extra offset.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Tom so you have only tried one SD card? Do you want to order http://www.ebay.com/itm/401270523426 since these are two different cards?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
See above, the last thing I tried last night was a 1GB Kingston FAT format card. I had been using a 16GB FAT32 formated Kingston card for a month or so. Both show the same results. I have some 32GB Samsung for the gopro that I can try. I may have some others laying around.russian wrote:Tom so you have only tried one SD card? Do you want to order http://www.ebay.com/itm/401270523426 since these are two different cards?
Re: Miata NA 1990, 1.6L stock #21
Some good news...
I bought a new Sandisk 8GB card at walmart, FAT32 format, and it worked with the RevD board with 2/4 firmware on Frankenso in the car.
But, some new problems with this config with engine running rough and very rich and feels like running on 2 cylinders.
Also, new warnings on TPS:
low: -1.20,msg,WARNING: TPS too low: -1.28,msg,WARNING: TPS too low: -1.28,msg,WARNING: TPS too low: -1.28,msg,WARNING: TPS too low: -1.20,msg,WARNING: TPS too low: -1.20,msg,WARNING: TPS too low: -1.04,msg,WARNING: TPS too low: -1.04,msg,WARNING: TPS too
And recalibrating TPS did not fix it...
I'll gather up more logs and post.
I bought a new Sandisk 8GB card at walmart, FAT32 format, and it worked with the RevD board with 2/4 firmware on Frankenso in the car.
But, some new problems with this config with engine running rough and very rich and feels like running on 2 cylinders.
Also, new warnings on TPS:
low: -1.20,msg,WARNING: TPS too low: -1.28,msg,WARNING: TPS too low: -1.28,msg,WARNING: TPS too low: -1.28,msg,WARNING: TPS too low: -1.20,msg,WARNING: TPS too low: -1.20,msg,WARNING: TPS too low: -1.04,msg,WARNING: TPS too low: -1.04,msg,WARNING: TPS too
And recalibrating TPS did not fix it...
I'll gather up more logs and post.
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
So why multiplier 2.5 and flow 215?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
Sorry, didn't get around to answering this earlier.russian wrote:So why multiplier 2.5 and flow 215?
The 2.5 Analog divider (coef) came from the tune I started with from @thommm's smurf tune. I didn't notice that it was different from standard.
The injector flow came from a reference I found when I searched around forums to check the value for the injectors I have. I don't remember where I got that.
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Problem is actual hardware is a 2.0 analog divider. And changing this value would throw everything off.tomiata wrote:The 2.5 Analog divider (coef) came from the tune I started with from @thommm's smurf tune.
But using the real divider is probably the right thing to do? But it would throw all you sensor calibrations and maps off.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
I got this going through much trial and error, and not knowing what I was doing. I want to make it all as it should be to follow "standard" settings. I don't mind changing it.russian wrote:Problem is actual hardware is a 2.0 analog divider. And changing this value would throw everything off.tomiata wrote:The 2.5 Analog divider (coef) came from the tune I started with from @thommm's smurf tune.
But using the real divider is probably the right thing to do? But it would throw all you sensor calibrations and maps off.
Re: Miata NA 1990, 1.6L stock #21
Here is the chart where I found the 215 value for injector flow volume.
http://www.robietherobot.com/storm/fuelinjectorguide.htm
Btw, the smurf tune had a value of 200.
http://www.robietherobot.com/storm/fuelinjectorguide.htm
Btw, the smurf tune had a value of 200.
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
Let's start by changing multiplier to 2.0
I've actually realized maybe only sensors would need to be re-calibrated but maps would stay the same.
I've actually realized maybe only sensors would need to be re-calibrated but maps would stay the same.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
Is there a jumper wire configuration for this setup? Or was this just 0R's I know we tried to make it work with some specific setups, but other models have different pin outs. Keep in mind we can make a small PCB which can be put over the jumper area, then you can solder the via's on this PCB and it can function as the jumper wires, instead of installing a bunch of wires.
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
http://rusefi.com/forum/viewtopic.php?f=4&t=1174kb1gtt wrote:Is there a jumper wire configuration for this setup?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Miata NA 1990, 1.6L stock #21
Ok. I changed the multiplier to 2.0 and I'm reworking the settings using the RevD Discovery board. Now I see why it was so hard to get my CLT and IAT to match reality. I had to fudge the bias resistor settings to make it work before. I thought there was a problem with my sensors or something.russian wrote:Let's start by changing multiplier to 2.0
I've actually realized maybe only sensors would need to be re-calibrated but maps would stay the same.
Also, when I first installed the MPX4250 map sensor originally, the built-in setting didn't work right and set up custom config to make it work.
I still need to fix the WBO inputs. The rusefi readings are off from the AFR gauge. But the car starts ok.
I recalibrated TPS, but still get the TPS warnings about too high or too low.
When I tried it last night it was running very rough and seemed like was running on 2 or 3 cylinders. But today (before i started work on the sensor settings) it ran ok. I checked all the plug wires and saw flashes on a timing light. I don't know what was going on there. That's all the time I have for this now. I'll work on WBO later. It's good to know why I had so much trouble before.
Re: Miata NA 1990, 1.6L stock #21
I got WBO straightened out and recalibrated. Now running with Feb. 4 firmware on revD board with prototype top side sdcard (thanks @russian for sending that!)
Sensors are recalibrated and car is running with a rough tune. I turned off the closed loop fuel correction option. Should I try that yet?
Response is not quite as good as previous stable config, but needs more run time. Here is the current tune and logs from a drive.
Sensors are recalibrated and car is running with a rough tune. I turned off the closed loop fuel correction option. Should I try that yet?
Response is not quite as good as previous stable config, but needs more run time. Here is the current tune and logs from a drive.
- Attachments
-
[The extension msq has been deactivated and can no longer be displayed.]
-
- rus-2017-02-15.msl
- (928.35 KiB) Downloaded 472 times
Re: Miata NA 1990, 1.6L stock #21
As soon as you have the VE table tuned reasonably well, you can engage CL for AFR. Wouldn't do it before that.tomiata wrote:I got WBO straightened out and recalibrated. Now running with Feb. 4 firmware on revD board with prototype top side sdcard (thanks @russian for sending that!)
Sensors are recalibrated and car is running with a rough tune. I turned off the closed loop fuel correction option. Should I try that yet?
Response is not quite as good as previous stable config, but needs more run time. Here is the current tune and logs from a drive.
Re: Miata NA 1990, 1.6L stock #21
Sensors are calibrated now, and tune is fairly stable running Feb. 15 firmware on revD Discovery.
But I still get lots of warnings, like about 460 per second. Looks like all are TPS too high or too low.
Any idea what's going on there?
But I still get lots of warnings, like about 460 per second. Looks like all are TPS too high or too low.
Any idea what's going on there?
- Attachments
-
- rus-2017-02-17-2.msl
- (668.12 KiB) Downloaded 499 times
Re: Miata NA 1990, 1.6L stock #21
Don't know what's going on, but I'm getting the same messages, running your tune with a stimulator.tomiata wrote:[...]
But I still get lots of warnings, like about 460 per second. Looks like all are TPS too high or too low.
Any idea what's going on there?
- AndreyB
- Site Admin
- Posts: 14361
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Miata NA 1990, 1.6L stock #21
I know what's going on
Just updated https://svn.code.sf.net/p/rusefi/code/trunk/firmware/controllers/algo/obd_error_codes.h file mentioned on the minimalistic
http://rusefi.com/wiki/index.php?title=Manual:Error_codes page
I bet your configuration has grandfathered both TPS low and high value detection thresholds as zero. My bad these settings were not exposed in the TS project - just commited, these would appear below "tps adc channel" setting. You probably want the defaults which are -10% for too low error and 110% for too high error.
Just updated https://svn.code.sf.net/p/rusefi/code/trunk/firmware/controllers/algo/obd_error_codes.h file mentioned on the minimalistic
http://rusefi.com/wiki/index.php?title=Manual:Error_codes page
I bet your configuration has grandfathered both TPS low and high value detection thresholds as zero. My bad these settings were not exposed in the TS project - just commited, these would appear below "tps adc channel" setting. You probably want the defaults which are -10% for too low error and 110% for too high error.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute