David,
Thank you again for your reply.
You are right, I
am not afraid of Linux, just not as strong in it as I would like to be.
(Basically anything using grep makes almost zero sense but that is a
different issue).
The programmer in me has zero problems using
method calls as parameters into other methods, but I guess the idea (and
practice) of using separate programs/scripts as arguments to a program
was were my mind was blocking.
I was hoping to use TBEACON with
embedded telemetry in the same way that telem-balloon.conf uses PBEACON
(see lines 38-40). If I understood your reply correctly it just isn't
supported, and would be better implemented as separate TBEACON for
position only and CBEACONs for the telemetry data.
With the rate that car club wants to see this data my plan was to stay far away from 144.390
. I know I will end up monopolizing whatever frequency I end up on, but
it will only be for an hour or so on only a few days out of the entire
year. I am working with local hams that are more experienced than I to
find the best frequencies, and goal is always to use the lowest power
possible. No one wants to be that guy.
Looks like I have some
more testing ahead of me. (Just finished a python script to read data
from the serial port in a way it could be called/passed as a parameter
into infocmd=")
In your opinion would it be best to start a new discussion with my next question, or continue this thread?
The question(s) would be:
If
placing a Tracker w/ telemetry unit on each of 6-8 cars with the goal
of being able to receive data from these cars in? as close to real-time
as possible.
What would be the better design:
Option 1: All cars on the same frequency (not 144.39)
Option 2: Each car on it's own frequency.
There
are obviously pro's and con's to each set-up, but this post is already
getting too long. So I'll stop here for tonight and await your next
reply.
Again, thank you for your support. Quoting your first email this is a really cool project!
Tim...
