Hi everyone,
I tried out my fairly new Jolly Logic Altimeter Three (JLA3) today for the first time in a rocket flight.
I did two flights with my Estes Firestorm, in whose airframe I had drilled four tidy holes so that the altimeter could get a good reading.
The JLA3 did a fine job with the first flight, in which I used a B6-2 motor. The flight log downloaded right away to my iPhone just as it was supposed to. Later, when I got home and matched the recorded flight data to the predicted data according to RockSim, everything matched up beautifully.
So far, so good.
Then I flew the Firestorm on a C6-3 motor. I carefully protected the JLA3 with wadding, and I also put wadding aft of the parachute. Thus, going from fore to aft, I had the altimeter wrapped in wadding, then the parachute, then more wadding. I proceeded to fly the rocket, and I recovered it intact.
So here's the first of two anomalies. I had major trouble linking my iPhone to the JLA3 and downloading the data, although I eventually succeeded after numerous attempts. I had already done substantial testing on the JLA3, and I have never before had difficulty using Bluetooth to link the altimeter to my phone.
And then, once I checked my downloaded data, it was way off. RockSim predicted an altitude of between 90 to 100 meters, and the JLA3 was giving me data of half of that (less than 48 meters).
If I hadn't had such trouble linking the JLA3 to the iPhone, I would have thought that the 48 meters was what it was. But given the trouble that I had -- and which I am continuing to have -- with linking, I think that somehow the JLA3 has ceased functioning correctly.
Does anybody have an idea what happened? Can I somehow reboot the JLA3 to restore it to good operation?
Thank you.
Stanley
I tried out my fairly new Jolly Logic Altimeter Three (JLA3) today for the first time in a rocket flight.
I did two flights with my Estes Firestorm, in whose airframe I had drilled four tidy holes so that the altimeter could get a good reading.
The JLA3 did a fine job with the first flight, in which I used a B6-2 motor. The flight log downloaded right away to my iPhone just as it was supposed to. Later, when I got home and matched the recorded flight data to the predicted data according to RockSim, everything matched up beautifully.
So far, so good.
Then I flew the Firestorm on a C6-3 motor. I carefully protected the JLA3 with wadding, and I also put wadding aft of the parachute. Thus, going from fore to aft, I had the altimeter wrapped in wadding, then the parachute, then more wadding. I proceeded to fly the rocket, and I recovered it intact.
So here's the first of two anomalies. I had major trouble linking my iPhone to the JLA3 and downloading the data, although I eventually succeeded after numerous attempts. I had already done substantial testing on the JLA3, and I have never before had difficulty using Bluetooth to link the altimeter to my phone.
And then, once I checked my downloaded data, it was way off. RockSim predicted an altitude of between 90 to 100 meters, and the JLA3 was giving me data of half of that (less than 48 meters).
If I hadn't had such trouble linking the JLA3 to the iPhone, I would have thought that the 48 meters was what it was. But given the trouble that I had -- and which I am continuing to have -- with linking, I think that somehow the JLA3 has ceased functioning correctly.
Does anybody have an idea what happened? Can I somehow reboot the JLA3 to restore it to good operation?
Thank you.
Stanley