LabVIEW
how to divide binary string in two binary strings.
Solved!
@altenbach wrote:
@billko wrote:
But it does (at least somewhat) fit onto a postage stamp, so there's that...What is the plural of "it"? 😄
... and if we wrap it into a inlined subVI, it's even smaller. 😄
It is all off topic though:
Re: how to divide binary string in two binary strings.
Although obviously that question might not be the right one.
Search LabVIEW like a graph!
wiebe@CARYA wrote:
Re: how to divide binary string in two binary strings.
Although obviously that question might not be the right one.
Well, but the string is 8 bytes, not 8 bits..... (If each byte represents one formatted bit, then its not a "binary string", but a "binary formatted string". Big difference, i.e. eight-fold! Also "split" is probably a better word that "divide", else we end up with Gerd's code again. 😮 Going in logical circles.... 😄 ).
@User002 wrote:i converted decimal numbers which are from 0 to 200 into the binary string of 8 bits. now i want to divide it in two equal part first 4 bits and other 4 bits. the Vi is attached.
@altenbach wrote:
Well, but the string is 8 bytes, not 8 bits..... (If each byte represents one formatted bit, then its not a "binary string", but a "binary formatted string".
I get into this argument quite a bit when people say a "hex string". Are we talking about an ASCII formatted text with hexadecimal characters (what I refer to as "ASCII Hex")? Or are we talking about the raw data value that just happens to have a string data format (what I often refer to as hex/binary/raw)? This is why examples are so important so we know exactly what "language" we are talking about.
In this case, the OP actually gave us an example of what was desired. So I could quickly determine they had an "ASCII Binary" format. Easy enough to deal from there. Whether or not it is a smart format is not my concern. That is up to the OP and/or whatever it is they are trying to talk to. A command-line interface is a perfectly rational reason to use this format, which I have done before.
@crossrulz wrote:
@altenbach wrote:
Well, but the string is 8 bytes, not 8 bits..... (If each byte represents one formatted bit, then its not a "binary string", but a "binary formatted string".I get into this argument quite a bit when people say a "hex string". Are we talking about an ASCII formatted text with hexadecimal characters (what I refer to as "ASCII Hex")? Or are we talking about the raw data value that just happens to have a string data format (what I often refer to as hex/binary/raw)? This is why examples are so important so we know exactly what "language" we are talking about.
In this case, the OP actually gave us an example of what was desired. So I could quickly determine they had an "ASCII Binary" format. Easy enough to deal from there. Whether or not it is a smart format is not my concern. That is up to the OP and/or whatever it is they are trying to talk to. A command-line interface is a perfectly rational reason to use this format, which I have done before.
Is there a standard (ISO? NEN?) for that? Perhaps there should be...
