From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
08-13-2006 04:59 PM
08-14-2006 01:04 AM
@j_es wrote:
What am I missing.
08-14-2006 06:34 AM
08-14-2006 09:59 AM - edited 08-14-2006 09:59 AM
Message Edited by j_es on 08-14-2006 10:01 AM
08-14-2006 10:38 AM
08-14-2006 11:00 AM
OK, let's back up for a second....
99% of the solution is clearly defining the problem. Why don't you make a tiny example VI with your real input string as default value in a control. (Create a control containing your data, then right-click...data operations...make current value default", then save the VI).
Now include indicators that contain your desired output as defaults. ...and we go from there.
As I mentioned before, your use of "Hexadecimal string to number" is not appropriate here, because your string is not a hexadecimal formatted string, it e.g. contains the hex character x00. A hexadecimal formatted string has two characters for each byte and only the ASCII characters zero to F are allowed.
08-14-2006 04:24 PM - edited 08-14-2006 04:24 PM
Message Edited by j_es on 08-14-2006 04:27 PM
Message Edited by j_es on 08-14-2006 04:28 PM
08-14-2006 04:52 PM - edited 08-14-2006 04:52 PM
Oops. That didntt work either. a-f didnt work.
Heres what works.
Just so I know the lingo.
What was coming in. To me it was just digits represented as hex in labview. Was this consider unicode or somehitng?
Message Edited by j_es on 08-14-2006 05:00 PM
08-14-2006 05:23 PM - edited 08-14-2006 05:23 PM
Message Edited by altenbach on 08-14-2006 03:24 PM
08-15-2006 10:19 AM