Quantcast
Channel: All LabVIEW posts
Viewing all articles
Browse latest Browse all 203191

Re: Labview + xbee read sensor, uncoding the hex string

$
0
0

Hey John :)

thanks for all the information, and yes you are correct about everything, took the last hours to recheck the last 2 bytes
As for the xbees, for now i'm only using 2, but the final project requires like 11 xbees so i will been the coordinator to be API to have organization, but i will only read one xbee at a time

or i must find a way to read the each one and manage to monotorize everything

 

for example, just speaking about temperature reading

if i have 2 or more xbees label as router AT, i know that each one sends a diferente string, but all will start with 7E, and have the 2 bytes indicating the lenght of the string, i think it will also there is a byte to identify the router that it comes from.

Thats why i wanted to learn how to extract information from the string, if i can extract temperature values (like i already manage to do thanks to you guys) then all i have to do is find the byte to identity the router, then associat his information to a termometer for example (thinking about 11 termometers displays)

but yes, your information is useful, you guys are really great with me, thanks again :) you are saving my life

you also said "In your message, the carriage return and the new line are actually part of the message you are sending from the remote device and not the end of message delimiter" but no, from arduino (my device connected to the xbee router as MCU) is displaying only the values of temperature and a \n, nothing more. is that it?

 

 

 

 


Viewing all articles
Browse latest Browse all 203191

Trending Articles