[OUTDATED] piAware 3.5.3 image - WORKING MLAT REQUIRES MANUAL UPDATE

I got this to work: The Pi “image” based on piAware 3.5.3. I am seeing the occasional airplane! (But not as many as I would expect... I may need a better antenna or placement...) in any case, to also look at 978Mhz data, can I use one of the same FlightAware receivers? I currently have the blue one, I am thinking I may need the orange one for a different frequency range as it is unfiltered.

The FlightAware page is telling me that MLAT is not enabled. I must have missed something in the setup. What do I need to do to enable it?

Thanks for your help! This is a fun project.

 

So, do I edit the port in that script such that it matches the zCon entry? I went and picked one of the 51xxx entries at random from the list on the Custom Feeds and set it in the menu. I then went and edited the netcat script and changed the port # in 2 places on the line. I'm still not seeing the traffic on the map. What am I not doing correctly? Thanks for the help.

 

I've been feeding my custom port for 5 days now successfully. I filled out the form to request a name for it around the same time but haven't seen my name pop up on the receivers list yet.

 

I was neglecting the all-important "Reboot Pi" step. All working now and I'm registering my feed. Thanks for the help!

 

What is the best way to

- Update piaware (via their website?)
- and adsbexchange?

I am looking to keep adsbexchange client up to date via command line.

Thanks!

 

Hi Marcin,

thanks for your quick reply. Yes, for piaware I also think this is best.

Looking forward to an idea how to update adsb exchange via CLI.

 

I downloaded ADSBX Pi image 3.5.3.2.1 twice but and installed it on to SD card but both times it did not work (red light on Pi just flashed), I extracted the image and found it was corrupted did a 3rd download and it to is corrupted, just wondering if others may have had this issue.

 

The adsbx image files are fine here
What I have found out that may be the cause is the micro sd card is been corrupted. Most sd cards on the market don't have built in protection from levelling.
Leveling is where an sd card keeps writing to the same spot rather than spreading out the wear evenly all over the card
I have found and recommend now Samsung EVO cards up to 32 gb only

 

In my case it is the actual zip download that is corrupted not the SD card I did suspect the card only used once for 3 pictures, but on a brand new unused card it to failed. it's a bit hard to diagnose on the Pi as the Pi won't boot up and on my computer only can look at certain files only. Unless the new card is an issue as well.

 

Try a fresh download as the image files here are not corrupted
As I stated most sd cards don't have levelling protection
I have found that even new sd cards with no levelling protection get corrupted from just simply writing a fresh image
Check on the web and find out if your brand of sd card has levelling protection

 

OK thanks I'll keep on susing it out, have a coldy and re think.

 

OK found the issue, it wasn't the SD card, I've suspected I might be having issues with the SSHD on the computer as odd weird things are happening every now and then , I downloaded again but on to a USB flash drive and then onto the SD card and it now works. so in this case a SSHD is going dodgy on my computer.

 

How do you run the PUTTY terminal program with this image, I've tried adding an empty ssh file (no extension) (using Windows) to the boot directory but it seems to get erased every time I load the card into the pi.
I've got the image working ok and sharing to FA but I want to add other recipients (like FR24)
I'm using this image because I believe it's the only way of using the Beast receiver with the pi - I have another pi up and running using a dongle and I have that sharing to many recipients without a problem
Paul

 

Ok, thanks, I assume this goes in the PUTTY host name box, could you give me a link to the other thread, it might be useful to me