Difference between revisions of "System Testing"
Jump to navigation
Jump to search
(Created page with "Trust, but verify ==Chassis Dynamometer== ==Test Procedures== ==System Data and Data Collection== Category:Internal Combustion Category:Data Acquisition") |
SpookySimon (talk | contribs) (added note to add orthogonal array later) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Trust, but verify | Trust, but verify | ||
| − | + | To add: | |
| − | == | + | Orthogonal array |
| − | == | + | =Chassis Dynamometer= |
| − | [[Category:Internal Combustion]] [[Category:Data Acquisition]] | + | used to tune [[Engine control|engine control]] |
| + | |||
| + | =Test Procedures= | ||
| + | |||
| + | =System Data and Data Collection= | ||
| + | ==Data to collect== | ||
| + | ===Safety Critical Data=== | ||
| + | This is needed to make sure the driver and engine is safe and can operate reliably. These should all come stock on a motorbike engine and can easily be adapted for a DAQ system. | ||
| + | * Oil temp | ||
| + | * Oil pressure | ||
| + | * Coolant temp | ||
| + | ===Basic vehicle data to collect for analysis=== | ||
| + | '''Time''' | ||
| + | * Used to correlate all data collected | ||
| + | * Automatically tracked by most off the shelf DAQ systems | ||
| + | '''GPS Tracked Distance''' | ||
| + | * Useful for general review of test day | ||
| + | * Not always needed but collected by most off the shelf DAQ systems | ||
| + | '''Longitudinal acceleration''' | ||
| + | * Most off the shelf DAQ systems will track this, often by GPS | ||
| + | * More accurate data can be collected with accelerometers | ||
| + | * Needed for g-g Diagram | ||
| + | * One of the most important values being tracked when tuning | ||
| + | * Almost always: higher average is better (except when it sacrifices lap time or competition score... or safety) | ||
| + | '''Ambient weather temp and humidity''' | ||
| + | * Used to control for varying test results across different days or changes in conditions | ||
| + | '''Track Conditions''' | ||
| + | * Used to control for varying test results | ||
| + | '''Vehicle Speed''' | ||
| + | * Often GPS Tracked by off the shelf DAQ systems | ||
| + | * Can be derived by undriven wheel speed sensors (industry standard) | ||
| + | * Higher average speed = better | ||
| + | '''Lap time''' | ||
| + | * Can be collected by stop watch or phone timer | ||
| + | * Most important, simplest data to drive engineering decisions, but also often hard to decipher without other data such as acceleration, driver input, etc. | ||
| + | * Only useful if a consistent track is driven multiple times and with variable(s) changed | ||
| + | ===Powertrain basic specific data necessary to collect=== | ||
| + | '''Engine RPM''' | ||
| + | * Collected by stock engine speed sensor | ||
| + | * Vroom vroom | ||
| + | '''TPS''' | ||
| + | * Needed for engine to run (if alpha-n tuned) | ||
| + | * used to look at driver input | ||
| + | '''Coolant temp delta of radiator''' | ||
| + | * just two thermocouples | ||
| + | * used to show radiator efficacy | ||
| + | ===Data used for finer tuning and correlating with simulations=== | ||
| + | * MAP | ||
| + | * IAT | ||
| + | * APPS | ||
| + | ===Not powertrain data but good to collect=== | ||
| + | * Suspension Travel | ||
| + | * Lateral acceleration | ||
| + | * Tire temperature | ||
| + | * Wheel Speed | ||
| + | * Brake Pressure | ||
| + | * Air speed/pressure for aero | ||
| + | ==What to do with the data== | ||
| + | * TPS v RPM Map (with speed) | ||
| + | used to show where the engine is being operated during a test drive. This only makes sense for analyzing an auto-cross style event with varied expected engine operating conditions. Can be used to show differences between drivers. | ||
| + | |||
| + | This should be a heat map or other 3d data visualization. | ||
| + | |||
| + | * TPS v time map | ||
| + | Used to justify open loop or closed loop engine control. Used to show driver input in easily understandable way. | ||
| + | |||
| + | * TPS v MAP | ||
| + | should be correlated | ||
| + | |||
| + | [[Category:Internal Combustion]] | ||
| + | [[Category:Data Acquisition]] | ||
Latest revision as of 15:10, 17 May 2022
Trust, but verify To add: Orthogonal array
Chassis Dynamometer
used to tune engine control
Test Procedures
System Data and Data Collection
Data to collect
Safety Critical Data
This is needed to make sure the driver and engine is safe and can operate reliably. These should all come stock on a motorbike engine and can easily be adapted for a DAQ system.
- Oil temp
- Oil pressure
- Coolant temp
Basic vehicle data to collect for analysis
Time
- Used to correlate all data collected
- Automatically tracked by most off the shelf DAQ systems
GPS Tracked Distance
- Useful for general review of test day
- Not always needed but collected by most off the shelf DAQ systems
Longitudinal acceleration
- Most off the shelf DAQ systems will track this, often by GPS
- More accurate data can be collected with accelerometers
- Needed for g-g Diagram
- One of the most important values being tracked when tuning
- Almost always: higher average is better (except when it sacrifices lap time or competition score... or safety)
Ambient weather temp and humidity
- Used to control for varying test results across different days or changes in conditions
Track Conditions
- Used to control for varying test results
Vehicle Speed
- Often GPS Tracked by off the shelf DAQ systems
- Can be derived by undriven wheel speed sensors (industry standard)
- Higher average speed = better
Lap time
- Can be collected by stop watch or phone timer
- Most important, simplest data to drive engineering decisions, but also often hard to decipher without other data such as acceleration, driver input, etc.
- Only useful if a consistent track is driven multiple times and with variable(s) changed
Powertrain basic specific data necessary to collect
Engine RPM
- Collected by stock engine speed sensor
- Vroom vroom
TPS
- Needed for engine to run (if alpha-n tuned)
- used to look at driver input
Coolant temp delta of radiator
- just two thermocouples
- used to show radiator efficacy
Data used for finer tuning and correlating with simulations
- MAP
- IAT
- APPS
Not powertrain data but good to collect
- Suspension Travel
- Lateral acceleration
- Tire temperature
- Wheel Speed
- Brake Pressure
- Air speed/pressure for aero
What to do with the data
- TPS v RPM Map (with speed)
used to show where the engine is being operated during a test drive. This only makes sense for analyzing an auto-cross style event with varied expected engine operating conditions. Can be used to show differences between drivers.
This should be a heat map or other 3d data visualization.
- TPS v time map
Used to justify open loop or closed loop engine control. Used to show driver input in easily understandable way.
- TPS v MAP
should be correlated
