Help: why is the output is different than input?

RE: Help: why is the output is different than input?

bjorn-spockeli — Mon, 11 Apr 2016 12:07:41 GMT

As @rols(RK) and @awneil has pointed out, there is nothing to fix since MCP just displays raw bytes. It is up to the application to interpret the data that is received over the BLE link.

-Bjørn

RE: Help: why is the output is different than input?

FormerMember — Sat, 09 Apr 2016 15:34:29 GMT

R K, you said that the value i transfer is little endian, what if i transfer it as big endian. Will it be store in opposite memory address? If so, how could i do it? Thanks for your help!

RE: Help: why is the output is different than input?

awneil — Sat, 09 Apr 2016 14:55:44 GMT

As RK says, all the MCP knows is raw bytes - it has no idea what interpretation you might want to put on those bytes.

RE: Help: why is the output is different than input?

RK — Sat, 09 Apr 2016 14:03:53 GMT

I have no clue - I've never used the Master Control Panel so I have no idea what functions it has and what data types it can display. I use Lightblue usually and in that you can tell it you have 16 bit little endian data and it shows it as a number. Perhaps if you add the data type characteristic for that data the MCP will display it in that format, and perhaps it won't.

But honestly this is just like looking at data with a debugger, you see bytes because that's how the data actually is represented. The MCP always seemed to me to be the equivalent of a debugger for bluetooth.

RE: Help: why is the output is different than input?

FormerMember — Sat, 09 Apr 2016 13:58:59 GMT

Thanks for your response. But it look very messy which it don't look like it's the 16 bit data. Is there any way to get this to show what its input show as?

RE: Help: why is the output is different than input?

RK — Sat, 09 Apr 2016 11:13:33 GMT

The value is transferred little-endian, the MCP just shows the bytes in order they arrive. Nothing needs swapping, it's fine the way it is. The MCP is just a viewer of data, if you have an actual application on the other side reading the data it would know the two bytes are little-endian and interpret them correctly.

You've tried all day to fix a problem you don't have.