Computing > Programming

Programming help - Bitfields in windows (64b) environment with .NET?

(1/2) > >>

I'm writing a little program grab some data off a CAN bus, using the popular Peak CanUsb dongles, for which they supply a suitable Windows API.  So far so good, no issues, i'm getting data when i should. 

For people who aren't CAN experts (basic) CAN has an 8 byte (64bit) payload, and individual parameters can be encoded by the bus architect into those bytes.  For example, on a car, you might have the engine ecu sending the engine speed to the dash board to display to the driver, and engine speed might be encoded with a scaling of 1, and offset of zero, and a width of 16bits, and those two bytes might say be located in the 1st and 2nd byte of the CAN message.

Ie, the 8 bytes look like this (where X is don't care)


Here, we take 19, multiply it by 256 (4864) and add 136, for a total of 5000, ie "5000 rpm" for example

So that's an easy one, because to decode the data from the message payload you just grab the first two bytes, multiply the most significant byte by 2^8 and add it to the least significant byte and it's job done (ignoring the issues surrounds motorola and intel encodings for now....).

But, what if i want to decode values that don't fall on nice byte boundaries. Say a parameter was a 3 bit value (0 to 7), encoded into say the 23 to the 25th bit of the message bytes? It would start in the last two bits of the 3rd Byte, and finish on the 1st bit of the 4th byte.

 In an embedded scenario id have no problem in doing some basic bit shifting and some bit masking or use some bitfield unions to pull out just the bits i'm interested in, but how do i do that in a windows environment?

I'm coding in visual studio, with .NET mostly in a visual basic forms style.

Whats the best way of approaching bitwise operations in a 64b native high level environment?  Anyone have experience or ideas?   :-+

You could just use a 8 byte array or 2 32bit variables.
You can use AND and OR bitwise operations to determine the state of a bit inside a byte.


You can read the individual bits and then add them to a variable by using shift left...

byte bit_value = [get bit n from byte] 0 or 1
byte result = result <<1 + bit_value    (shift bits in result one bit to the left, then put 0 or 1 on the last bit)

One thing i need to be a bit (sic) careful with, is that although CAN 2.0b is a maximum of 8 bytes, and hence could be handled directly in a 64b environment, things like CanFD, which i don't (yet) have to accommodate, have up to 64 bytes of payload, so are outside the direct handling / conversion.

Looking at BitArrays ( ) which turn an array of bytes into an array of bits, stored as booleans, and can handle arbitrary lengths, could be an option.  I could effective convert the whole data byte array into a bit array, then reference each bit as the index of the bitarray, pull out the number of bits i need to look at, and use that boolean info to set the bits in another parameter. That also gives me a way of handling the motorola/intel formatting, because say my data sits between the 23 and 25th bits, i can simply start at the right end and work forwards or backwards through the array?

Should be reasonably fast, as well, as i will have to decode these messages at a reasonable rate (bus baud rate is a max of 1Mb, average data rate could be say 500 700kbs)

There is the BitConverter class that converts arrays of bytes to built-in types.  Beware of the endian-ness, which is fixed to the local machine architecture.

Sam Hobbs:
If it were me I would define structures (structs) for each format. You can do bitwise copies of the data from your buffer to the specific structure or perhaps read directly into the relevant structure. I have done that type of thing in C++ but I could figure out how to do it using C# if I needed to. The thing is that you might get resistance from other programmers; your C++ programmers are not familiar with such techniques that were common when C++ (so before C#) was first designed. I think that C# structures are defined (have limitations) to make that type of thing possible.


[0] Message Index

[#] Next page

There was an error while thanking
Go to full version