Troubleshooting
The things that go wrong most often, and the differences that look like bugs but are not.
My layout is not there
Almost always the wrong account. Layouts are per sign-in. Check the address at the top of the picker: it says Synced to <email>, or This device only when you are signed out or not Pro. Signing in with the other address brings them back.
A histogram says a parameter is missing
The table wants a channel this log does not have, or a math channel that was deleted. The panel offers Choose replacement… with a dropdown per missing slot, so you can point it at a channel from this log without rebuilding the table. If it names a math channel, check it still exists in the Math Channels manager.
A gauge reads N/A
A dashboard built on another car is bound to channels this log does not have. Right-click the gauge: if the role cannot be resolved the menu leads with Not available in this log and offers channels to map it to instead.
Differences that are not bugs
- An HP Tuners channel reads differently than in VCM Scanner. Scanner applies per-channel display units from your tune, so a MAP channel stored in psi can show as inHg there. BigData converts by quantity instead, and always shows US units.
- An .hpl trace looks smoother than you expect. HP Tuners logs are put on an even 25 Hz grid so every channel shares one time base. A channel logged faster is reduced to that.
- A Haltech channel looks like a staircase. Haltech logs different channels at different rates and the export repeats the last value between updates. That is how NSP draws them too.
- SCT measured AFR looks like lambda. Because it is. SCT names the channel AFR but logs lambda, so it is treated as lambda rather than mis-scaled.
- A Holley digital input has the wrong name. Standard Holley channel names come from the firmware layout; your configured analog inputs are read from the log, but some digital input/output names still come from the reference layout. The values are right, the label may not be.
- A Holley .dl and its CSV export start at different times. The .dl is zeroed at its first sample; Holley's CSV keeps the negative pre-trigger time.
Windows blocked the installer
Expected while the app is in beta and not yet signed. Click More info, then Run anyway. See Installing.
It feels slow on a huge log
Graphs draw from a reduced set of points, but histograms bin every sample, so a very long log with several tables takes a moment on each change. Setting Range to Selection so a table only bins what you are zoomed to, disabling tables you are not using, and raising Min Hits all help.
Still stuck
Send the log and a line about what you expected to see. If a log fails to open for a Palm Beach Dyno address it is uploaded automatically and looked at without you doing anything.
This page is part of the manual built into BigData for Windows, where the same topics are available offline with F1.