I picked up the trial version yesterday, but despite their claims, it wouldn't open anything but their own format - and they don't even provide a sample file, so I have no idea what that is. The software costs $40 and there is a trial version. Their MegaLog viewer opens most logs - ECUTek logs are not listed but it opens them just fine. But I'm curious about the "official" EcuTek labels - does that mean that the column labels must match something inside the viewer? That is, I can't create a column with a custom label?ĮFI Analytics is the company that developed TunerStudio for the Megasquirt platform. Of course it didn't like it - XML and CSV are VERY different animals. I just tried opening a DD log with ProEcu w/o cleaning it up. I suspect that if you replaced the column labels in say a DashDaq log with the "official" EcuTek ones, and cleaned up some header stuff in the first few lines, then you could use the ProEcu viewers. The ProEcu logging format is CSV with column labels. At this point in my life I'm just not up for the work involved. I'd especially love to hear from somebody who knows where a good viewer can be had, hopefully cheap.īTW, before anybody accuses me of potential "commercial activity", let me emphasize that all this is for my own use, and I have no intention of popping a product out of this. I haven't seen what EcuTek uses maybe it's worth having, but I'm trying not to spend a bundle. I've searched the web for viewers to try, and they're universally terrible (although each in it's own way). OK, maybe pictures "too", since I realize that there are things you can do at the spreadsheet level that wouldn't be possible pictorially. I know some folks (Jay in particular) love to use spreadsheets, but I'm just not good enough to visualize what's happening with just numbers - I want pictures. I've toyed with a binary format, but that means no other tool will ever be able to use the files (text files could at least be converted to another format). The CSV format that seems to be becoming popular has very low self-definition capability. DynoScan uses an XML format that has lots of capability to it, but I have very little visibility into what the viewer can handle - it may be able to do more than I know how to use. I've pretty much got all that now.įor a log format, I want something completely self-defining, and yet low bandwidth. I wanted much higher data performance than I was seeing from existing loggers, and the ability to manipulate the data before it was logged. I wanted to log on an SD card, so I didn't ever have to bring a computer to the car. I improved considerably on the logger itself, but GUI software isn't a strong point for me, so I've stuck with the viewer, which sucks worse every time I use it.įor a logger, I wanted something I could just leave in place, and log every drive automatically. In order to feed the viewer, I built a custom piece of hardware, and wrote some DashDyno-compatible firmware for it. I got it with a borrowed DashDyno, which sucked on its own, and I returned to the lender. I've been using the DynoScan viewer, which comes with DashDyno. Please tell me what you like and don't like, want and don't want. So this thread is to discuss choices available, their strengths and weaknesses, and logging needs from a driver and tuner perspective. If you do use somebody else's format, you're stuck with their viewer, and they seem to suck. And unless you stick to somebody else's format, you have to also write a log viewer. That leads to a choice of log formats, and there are lots of trade-offs to be made there. I've built my own from scratch, because so far I just haven't found one worth having. Car has no other mods.As some of you may know, I've gotten deeper into logging than is probably healthy. I run 91 from shell or chevron in California so could poor fuel quality be a consideration?ĮDIT: Logs are with Stage 1 91 NWG Version 2.00. Is there a risk of damage if I run a HWG map without needing it? I checked the clamps along my intake and they seem snug enough but it's hard to be 100% sure. I'm unsure if it's just not making target boost (in which case should I use a HWG map?) or is there another reason, such as an intake leak (hose clamp issues)? Target boost is supposed to be 15.9, right? I'm hitting 18psi around 3.5k but it tapers off to 12ish psi past 5k. After flashing the new 2.00 maps, I decided to check boost pressure vs RPM to see if I'm actually hitting target boost and I'm now I'm unsure. However, I was feeling like my WRX was down on power but i was attributing that to a more linear throttle response. When I first flashed my maps I was only looking at things like DAM, Feedback/ Knock Corrections and A/F learning and everything seemed fine.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |