Bug in the cropping, which I think has been there since the cropping tool was revised. If you have some noise etc you want to smooth, then smooth function always uses the first place you started cropping.

So if i smooth 4000-4200 rpm that's fine.  But then if i try and do 4200-4300 it instead draws a straight line from 4000-4300.

Regarding the cropping tool, I cannot get the undo function to work.

I liked it better when it was a box rather than a vertical line on the x axis 

Awesome work on the upgrade! Love the data setup. Makes searching runs so much easier now. 

I have an issue where the roller size isn’t staying updated. Seems to default back to 100cm. 

also the after a run is manually stopped (although haven’t checked in auto mode) the brake doesn’t seem to apply to slow down untill near the 1000 rpm zone. 

I there a way to import all the original Dyno setup files to UnaVision? So retarder settings and calibration data etc copy across from old to new? 

thanks again 🙂 

@bendd regarding cropping. You cannot undo a crop on imported runs by right clicking, because of the file format. However, crops are not stored either, so just unload the run and read it again ang it will be back to how it was. 

For runs in UnaVision you can crop and uncrop.

The best is to crop in Results vs Time. All tabs are updated if you do crop in one. Crops in Results vs RPM is sometimes not possible, for example when RPM goes up then goes down again.

@trevor-briggs on the options import: Yes, on the old YourDyno program, do an Options->Backup options to file, and in UnaVision do a Options->Dyno types and profiles->Restore options from file

On the roller size, this is stored when you exit YourDyno. It can be overwritten if you load some new settings file or default settings, but otherwise shall not change. Contact me on jostein@yourdyno.com if yours continue to change for no reason, I would like to login and check your setup. 

I just checked the brake after run and it works correctly here. You can mail me your config file and I can check it

Thanks Jostein I will import the original settings from yourdyno into UnaVision first. Then see if it still acts weird or if it’s some setting I’ve forgotten! 

Just one more, my AFR doesn’t seem to update on my run screen, it’s setup and shows on my on my analogue channel 1 but when selected on the run screen the PID doesn’t show any data. 

I’ll update everything first and restore the settings and see if it’s still not updating. 

🙂 

@trevor-briggs I had this too but after a few times it worked. I was trying to put circumference (173cm) but only after I bit I realized I had to put diameter and it would store then the circumference in the config file. You cannot enter a value over 100 cm but mine are 55 cm and that worked fine.

Hi Jostein,

I tried the cropping in results vs time and the problem is still there.  No matter how many crops you do, you just get a straight line from the first point you originally cropped from to where you finally cropped.

Example, the power curve is nice and rounded, apart from a noise spike at 5000rpm, then another at 6000rpm.  If you smooth out the spike at 5000rpm to 5100, then try and smooth out a spike from 6000 to 6100rpm, you just end up with an artificially straight line from 5000 to 6100 the data between 5100 and 6000rpm is lost.

@dev I just tested what you described and cannot reproduce the problem. I can login to your PC and see if I understand what you mean. Contact me directly on +47 4840 1279 or mail

Folks,

UnaVision 4.0.36 was just released (Beta). 

A few fixes:

• Channel averaging was always turned on for all channels, even though only Power and Torque were selected. This caused loading run from the database to be slow on slow computers/long runs
• If something was wrong in the CAN output channel definition, then you could not start a new run (without any error message). Now wrongly configured CAN out channels are ignored
• RPM3-4 and Freq1-2 were not behaving correctly in some cases on Firmware 3.20 and 4.20, therefore a new 3.21/4.21 is a mandatory update. In practice it works with 3.19/4.19 too, but you will get a flashing "Update firmware" message until you click Update to latest
• Fix of Brake Specific Fuel Consumption plugin when using flow units other than gal/hr (for example liters/h). 

More improvements are underway based on your feedback 🙂