Bdale:
What is your RMA process or Paid Repair process?
The USB connector on my TeleBT popped off the PCB board when I plugged in
a cable the other day. I don't trust my soldering skills to reconnect
something this small. So I figure it's best to have you repair it vs. me
screwing it up and them coming back to have it repaired.
PS: Should I ship just the board/connector or do you want me to send you
back everything (Case, LiPo, etc)?
Thanks,
Alby
[image: Screenshot_20210920-095326_Photos.jpg]
I’ve noticed a strange behavior from the beeper on my EasyTimer. On boot up, the beeps are as expected, however subsequent beeps are at a much higher frequency and barely audible. If I change the frequency both the boot up and subsequent beeps change but they are still at different frequency with the subsequent beeps at a higher frequency than the boot up beeps. I’ve noticed this with both 1.9.8 and 1.9.10. Whether or not it did it with previous versions I can’t say because I upgraded it to 1.9.8 as soon as I got it.
Do you have a recommended sequence for connection the TeleBT (bluetooth) to a TeleMetrum? I was able to connect with my iPad but the windows machine and new software connected to the TeleBT but wasn't connecting. to the Telemetrum. I'm not sure if it's a timing issue or sequence.
Mike Lloyd
Altus Metrum announces AltOS 1.9.10
Announcing AltOS 1.9.10
Altos 1.9.10 is another bug-fix release.
AltosUI Changes:
* Rework the windows DLL build to make AltosUI run on more instances
of Windows 10.
AltosDroid Changes:
* Adapt to an Android security change with prevented AltosDroid from
storing received telemetry. Flights are now stored in
/storage/emulated/0/media/org.altusmetrum.AltosDroid/AltusMetrum,
and AltosDroid will display an error message if flight data cannot
be logged.
Read more about AltOS here:
https://altusmetrum.org/AltOS/
I had the strangest behavior yesterday with my tracking system. It still
took me to the rocket which landed almost 2 miles away but during the
flight the altitude readouts in particular were way off.
The flight was supposed to go 15,000 feet but I was getting readouts
from Altos Droid that apogee was 8,000 feet. The descent rates seemed
reasonable but as the rocket descended the altitude readouts went into
negative numbers. The last data packet claimed the rocket was at
-5085. The data from the flight was not recorded since my phone hadn't
updated to the newest version of Altos Droid yet. I did capture screen
shots from my phone of the flight when I got home last night. For
reference the launch site is at 3,000 feet ASL.
I powered up the electronics and checked that everything was working
correctly and the rocket sat for some time as I the range was then
closed to high flights due to clouds that moved into the area. I
powered down and waited for nearly four hours for a break in the
clouds. It was then a rush to the power up and get the pads when we got
a short break in the clouds. I only checked that I was getting data
updates before taking the rocket to the pad and launching it.
When I got home and downloaded the data from the rocket it looked
strange as well. The reported altitude agrees with that of the two
Easy-Mini altimeters but there seem to be long pauses in the data that I
don't understand.
Does anyone have any ideas as to what happened?
Terry
Hi Folks:
I find it very difficult to separate the JST connectors on the battery
pack from the receptacle on my AltusMetrum devices.
Is there a "pliers like" tool for that?
Or maybe somebody has 3-D printed a C-shape tool that gives you a bit of
leverage for pulling on the connector?
73,
Will
--
Will Marchant, KW4WZ
will(a)spaceflightsoftware.com
http://www.spaceflightsoftware.com/will/
Altus Metrum announces AltOS 1.9.9
Announcing AltOS 1.9.9
Altos 1.9.9 fixes a couple of bugs in the 1.9.8 software
Firmware Changes:
* Fix TeleMega and EasyMega configuration update from pre-1.9.8. If
you're running 1.9.8, you need to upgrade to 1.9.9 and check your
configuration closely.
AltosUI Changes:
* Fix TeleMega v5.0 eeprom file parsing. AltosUI would not
recognize TeleMega v5.0 files.
Read more about AltOS here:
https://altusmetrum.org/AltOS/
Hello again,
While I love all of my Easy Minis my Easy Timer continues to give me problems. I set "After motor number" = 1 and "Delay after other condition(s)" = 1.5 hoping to get a 2nd stage motor to fire 1.5 seconds after booster burnout. Result was a good boost and no sustainer ignition. Fortunately my Easy Mini riding tandem saved the rocket. Now, to further complicate things, when I try to connect the ET to my laptop 95% of the time the communications drops after a second or two. Once I was able to stay connected and was able to reset some parameters (now going to try "Time since launch greater than" and set the Delay after other condition(s)" = 3.0 seconds. Any help figuring out what is going on would be appreciated!
Sent from Yahoo Mail on Android
