altusmetrum August 2018

altusmetrum@lists.gag.com

14 participants
18 discussions

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

EasyMega apogee config recommendations for flights over 100k'

by Plugger Lockett

Hi Everyone, To provide a bit of background, I'm attempting to assist Mike Passaretti with getting an electronics apogee deployment configuration nailed down for his planned flight at Balls this year. His initial plan was to use two Raven 3s to provide all the required deployment events in his flight. Unfortunately his Raven 3s aren't high alt firmware models and it seems there isn't even a high alt firmware available for the Raven 3 boards. Given this we're running into some pretty severe board configuration limitations and about the only way we can get a apogee deployment configuration to work given these limitations is to program around the baro sensor cutting out (apparently this occurs at 104k' MSL) and then add a delay to the event calculated by taking the simulation time it takes to get to 104k', subtract that from the simulation time to apogee, and configure the delay time value to be equal to that value. As you can imagine this is not an entirely ideal approach. Given this I've offered Mike my EasyMega with the latest firmware to use. But I wanted to ask the list what is the recommended method for getting reasonably accurate apogee deployment events to work when you're above the effective range of the baro sensors we use on our various FCs. My expectation is that at worst I can configure the pyro event as a simple timer by enabling the following configurations. Pyro Channel A *Height above pad greater than (m)* enabled and configured for *10,000* meters to ensure Mike's well above ground for the event to occur. *Time Since launch less than (s)* enabled and configured for *85* seconds. *Time Since launch greater than (s)* enabled and configured for *84 * seconds. Would that configuration work as a "pure timer" apogee deployment event envisioned for 84 seconds after liftoff? Is there another way to configure apogee deployment events above 100k' on the EasyMega that would be a smarter or more advantageous way of accomplishing this task instead of a simple timer configuration? Any advice in this area would be much appreciated folks. Kind Regards, Andrew Hamilton

4 years, 6 months

One more newbie TeleMega question

by Gary Lech

I've looked high and low and kinda know the answer but thought I'd ask anyway. Can the TeleMega be configured using the AltosDroid version? It's easy enough to make changes using the AltosUI Windows version but using a smartphone for changing things like the callsign would be a nice feature. Or am I completely missing it somewhere like in a case of refrigerator blindness which my wife likes to tell me? I'm ready to fly 'em. Thanks for all the help, Gary

4 years, 6 months

Re: [altusmetrum] Newbie would like settings confirmation

by Gary Lech

Thank you for that. I knew that was the case but because this was the config set in the previously flown version I thought there was some other thinking. I used the TeleBT and my smarthphone to fire the e-matches for ground testing today. That is a very nice feature. Thanks for all the help Keith. What a great product. Gary -----Original Message----- From: Keith Packard <keithp(a)keithp.com> To: Gary Lech <glech(a)aol.com>; altusmetrum <altusmetrum(a)lists.gag.com> Sent: Mon, Aug 27, 2018 3:26 pm Subject: Re: [altusmetrum] Newbie would like settings confirmation Gary Lech <glech(a)aol.com> writes: > Hopefully the list will accept these embedded screen shots. I've got > this altimeter configured identical to one that has flown ARLISS in > the past but just want to make sure that my understanding is > correct. ARLISS is unique in that it ejects a payload precisely 6 > seconds after apogee. At apogee the first charge blows. Then 6 seconds > later the Pyro Channel A blows. Then 2 seconds later (8 seconds after > apogee) the Pyro Channel B blows. Then at 1000' the Main charge > blows. Is that correct? You've got it configured to fire Channel A correctly (6 seconds after apogee), but Channel B is configured to fire just 2 seconds after apogee. If you want that to fire 8 seconds after apogee, you would want to set the delay to 8 instead of 2. The channels are entirely independent; it doesn't sequence through them, you can use them in any order. -- -keith

4 years, 6 months

APRS time slot?

by Gary Lech

Is there a way to set a time slot value for APRS transmissions? It's not a must have but it would be nice when listening to several TeleMegas on the same frequency. Thanks, Gary - WA7GL

4 years, 6 months

Connection issues with TeleBT on AltosDroid

by Chris Attebery

Hello, I received a new TeleMega over the weekend and I had trouble getting my TeleBT to connect to my tablet whenI first tried to use it. I've had similar issues getting AltosDroid to connect in the past. I've used this TeleBT on this tablet before so it's already paired. I also have a TeleMetrum that I've used with this setup. Here's the procedure I'm using: 1. Start AltosDroid. 2. Turn on TeleBT. I don't see any LEDs turn on at this point. 3. I try to connect to the device from the drop down menu. There's a message " Connecting to XXXX" at the top of the screen. 4. Turn on TeleMega or Telemetrum. After this I plugged the TeleBT into a USB cable on my PC and used Altos to configure the altimeter. At this point AltosDroid started doing announcements and the TeleBT was connected. I turned everything off, unplugged the USB cable and then started a new AltosDroid session. The TeleBT and TeleMega both connected to AltosDroid without any issues. So, am I not understanding how this should work? If I turn on AltosDroid and the TeleBT will they connect before I turn on the TeleMega or does the connection sequence only work if the altimeter is on? Thanks, Chris

4 years, 6 months

Newbie would like settings confirmation

by Gary Lech

Hopefully the list will accept these embedded screen shots. I've got this altimeter configured identical to one that has flown ARLISS in the past but just want to make sure that my understanding is correct. ARLISS is unique in that it ejects a payload precisely 6 seconds after apogee. At apogee the first charge blows. Then 6 seconds later the Pyro Channel A blows. Then 2 seconds later (8 seconds after apogee) the Pyro Channel B blows. Then at 1000' the Main charge blows. Is that correct? Thanks for the help, Gary - WA7GL

4 years, 6 months

TeleMega and TeleBT questions

by Gary Lech

Greetings, I've been studying the TeleMega product in advance of a purchase. From what I've read in the documentation the TeleMega is capable of transmitting APRS packets such that it can be decoded with my TH-D7A or the MobilinkTNC. But in order to receive in-flight telemetry and voice altitude, speed, etc, I would need to use the TeleDongle or TeleBT which uses a proprietary protocol. Does it transmit both packet types in the same flight? Is my understanding correct. All replies are greatly appreciated, Gary TRA/NAR L3 - WA7GL

4 years, 6 months

TeleBT on both USB and BT at the same time

by Gary Lech

Holey moley I tried using my TeleBT connected to Windows using the USB port and then connected my Android smartphone via bluetooth at the same time and was surprised to see that it works. I'm able to monitor 3 TeleMegas simultaneously on both a laptop and a smartphone. Has anybody else done this or am I asking for trouble by testing the communication limits? Gary - WA7GL

4 years, 6 months

TeleMega and Windows BS

by Gary Lech

Help. I have tried 2 different TeleMegas (v3.0) on 2 different PCs running Windows 7 and can't get it to stay connected long enough to configure either one. It will connect for about 5 seconds and then it drops out. I suspect it's a Windows driver/comm port issue issue. What's curious is that I also have an older TeleMega v2.0 and it works just fine. Any suggestions on what to try next. I'm prepping for ARLISS so the countdown clock is running. Cheers, Gary - WA7GL

4 years, 6 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

altusmetrum August 2018