Recommended Posts
DSE 5
On Mon, Tues, Wed (yesterday) I jumped with two and three units, stored in my pant pocket, neck bag, and stocking. No issues presented themselves, and the units weren't powered up until we were doing the 10K gear check (they'd been powered up on the ground).
GPS access in this area is generally pretty good on my Droid, although there are places near the pass and of course at the mouth of the Ortega highway where it's not visible.
Migs 0
QuoteQuoteQuoteHere is more food for thought folks Provided by NAVCENT/US Coast Guard:
TEST PERIOD APPROVED BY DEPARTMENT OF DEFENSE JOINT CHIEFS OF STAFF.
TEST LOCATION
EXACT DATES AND TIMES OF TESTING, DURING APPROVED PERIOD, WILL BE DETERMINED BY TEST RANGE EVENT PLANNERS.
GPS NAVIGATION SIGNAL WILL BE UNRELIABLE
WITHIN A: xxx NM Radius of Position
China Lake, CA
(CHLK 11-13)
07 NOV 11 - 16 DEC 11 (Dates/Distance are Approximate)
100 NM RADIUS OF POSITION:
36 09 18N; 117 37 32W
After doing a Radius measurement from China Lake to Lake Elsinore... it is only 23 NM outside of the testing range. This is very possibly that this was the cause of all the signal conflicts over the weekend.
So far the most plausible explanation, although we were competing on the 5th of november.. Any way we can contact these guys and get them to confirm they were testing last weekend?
Here is the contact link and numbers:
http://www.navcen.uscg.gov/?pageName=gpsUserInput
Also, scheduled testing:
http://www.navcen.uscg.gov/pdf/gps/gpsnotices/GPS_Interference.pdf
On Facebook
KrisFlyZ 0
Try before You Buy with Wicked Wingsuits - WingsuitRental.com
Edit to add: How many of you have turned off the FlySight while under canopy, turning off the camera also because you knew that of the 16GB space a lot was used already and you have had so many landings filmed already? I have, I admit it and I know there's a lot out there that I know not yet!
lurch 0
Re: trouble:
I'm thinking most likely its that DOD testing thing.
Things I noticed:
1: In Gransee we powered each unit up until blinky light right before getting in the plane, shutting it off, then restarting at 9k. No jumps were lost, I got green blinking every time, -in- the plane regardless of where in the plane it was. I know the things were ground tested here but I don't think anyone was following that exact procedure to start. When my first data dump got nothing, I started doing this. One jump later I started getting results... may be just coincidence, maybe not. May just be they quit the interference-causing activity at that time. No way to tell.
2: Last jump I kept the GPS turned on all the way up and physically held to the window most of the ride up and watched it. I don't think mountains had anything to do with problem... I had green blinky for most of the ride, then in the last 3000 feet of the climb it began blinking erratically, visibly gaining and losing satellite lock every few seconds. Window view or not, it did it.
Joel was sitting opposite side of plane from me. He had two, both working fine, and offered one to me since it looked like mine was about to conk out entirely. When I reached over to his side of the plane, (left/pilot side) I had mine in hand, and as long as I held it in the same space Joel and Robi were occupying on that side of the plane the erratic blinking stopped and mine worked as well.
I ended up physically holding my wing with both GPS's in it, (one in wing pocket one dropped into wing root) into the left half of the plane's interior so they could get a view out the left windows in the last minutes before exit. Result: Both units worked and recorded roughly the same track. I didn't look at it myself but when Jarno checked em he said they both got stuff and the stuff agreed with each other.
What I'm thinking is either busy/tested satellites making the devices selectively directional, or just the interference itself chewing up the signals on us in-flight.
The jump runs were awesome on this, naturally straight lines home. After every window, from 6000 feet on down was enough time to pull some nice long planeouts and run home. Those post-window planeouts were MUCH longer than the period on the ground in which I was booting the unit and making sure I had a lock. I had units inside my wing where in-flight they had a huge wide view of the sky for as long as they could have wanted. By all logic, even IF they had no lock when I exited, they should have long since got a perfect lock in midflight. Above the mountains, zero obstacles, nothing in between it and sky except 2 layers of nylon fabric. And still, I got nothin till second half of the comp.
Personally I'd put money on Migs' contribution, this DOD notification. Our stuff was getting chewed up in midflight. There was stuff we did differently than Gransee, (exit order, timing, number of jumps per run, whether or not each unit was pre-booted right before boarding) but none of that should have made squat for a difference 45 seconds after exit. But some of us all our stuff was completely wiped out. I'd bet if we held the comp today everything'd work fine. Seems kinda open and shut case to me... DOD says "we're fucking with it and it'll be unreliable today" and it was.
We were on the edge of their interference zone and I bet we got a good dose of it. I wouldn't be surprised if my directional observations in the plane actually meant that when I was holding the GPS to the pilots side, the bulk of the plane was shielding the device from some of the interfering signal. Maybe they were generating a lot of HF radio noise with some high energy multibilliondollar killer whizbang. The DOD is known to have a lot of such toys. China Lake wouldn't happen to be roughly due north or due south of us would it?
Anyway my bet is, we get no such issues with future comps unless the DOD happens to have issued such a notice that day, too.
-B
Migs 0
Quote
China Lake wouldn't happen to be roughly due north or due south of us would it?
Anyway my bet is, we get no such issues with future comps unless the DOD happens to have issued such a notice that day, too.
-B
123 NM Northeast of Lake Elsinore.
On Facebook
vidiot 0
QuoteHere is more food for thought folks Provided by NAVCENT/US Coast Guard:
TEST PERIOD APPROVED BY DEPARTMENT OF DEFENSE JOINT CHIEFS OF STAFF.
TEST LOCATION
EXACT DATES AND TIMES OF TESTING, DURING APPROVED PERIOD, WILL BE DETERMINED BY TEST RANGE EVENT PLANNERS.
GPS NAVIGATION SIGNAL WILL BE UNRELIABLE
WITHIN A: xxx NM Radius of Position
China Lake, CA
(CHLK 11-13)
07 NOV 11 - 16 DEC 11 (Dates/Distance are Approximate)
100 NM RADIUS OF POSITION:
36 09 18N; 117 37 32W
This could very well be the reason and would fit my suspicion of jamming.
This could also explain why the units worked on side of the plane and not on the other. Was this maybe the side pointing to Crystal lake?
[Edit: From what Lurch describes (Signal was lost on the way up and re-aquired ont the way down): Is it possible the mountains were actually shielding the jamming signal?]
Does anyone know what kind of tests were performed? From the description it definitly sounds like jamming tests. Maybe someone wants to let the Army know how succesful they were? ;-)
FYI - the same units have worked flawlessly before without repeaters (which are absolutely unnecessary in normal jump planes like Otters, SkyVans, Caravans, etc.) and AFAIK Spot used the FS in Elsinore before without any problems as can be seen on PPC.
On the comments that there might be better units out there I think I can speak for Michael when saying the FS has the most modern receiver available on the consumer market: a u-blox 6 module.
@Sam [Edit: Mig]: Is there a public link for thess outage informations? Might be worthwhile to put it up on PPC... [Edit: - I see it's already up there]
Klaus
[Edit: 150nm from the Elsinore to the coordinates given]
So far the most plausible explanation, although we were competing on the 5th of november.. Any way we can contact these guys and get them to confirm they were testing last weekend?
Share this post
Link to post
Share on other sites