Datalogging fields can't be removed?

For discussion of Phil Tobin's Tuner Studio software (Only about the tuning software itself, not about how to tune or firmware features)

Moderator: LT401Vette

Post Reply
krisr
Master MS/Extra'er
Posts: 799
Joined: Wed Aug 17, 2005 1:17 am
Location: Sydney, Australia

Datalogging fields can't be removed?

Post by krisr »

I'm trying set fields for SD Card datalogging and it looks like some fields are tied together? I.e. fuel pressure? Is that normal and does it takes up space on the SD Card? If it does, is there a way to "uncouple" these fields as I don't think people really need all variants for example log fuel pressure in bar/psi/kpa...

What bought this to my attention was, I'm trying to also log the "trip meter" so I can overlay drag strip runs and know exactly where to overlay the runs the minute the tyre turns and stop @ 1320ft and alot of the fields I log help, except for fuel pressure as mentioned.

Kris
Sydney, Australia
1971 Holden Monaro HQ
MS3X Sequentially fuelled 400 Pontiac
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Datalogging fields can't be removed?

Post by LT401Vette »

Each Data log Field is based on an OutputChannel.
There are 2 types of Outputchannels

1. Controller Channels - values contained in the runtime data stream received from the controller.
2. Expression based Channels - new channels based on any other channels or Constant using mathematical operations and TunerStudio functions.

Type 1 are primarily used by Firmware developers as they are read directly from the controller, type 2 are created by combining or altering type 1 in mathematical expressions, they can be added to the ini file by firmware developers or be user extensions.

TunerStudio can only really tell the controller to log what it know, and at the time of transformation into a normal data log really only know what type 1 fields were selected. So, if you add a Type 2 field, it will actually add all the dependent channels. Or if you have all the fields needed to create a type 2, that will automatically come along for the ride.

Then when it displays what is going to be logged, it will display all the fields that it can and will recreate when the raw SD data is transformed into a normal data log.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
krisr
Master MS/Extra'er
Posts: 799
Joined: Wed Aug 17, 2005 1:17 am
Location: Sydney, Australia

Re: Datalogging fields can't be removed?

Post by krisr »

So just to clarify, all the channels that 'come along for the ride' don't take up room on the SD card? If so that's sweet. I'll try and make my sd card logging more optimised and drop absolutely non critical fields.
Sydney, Australia
1971 Holden Monaro HQ
MS3X Sequentially fuelled 400 Pontiac
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Datalogging fields can't be removed?

Post by LT401Vette »

krisr wrote:So just to clarify, all the channels that 'come along for the ride' don't take up room on the SD card? If so that's sweet. I'll try and make my sd card logging more optimised and drop absolutely non critical fields.
Exactly.

If you look under the "Available Datalog Fields" list, each time you click on a selection, it will display 1 or more output channels it is dependent on. Those will be only type 1 fields and are displayed there. Those are the driving factor.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
Post Reply