Update: Kvaser has released the updated Kvaser Memorator Light HS v2. For more information, click here.
In-vehicle data logging has a role to play throughout the development process – from development to after-market/service scenarios. Whether you need to analyse performance data during ECU development or investigate intermittent faults caused by individual components when the vehicle is in use, placing a data logger on the vehicle’s electronic network for an extended period and evaluating the results is considered best practice.
It is tempting to think that ‘bigger is better’ when it comes to the memory capacity of data logging devices. After all, when the automotive industry talks about data these days, it is generally in the context of RAID systems capable of holding terabytes of data. This is relevant in autonomous vehicle scenarios, when testing multi-radar, multi-video ADAS systems. But this is overkill for most data logging tasks. The question to ask is: just how much relevant data do I want to collect and process? Wherever your task features on the megabits to terabits scale, there are ways to refine the data gathered. This will save you from a cumbersome and expensive data block (literally) which costs you in storage, transfer speed, and analysis time.