"Hannan, Nathaniel P" writes:
> Hello,
>
> My name is Nathaniel and I am part of the Oregon State University USLI NASA
> competition team. We recently did a full scale test launch in Brothers
> Oregon. The first seconds of the flight went well up until approximately
> 2.86 seconds after boost.
Altus Metrum announces TeleMega v6.0, TeleMetrum v4.0 and AltOS 1.9.15
Announcing TeleMega v6.0
TeleMega is back in stock! We're pleased to announce the next version
of our top of the line flight computer, TeleMega. Version 6.0 is
feature and performance compatible with version 5.0, using a new
Altus Metrum announces AltOS version 1.9.14
This release contains only a fix for TeleLCO; the previous version
(1.9.13) introduced a regression that broke the scanning process for
discovering available TeleFire devices. We're making this announcement
just to let people with TeleLCO boxes know not
Altus Metrum announces AltOS version 1.9.13
This release contains a couple of important firmware changes and users
with TeleMetrum, TeleMega and EasyMotor boards are strongly encouraged
to update.
AltOS Changes:
* Add option to beep max height in feet after landing
* Fix APRS reports to be
Altus Metrum announces EasyMini v3.0, EasyMotor v3, and AltOS 1.9.12
Announcing EasyMini v3.0
EasyMini is back in stock! We've managed to find parts for a slightly
redesigned EasyMini. This version works just like the older verisons
and it's still priced at only $80. EasyMini is a two-channel
Stan writes:
> Keith, when I attempt to open Altos-Windows-1-9-10.exe on my Win 10
> machine Kapersky automatically cleans if off. In doing so it has
> cleaned off my older version which prevents me from programming my
> EasyMini. I don't see a way in Kapersky to exclude a given file, but it
Terry writes:
> 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.
Yeah, TeleGPS doesn't have a notion of 'flight', so the 'height' values
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
Will Marchant writes:
> 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?
I use some curved tweezers for this; they're small enough to slip under
the 'ears' of the
Terry writes:
> After installing the new software I am seeing the following error
> messages.
Best we can tell, this is caused by anti-virus software running on your
box. You might make sure the files did get installed; you should see
these files on your machine (assuming you left the default
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
Leland Dexter writes:
> 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
Jesse Frey writes:
> Thanks for the ARM build! Just installed it on my pinebook
You're welcome! Bdale had to install quite a few compilers to make this
work :-)
--
-keith
signature.asc
Description: PGP signature
___
altusmetrum mailing list --
Altus Metrum announces TeleMega v5.0 and AltOS 1.9.8
Announcing TeleMega v5.0
We're pleased to announce the next version of our top of the line
flight computer, TeleMega. Version 5.0 is feature and performance
compatible with version 4.0, replacing the integrated 9-axis IMU with
the 6-axis
AlbyVA writes:
> So my question is there a way, or to put in a request for the
> next firmware update, that AltosUI get the same voice as the AltosDroid
> loaded in as a choice?
There's no way to do that -- the AltosDroid voice uses one built into
Android, which we don't have on the desktop.
Charles L Hakes writes:
> Okay - restart and re-install and it works. However, the new version
> doesn’t show up in Launchpad. (The old version did, and Launchpad
> was still pointing there. Easy to see if you rename.) The new version
> also identifies itself as JavaApplicationStub Version
Leland Dexter writes:
> Hello,
> I would like to set my Easy Timer to start timing sustainer ignition
> from booster burnout. Do I check off "After motor number" and type in
> "1", do I check off "Flight state after" and select "Boost" or do I
> need to do both?
Just 'after motor number'
--
Larry Gegel writes:
> I use the 70cm version and get the orange one so it’s nice and
> visible. I use one on my Yeasu FT3D when I’m only operating 70cm
> as well. I’ve only had them a few months so while their
> performance seems good I don’t have lots of data.
We
AlbyVA writes:
> I believe the answer to this question is "No", but I'd like to
> confirm that this upgrade to v1.9.7 is only for the Altos UI and not
> the actual flight computer (TeleMetrum v3 in my case)? In that, there
> is no firmware update associated with v1.9.7 for TeleMetrum or the
>
Altus Metrum announces AltOS 1.9.7
Announcing AltOS 1.9.7
This is a bug-fix release. Anyone using TeleGPS should upgrade the
firmware to 1.9.7 or later. Anyone using TeleMega v4.0 or TeleMetrum
v3.0 should upgrade the host software to 1.9.7 or later.
Firmware Changes:
* Fix TeleGPS bug
Joe Hepworth writes:
> Does the Telemetrum now work antenna down?
We're working on a 1.9.7 release of the ground station software which
includes a fix for configuring TeleMetrum in antenna down mode. That
should be released in the next week.
--
-keith
signature.asc
Description: PGP
Jesse Frey writes:
> There are a bunch more similar errors but they seem to be similar.
> My googling on these errors hasn't been super helpful. How can I fix
> these errors?
You need to install the cairo-5c package; if you're running a
debian-derived distro, that should be as easy as
Keith Packard writes:
> From the crash report I see on Google, the crash appears to be where I
> changed some code to avoid using a deprecated API. I've switched that
> code back and have uploaded a test version. I think this link should
> work to let you try it out:
>
> https
Andy Barwick writes:
> Getting ready for the spring flying season and updated Altos Droid to the
> latest version. Now the app crashes immediately upon opening?
> "Unfortunately, Altos Droid has stopped." is the only error i get.
>
> Tablet is a Samsung Galaxy Tab A (2016) The Android version
burnwuf...@aol.com writes:
> In particular, does a Telemetrum transmitting on 70 cm. interfere with
> a Perfectflite Stratologger SL-100? Anyone have any experience?
I've seen several people fly this combo with good results. Ground
testing with the fully assembled rocket and both flight
Terry writes:
> Thanks Keith. I saw the three suggested frequencies in the setup and
> assumed that was the extent of my choices. I tried other frequencies
> for the beep tone and you are correct again. The lower the frequency the
> lower the level so the lower pitch didn't really help.
Terry writes:
> Is there anyway that I can lower the pitch of the mode beeper on my
> EasyMini. The two available settings are so high that I have a hard
> time hearing them. I would love it if they could be configured to have
> a pitch somewhere between 500 and 1000 Hz.
You can type
Gary Lech writes:
> Thanks Keith. Is there any reason to do a recalibration. My inclination is
> to leave well enough alone if all is working normally.
Yeah, the accelerometers seem to age a bit and can use periodic
re-calibration, say once a season or so. That's why we added this to the
UI; we
Gary Lech writes:
> Greetings,
> Can anyone say what the Accel Plus and Accel Minus values are. I couldn't
> find anything in the manual that discusses them.
They're the calibration values showing the raw accelerometer numbers for
+1g and -1g.
You can set them by running the 'calibrate
AlbyVA writes:
> Keith:
>
> Thanks. Time to order a longer USB cable.
Yeah, I keep looking at doing BT support for OS X but it's really
complicated seeming...
--
-keith
signature.asc
Description: PGP signature
___
altusmetrum mailing list
AlbyVA writes:
> Keith:
>
> Thanks. Got any recommendations on an external USB Bluetooth dongle that
> could be used until
> Mac OS X BT is supported?
The only connection supported for TeleBT on Mac OS X is USB. Bluetooth
is supported on Android, iOS, Linux and Windows.
--
-keith
AlbyVA writes:
> So what on earth is going on with MacBooks and Bluetooth with the
> TeleBT?
We don't have any bluetooth support for Mac OS X at this point.
--
-keith
signature.asc
Description: PGP signature
___
altusmetrum mailing list
Stewart Campbell writes:
> Thanks for the replies everyone. Looks like I need to build a TNC and have
> the TeleMega send APRS :-(.
>
> Keith, is it possible to add a feature to AltosUI to output NMEA formatted
> strings on a serial port on the PC running the software? Can I put that in
>
Stewart Campbell writes:
> Hi, I am setting up an antenna tracking system that needs a data
> stream out of the TeleBT (or attached computer) that I can feed to the
> antenna tracker to have it follow the rocket automatically during
> flight. How do I go about getting something like that
Charlie Peckham writes:
> Hi,
> I have my own noob question. I have hooked up my telemetrum to a
> charged battery. It starts beeping. But when I hook up the apogee
> and main terminals to 6 V light bulbs and put it into a vacuum chamber
> nothing happens. The lights dont come on at all.
Jesse Frey writes:
> I've got another pesky telemetry question. I just did a flight with a
> companion board. When I download the data from the TeleMetrum I have
> no option to plot any of the companion channels and the CSV does not
> show them. Are the companion channels in the log file? if so
writes:
> The apogee match was burned. Why would the apogee battery voltage not dip
> if it fired at apogee. I looked at some of my other flight with different
> telemetrums, and they all showed the apogee voltage dipping when the drogue
> fired.
Once apogee happens, we only sample the
writes:
> Does the attached graph make any sense to anyone? To me it looks like
> the Apogee voltage fired when the main should have.
Urf. That does not look like any fun at all.
I'd bet the violent activity when the main deployed just shook things
around enough to make it look like the
Plugger Lockett writes:
> Just to piggyback on this thread, is the USB connection the only way to
> update firmware for the TeleMini v3.0?
Yes.
--
-keith
signature.asc
Description: PGP signature
___
altusmetrum mailing list
Christopher Harris writes:
> It was a revision issue. Upgraded to newest rev and everything is
> good. Had to use my linux VM, old OSX doesn’t like the newer rev due
> to old JAVA.
We're now recommending that you run the 'adoptopenjdk' version of Java;
that should let the latest version run on
Christopher Harris writes:
> Bdale,
>
> Still not loading the tiles?
>
> Please add Tripoli Houston South Site to the DB.
We've got it listed; looks like about 4.2km northeast of Chocolate Bay?
> 29 13’ 42.58” N
> 095 05’ 28.84” W
Yup, looks about right. On iOS, you'll have to restart the
Larry Gegel writes:
> After not using my Altus Metrum stuff since last summer I’m getting
> everything ready for this springs flying season. I’m having problems
> with AltOSUI. For the main menu and any screen that has no user input,
> such as ‘Monitor Flight’ or ‘Monitor Idle’ everything works
Sam TC writes:
> Hey Keith,
>
> I uninstalled Java and reinstalled 1.9.6/
>
> All good!
Yay! Mac OS X is hard for independent app developers...
--
-keith
signature.asc
Description: PGP signature
___
altusmetrum mailing list
Sam TC writes:
> I installed the Altus Mac software on my MacBook Pro running Catalina
> with no issues. When I launch Altus, it errors out asking for Java
> 6. I tried to install the AdoptOpenJDK project but an install error
> stated there was a later version of Java running. Where to from
Jesse Frey writes:
> This makes a lot of sense however, I do mostly like to use the app at
> the field. If you did have hardware would you consider updating this?
> or is this kind of an unmaintained feature that you don't have any
> plans to pick up?
Afraid the latter -- we don't lack for
Jesse Frey writes:
> The companion interface seems to be an underutilized feature of Altus
> Metrum products. And I understand if most of these will not be
> addressed.
>
> 1) It seems that AltosDroid does not support displaying companion
> telemetry. Is there any plans do add this in the
Brandon Davis writes:
> Good afternoon,
>
> I was wondering if there is a way to be able to configure the initial
> settings without the use of the TeleDongle/TeleBT by plugging the EasyMega
> or Telemetrum into the computer via USB when I have everything connected
> (battery and switch).
Yes,
Andrew Grippo writes:
> Bdale.
> I couldn't resist trying your suggestion so I cut up a cable and
> hooked everything up and it worked perfect. The Telemini is at the
> latest firmware version now.
Wow. I'm impressed :-)
--
-keith
signature.asc
Description: PGP signature
Andrew Grippo writes:
> I have been poking around the manual and forums for a few hours and I
> am not able to find the correct steps to take to flash a TeleMini Ver
> 3.
We don't have an easy way to reflash TeleMini at this point, I'm afraid.
> I tried using a Teledongle 3.0 to connect to
Justin Stotter writes:
> Brett,
>
> I had this same issue recently with my new Mega using AltosUI. On the FB
> group Chris suggested I calibrate and then change to antenna down via putty
> and that worked for me.
Yup, that will work -- there's a bug in AltosUI which we've got a fix
for, but
Brett Bachman writes:
> Thanks Keith.
>
> I changed the orientation to antenna up and now the X beep code goes away.
>
> I planned to fly this project at the 12/12 ARSABQ launch. Any chance the
> firmware fix will be ready by then? If not, what is the ETA?
The firmware is fine -- it's the
Brett Bachman writes:
> 4. I then oriented the antenna down, flight ready, and rebooted.
Current AltosUI has a bug in antenna down mode; we'll be updating
soon.
--
-keith
signature.asc
Description: PGP signature
___
altusmetrum mailing list
"David W. Schultz" writes:
> ao_bmx160_init();
>
>
> Which I would think would generate a warning from the compiler at
> least.
ao_bmx160.h gets included by ao_data.h which is included by ao.h, so
there's no compiler warning. ao_easytimer.c should probably include it
directly as a way
Altus Metrum announces AltOS 1.9.6
Announcing AltOS 1.9.6
This is a bug-fix release. Anyone using EasyTimer should upgrade the
firmware to 1.9.6 or later immediately!
Firmware Changes:
* Fix EasyTimer bug where it might mis-detect boost (either
detect it early or not at all) due to
Gary Lech writes:
> I have ALTOS Android version 1.9.2 installed which is what's shown in
> the Google Play store. Is there a newer version available.
I haven't updated the android app in a while. I should get the Monitor
Idle changes incorporated though; that'd be a good improvement.
--
Terry writes:
> Tried it on another PC and had the same results. One is Win10 Home and
> the other is Win10 Pro.
We did update the release to fix a problem with the Altos Library. Have
you tried re-downloading today?
--
-keith
signature.asc
Description: PGP signature
Alex Zoghlin writes:
> The easy answer is to always use a separate pyro circuit, but that isn't
> always feasible.
As Bdale says, there's a special circuit on our boards designed to
prevent brown out which was first included in TeleMega v1.0.
The TeleMega v1.0 design was finished just before
Robert Watzlavick writes:
> Keith - I'm very certain the TeleMetrum is not still beeping when the
> problem occurs now that I think about it. A power cycle fixes it. Are
> there any timeouts that make it shut down after a while on the ground?
Nope. It should keep running as long as there is
Robert Watzlavick writes:
> I was able to flash it with 1.9.5 - thanks! Can you provide the radio
> calibration for TeleDongle S/N 5177?
We'll have to wait for Bdale to find that information; he's en-route to
AirFest today.
> Regarding the intermittent telemetry, it doesn't seem related to
Robert Watzlavick writes:
> I was attempting to upgrade a TeleDongle 3.0 from 1.9 to 1.9.2 and I
> managed to get it in a bad state. When I tried to flash the image under
> Linux, I got an error (can't remember the message) and it then it
> wouldn't show up as a USB device. Every time I try
Altus Metrum announces AltOS 1.9.4
Announcing AltOS 1.9.4
This release fixes a few errors in the 1.9.3 firmware:
* Fixed firmware for TeleDongle v3.0 and TeleBT v4.0. Version 1.9.3
bricked those devices requiring them to be opened up to get them
working again.
* Fixed firmware for
Altus Metrum announces EasyTimer v1 and AltOS 1.9.3
Announcing EasyTimer v1
We're pleased to announce a brand new Altus Metrum product: EasyTimer.
EasyTimer is an advanced flight electronics board with two pyro
channels and tilt limits designed to control events during ascent,
including staging,
Altus Metrum announces TeleMega v4.0 and AltOS 1.9.2
Announcing TeleMega v4.0
We're pleased to announce the next version of our top of the line
flight computer, TeleMega. Version 4.0 is feature compatible with
version 3.0, incorporating a new 200g high-g accelerometer, a new
9-axis IMU, and the
Denis Banovic writes:
> Hi Mike,
>
> Haven't heard from you in a while, is there an update coming for the app
> soon?
Mike and I have been working on it quite a bit this winter; if you sign
up for the open beta, you can help test the latest drops. Once we're
happy, we'll move that to
Miles Klima writes:
> I'm having problems with Windows 10 not detecting my EasyMini.
>
> I have tried different usb ports on my laptop. I have tried turning on
> the easymini while it is plugged in to the usb. The easymini does go into
> pad mode,
That means that Windows isn't seeing it.
Altus Metrum announces TeleMetrum v3.0 and AltOS 1.9.1
Announcing TeleMetrum v3.0
We're pleased to announce the next version of our TeleMetrum flight
computer. Version 3.0 is feature compatible with version 2.0,
incorporating a new 200g high-g accelerometer along with the updated
uBlox MAX 8Q
Jesse Frey writes:
> Ok, that makes some sense. Is there a way to know how long to expect the
> lag to be? Or do I just launch it and see how long it took?
There's no easy way to compute what the delay will be; the Kalman filter
is somewhat hard to understand in that way.
--
-keith
Jesse Frey writes:
> The last 2 launches of my Nike Appache have been on Warp 9 booster
> motors. Looking at the data, I see that switching into boost mode lags
> the drop off of the acceleration (see attached). In the case of the
> J599 this is close to 1 s. Is this the intended behavior or is
"Tim Navickas" writes:
> Does this graph make sense? Mainly the speed part. It was a very
> windy day.
You didn't get a lot of data after the motor burned out until
apogee. Because the 'Speed' value is computed on the ground by
integrating acceleration, you can see it's pretty confused by the
Clay and Carly Dunsworth writes:
> Sorry for my response, I guess we said the same thing, except gravity
> is why the mass is important for thrust to weight ratios during the
> burn. So if you update the code for the moon, we could launch from
> there to mars cheaper.
Yay! Let's go!
--
Craig Klimczak writes:
> Your're right. :-) I really don't understand what the
> accelerometers are reporting. I assumed that the accel would detect
> the de-acceleration as the rocket reached apogee, reach a point of
> zero acceleration and then start accelerating back toward Earth.
Uh.
Craig Klimczak writes:
> Casey and Drew pointed out that at over 100K the exact timing of
> apogee will not be that big of deal. There is not enough atmosphere to
> zipper the rocket.
Yup. If you've seen a descent plot for any of these flights, it's
parabolic until you get down to about
Casey Barker writes:
> The *Megas use a Kalman filter to fuse both accel and baro
> data into the model, up to 100k', so I don't think the apogee detect should
> be all that sensitive to off-vertical flight.
Older *Mega firmware would lock out the baro sensor above mach 1. Flying
well above
Craig Klimczak writes:
> Are there any special considerations for setting up the TeleMega for
> flights to over 100,000 feet?
Yup, 100k' is where the baro sensor ends and you end up flying on accel
alone (really, it's just coasting at that point, so even the accel is
reading 0). This means
Bryan Duke writes:
> The foam I’ve used in this case looks like the stuff here:
> http://flyingeinstein.com/index.php/tutorials/barocover
>
> There are forum posts about people using the black foam that hard drives are
> packed in, the foam on the inside of those squishy sanding blocks, and
>
Bryan Duke writes:
> One other thing I haven’t tried on a rocket is the technique that some
> quadcopter/drone pilots use on their baros of putting a little piece
> of foam on the top of the sensor. They do it to help smooth out the
> wind flowing around the sensor so that it gets smoother
>
Reinhard Rath writes:
> For a group project, I'm looking into replicatingfunctionality similar
> to the Jolly Logic Chute Release, but with a pyro cutter instead of a
> servo releasing a rubber band.
>
> For mechanical reasons, the EasyMini would be mounted in the nose cone
> and subjected to
Bdale Garbee writes:
> Reinhard Rath writes:
>
>> Is there a straightforward way to recover at least some data if a
>> readout results in a CRC error?
>
> Not easily, but Keith has been known to extract useful information from
> a raw dump of the flash contents... CC'ing him for an explicit
Gary Lech writes:
> Greetings,I have a TeleMega SN: 1240 that is part of the ARLISS fleet
> with an unknown history. I'm unable to communicate with it using
> either USB or the TeleBT. When powered up it gives me an unusual beep
> code:dah dit dit dit ditI didn't see it listed in the manual. I
Casey Barker writes:
> The serial on this unit is #373. I tried using ao-load (Ubuntu 16.04, altos
> 1.6-1) to load a couple of different firmware revs, but it wanted a "map"
> file, which I eventually figured out was a symbol table I didn't have. So
> on a whim, I tried ao-rawload, and that
Casey Barker writes:
> I'm pulling an old rocket out of mothballs to fly at NAR NSL, so I started
> by updating firmware. I updated my old TeleMetrum v1.1 to AltOS 1.87 and
> (ignoring the manual stating it wasn't necessary) figured I might as well
> upgrade my TeleDongle v0.2 while I had the
chuck fauser writes:
> Hey guys,I used my TeleGPS for the first time this past weekend. I few
> two separate flights (one each day) and used the TeleBT to walk right
> to the rocket both times. Today when I went to download the flight
> files, I find only one file on the TeleGPS and it is
GÖKBÖRÜ ROKET writes:
> Hello, we have a question. Our telemetrum and teledongle do not have red
> pins and red cable in our device. If you show us their connection diagram,
> we can link them here. this is a very important and urgent matter. we
> need to train the competition.
You should
GÖKBÖRÜ ROKET writes:
> Hello there,
> I have a question. Where can I get the program of the telemetrum card?
All of the software for our devices is available from
https://git.gag.com/?p=fw/altos;a=summary
--
-keith
signature.asc
Description: PGP signature
"Tim Navickas" writes:
> Does this graph make sense? Why is max height and Max GPS Height so
> different. The Max height agrees with my backup altimeter. This was flow
> in Argonia Kansas elevation ~1100 feet.
Looks like GPS didn't get a solid lock at apogee. Can you send along the
full
Bdale Garbee writes:
> I think the green LED on the processor should flash briefly during power
> up, but the flash might be short enough to be hard to catch? Then I
> think that LED blinks every 3 seconds once GPS lock is acquired. Did I
> get that right, Keith? If so, we should probably add
"Tim Navickas" writes:
> It has been a while since I used my TeleGPS and I am having problems.
> I can connect to it via ALTOS with a USB cable but not with the tele
> Dongle or Tele BT.
How are you trying to connect? TeleGPS doesn't support the duplex packet
mode for remote configuration. If
"Keith Packard" writes:
> I think it would be sufficient to just add a 64-bit random nonce to the
> packets and leave the rest of the protocol alone.
Oops. For this to work, the pad boxes would have to remember the nonces
seen before and ignore them.
A longer time stamp in
"David W. Schultz" writes:
> My favorite source of entropy is the user. Run something like a linear
> feedback shift register (or just run AES over and over) until the user
> does some randomly timed thing. In other words, shuffle the bits until
> the user stops it. For bonus points, save the
"David W. Schultz" writes:
> But even with a 32 bit counter attacks are still possible, it just takes
> more time. If the count always starts at zero, then I can still build a
> library of packets and when they will be good. Usable the next time the
> system restarts. Starting with a random
"David W. Schultz" writes:
> But in block chain mode the current checksum will depend on all previous
> checksums. What happens when a packet gets dropped?
It's a packet protocol, not a stream protocol. Each packet is
checksummed separately.
> How do you prevent someone from recording a valid
Scott Mcintosh writes:
> Hum. Looks like the attachment was removed. How would you like me to
>send this? You can contact me directly at the address below. p
If you sent it back to me at this address (kei...@keithp.com), I should
get it without trouble.
--
-keith
signature.asc
Scott Mcintosh writes:
> I can not get my EasyMini to come up in idle mode.
>
> Regardless of whether it is connected to the computer or not, when
> powered on It beeps out what I interpret as a: dit brap dah dah dah
> dah
We should make recordings of these sounds so you can actually tell
Altus Metrum announces EasyMega v2.0 and AltOS 1.9
Announcing EasyMega v2.0
We're pleased to announce the next version of our EasyMega flight
computer. Version 2.0 is feature compatible with version 1.0,
incorporating a new 200g high-g accelerometer along with the updated
9-axis IMU first used
Casey Barker writes:
> Thanks, Keith. This issue is fixed for me.
yay!
--
-keith
signature.asc
Description: PGP signature
___
altusmetrum mailing list
altusmetrum@lists.gag.com
http://lists.gag.com/mailman/listinfo/altusmetrum
Erik Ebert writes:
> I just ran into the same issue. My java control panel shows java 8,
> but that error message seems to indicate that it is trying to execute with
> a much earlier version of java.
I figured out what was going on with this. When you install Java 8 from
Oracle, it only
Plugger Lockett writes:
> Gents,
>
> Thanks for the thread replies. I've just realised that it would probably
> make more sense if I attempt to accomplish this myself. I've got two
> TeleDongles so as you said I should be able to flash one with the other
> assuming I've got the pair programming
Altus Metrum announces AltOS 1.8.7
Announcing AltOS 1.8.7
AltOS 1.8.7 contains ground station software changes to fix Google
Maps access, and incompatibilities with Mac OS X Java versions.
Version 1.8.7 includes firmware for TeleMega v3.0 devices, and a
radio calibration fix for TeleBT v4.0
Stewart Campbell writes:
>> # apt install git
> Seemed to work
>> # apt build-dep altos
> Seemed to work
>> $ git clone git://git.gag.com/scm/git/fw/altos
> Tried this at $ prompt
> Fatal: Could not create work tree 'altos': Permission denied.
> Tried again at # prompt
> Fatal: remote error:
Stewart Campbell writes:
> Hi Keith,
> Thanks for the tips. Please remember I have almost zero Linux experience!
>
> So, what I have done so far:
>
> * Created a VM on a windows machine
> * Installed Debian to the VM
> * Installed most of the altos stuff (commands mentioned below)
> * Got the
1 - 100 of 269 matches
Mail list logo
