Author Topic: RS232 jamming  (Read 550 times)

Offline LePaul

  • Platinum Member
  • ******
  • Posts: 7988
RS232 jamming
« Reply #15 on: October 07, 2007, 12:19:30 AM »
Hornet

The product I used to work for (The Capn nav software that all Coast Guard vessels have) got calls about that a lot from the civilian side.

While impractical for the air, we'd ask customers to "capture" the NMEA 0183 data in HyperTerminal, then email it to use.  Viewing the data, you could see that the coordinates would be fine, then show random odd readings several hundred miles away, then fine.  Our software would endure X amount of these random hits til declaring the GPS input as bad.

If it was bad all around, then we'd speculate about wiring (noise, etc).  But to have good data, then bad, then get it back, seemed to just be a bad spot in regards to signal coverage.

I dont know if the AIR GPSs have a means to debug like this, though.  Usually these would be posted as known problem areas.

Offline DREDIOCK

  • Plutonium Member
  • *******
  • Posts: 17775
RS232 jamming
« Reply #16 on: October 07, 2007, 01:49:40 AM »
Quote
Originally posted by Meatwad
Around here there is a big natural gas pipeline and an oil pipeline. When you pass over these in spray and spreader trucks, it temporally screws up the GPS and the guidance lightbars in the trucks.

Why would a pipeline cause that


Maybe its not really a pipeline.
Maybe they just want you to think that :noid
Death is no easy answer
For those who wish to know
Ask those who have been before you
What fate the future holds
It ain't pretty

Offline Hornet33

  • Gold Member
  • *****
  • Posts: 2487
RS232 jamming
« Reply #17 on: October 07, 2007, 05:04:44 AM »
Quote
Originally posted by LePaul
Hornet

The product I used to work for (The Capn nav software that all Coast Guard vessels have) got calls about that a lot from the civilian side.

While impractical for the air, we'd ask customers to "capture" the NMEA 0183 data in HyperTerminal, then email it to use.  Viewing the data, you could see that the coordinates would be fine, then show random odd readings several hundred miles away, then fine.  Our software would endure X amount of these random hits til declaring the GPS input as bad.

If it was bad all around, then we'd speculate about wiring (noise, etc).  But to have good data, then bad, then get it back, seemed to just be a bad spot in regards to signal coverage.

I dont know if the AIR GPSs have a means to debug like this, though.  Usually these would be posted as known problem areas.



You worked on the Capn program?? Man I hated that software. I used to get tech assist calls all the time about that thing. We were just starting to field CapnII when I retired. Software was alot better but the laptops HQ purchased for it sucked. Over 50% failure rate right out of the box on the hardware side. I tried to stay as far away from that project as I could.
AHII Con 2006, HiTech, "This game is all about pissing off the other guy!!"

Offline LePaul

  • Platinum Member
  • ******
  • Posts: 7988
RS232 jamming
« Reply #18 on: October 07, 2007, 05:20:40 AM »
I was with em from 1999 til 2004, when I left we had been sending them the DNC versions with the chart quilting, etc.