Ahh! I see! Well, that removes the danger of missinterpretation at the
cost of increased bandwidth as you say.
Sampling only a couple of times a second means that the bandwidth wont
be a problem in and of itself, however, we are running the PIC
controller on at a very low clock rate (32.kHz) and t
Dargar <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> Hu. Interesting.
> The biggest disadvantage I can see with this is that it feels more
> complex. I'm in the process of learning and I feel like it is easier
> to "understand" what I'm doing if I use a measure-identifier.
Hu. Interesting.
The biggest disadvantage I can see with this is that it feels more
complex. I'm in the process of learning and I feel like it is easier
to "understand" what I'm doing if I use a measure-identifier.
I see that having a certain telegram format where the second data is,
say, T2,
>
> The nano satellite will "talk" on RS-232 9600 baud and since I'm
> programming the PIC MCU I can make up my own protocol.
>
> I'm thinking something like:
> Groundstation sends this: ?Temperature1
> And the satellite then replies: !Temperature1[Data]EndofData
>
> I will have 10 different pro
Thank you Brian Powell!
Together with Greg McKaskle you have provided tremendous help. I have
figured out the star system thing, and have upgraded you both to four
stars since all your replies taken into consideration makes it a four
star from my point of view, even if you hadn't managed to get
"s
You cant edit messages? Oh well.
I forgot to answer your question Brian and the answer is 10 bits of
data/request, so by having at least 3 characters, the data can never
be equal to the header or footer. :)
To save on bandwidth I will probably cut it down to 3 characters for
the final implementat
Before I forget to ask, will you just be reading back individual
values, or will you get several values for any probes? I.e., will you
ever get something like this...
!Temp1987654321EndOfData
(where "98" is the first point of 16-bits, "76" the next, etc.) or
will it always just be a single point
I'm sorry Brian, but the "rate this answer" doesn't show on your
latest reply?
As for the query thing, you're right, it doesn't make sense to be able
to do both I guess. So either I'll have the computer request each data
by sending "?Temp1" requests and listen for the replies, or else I
will h
So it sounds like you want to send back a sequence of two-byte binary
data samples. Thus, you'll use the Type Cast function.
(When I talked about ASCII, I meant that encoded the value "142" as
three ASCII characters, '1', '4' and '2'. It sounds like you are not
going to encode your data this way
Hi Brian and thanks for your feedback.
A few comments:
I'm "tagging" the data, because I want to be able to sample and send
in a loop from the satellite side, without querying for the data. But
I also want to be able to query specifically for data manually. I
don't know what I will end up doing i
Regarding your string parsing...
Maybe I don't understand your protocol, but it looks to me like it's
just a simple query/response protocol. So I'm not sure what you mean
when you talk about a continuous stream of data.
It seems like you'd just send "?Temperature1\n" and immediately do a
VISA Re
Hi!
I'm a student and I'm working with LabView 7 for the first time. I'm
looking for tutorials or hints from you on how to solve the following
problem:
I have managed to set up serial comm. so I get a string, I can log
data to a file and I can show the raw data in a text display.. now..
I'm talkin
12 matches
Mail list logo
