t.mettler/giesCANne
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

A large update to the help files. The reference pictures have been

Browse Source 
updated and several of the help files have been updated. This process
is not done yet.
This commit is contained in:
Collin Kidder
2021-08-19 21:30:54 -04:00
parent d8f2c2d0e3
commit 20f7217ad3
30 changed files with 143 additions and 98 deletions
Download Patch File Download Diff File Expand all files Collapse all files
help/temporalwindow.md
+5
View File
@@ -18,3 +18,8 @@ bright streaks in the background color). There isn't a lot that can be done to m
zooming and panning the view. If you get the view too messed up the R key will reset the view back to standard. As with the Graphing Window, it is
possible to select just the X or Y axis and zoom/pan that axis without affecting the other one. To do so, click on the axis marks of the axis you'd like
to independently control. To control both again click in the graph itself.
So, what is it good for?
========================
The idea here is to find areas of high traffic so that you can investigate those areas. Chances are, things that are sent rapidly are important. Steering data is usually sent rapidly, low level engine performance data is usually sent rapidly. These things can change rapidly and are safety critical so they tend to have a high rate of transmission. This window can also show where "clusters" of IDs are. Sometimes a given device will send long form data over a range of ideas, say, 0x102, 0x103, 0x104. These clusters could be visible on the temporal graph. A reasonable rule of thumb is that the "busy" areas of the temporal graph are probably important. The question is, for what? This window thus takes a supporting role and other windows would help answer the question of "why is there so much traffic there?"