altusmetrum October 2018

altusmetrum@lists.gag.com

7 participants
5 discussions

by Casey Barker

I see an error when running AltosUI.app 1.8.6 on Mac OS 10.13.6, running the stock Java 2017-001 from Apple. I also tried it on a second Mac OS computer, and it's consistent. I rolled back to 1.8.5, and the error goes away, so it's something between those two versions. Cannot launch Java application Uncaught exception in main method: java.lang.UnsupportedClassVersionError: com/sun/speech/freetts/VoiceManager : Unsupported major.minor version 51.0 Not sure if I should use the 1.8.5 UI with newer firmware, so I'll switch to a VM. Casey [image: Error.png]

4 years, 5 months

Re: [altusmetrum] altusmetrum Digest, Vol 88, Issue 6

by Stewart Campbell

I also have a programming cable or two Andrew :-) Stewart On 10-Oct-18 19:23, altusmetrum-request(a)lists.gag.com wrote: > Send altusmetrum mailing list submissions to > altusmetrum(a)lists.gag.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.gag.com/mailman/listinfo/altusmetrum > or, via email, send a message with subject or body 'help' to > altusmetrum-request(a)lists.gag.com > > You can reach the person managing the list at > altusmetrum-owner(a)lists.gag.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of altusmetrum digest..." > > > Today's Topics: > > 1. Re: Issues with newer AltOS and TeleGPS applications > connecting to TeleGPS with old TeleDongle (Grant Diffey) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 10 Oct 2018 19:23:01 +1100 > From: Grant Diffey <gdiffey(a)gmail.com> > To: Altus Metrum <altusmetrum(a)lists.gag.com> > Subject: Re: [altusmetrum] Issues with newer AltOS and TeleGPS > applications connecting to TeleGPS with old TeleDongle > Message-ID: > <CACckToVFtz5fcuw8=osE2nutHNKMLunHW9K0KcF=DhW0t_=wrQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Trippoli au but I've been somewhat dormant for a little while. > > I definitely have at least one programming cable. > > Grant. > > On Wed, Oct 10, 2018 at 7:05 PM Plugger Lockett <plugger.lockett(a)gmail.com> > wrote: > >> Hi Grant, >> >> Over here in Perth. As to the reprogramming, I don't have a >> programming/pair cable (whatever they call it) so I'm a bit stuck. >> >> Do you fly with MARS, Tripoli AU, or both? >> >> Thanks for reaching out. >> >> drew >> >> On Wed, Oct 10, 2018 at 3:57 PM Grant Diffey <gdiffey(a)gmail.com> wrote: >> >>> Andrew... >>> >>> Where in au are you? >>> >>> I'm in Melbourne and pretty familiar with this stuff.. you can reprogram >>> a teledongle with another teledongle. >>> >>> Grant. >>> >>> On Mon, Aug 27, 2018 at 4:53 PM Plugger Lockett < >>> plugger.lockett(a)gmail.com> wrote: >>> >>>> Afternoon Bdale, >>>> >>>> Just to provide an update, I was able to get my hands on another >>>> TeleDongle. Sadly it's running the same firmware and is even older from a >>>> serial number perspective (#363 iirc). I'm still having the issues with >>>> getting a stable and repeated telemetry link with my TeleGPS with this >>>> TeleDongle as well. But on the plus side I've got APRS output working on my >>>> TeleGPS so I've got a workaround/fallback method for finding the rocket if >>>> required. I'll update the other thread with a bit more info on that one. >>>> >>>> Given I've now got two at issue TeleDongles would it be possible for me >>>> to return one to you to get a firmware update accomplished? I definitely >>>> don't have easy access to the right bits and pieces to get this sorted >>>> myself. >>>> >>>> Regards, >>>> >>>> Andrew Hamilton >>>> >>>> On Wed, Aug 8, 2018 at 9:46 AM, Plugger Lockett < >>>> plugger.lockett(a)gmail.com> wrote: >>>> >>>>> Hi Bdale, >>>>> >>>>> One other thing. I just installed AltOS on my Kali laptop via the Kali >>>>> repositories as I much prefer to have apt handle upgrading and dependencies >>>>> when compared to installing applications manually (like the v1.8.6 shell >>>>> script on the AltOS page). My installation went fine and I'm able to run >>>>> AltOS on Linux now. That said the repository installed version is still >>>>> v1.8.5. Any idea how long it'll take v1.8.6 to hit the repos? >>>>> >>>>> Regards, >>>>> >>>>> Andrew H. >>>>> >>>>> On Wed, Aug 8, 2018 at 9:14 AM, Plugger Lockett < >>>>> plugger.lockett(a)gmail.com> wrote: >>>>> >>>>>> Hi Bdale, >>>>>> >>>>>> Thanks for the quick response. To continue. >>>>>> >>>>>>> Either Keith or I can take care of this for you if you don't have >>>>>> easy >>>>>>> access to the right bits and pieces any more. >>>>>> I think I'll take you up on that offer but it would be October at the >>>>>> earliest as we're still in flying season and crop is now getting to optimum >>>>>> rocket hiding levels. I will then need the unit back by March as April is >>>>>> THUNDA over in Queensland and I will require it then. I'm planning on >>>>>> ordering another TeleGPS (v2.0 this time) as well as a new TeleDongle >>>>>> Starter Pack with the v3.0 TeleDongle so it might make sense to order the >>>>>> new kit after returning my old TeleDongle to consolidate shipping costs. I >>>>>> might also request a pair programming cable to be included for future use >>>>>> as I also own a TeleMetrum v1.2 and to update that requires that cable. I >>>>>> did have one but IIRC I loaned it to a guy at Balls in 2013 and never saw >>>>>> it again. >>>>>> >>>>>>> I'm hoping Keith will chime in here about why v1.0.2 TeleDongle >>>>>> firmware >>>>>>> might work ok with v1.7 but not v1.8.5. I just skimmed through the >>>>>>> release notes and don't have an immediate answer. >>>>>>> Do you happen to have access to some other TeleDongle or TeleBT, >>>>>> perhaps >>>>>>> with newer firmware? >>>>>> I'd be curious to hear from Keith regarding this as well. Sadly I >>>>>> don't have access to any other ground station hardware at the moment but I >>>>>> might know one or two around the traps that I could get my hands on. I >>>>>> suspect they'll all be similar to mine in terms of versioning though as >>>>>> they would have been purchased from Blake at Australian Rocketry when he >>>>>> brought a whole slew of TeleMetrum v1.0 and v1.2 Starter kits. >>>>>> >>>>>>> Have you actually tried it? I'm curious whether this is something >>>>>>> unique to the workstation software build or if the AltosDroid is also >>>>>>> affected. They both share the same library of functionality >>>>>> including >>>>>>> packet decoding, so I'm guessing AltosDroid is affected too. >>>>>> Yes, I have tried it. I get no comms link when I plug in my TeleDongle >>>>>> to my phone via an OTG cable. As mentioned with earlier variants (I'm >>>>>> assuming v1.7 or before) everything just automatically worked just like on >>>>>> on my laptops as my TeleDongle starts up on the channel I've configured the >>>>>> TeleGPS to communicate over. With v1.8.5 I get nothing though. Given the >>>>>> ability of the AltosDroid App to be able to know where you are as the phone >>>>>> has its own GPS chipset it does provide a better experience imo for rocket >>>>>> recovery when compared to using a laptop without GPS. Not to mention >>>>>> carrying a phone through crop is much easier than lugging a laptop, >>>>>> especially when I've got a yagi in the other hand! Given this and the fact >>>>>> that I don't expect to program my EasyMega with AltosDroid I'd ideally like >>>>>> to revert back to v1.7 of AltosDroid on my Pixel, turn off automatic >>>>>> application updating for that app, and leave it be. If you could point me >>>>>> to where I could find that apk I'd greatly appreciate it. >>>>>> >>>>>> FYI I upgraded one of my windows laptops to AltOS v1.8.6 last night >>>>>> and promptly upgraded the firmware on my TeleGPS. That worked flawlessly >>>>>> and I was able to confirm I'm now running the v1.8.6 firmware on my TeleGPS >>>>>> with the "Configure Altimeter" menu. I then went to upgrade my EasyMega >>>>>> v1.0 to v1.8.6 firmware. That didn't work. I should have taken a screenshot >>>>>> for you (and can do tonight) but once I selected the relevant EasyMega v1.0 >>>>>> 1.8.6 firmware in C:\Program Files\Altusmetrum\ the application would >>>>>> provide no further output. I was expecting the small window that confirms >>>>>> serial and radio configurations and then the firmware installation progress >>>>>> window but neither appeared. I then attempted to run the "Configure >>>>>> Altimeter" and whilst the unit still appears as available the identifier >>>>>> for selection had changed from something along the lines of "EasyMega >>>>>> serial xxxx" to "Altusmetrum 1" which strikes me as maybe a bootloader ID >>>>>> string. Luckily a power cycle of the FC allowed it to reboot successfully >>>>>> which was confirmed by rerunning the "Configure Altimeter" command. I >>>>>> could see all my relevant configs, serial, and current firmware (v1.8.5). >>>>>> Just an FYI as it does appear the EasyMega v1.0 firmware upgrade isn't >>>>>> working in Altos v1.8.6. >>>>>> >>>>>> Safe to say I've developed a bit of an appetite for this testing. >>>>>> Today I'm going to install AltOS on my work Kali laptop (which is Debian >>>>>> based) and do more testing tonight. Is there anywhere on Linux or Windows >>>>>> where I can get more granular console output or logging info regarding >>>>>> what's happening inside AltOS? I don't mind digging through console output >>>>>> if it will assist in resolving my comms issues. Plus it'll be interesting >>>>>> to see if and how the comms differ between the different platforms. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Andrew H. >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Aug 7, 2018 at 11:04 PM, Bdale Garbee <bdale(a)gag.com> wrote: >>>>>> >>>>>>> Plugger Lockett <plugger.lockett(a)gmail.com> writes: >>>>>>> >>>>>>>> I believe I've identified an issue with the AltOS and TeleGPS >>>>>>> applications >>>>>>>> when using an original TeleDongle for telemetry. The old TeleDongle >>>>>>>> assumption is just that but I'm assuming if this was a bug for all >>>>>>>> TeleDongles it would have been found before now. I "discovered" >>>>>>> this issue >>>>>>>> when I attempted to use AltosDroid v1.8.5 in the field with my >>>>>>> TeleGPS 1.0 >>>>>>>> and I couldn't get telemetry to work at all. So I attempted some >>>>>>> bench >>>>>>>> testing over the weekend and I believe I've identified a bug in the >>>>>>> newer >>>>>>>> software stacks. >>>>>>>> >>>>>>>> First off, here's my TeleDongle details. >>>>>>> Your TeleDongle v0.2 is running truly ancient firmware, v1.0.2. I'm >>>>>>> not >>>>>>> sure offhand why that would cause the issues you're seeing (Keith may >>>>>>> have more insight here), but the first thing I'd do if the hardware >>>>>>> were >>>>>>> in my hands is update that to current firmware. Because it's an early >>>>>>> product based on the CC1111 RF system on chip, it needs to be pair >>>>>>> programmed (cannot be re-flashed over USB). >>>>>>> >>>>>>> See appendix C.2 in the system manual for more details: >>>>>>> >>>>>>> http://altusmetrum.org/AltOS/doc/altusmetrum.html#_pair_programming >>>>>>> >>>>>>> Either Keith or I can take care of this for you if you don't have easy >>>>>>> access to the right bits and pieces any more. >>>>>>> >>>>>>> By the way, it's always cool to see folks still using some of our >>>>>>> earliest products! >>>>>>> >>>>>>>> 1) Assuming v1.8.6 is affected by this bug as well (I'll test that >>>>>>> in the >>>>>>>> next few days) then can you investigate this issue? >>>>>>> I'm hoping Keith will chime in here about why v1.0.2 TeleDongle >>>>>>> firmware >>>>>>> might work ok with v1.7 but not v1.8.5. I just skimmed through the >>>>>>> release notes and don't have an immediate answer. >>>>>>> >>>>>>> Do you happen to have access to some other TeleDongle or TeleBT, >>>>>>> perhaps >>>>>>> with newer firmware? >>>>>>> >>>>>>>> 2) I've got an EasyMega as mentioned earlier and am planning to use >>>>>>> it in a >>>>>>>> 2 stage stack in April. I will be upgrading the firmware to v1.8.6 >>>>>>> as >>>>>>>> recommended. >>>>>>> Good. >>>>>>> >>>>>>>> - Do I need to be running the latest software to properly >>>>>>> configure >>>>>>>> staging and get correct CSV output post flight? Or will AltOS v1.7 >>>>>>> do this >>>>>>>> correctly with a EasyMega v1.8.6 FC? >>>>>>> I don't think I've ever intentionally tried using older ground station >>>>>>> software to configure newer flight computer firmware. I'd personally >>>>>>> want to use v1.8.6 for everything in this case. >>>>>>> >>>>>>>> 3) AltosDroid - Ideally I'd like to use my phone (Pixel XL) as my >>>>>>> ground >>>>>>>> station in conjunction with my TeleDongle. I've had this work in >>>>>>> the past >>>>>>>> but my AltosDroid software automatically updates and is currently >>>>>>> running >>>>>>>> v1.8.5 as well. Is there somewhere I can download the AltosDroid >>>>>>> v1.7 apk >>>>>>>> in the interim until this bug is resolved? >>>>>>> Have you actually tried it? I'm curious whether this is something >>>>>>> unique to the workstation software build or if the AltosDroid is also >>>>>>> affected. They both share the same library of functionality including >>>>>>> packet decoding, so I'm guessing AltosDroid is affected too. >>>>>>> >>>>>>> Bdale >>>>>>> >>>>>> >>>> _______________________________________________ >>>> altusmetrum mailing list >>>> altusmetrum(a)lists.gag.com >>>> http://lists.gag.com/mailman/listinfo/altusmetrum >>>> >>> _______________________________________________ >>> altusmetrum mailing list >>> altusmetrum(a)lists.gag.com >>> http://lists.gag.com/mailman/listinfo/altusmetrum >>> >> _______________________________________________ >> altusmetrum mailing list >> altusmetrum(a)lists.gag.com >> http://lists.gag.com/mailman/listinfo/altusmetrum >> >

4 years, 5 months

Issues with newer AltOS and TeleGPS applications connecting to TeleGPS with old TeleDongle

by Plugger Lockett

Hi Keith and Bdale, I believe I've identified an issue with the AltOS and TeleGPS applications when using an original TeleDongle for telemetry. The old TeleDongle assumption is just that but I'm assuming if this was a bug for all TeleDongles it would have been found before now. I "discovered" this issue when I attempted to use AltosDroid v1.8.5 in the field with my TeleGPS 1.0 and I couldn't get telemetry to work at all. So I attempted some bench testing over the weekend and I believe I've identified a bug in the newer software stacks. First off, here's my TeleDongle details. I started the process by upgrading my TeleGPS firmware. Not that it was needed or necessary but I prefer to run up to date software if at all possible so I took the opportunity to update both my TeleGPS and EasyMega to firmware version 1.8.5. Both updates were successful. So after I attempted to test the connection to the TeleGPS with a Windows 10 1803 build laptop running AltOS 1.8.5 and TeleGPS software v1.8.5. Below are the results of those tests. Strangely it appears that both applications are receiving some data from the TeleGPS radio, but it's not being interpreted/displaying correctly. AltOS v1.8.5 output TeleGPS Software v1.8.5 output So I reverted back to another laptop (also Windows 10, build 1803) that is my "known good config" TeleGPS Telemetry host. As soon as I opened the TeleGPS app with my TeleDongle plugged in I was receiving successful telemetry data automatically within ~10 seconds, as expected. I fired up the AltOS app on the same host and that also connected fine. So I checked my software version on the working host, both the TeleGPS and AltOS apps were running version 1.7. So I then went back to the original laptop and downgraded both the TeleGPS and AltOS applications from v1.8.5 to v1.7 and ran the tests again. Both worked successfully (see below) AltOS v1.7 output TeleGPS Software v1.7 output I was running these tests indoors so I'm unconcerned with the lack of GPS lock. I then uninstalled v1.7 of each application and reinstalled v1.8.5 and retested and confirmed v1.8.5 didn't work. I then rolled back to v1.7 as I need telemetry working, tested, and everything worked fine. But this led me to a few questions. 1) Assuming v1.8.6 is affected by this bug as well (I'll test that in the next few days) then can you investigate this issue? 2) I've got an EasyMega as mentioned earlier and am planning to use it in a 2 stage stack in April. I will be upgrading the firmware to v1.8.6 as recommended. - Do I need to be running the latest software to properly configure staging and get correct CSV output post flight? Or will AltOS v1.7 do this correctly with a EasyMega v1.8.6 FC? 3) AltosDroid - Ideally I'd like to use my phone (Pixel XL) as my ground station in conjunction with my TeleDongle. I've had this work in the past but my AltosDroid software automatically updates and is currently running v1.8.5 as well. Is there somewhere I can download the AltosDroid v1.7 apk in the interim until this bug is resolved? If you have any questions please let me know. Regards, Andrew Hamilton

4 years, 5 months

[AD] Altus Metrum announces AltOS 1.8.7

by Keith Packard

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 devices. If you have a TeleBT v4.0 device, you will want to re-flash using this version of the ground software to ensure your unit has the correct RF calibration value. AltosUI, TeleGPS and MicroPeak changes * Poll for new devices while Device dialog is displayed * Wait for device to re-appear when flashing new firmware * Fetch correct TeleBT v4.0 RF calibration values from web site when re-flashing. * Change gyro headings in .csv files from x/y/z to roll/pitch/yaw * Add documentation about Packet Link mode * Add documentation about forcing TeleMini RF parameters to known values. * Use a proxy server for Google Maps to re-enable map images * Fix Java version info in all distributed jar files so that applications will run with standard Mac OS X Java. * Replace JavaApplicationStub for Mac OS X so that applications will run with Oracle Java. AltosDroid changes * Use a proxy server for Google Maps to re-enable map images

4 years, 5 months

Frequency response of extra pyro inputs on TeleMega?

by Stewart Campbell

Hi, I am using the extra four inputs on the TeleMega to provide logging of my servo PWM commands on my Vertical Trajectory System. I was wondering what filtering you have on those inputs and what the logging rate is please? I see there is no capacitor for filtering the input, just a voltage divider, so I assume you are using an IIR filter (or Kalman?) of some sort since the logging trace is quite clean :-) . I am trying to figure out if I should be able to see signals in the region of 2.5Hz (give or take) or perhaps a little faster, or be able to estimate any attenuation or phase shift I might be seeing. Any info would be greatly appreciated. If it is a bit sluggish, is it possible to crank it up a bit faster maybe? Also, what is the logging rate and frequency response on things like XYZ roll, acceleration, etc please Sorry for the tricky questions :-) Thanks Stewart Campbell

4 years, 5 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

altusmetrum October 2018