Highlight cells in Scal tables

[ZekeO]

IT would be good to be able to highlight cells in the Scal tables in certain colours.

I think this would be helpful when tuning and also going between different tables but monitoring load/rpm/ key points.

[stevieturbo]

Toggle delta hotspots sort of does this for changes made.

But a tracer over the table like other ecu's would be nice too when doing quick lookbacks.

[ZekeO]

It would also be immensely great to be able to export and load tables. Currently, the whole calibration file must be loaded and saved.

[stevieturbo]

export where or do what ?

[ZekeO]

Say you have a fuel base table 1 and want to copy that exact table 2, 3, 4?
OR
You have a base file with a pleathora of changes but want to go back to a certain base timing table.

I imagine it could be implemented as so:

File or PasteCal > Export table > save as csv or text.
Then
File or PasteCall > Import table > csv or text

[stevieturbo]

If you simply want to copy an entire table, bog standard copy n paste of all the values works.

[ZekeO]

That's good for "in-session" copy/paste.

The ability to revert to a table from a point in time without reloading the whole calibration .

[stevieturbo]

That's good for "in-session" copy/paste.

The ability to revert to a table from a point in time without reloading the whole calibration .

I don't think any ecu anywhere offers such a feature ?....most have no notion of time at all.

[RICE RACING]

That's good for "in-session" copy/paste.

The ability to revert to a table from a point in time without reloading the whole calibration .

This already exists and is simple to do.
Pastecal load (the last version *with your cal notes*)
Then if you molest any given table, simply import back the prior saved cal table to your point in time where that table was correct.

Doing an arbitrary relative in time line points is well just that, the idea once anyone does hundreds of these dare I say thousands of calibration updates is documentation of the changes you do, if they are significant to justify an incremental nomenclature ratchet up then it should be documented and as such its a saved cal version, any nominal or incremental steps on dyno or road in real time will as Stevie says be there when hotspots are displayed, and if its going the wrong way and you want to start again with a validated prior version then you refer to your last saved. Simply importing this map assuming its not restricted (there is only a few of us who work with different ID's) then is really simple and the system works great.

For anyone interested I can show them how I do it if this helps? Its not uncommon to have 'hundreds' of calibrations over the development cycle of a customers car and being able to quickly and easily do what you have asked above is not only important but it is there and ready for you to use.

Maybe the picture below will help rather than words

example RR.jpg (627.28 KiB) Viewed 27353 times

[RICE RACING]

Further to above which I forgot to mention, if you are in say a fuel table and you have done 20 changes, I just tested this (could not be stuffed to try more than that lol) and typing E the U short for edit undo you can unwind these changes until all those hotspots are gone, not sure how many you can do but if its more than 20 then you are maybe in trouble and should start again (paste cal import that map)