Convert a Single Number to a 32-bit hex string and swap the high and low bytes

[drb12345]

I need to convert a Single Precision Floating Decimal number to 32-bit hexadecimal form, swap the high and low bytes, and convert that to a hex string.  I have tried using the "Swap Word" function but it doesn't seem to have any affect on the Single number.  

So

Input a Single Decimal # : 100

Convert to 32 bit Hexadecimal String with the low byte first: 0000 42C8

 Any one have any ideas?

Thanks

[altenbach]

Use "flatten to string" and set the byte order to little endian.

[drb12345]

awesome! thanks

[altenbach]

Actually, the above answer is incorrect if you really want the 100 -> 0000 42C8 functionality. You seem to want an unusual conversion.

Try this instead:

(left to right: typecast to U16 array, reverse array, typecast to string)

[drb12345]

Sorry spoke too soon...

That using flatten string with little endian gives me "0000 C842" instead of "0000 42C8"

[drb12345]

Yeah that's what i'm looking for.  I am using Modbus RTU to control a motor controller and it calls for its data in that format.

[altenbach · Accepted solution]

Slighly more lightweight, try casting to U32 and swap the words. Same difference. 😉

(apparently, swap words is a NOOP for SGL, but still accepts SGL without coercion dot. Interesting...)

[altenbach]

You should unmark message 2 and instead mark message 4 or 7 as solution. Thanks!

[altenbach]

---

@altenbach wrote:

(apparently, swap words is a NOOP for SGL, but still accepts SGL without coercion dot. Interesting...)

---

I have the feeling that the current behavior of swap words is incorrect for SGL inputs. I created an note in the monthly bug thread. Any comments are welcome.

[Darin.K]

---

@altenbach wrote:

---

@altenbach wrote:

(apparently, swap words is a NOOP for SGL, but still accepts SGL without coercion dot. Interesting...)

---

I have the feeling that the current behavior of swap words is incorrect for SGL inputs. I created an note in the monthly bug thread. Any comments are welcome.

---

My guess is that this is somewhat intended behavior.  You are able to wire a cluster with multiple data types and it will swap bytes/words on integers and leave the others alone.  Not that I have ever thought about doing this....

still seems a bit strange.

Detailed Help: data is an integer, an array of integers, or a cluster containing integers that you want to byte swap. If data is a cluster that contains integers, this function swaps only the integer elements of the cluster.