Keith and I both hope to be able to attend "Thunda Down Under"[1] in
2015, and I've sent the organizers email requesting information on what
it takes to be treated as an on-site vendor.
Of course, it's always more fun to be at a launch when you have something
interesting to fly! Thus, while Keith and I might each show up with a
modest "travel rocket" of some sort... I've started pondering possible
larger "Altus Metrum" group projects. Since transporting a large
airframe to Australia would be a hassle, I wonder if a group project to
build an airframe in-country makes more sense? To that end, I'd be
pleased to know if any of our friends and customers in Australia want to
sign up to help with such a project?
My thoughts would be to engage in some group-think about project scope
and goals, then hope friends in-country would take on the sourcing and
preparation of suitable airframe materials. Depending on who wants to
participate and how tasks get taken up, we might plan to arrive a bit
early to help with any final assembly or other preparations,
installation of suitably fresh Altus Metrum electronics, etc.
So, to all our Aussie friends... does this sound like fun? If so,
please chime in with a reply. I don't expect the email associated with
such a project to be too heavy a load for this list to carry, but we can
always spawn a dedicated lists.gag.com list if I'm wrong.
Regards,
Bdale
[1] http://thunda.com.au/
When a Telemetrum or TeleMega are in launch mode, they're transmit only so
you should be able to receive packets on both your laptop and phone at the
same time.
-Kevin
-----Original Message-----
From: altusmetrum [mailto:altusmetrum-bounces@lists.gag.com] On Behalf Of
Tim Navickas
Sent: Thursday, July 30, 2015 7:11 PM
To: 'Altus Metrum'
Subject: [altusmetrum] Tele BT
This may be a dumb question but is there anywhere that describes how to know
when the TeleBT is fully charged? Also, Can a TeleBT be connected to the
Telemtrum via phone and at the same time a teledongle be connected to the
same Telemetrum via computer?
Thanks,
Tim
_______________________________________________
altusmetrum mailing list
altusmetrum(a)lists.gag.com
http://lists.gag.com/mailman/listinfo/altusmetrum
Hey guys,
I finished my altimeter bay integration last night. I fired up the
Telemetrum 2.0 by itself and it took 5-10 minutes for it to get GPS lock. I
turned it off and then turned on my camera and Missile Works RRC2+ before
turning on the Telemetrum on this time I let it sit for 6 minutes and it
never found any satellites and never got a lock.
I have the camera board shielded but the camera module is unshielded and
near the Telemetrum. I've been told that writing to the SD card on the
camera produces a lot of noise and can interfere with GPS signals. Any
suggestions?
We'll put out a full product release message later, but for those of you
who have been patiently waiting, the new TeleBT v3.0 is now available
for purchase at
http://shop.gag.com/ground-stations/telebt3.html
Enjoy!
Bdale
Hi All,
I've been trying to setup my second Telemetrum and am not able to connect
in "idle" mode using the TeleDongle (RF connection). What's odd is that I
can connect when it's in pad/flight mode. Scanning also does not show the
Telemetrum when it's booted in idle mode.
Stranger still, I pulled out my other Telemetrum for comparison (which has
run fine in the past) and noticed the same behavior. It'll connect just
fine in PAD mode, but I can't connect in idle mode. About three months ago
I used this setup to ground test ejection charged and it worked fine.
I'm running AltOs 1.6 on OS X 10.10.3 (Yosemite) . Both units are flashed
with the latest Telemetrum 2.0 image as well. All I can think of is that
there's some OS X upgrade that it causing issues with the TeleDongle or
AltoOS software. Any ideas here? I've tried on both my desktop and laptop
with no luck.
Thanks!
-Rob
We launched a two-stage flight last weekend attempting to break 100K again.
The sustainer ignitor failed (incomplete pyrogen burn), but the recovery
was mostly successful, and we'll try again next month.
In the updated design, we've got one TeleMega and one EasyMega each, for
both booster and sustainer. All four units worked great. Having a common
programming interface and terminal block across everything has really
simplified our lives!
We had a couple of questions arise out of the flight. They're all about
sustainer ignition. To be clear, the TeleMega clearly fired it because the
igniter was partly burnt. I'm just trying to understand the data a bit
better. Here's the .eeprom file:
https://drive.google.com/file/d/0Bw8Fmi_7rzqMVnBLN2pjZFloUDA/view?usp=shari…
1) We used the tilt angle lockout on the sustainer ignition. I can see this
is the tilt relative to the pad orientation immediately before liftoff
(ao_ground_roll/pitch/yaw). I see the derived ao_sample_orient goes in the
OTA telemetry, but not the eeprom log, which instead gets the ground values
stored in the header along with raw r/p/y. Presumably, that's enough data
to reproduce the same math. Unfortunately, I'm not good enough at java to
discern how these get plotted in the UI. When looking at the .eeprom graph,
is the "tilt angle" still the angle vs. pad orientation? (Or is that a
silly question, because the gyros only give rates not absolutes?)
I'm interested because the tilt angle graph seems to start at a flat,
non-zero value, roughly 3.7. We did launch at about 2 degrees off vertical
to compensate for wind, but I wouldn't expect that to show up in the plot
if it were relative to pad.
2) We also set a time window of >17 seconds and <19 seconds on the
sustainer ignition. (Really, we want it to fire at 17 seconds, but we
learned last year that we needed to close the window in the event the
sustainer was off-angle to prevent a misfire during recovery.) In the
eeprom file, the "Ignitor A" event shows up at ~17.2 seconds. However the
"Ignitor A Voltage" shows a brief drop around 15.5 seconds, and no sign of
a drop at the actual event. The other ignitor voltage drops line up with
their events, or immediately after. It seems strange that this one was over
a second early. I can't explain that... We know it burned. Did our wiring
briefly glitch right before?
Also, possibly a minor bug: I don't see the ground r/p/y and aux ignitor
voltages in the csv export. (I should learn java...)
Casey
PS: I made the new avionics bays on a 3D printer. The bay models
themselves probably aren't useful to others, but I do have basic solid-body
STL models of both computers for evaluating fit and screw posts. I'll share
those when I get a chance.
I saw the earlier question and answer in April about the TeleBT being back
in production soon. Do you have any new information about when it will be
available?
I would like to fly a TeleGPS at AirFest on Labor Day weekend, and need to
decide whether to buy one with a TeleDongle now, or wait for the shiny new
TeleBT. Thanks!
Dan Crank
