Got a new oxygen sensor installed, tuned it a bit, and went to an autocross in my 280Z a couple weeks ago. I was third in my class! Out of three, though. So last. Still, the real victory is that my car made it there, ran, started and restarted fine, and then made it back home.
I also got to try my slicks out for the first time, and man, they make the car much more predictable. Lift-off oversteer is still there but manageable and much more forgiving (which probably doesn’t help that I have a bad habit of inducing it). Traction is not as greatly improved as I thought it would be, but I was just running them on the rear.
Anyway, here are a couple runs. A fun run (no time, just learning the course), and my fastest run.
It’s been a while since I’ve worked on my Z. I’ve been working on rebuilding my wife’s 300ZX, which is progressing slowly. My Z had a dead oxygen sensor and was not tuned correctly. It also had a fuel leak. But last week I fixed both of those issues and now it runs like a champ.
I then leaned out the fuel table by about 25% (I had richened it up when the sensor died to be safe). I was able to use autotune to then fix up the fuel map quite a bit. I really think it’s time to get it tuned on a dyno, but haven’t committed yet.
Sent off my oil temperature gauge to get the range changed from 100-300 degrees F or so to 60-260.
I’d like to use the slicks I got in at least one race this season, but I need to remove my bump steer spacers for the 15″ wheels they are on to fit.
So I picked up a Bosch 044 fuel pump for a song, and decided to get rid of my Fuelab Prodigy pump. I almost wrote about the Fuelab install, but since I intended on replacing it, it wasn’t worth it. It was just too much for my vehicle, even at my target boost levels.
The Fuelab pump was brushless, and so was very picky about voltage. It was unusable during cranking due to a large voltage drop because of my small battery. So I had to add in a check valve, which helped, but I still needed to do a ten-fold increase in my cranking pulsewidth calculations. Then there was the speed control wiring. It was too much ‘because racecar’, so I decided to swap to the Bosch when offered.
To my surprise it came with a check valve integrated in to a type of banjo fitting. But, since I already added a check valve closer to the fuel rail, this would be redundant. Also, banjo fittings flow poorly.
A couple of new fittings and moving the mounting brackets over a bit was all it took to get it installed. Note all the holes for all the difference bracket configurations on my mounting plate. Heh.
When I first installed an aftermarket ECU (Megasquirt I) in my 1984 300ZX, years ago (almost 10 as of this writing!), I used the recommended GM sensor for coolant temperature. It required a bit of machining to fit the sensor, nothing major.
With my latest engine (and the two cars it was in), I decided to use the OEM Cylinder Head Temperature Sensor, since hey, why not? It was already there, in an optimal spot. All I had to do was make software changes to calibrate MS-II to it’s temperature/resistance curve. I had the data in the Factory Service Manual, all was well. Continue reading
I finished up the tail light and signal wiring. I still have 4 LED clearance lights to place somewhere, but I’ll wait until I figure out what else is going on the trailer before placing them, in the hopes I can place them higher up.
So I’ve got this autocross bug, despite being a terrible driver. After about 5 seconds of thought, I came to the conclusion that I must get an autocross trailer in order to improve my skills.
So, after a bit of research it looked like item #90153 was the thing to get. The key is it has 12″ wheels, whereas the cheaper one (#42708) has 8″ ones. The larger the wheel the less RPM the wheel bearings see, which is good. The increased payload capacity and trailer height were just bonuses. Since I plan on hauling some wheels and tires and some tools, I don’t see coming near the 1000+ lb. payload capacity. And if you wanted to carry more, all you’d really need is some better tires, since that’s the actual limiting factor. However, I don’t recommend carrying anything near the payload capacity.
Note that this is one of the few big-ticket items you can use the 20% coupon on, so if you want to save $46 or so off the price, use one! I got it and built it:
I also picked up a trailer jack, LED lighting kit, 1-7/8″ ball, and ratcheting straps from HF. From elsewhere I got a backup alarm, more LED lights, battery tray, some wire and a voltage gauge.
I then painted the frame and wheels to match my 280Z:
Well, I’ve only been working on it a little so far, but I suppose it’s good enough to post about at this point.
The site is msqur.com, and it’s for Megasquirt ECU users to share their tunes (from the TunerStudio MS software). You can upload (multiple) .msq files, assign some engine information to them at upload, and share them with other people for troubleshooting or tuning help. The goal is to make something easier than attaching a file to a forum post that others have to download and fire up the full tuning software suite to just view it.
Currently, as of this posting, it just shows you the VE, Spark and AFR tables from MS2 or MS2-Extra only. It might with with other firmwares but I have no expanded it yet. You can also enable or disable the table coloring, and normalize the VE table, converting any VE table to 5-250 VE for ease of comparison. I hope to expand it to view all data available from the MSQ file in a familiar format.
I only get to work a bit each week on it, since I’ve got a few other projects going. But it shouldn’t take too long to get this site to 90%. It’s also a nice break from the C code for the DRD project. So, I’ll post every now and then about any updates to it, so check the msqur tag for the latest info.
Over a year ago I got an Arduino Uno and a CAN-BUS Shield to try and make some kind of datalogger for my car. I was also interested in using the OpenXC library with it (which might need a port if there isn’t one already, since it uses the Digilent chipKIT Max32 development board). While OpenXC allows interfacing with Android stuff for phones, I’m more interested in a self-contained datalogging type deal. Connecting a phone to review/control things would be a plus, but not required. Mainly, it would record to an SD card for later manipulation on any platform.
The problem with the Uno was that it has limited flash storage space, 32KB total. Lots of strings (for LCD output) in my source combined with some poorly written C++ CAN-BUS/SD/GPS libraries that SK PANG provide with the CAN-BUS shield, and the compiled output is just too large. The libraries are a hodge-podge of various OSS projects. I intend to rewrite them in C. You can run the binaries off the SD Card, but that’s not what I wanted the SD Card for.
So, I just got a Arduino Galileo, which is way overkill. It was either get a Arduino Mega, which has enough flash but is otherwise relatively the same (and likely going to be obsolete soon), or get the Galileo. Instead of Atmega powered, it has a real Intel x86 SoC and runs Linux! No more AVR cross-compiling. And since it is Arduino Uno “shield compatible”, I don’t have to worry about the shield not working (I think! I’m assuming the shield follows the Uno spec.).
8MB Flash, 400MHz clock speed and a whole other bunch of superior specs I don’t remember. Now, the embedded Linux kernel is on that 8MB, and takes most of it up. So at first it looked like I was in the same boat. However, it has a built-in SD card slot that you can load up another, larger, image onto. Now I have two SD Card slots, one on board and one on the CAN-BUS shield. One for the OS, one for logging data. Perfect.
First I have to get familiar with the Galileo and setup the environment. After that I can start developing. So this will be split up into at least two other parts.