Updated help files for several screens.

This commit is contained in:
Collin Kidder
2023-02-13 22:02:47 -05:00
parent ba2d3c221f
commit 5ef8403d40
9 changed files with 97 additions and 46 deletions
+4 -2
View File
@@ -6,9 +6,11 @@ DBC Signal Editor
Defining and Editing Signals
============================
On the right side you can rename the signal and you'll see that it is renamed in the DBC window as well.
At the top you can rename the signal and you'll see that it is renamed in the DBC window as well.
"Bit Length" - This sets how many bits the signal uses. Once you do this you'll see that that many bits are now highlighted in the 8x8 data grid above. The black bit is the "start" bit, green bits are the other bits in the signal. Gray bits are already used by another signal. You can still use them for the current signal too but doing so would be quite unusual unless you have multiplexed signals.
The majority of the view is taken up by the bitfield grid. This view shows all the signals contained within this message (that have the same multiplexor value as this one). They're all labeled as well. Bonus fun fact - SavvyCAN technically does support CAN-FD DBC files! That's right, you can load DBC files with CAN-FD signals and they will work. Now, you might wonder how this could work since the grid is 8x8. Well, it won't be if the message you're working on says it has more than 8 data bytes. Up to 64 are supported and the bitfield will adjust accordingly. If you want to see that beautiful 64 byte footage without a CAN-FD signal then try middle clicking on the bitfield. This actually works basically anywhere the bitfield is found in the program. You heard it here first.
"Bit Length" - This sets how many bits the signal uses. Once you do this you'll see that that many bits are now highlighted in the data grid. The black bit with diagonal stripes is the "start" bit, green bits (with stripes the other way) are the other bits in the signal. Bits used by other signals are colored according to a secret list of colors. They also have the signal name. You should not overlap onto other signals. This could be possible with multiplexed signals but you will NOT see signals on this grid that are not part of the same multiplexor value as this signal so you should NOT overlap here.
"Byte Order" - The way that the green bits are filled out is changed by this checkbox. Checking it selects little endian mode whereas deselecting chooses big endian mode. This will have an effect on any signal that crosses byte boundaries. The simplest explanation is that little endian signals start at the start bit and then go "down" in bit numbers while big endian mode goes "up."