Differences

This shows you the differences between two versions of the page.

--- waoarc25-kit-builds:gi3jmc [2025/07/30 20:07] – [The Hardware Interlude.] gi3jmc
+++ waoarc25-kit-builds:gi3jmc [2025/07/30 20:47] (current) – [Software Saga - Part 2] gi3jmc
@@ Line 78: / Line 78: @@
 {{:waoarc25:wsprkit-filter-installed.jpg?direct&600|}}
 </WRAP>\\
-<WRAP left round box half>
+<WRAP centre round box full>
 |{{:waoarc25-kit-builds:gi3jmc:wsprypi_tower_1.jpg?direct&600|}} | {{ :waoarc25-kit-builds:gi3jmc:wsprypi_tower_2.jpg?direct&600|}}|
-</WRAP>//
+</WRAP>\\
 ----
 ==== Software Saga - Part 2 ====
-Debugging here
+<WRAP left round box half>
+I temporarily connected a long piece of wire for testing, dangling the end of it out of the window.  The trimmer variable resistor was also rotated anti-clockwise to decrease the output signal strength.
+Transmission was enabled on the wsprrypi configuration page, and I started WSJT-X to check that a signal was getting transmitted, and that it got decoded successfully.
+As you can see in the waterfall image, something was quite wrong.
+</WRAP>
+<WRAP left round box half>
+{{:waoarc25-kit-builds:gi3jmc:wspr-waterfall-bad-signal1.png?direct&600|}}
+</WRAP>\\
+<WRAP left round box half>
+Wondering if I had some kind of faulty Pi Zero2W, I moved the hat and the MicroSD card to a Pi4 appropriated from my digital voice hotspot.  The transmission was the same weirdly stretched out signal that lasted for 900-ish seconds instead of the 110 seconds that WSPR-2 is supposed to.
+I resorted to testing the TAPR image dated April 2021, but was less than thrilled at the prospect of running a very out-of-date operating system.  It worked
+</WRAP>
+<WRAP left round box half>
+|{{:waoarc25-kit-builds:gi3jmc:wspr-waterfall-bad-signal2.png?direct&275|}} |{{:waoarc25-kit-builds:gi3jmc:wspr-waterfall-good-signal1.png?direct&275|}} |
+|broken wsprrypi on the Pi 4B |Working TAPR image |
+</WRAP>\\
+<WRAP left round box half>
+I consulted with the WAOARC25 Kit team, but for a time we could not figure out why my installation was broken, but Tom 2E0JJI's prototype using the same software setup was working fine.  After having a look at an image of my MicroSD card, 2E0JJI noticed that I had version 2.1.1 of the wsprrypi software installed, where his prototype was still on version 2.0.1.
+After a short time, Tom got me to try installing the software on the Pi Zero 2W with a modified command, forcing it to use version 2.0.1.  If you were wondering why the installation guide has such a different install command than the actual documentation for wsprrypi, you've just found the answer!
+Version 2.0.1 worked well with transmissions appearing as expected on the waterfall in WSJT-X, and were also getting decoded sucessfully.  Tom then wondered if it would also work on a Pi 4, so I did some more hat-shuffling and started it up.  It worked on the Pi 4 without a problem.
+I submitted a bug report on the wsprrypi github[[https://github.com/lbussy/WsprryPi/issues/215]] and at the time of writing, the developer is investigating.
+As part of the testing they have asked me to use a 64-bit version of the Raspberry OS and install the software (although I don't think that configuration is supported just yet).  It has been running temporarily connected to the 9:1 with about 20m wire that is normally used by my packet node (GB7BMY) on 40m, and seems to be doing well.
+</WRAP><WRAP left round box half>
+{{:waoarc25-kit-builds:gi3jmc:wspr-beacon-map.png?direct&600|}}
+</WRAP>\\
 ----