3 issues with Rev Built MS3-Basic
03-01-2016, 10:08 PM
#21
Junior Member
Join Date: Sep 2015
Posts: 45
Total Cats: 1
I thought I was the only one that experienced issue #2, as I couldn't find anything online. I chased this issue for a while a few months back, but eventually gave up and switched to the Analog input.
I am using the AEM Uego, Rev MS3, w/ Can wideband unit.
When using the CAN unit, every once in a while, seemingly out of the blue, my AFR readings in TunerStudio become highly inaccurate and "freeze" in place. This happens after driving normally, or using VEAL after 15-20 minutes.
My gauge is still showing accurate readings, moving around as it should, but in TunerStudio it will freeze on a particular reading for a long period of time, totally out of sync with my gauge.
I have to turn it off and turn it back on in order to get it to behave normally again. If I'm in the middle of VEAL, it will start screwing with the cell changes. Super frustrating.
I have a log of this occurring.. you can see the AFRs "flatlining" - check it out here: Wacky AFR Reading
Would love to figure this one out.
I am using the AEM Uego, Rev MS3, w/ Can wideband unit.
When using the CAN unit, every once in a while, seemingly out of the blue, my AFR readings in TunerStudio become highly inaccurate and "freeze" in place. This happens after driving normally, or using VEAL after 15-20 minutes.
My gauge is still showing accurate readings, moving around as it should, but in TunerStudio it will freeze on a particular reading for a long period of time, totally out of sync with my gauge.
I have to turn it off and turn it back on in order to get it to behave normally again. If I'm in the middle of VEAL, it will start screwing with the cell changes. Super frustrating.
I have a log of this occurring.. you can see the AFRs "flatlining" - check it out here: Wacky AFR Reading
Would love to figure this one out.
Reply
0
0
03-01-2016, 10:19 PM
#22
google searching "AEM UEGO serial data logging problems" gets me a few results. Seems quite a few people get it to lock up after a few seconds and get stuck at a fixed value. It might not be a reverant converter box problem.
It seems the serial port on the uego might not be grounded as it comes. My mtx-l came with a serial cable, but as far as I can tell the uego might not come that way? Can you easily tie the uego ground wire with pin #5/ground on the reverent wideband interface? I wonder if that might help?
It seems the serial port on the uego might not be grounded as it comes. My mtx-l came with a serial cable, but as far as I can tell the uego might not come that way? Can you easily tie the uego ground wire with pin #5/ground on the reverent wideband interface? I wonder if that might help?
Reply
0
0
03-01-2016, 10:21 PM
#23
^ yeah, and we loaded the .ini file yesterday, and today it's still miss communicating...
pretty ******* annoying, since I specifically paid for the can wideband unit to eliminate communication issues.
AFRs spiked to 13.1 at wot, then was idling past the lean limit of the gauge... cycled the car off, then on... and voila... idles at 14.7 again...
pretty ******* annoying, since I specifically paid for the can wideband unit to eliminate communication issues.
AFRs spiked to 13.1 at wot, then was idling past the lean limit of the gauge... cycled the car off, then on... and voila... idles at 14.7 again...
Reply
0
0
03-01-2016, 10:25 PM
#24
Junior Member
Join Date: Sep 2015
Posts: 45
Total Cats: 1
The AEM UEGO instructions state that Pin #5 on the serial connector should be grounded (check it out here).
I tested with and without this pin grounded (to chassis, and also to the DB37 harness), and it had no impact on this communication error.
I tested with and without this pin grounded (to chassis, and also to the DB37 harness), and it had no impact on this communication error.
Reply
0
0
03-05-2016, 06:42 PM
#27
So I connected ground and power to the oem BOOST sensor, and extended a wire through the firewall from the remaining wire (not sure what to call it.. sensor readout? idk)
Now, where/how do I connect this wire to the megasquirt?
Do i push it into any of the external ports?
Do i need to change anything internally in the megasquirt?
Please be as specific and thorough as possible.
Thanks
Now, where/how do I connect this wire to the megasquirt?
Do i push it into any of the external ports?
Do i need to change anything internally in the megasquirt?
Please be as specific and thorough as possible.
Thanks
Reply
1
1
03-06-2016, 03:26 AM
#29
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,977
Total Cats: 356
The baro sensor is already getting 5V power (green/red) and ground (black/red) from the car's harness. The signal wire is the blue yellow wire. This goes back to the ECU, on the largest of the 3 connectors. Splice a wire into it, and connect it to pin 11 on the DB-37 connector. Pin #1 is the white/red wire, pin 19 is the orange wire, so count to 11 from either one. Pin 11 is the "EXT_MAP" analog input in the menus.
Reply
0
0
03-10-2016, 09:06 AM
#35
Yep, I'll prune this thread in a bit.
*edit: here's the new thread
https://www.miataturbo.net/megasquir...cussion-88117/
*edit: here's the new thread
https://www.miataturbo.net/megasquir...cussion-88117/
Last edited by 18psi; 03-10-2016 at 01:25 PM.
Reply
0
0
03-10-2016, 11:47 AM
#36
Retired Mech Design Engr
iTrader: (3)
Join Date: Jan 2013
Location: Seneca, SC
Posts: 5,009
Total Cats: 857
A few pertainent questions/ comments:
1) How do you plan to calibrate the 2nd MAP sensor?
2) Please post your curves when complete.
3) Tuner Studio discusses 2nd MAP sensor with information about -47 and 147 for calibration and using all zeros for correction, if updating from old FW. Reverant, can this be ignored and one use corrections based on 100% rather than zero, with the sensor calibrated as 18psi will tell us from item 1? (MS3 1.4 FW).
1) How do you plan to calibrate the 2nd MAP sensor?
2) Please post your curves when complete.
3) Tuner Studio discusses 2nd MAP sensor with information about -47 and 147 for calibration and using all zeros for correction, if updating from old FW. Reverant, can this be ignored and one use corrections based on 100% rather than zero, with the sensor calibrated as 18psi will tell us from item 1? (MS3 1.4 FW).
Reply
0
0
03-10-2016, 01:22 PM
#37
Junior Member
Join Date: Oct 2012
Posts: 138
Total Cats: 5
A few pertainent questions/ comments:
1) How do you plan to calibrate the 2nd MAP sensor?
2) Please post your curves when complete.
3) Tuner Studio discusses 2nd MAP sensor with information about -47 and 147 for calibration and using all zeros for correction, if updating from old FW. Reverant, can this be ignored and one use corrections based on 100% rather than zero, with the sensor calibrated as 18psi will tell us from item 1? (MS3 1.4 FW).
1) How do you plan to calibrate the 2nd MAP sensor?
2) Please post your curves when complete.
3) Tuner Studio discusses 2nd MAP sensor with information about -47 and 147 for calibration and using all zeros for correction, if updating from old FW. Reverant, can this be ignored and one use corrections based on 100% rather than zero, with the sensor calibrated as 18psi will tell us from item 1? (MS3 1.4 FW).
So what counts as "old FW"? What needs to be changed to switch to the "current" calibration method/values? I have upgraded from 1.3.x to 1.4.x over the years and have no idea based on the TS manual how my MS3 2nd MAP sensor should be set... Anyone have any insight?
Reply
0
0
03-14-2016, 10:03 AM
#38
cross posting this here so we can keep it all in one thread
Well, OP is leaving Suck-rah-mento today and taking the long trip back to Utah.
This was seriously a lot of fun (sometimes more than others lol), and I can say that we have become friends after all this
There are still some issues to work out with this car, but it runs well and we got a TON of stuff done to it.
@Reverant
There are issues with the MS3 basic that OP got, in addition to the ones already outlined in the MS section thread. OP will be contacting you about those and I'll outline them more in that thread. (hint: his DB37 appears to be missing more than HALF of the inputs/outputs outlined in the instructions. not sure if those were missed or left out intentionally for some reason. also his CAN unit still acts up every now and then causing all sorts of terrible-ness in fueling)
Other than the above, the car is much quicker, handles amazing, and now that OP got the lip kit painted and installed, it actually looks sexier too
This was seriously a lot of fun (sometimes more than others lol), and I can say that we have become friends after all this
There are still some issues to work out with this car, but it runs well and we got a TON of stuff done to it.
@Reverant
There are issues with the MS3 basic that OP got, in addition to the ones already outlined in the MS section thread. OP will be contacting you about those and I'll outline them more in that thread. (hint: his DB37 appears to be missing more than HALF of the inputs/outputs outlined in the instructions. not sure if those were missed or left out intentionally for some reason. also his CAN unit still acts up every now and then causing all sorts of terrible-ness in fueling)
Other than the above, the car is much quicker, handles amazing, and now that OP got the lip kit painted and installed, it actually looks sexier too
Oh, well that explains our confusion when we opened it up then.
Yes, I'll upload the logs we did get to the other thread.
Also it started giving an error message on the last day "unable to communicate with CAN" or something like that. I'll see if we can send you a screen shot.
Basically it completely stopped being able to datalog as of Saturday. Every time you open TS it gives you that error, and after you log the car, you open the log and it error's out in MLV saying "data corrupted or no data" or something like that. again, I'll upload screenshots.
I've no idea why it suddenly started doing that, but we ran out of time and couldn't diagnose it further. And we still couldn't hook up BARO correction because OP tried to solder in the connection and just couldn't do it.
Yes, I'll upload the logs we did get to the other thread.
Also it started giving an error message on the last day "unable to communicate with CAN" or something like that. I'll see if we can send you a screen shot.
Basically it completely stopped being able to datalog as of Saturday. Every time you open TS it gives you that error, and after you log the car, you open the log and it error's out in MLV saying "data corrupted or no data" or something like that. again, I'll upload screenshots.
I've no idea why it suddenly started doing that, but we ran out of time and couldn't diagnose it further. And we still couldn't hook up BARO correction because OP tried to solder in the connection and just couldn't do it.
Reply
1
1
03-22-2016, 01:55 PM
#39
Ok, so I've had AN IMMENSE amount of issues on my drive to utah. I had to endanger myself 4 different times on the side of mountain roads without a shoulder to **** with the settings on the ms3, in hopes I could get it to not lean out a lot at wot.
Now that I'm here, the car takes sometimes 40 seconds (total) cranking time to finally fire and start, sometimes dies when braking, or just putting the car in neutral while rolling, sometimes loses connection with the wideband and idles over 17afr....
anyways...
Reverent, please email me at marmarchesini@yahoo.com
I want to buy a new ms3, wideband and can module...have you integrate two baro sensors, wire everything completely, test thoroughly for CAN connectivity issues. I'll be returning the old ms3 with gauge and can module once i receive the new attempt.
Please take your time, and make everything perfect. I don't want any issues. I am now 80 miles away from the nearest city, and 25 miles away from the nearest town with any automotive services.
Maybe second time is a charm?
Now that I'm here, the car takes sometimes 40 seconds (total) cranking time to finally fire and start, sometimes dies when braking, or just putting the car in neutral while rolling, sometimes loses connection with the wideband and idles over 17afr....
anyways...
Reverent, please email me at marmarchesini@yahoo.com
I want to buy a new ms3, wideband and can module...have you integrate two baro sensors, wire everything completely, test thoroughly for CAN connectivity issues. I'll be returning the old ms3 with gauge and can module once i receive the new attempt.
Please take your time, and make everything perfect. I don't want any issues. I am now 80 miles away from the nearest city, and 25 miles away from the nearest town with any automotive services.
Maybe second time is a charm?
Reply
0
0
