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
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 probes in the
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, I
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
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
I think using a history buffer and have one graph will be to slow. The
satellite will be active for 6 - 8 hours, and towards the end of that
time, I think (I don't know) that the time it would take to read in
the buffer and then display the data would be significant, taking away
resources
I don't have any 100% accurate values at this time since we have not
desgined the sample system yet. However, going with what I have to
estimate one:
Assuming data is transferred in binary format (header and footer in
ASCII)
10 data sources, each is app. 10-13 bit long, round up for worst case
=
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...
Thanks for a fast reply with relevant information! :)
I think using a history buffer and have one graph will be to slow. The
satellite will be active for 6 - 8 hours, and towards the end of that
time, I think (I don't know) that the time it would take to read in
the buffer and then display the
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
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 in
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
Also, I'm wondering if it is possible to have several graphs
underneath each other in the front panel, so that when the user
presses say, F1 through F10 it brings to the front different graphs.
That way I can have 10 graphs but only show one at a time (but I can
scroll them back in time to
13 matches
Mail list logo
