LabVIEW
Nibble to Hex
This is an unusual request. Tell us the reason why; I have a feeling you don't have to do this.
Limit your integer to 4bits and set the display format to %x.
You are not talking about datatypes, so if the input is a decimal string containing numbers 0..9, and the number is less than 0 through 15 and you want to convert it to a string containing two characters in the range 0 through F, that would be equally easy.
You can use an 8-bit enum and populate items 0-15 (even if the names are just "0" through "15") to make it pretty idiot-proof to enter invalid values. Then it's just a matter of changing it into an array of Booleans and take the first four elements.
@altenbach wrote:
Limit your integer to 4bits and set the display format to %x.
You are not talking about datatypes, so if the input is a decimal string containing numbers 0..9, and the number is less than 0 through 15 and you want to convert it to a string containing two characters in the range 0 through F, that would be equally easy.
Oh, I didn't think to interpret it this way. Thanks for catching that. But how do you limit your integer to 4 bits?
And if Life give you an unsigned Byte, here's how to get two Nibbles (hey, I just got the pun ...):
Bob Schor
@billko wrote:
But how do you limit your integer to 4 bits?
If it is an integer control, you can play with the "data entry" feature and restrict the allowed range. If the value comes from wlsewhere you need to decide what to do if the value is out of range (pop an error, ignore the extra bits, etc.)
Here's how you could blank all extra bits:
@manas0911 wrote:
I just want nibble hex conversion. Like 12 should give me output as 'C' and not '0C'.
Don't confuse "conversion" with display "formatting". The only reason to always see "0C" instead of "C" is if this is a string set to hex display. If you use any plain string or numeric you can freely format it as anything you want.
(Note that the mask guarantees that the value is limited to a single hex character and is not needed if the input is guaranteed to be limited to a nibble)
@altenbach wrote:
@billko wrote:
But how do you limit your integer to 4 bits?If it is an integer control, you can play with the "data entry" feature and restrict the allowed range. If the value comes from wlsewhere you need to decide what to do if the value is out of range (pop an error, ignore the extra bits, etc.)
Here's how you could blank all extra bits:
Oh, I thought there was some kind of magic involved. I see you were actually talking about how to limit an 8-bit number to "care" about just the lower nibble. 😄
