Raspberry Pi 3 B+ testing

[cyoung]

Testing image: https://www.reddit.com/r/stratux/comments/85nqif/rpi3b_image/

After writing the image, the main .sh updates can be used to bring the image up to v1.5b2. The .sh updates should fix the i2c issues, as well.

Anyone that has done testing, please add your experiences here.

[jocamero]

I’ve been using a 3 B+ for many months now without any (related?) issues. Any specific feedback you’re looking for?

[jocamero]

Per the Wiki here's the link to the update process: https://imgur.com/a/sKsjt I don't seem to recall it being an incremental update process. I went directly to the latest version. Also, I think the only supported way to update is via the web GUI and the .sh files unless something has changed.

tl;dr - get the latest .sh file here: https://github.com/cyoung/stratux/releases/ and upload via the web GUI

I'm still trying to track down documentation

[apr911]

Broke my Pi3B and wasn't paying attention/didn't realize it wasn't fully supported when I bought the new one which was a 3B+. I have a spare 3B at home but I'm currently on the road so for now it's make do with the 3B+ until I get home this time next month.

It seems to take forever to connect to any towers and when I do connect, I usually only get a "marginal" connection at best.

I am using the vk-162 external GPS (works great so at least I still get track logs) and the v2 antennas (want to get a 978v3 but doesn't fit the summitlink case and would need to wait until I have a normal 3B or have resolved this issue first to limit variables anyway)

There are a couple variables I am trying to work through but thought I'd post the comment here and see if there were any suggestions.

Variables to work through:

1. Confirm Antennas are correct. - I didn't really change my build aside from swapping out the board but it's possible the 1080 and 978 SDR's got swapped around. That being said, I can just barely make out the markings on the 978 SDR so Im fairly sure I have the antenna's paired to the correct SDR and I do pick up equipped traffic, just cant seem to get towers for the non-equipped traffic and weather.

2. Try new Location/Altitudes. As noted by 3b broke on a trip and I'm unfamiliar with reception in my current location (KISM/KGIF). After looking at the ADSB tower maps, I appear to be closer to some towers but further from others than I was back home at KMQS/KOQN/KPTW in PA and 47N/N51/KSMQ in NJ. I know the tower types and altitudes vary so I may just not be close enough to a low-altitude tower in my new location. My most recent flights have also not gotten particularly high usually staying in the 2000-3000 ft range but there is no "terrain" to speak of in the area and I usually get the marginal signal coverage at altitudes of 1000 ft when I am coming back closer in to KISM while get no signal on my departure from KISM and while flying between 2000 and 3000 ft in the vicinity of Davenport, FL and Winter Haven (KGIF) airport. In PA and NJ I've gotten solid connections to multiple towers once a few hundred feet in the air.

3. Try base 1.4r4 build and move up incrementally. I did an incremental upgrade from the "release" version 1.4r4 to 1.4r5 and then on to 1.5r1 and 1.5r2 but didnt stop to do any incremental version testing. As a result it is unclear if the issue existed with the base build or started after one of the upgrades.

4. Interference? Again dont know what's in the area around me or if its an issue with the equipment in the airplane but I did note yesterday that my normally quiet lightspeed headset was quite loud yesterday with white noise/static. I thought at first it was my passenger's mic picking up the wind since we had the window open but closing the window didn't seem to change it and when I commented on it, he suggested it happened in all of their planes and suspected it was some sort of antenna in the area interfering... I dont recall the noise the first time I flew in the area last week in another aircraft but my recollection may be off. I am flying another different aircraft today so if I have the static/white noise again today, will consider possible ground interference further.

5. Other ideas/suggestions?

I'm reimaging the 1.4r4 base build and will give that a try on my flight this afternoon. I'll lose AHRS but considering I dont have a mount for the stratux in my airplane, the AHRS data I get isn't the most accurate anyway and it will help to at least eliminate a variable in the form of version and/or update process.

[wa9als]

Pi 3B works great for me and 1.5b2. The new radios work great (after I exchanged once with Amazon). It appears I can confirm what others have said about new uat radio not only being lower power, but has increased sensitivity for towers and keeping them. Yay!

Sent from my iPhone

On Mar 15, 2019, at 7:53 AM, apr911 [email protected] wrote:

Broke my Pi3B and wasn't paying attention/didn't realize it wasn't fully supported when I bought the new one which was a 3B+. I have a spare 3B at home but I'm currently on the road so for now it's make do with the 3B+ until I get home this time next month.

It seems to take forever to connect to any towers and when I do connect, I usually only get a "marginal" connection at best.

I am using the vk-162 external GPS (works great so at least I still get track logs) and the v2 antennas (want to get a 978v3 but doesn't fit the summitlink case and would need to wait until I have a normal 3B or have resolved this issue first to limit variables anyway)

There are a couple variables I am trying to work through but thought I'd post the comment here and see if there were any suggestions.

Variables to work through:

Confirm Antennas are correct. - I didn't really change my build aside from swapping out the board but it's possible the 1080 and 978 SDR's got swapped around. That being said, I can just barely make out the markings on the 978 SDR so Im fairly sure I have the antenna's paired to the correct SDR and I do pick up equipped traffic, just cant seem to get towers for the non-equipped traffic and weather.

Try new Location/Altitudes. As noted by 3b broke on a trip and I'm unfamiliar with reception in my current location (KISM/KGIF). After looking at the ADSB tower maps, I appear to be closer to some towers but further from others than I was back home at KMQS/KOQN/KPTW in PA and 47N/N51/KSMQ in NJ. I know the tower types and altitudes vary so I may just not be close enough to a low-altitude tower in my new location. My most recent flights have also not gotten particularly high usually staying in the 2000-3000 ft range but there is no "terrain" to speak of in the area and I usually get the marginal signal coverage at altitudes of 1000 ft when I am coming back closer in to KISM while get no signal on my departure from KISM and while flying between 2000 and 3000 ft in the vicinity of Davenport, FL and Winter Haven (KGIF) airport. In PA and NJ I've gotten solid connections to multiple towers once a few hundred feet in the air.

Try base 1.4r4 build and move up incrementally. I did an incremental upgrade from the "release" version 1.4r4 to 1.4r5 and then on to 1.5r1 and 1.5r2 but didnt stop to do any incremental version testing. As a result it is unclear if the issue existed with the base build or started after one of the upgrades.

Other ideas?

I'm reimaging the 1.4r4 base build and will give that a try on my flight this afternoon. I'll lose AHRS but considering I dont have a mount for the stratux in my airplane, the AHRS data I get isn't the most accurate anyway and it will help to at least eliminate a variable in the form of version and/or update process.

Cross-posted to Reddit Conversation.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[apr911]

Tried swapping the antennas and using the base build 1.4r4 still marginal.

Still could be location/altitude and/or interference. I'll be flying a short XC on Tuesday so we'll see if it improves on that flight... If that doesn't do anything then I'm stuck until I am back home where I know I have good reception and can switch back to the regular 3B. I suppose it's also possible I damaged the radio's but wont know that until I can eliminate the other variables of location, 3B+ and image version.

[gmint]

I used a B3+ for several months and had quite a few problems with the stability of the unit. Unfortunately, I THINK this was probably power related. After replacing my power adapter, cable, and ultimately switching back to a 3B, I once again have a stable connection. Of course, since the 3B+ takes more power, that might have been exacerbated by that fact. Otherwise, everything seemed to work as expected.

[cyoung]

@gmint - Were you using the above testing image? Which radios and accessories were you using? If using two NooElecs, the unit was probably drawing over 1A total. That brings us back to our early power issues.

[gmint]

@cyoung - I was using the testing image referenced which I brought up to 1.5b2 with the .sh updates. I was using the v2 radios sold by stratux on Amazon (not the NooElecs). Honestly, I really think it was the 12v power supply I was using (my plane is old enough that it has a cigarette lighter) but when it started giving me issues, I started replacing cables, and using different adapters and all of that stuff. Eventually I just decided to go back to the 3B to really eliminate all of the possibilities. After that, I ended up swapping the power adapter after that and I've had a stable connection so far (I'm using ethernet instead of WiFi). Unfortunately I don't have great data for isolating any issues strictly to the 3B+. At the worst, I think the 3B+ just made it worse since I did seem to have good luck for a period of time.

Personally, I wish they'd ditch the micro-USB for power. Stratux is not the first time I've had power issues on a RPi and I think a ton of that is due to the tiny connector. Maybe we'll get USB-C on the RPi one day. Also something that crossed my mind—have you considered the possibility of Stratux on something more "industrial grade" like the balenaFin device?

[cyoung]

Stratux is not the first time I've had power issues on a RPi and I think a ton of that is due to the tiny connector.

Most of our power issues are from people using junk cables. The connector is fine to 2A or more.

[gmint]

Stratux is not the first time I've had power issues on a RPi and I think a ton of that is due to the tiny connector.

Most of our power issues are from people using junk cables. The connector is fine to 2A or more.

Oh I agree that technically the connector is fine, but in real world use, over time it becomes loose and very prone to becoming dislodged.

[rhole]

I would suggest that in aircraft use with the relatively high vibration environment that no push-in connector be installed without providing support for the inserted connector. The installer should provide both strain and vibration relief. This applies to, including but not limited, micro-USB, USB, the small polar power connectors. Anything which can be pulled out will, eventually, fall out.

Rick Hole

From: gmint [mailto:[email protected]] Sent: Wednesday, June 5, 2019 2:35 PM To: cyoung/stratux [email protected] Cc: Subscribed [email protected] Subject: Re: [cyoung/stratux] Raspberry Pi 3 B+ testing (#768)

Stratux is not the first time I've had power issues on a RPi and I think a ton of that is due to the tiny connector.

Most of our power issues are from people using junk cables. The connector is fine to 2A or more.

Oh I agree that technically the connector is fine, but in real world use, over time it becomes loose and very prone to becoming dislodged.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cyoung/stratux/issues/768?email_source=notifications&email_token=AEIIE7PGZT5R6YWVKQY5A6TPZAPPBA5CNFSM4GZ4HRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXA55FA#issuecomment-499244692 , or mute the thread https://github.com/notifications/unsubscribe-auth/AEIIE7PTABNOMSFI3IZ7TY3PZAPPBANCNFSM4GZ4HRJA . https://github.com/notifications/beacon/AEIIE7PHA4ROUFT42RHLHJTPZAPPBA5CNFSM4GZ4HRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXA55FA.gif

[gmint]

I would suggest that in aircraft use with the relatively high vibration environment that no push-in connector be installed without providing support for the inserted connector. The installer should provide both strain and vibration relief. This applies to, including but not limited, micro-USB, USB, the small polar power connectors. Anything which can be pulled out will, eventually, fall out.

I agree fully. I will likely hot glue the connector in once I'm done tinkering around with my unit.

[pvanessen]

won't compile on my 3B+ :(

make xdump978 xdump1090 xgen_gdl90 fancontrol make[1]: Entering directory '/home/phillip/stratux' cd dump978 && make lib make[2]: Entering directory '/home/phillip/stratux/dump978' gcc -c -O2 -g -Wall -Werror -Ifec -fpic -DBUILD_LIB=1 dump978.c fec.c fec/decode_rs_char.c fec/init_rs_char.c gcc -shared -lm -o ../libdump978.so dump978.o fec.o decode_rs_char.o init_rs_char.o make[2]: Leaving directory '/home/phillip/stratux/dump978' sudo cp -f ./libdump978.so /usr/lib/libdump978.so sudo: unable to resolve host stratux git submodule update --init Submodule 'dump1090' (https://github.com/stratux/dump1090) registered for path 'dump1090' Submodule 'goflying' (https://github.com/cyoung/goflying) registered for path 'goflying' Cloning into '/home/phillip/stratux/dump1090'... Cloning into '/home/phillip/stratux/goflying'... Submodule path 'dump1090': checked out '9a4fb850937565cfeadd1e5889cddbf93f45faf5' Submodule path 'goflying': checked out '0ba3e51be74b4848488e06ec0fee74ebaa7ef705' cd dump1090 && make make[2]: Entering directory '/home/phillip/stratux/dump1090' fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W pkg-config --cflags librtlsdr -c dump1090.c -o dump1090.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c anet.c -o anet.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c interactive.c -o interactive.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c mode_ac.c -o mode_ac.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c mode_s.c -o mode_s.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c net_io.c -o net_io.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c crc.c -o crc.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c demod_2000.c -o demod_2000.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c demod_2400.c -o demod_2400.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c stats.c -o stats.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c cpr.c -o cpr.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c icao_filter.c -o icao_filter.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c track.c -o track.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c util.c -o util.o fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c convert.c -o convert.o gcc -g -o dump1090 dump1090.o anet.o interactive.o mode_ac.o mode_s.o net_io.o crc.o demod_2000.o demod_2400.o stats.o cpr.o icao_filter.o track.o util.o convert.o -lpthread -lm -lrt pkg-config --libs librtlsdr fatal: No names found, cannot describe anything. gcc -DMODES_DUMP1090_VERSION="" -O2 -g -Wall -Werror -W -c view1090.c -o view1090.o gcc -g -o view1090 view1090.o anet.o interactive.o mode_ac.o mode_s.o net_io.o crc.o stats.o cpr.o icao_filter.o track.o util.o -lpthread -lm -lrt make[2]: Leaving directory '/home/phillip/stratux/dump1090' go get -t -d -v ./main ./godump978 ./uatparse ./sensors github.com/skelterjohn/go.matrix (download) github.com/gorilla/websocket (download) github.com/kidoman/embd (download) github.com/golang/glog (download) github.com/dustin/go-humanize (download) github.com/jpoirier/gortlsdr (download) github.com/mattn/go-sqlite3 (download) github.com/prometheus/client_golang (download) github.com/beorn7/perks (download) github.com/golang/protobuf (download) github.com/prometheus/client_model (download) github.com/prometheus/common (download) github.com/matttproud/golang_protobuf_extensions (download) github.com/prometheus/procfs (download) github.com/ricochet2200/go-disk-usage (download) github.com/stratux/serial (download) github.com/takama/daemon (download) github.com/tarm/serial (download) Fetching https://golang.org/x/sys/unix?go-get=1 Parsing meta tags from https://golang.org/x/sys/unix?go-get=1 (status code 200) get "golang.org/x/sys/unix": found meta tag get.metaImport{Prefix:"golang.org/x/sys", VCS:"git", RepoRoot:"https://go.googlesource.com/sys"} at https://golang.org/x/sys/unix?go-get=1 get "golang.org/x/sys/unix": verifying non-authoritative meta tag Fetching https://golang.org/x/sys?go-get=1 Parsing meta tags from https://golang.org/x/sys?go-get=1 (status code 200) golang.org/x/sys (download) github.com/uavionix/serial (download) Fetching https://golang.org/x/net/icmp?go-get=1 Parsing meta tags from https://golang.org/x/net/icmp?go-get=1 (status code 200) get "golang.org/x/net/icmp": found meta tag get.metaImport{Prefix:"golang.org/x/net", VCS:"git", RepoRoot:"https://go.googlesource.com/net"} at https://golang.org/x/net/icmp?go-get=1 get "golang.org/x/net/icmp": verifying non-authoritative meta tag Fetching https://golang.org/x/net?go-get=1 Parsing meta tags from https://golang.org/x/net?go-get=1 (status code 200) golang.org/x/net (download) Fetching https://golang.org/x/net/ipv4?go-get=1 Parsing meta tags from https://golang.org/x/net/ipv4?go-get=1 (status code 200) get "golang.org/x/net/ipv4": found meta tag get.metaImport{Prefix:"golang.org/x/net", VCS:"git", RepoRoot:"https://go.googlesource.com/net"} at https://golang.org/x/net/ipv4?go-get=1 get "golang.org/x/net/ipv4": verifying non-authoritative meta tag Fetching https://golang.org/x/net/websocket?go-get=1 Parsing meta tags from https://golang.org/x/net/websocket?go-get=1 (status code 200) get "golang.org/x/net/websocket": found meta tag get.metaImport{Prefix:"golang.org/x/net", VCS:"git", RepoRoot:"https://go.googlesource.com/net"} at https://golang.org/x/net/websocket?go-get=1 get "golang.org/x/net/websocket": verifying non-authoritative meta tag go build -ldflags "-X main.stratuxVersion=git describe --tags --abbrev=0 -X main.stratuxBuild=git log -n 1 --pretty=%H" -p 4 main/gen_gdl90.go main/traffic.go main/gps.go main/network.go main/managementinterface.go main/sdr.go main/ping.go main/uibroadcast.go main/monotonic.go main/datalog.go main/equations.go main/sensors.go main/cputemp.go main/lowpower_uat.go go get -t -d -v ./main go build -ldflags "-extldflags -static -X main.stratuxVersion=git describe --tags --abbrev=0 -X main.stratuxBuild=git log -n 1 --pretty=%H" -p 4 main/fancontrol.go main/equations.go main/cputemp.go # command-line-arguments /usr/local/lib/go/pkg/tool/linux_arm/link: running gcc failed: exit status 1 /usr/bin/ld: cannot find -lwiringPi /tmp/go-link-547846821/000002.o: In function `_cgo_b0c710f30cfd_C2func_getaddrinfo': cgo_unix.cgo2.c:(.text+0x678): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking collect2: error: ld returned 1 exit status

Makefile:21: recipe for target 'fancontrol' failed make[1]: *** [fancontrol] Error 2 make[1]: Leaving directory '/home/phillip/stratux' Makefile:14: recipe for target 'all' failed make: *** [all] Error 2

[Ergonomicmike]

I ran a B+ for months. Never had a problem (that I know of). Like @jocamero , am wondering what problems one should be on the alert for.

[Ergonomicmike]

I noticed that Fry's Electronics is selling the Pi 3 B+ for $13, on sale clearance.

That model didn't last long.

What's wrong with the B+?

[wa9als]

Fry’s heard it doesn’t work with Stratux.

On Mon, Sep 23, 2019 at 4:08 PM Ergonomicmike [email protected] wrote:

I noticed that Fry's Electronics is selling the Pi 3 B+ for $13, on sale clearance.

That model didn't last long.

What's wrong with the B+?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cyoung/stratux/issues/768?email_source=notifications&email_token=AJII6MZEX4J6SLWXZC6ZM2TQLEO3JA5CNFSM4GZ4HRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7MDIRA#issuecomment-534262852, or mute the thread https://github.com/notifications/unsubscribe-auth/AJII6M66NG7GPO6PCERSA4LQLEO3JANCNFSM4GZ4HRJA .

[ssokol]

Biggest complaint with the 3B+ is the power draw. It takes quite a bit more than the 3B, and you don't get a really significant bump in performance.

That said, I think it's more an issue for Frye's than it is for the 3B+. They want to clear it out to make way for the Pi 4. (Not that they're short of available shelf space these days....) From what I recall, the RPi Foundation has committed to continuing the 3B+ for several years.

[JohnMarzulli]

The Pi3B+ makes an excellent processor for my HUD project if you don’t want to run the HUD on the Stratux itself.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Steven Sokol [email protected] Sent: Monday, September 23, 2019 1:55 PM To: cyoung/stratux Cc: Subscribed Subject: Re: [cyoung/stratux] Raspberry Pi 3 B+ testing (#768)

Biggest complaint with the 3B+ is the power draw. It takes quite a bit more than the 3B, and you don't get a really significant bump in performance.

That said, I think it's more an issue for Frye's than it is for the 3B+. They want to clear it out to make way for the Pi 4. (Not that they're short of available shelf space these days....) From what I recall, the RPi Foundation has committed to continuing the 3B+ for several years.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/cyoung/stratux/issues/768?email_source=notifications&email_token=AFQDC3CD3OCPQ7KUPWD37R3QLEUKJA5CNFSM4GZ4HRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7MHSLQ#issuecomment-534280494, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFQDC3GVT6VMK5CP42YY6ODQLEUKJANCNFSM4GZ4HRJA.

[Ergonomicmike]

Okay on the power draw. I never noticed it. (Perhaps offset by the lower power SDR's.) I liked the B+ because it was quiet, RFI-wise, in the Glasair. I didn't do an exhaustive check of freqs, but I never had any noticeable Stratux-noise in the NAV/COM with the B+.

The Fry's store near me (Phx) is HUGE. And empty of people most of the time nowadays. Also empty of stock. I'm guessing it must cost $50,000/mo just in electricity to air condition the building in our summers. I can't image how the store can stay in business much longer.

[ssokol]

The latest batch of B3 units I've purchased have had the same metal shield caps on the primary ICs that the B3+ has. I've not done a side-by-side check, but I expect that will help bring the EMI level down.

Yeah, Fry's here (Bay Area) are all ghost towns. A reversal of fortune on almost the same level as Blockbuster Video...

[Ergonomicmike]

Here's another problem with the B+ that's not software related, but makes for a reliability problem in airplanes. The metal shield that surrounds the microSD card can detach from the PCB. The shield acts as part of the capture mechanism/cage for the card itself. So if the cage breaks, no electrical contact for the card. (Found this out after our Glasair purchaser sent me my Stratux back.)

[apr911]

@Ergonomicmike the hardware problem you describe exists in at least the 3b, 3b+ and even the new 4.

Its how I ended up using a 3b+ on my trip in the first place; the sd card cage on the 3b I had with me separated from the pcb and prevented the card and software from being read. Either I messed up ordering or the company I ordered a replacement from shipped the wrong one because I received a 3b+.

[Ergonomicmike]

Thanks. I'm confused because, IIRC, the 3B has the spring loaded "clicker" to hold the card in place. Whereas my card is held in by friction on the B+.

In any event, I'm going to try to solder the tangs down today on the B+. (If I can find high power magnifiers.)

[Ergonomicmike]

Soldering the tangs back down to the PCB worked. My 3 B+ Stratux is back up, running 1.6r1. (And I hot glued the micro-antenna connector in place on the 978 SDR.)

[Marliwahoo]

I'd love to try a version of stratux hat would work with the rpi4. Instructions or a working image would be great.

[VirusPilot]

A while ago the following worked for Pi4 (based in the Stratux Europe Fork):

• sudo -s
• rm /usr/local/lib/librtlsdr.*
• rm /usr/local/include/rtl-sdr*
• apt install librtlsdr0 librtlsdr-dev
• cd /tmp
• wget https://project-downloads.drogon.net/wiringpi-latest.deb
• sudo dpkg -i wiringpi-latest.deb
• cd ~/stratux
• make -B && make install

RFC!!

[MysticCobra]

Thanks. I'm confused because, IIRC, the 3B has the spring loaded "clicker" to hold the card in place. Whereas my card is held in by friction on the B+.

The 3B used a friction-fit SD card slot. Spring loaded slots were last used in the RPi 2 series.

[nikita-visnevski]

Folks, I am having a problem getting correct RPi 3B at this point. I order it and get 3B+ in mail instead. I returned two to Amazon already and have given up on them. Ordered directly from CanaKit. Explicitly picked Pi 3B as they had 3B+ as a separate option. After 14 days of waiting, received it today, opened, and it is 3B+. My point is, can no longer get 3B reliably. I understand all the power issues with 3B+ and 4, but this is the reality going forward. Soon these will be the only boards available. I personally power it off the cigarette plug in the plane, so depleting the battery is no real concern. Any way we can get stable release supporting 3B+? I tried to mess with this experimental build. Something is not right with it. Just voicing frustration over the situation. Are there any fundamental issues preventing Stratux support of 3B+ and 4? If not, any way to actually reliably supporting it? Thanks

[cyoung]

@nikita-visnevski - What issues did you have with the experimental build?

[nikita-visnevski]

AHRS does not seem to work for me in that one. I think it is based off of the earlier version of Stratux which did not support full AHRS protocol compatible with ForeFlight. It could be I am doing something wrong too.