Q&A Forum
Over time I've been reading in the forum that the data provided by YourDyno software are in .csv format. However, in UnaVision this seems to have disappeared in favor of a database format.
It is EXTREMELY important for me being able to have individual runs in .csv as I can very easily upload them into EFI Analytics MegaLogViewer HD, upload them in the table generator, do the adjustments according to AFRs and reflash the ECU.
This makes my tuning a very straightforward process that really helps when no live data collect software are avaliable for certain ECUs (Quite a lot in my case)
If there's a way I have not seen in UnaVision, please, let me know.
Hi,
You can create a results table with the channels you are interested in and the master channel of your choice (Time or Engine RPM typically), and adjust the interval (for example 0.1 seconds or every 100 RPM). This way you can define exactly what you want to export.
To export you can copy the table (Ctrl-A and Ctrl-C) or right click and select Copy to Excel.
I expect you can import to MegaLogViewer by just pasting the data? I think anyway it is a good idea to also be able to export to csv. I will add this. In the meantime, if MegaLogViewer does not handle copy/paste like that, then use any spreadsheet tool (Excel, Google sheets, etc) to create it from the Paste.
Thank you very much for the fast answer on Saturday!
I'm starting my learning on UnaVision and, on the worst case scenario, I can use my Zeitronix datalogger which has work fine in the past although is a simpler tool.
But, of course, I prefer to do everything on YourDyno as it is a great system.
Because of the low speed CAN line on this first test bike (Ducati 1098), I'm using the RPM pickup for revs and the Analog3 input for TPS. With a bit of playing side by side with my Texa diagnostic tool (TPS displayed in degrees) and UnaVision I've managed to match the values exactly.
This is why it would be so important. I can do a full TPS/rpm log, import it to MegaLogViewer HD, do the changes accordingly and reflash. Looping the process a couple of times is fast, easy and makes very happy guys out of my customers.
The data collected from the Zeitronix logger is not as precise as the TPS reads in % (not a big issue) but drifts a bit in the long run required to sweep all the Alfa/n tables (not ideal)
Please, keep in mind that my dyno and tuning knowledge and experience are 100% self-taught.
The way I work comes just from my own ideas about how things should work. Until now they have proven successful, but it's just my way and it might sound slow, awkward and eve inadequate for the expert dyno operators out there.
I've got this workflow from how my favourite system (Woolwich Racing) works and I've just tried to 'automate' datalogging as much as possible to apply their method to other ECUs not supported by them.
Si, if something of all this sounds silly to someone, it probably is!
THANK YOU for your help!!!
The solution you have provided has worked just perfectly!!!
The master channel must be TIME so that TPS vs RPM AFR data don't overlap. Interval 0.1 seconds, then copy and paste info excel and save as CSV. Nothing else neede to open in MegaLogViewer. Clean-up of the data with the help of the log plot and perfect result.
The sample I attach covers just a section of the map as the run ended unexpectdly, I guess I have some auto-stop feature activated.
GREAT TOOL and BETTER SUPPORT. Thumbs up for making my saturday at the workshop sooooo rewarding!!!!