Crashes when "Waiting for next WSPR transmissoin window".

[orsty3001]

Crashes when I try to start wspr on a raspberry pi 1. The only way to recover is unplugg the device and plug it back in.

[itdaniher]

could you take a picture of your test setup? this very well could be a power / grounding issue.

[orsty3001]

Since I posted I tried both the zero and the pi 1. I have also tried with just using the ground pin 9 and all of the grounds tied together. The pi zero gets a little bit further but hangs after about a minute of waiting to transmit instead of instantly like the pi 1 does.

https://i.imgur.com/23MumQz.jpg

[itdaniher]

Oh, if it crashes instantly then it's not likely to be a grounding issue - I'd only expect that to occur on transmission, not launch.

How are you powering the pis in question? Have you tried different variants of PSU / cable?

[orsty3001]

I have dozens of USB ac adapters. Most are 1 amp and above. I tried them all and the USB ports on my computer. Just now I tried a jumpbox and a USB 12v car adapter and it still hangs in the same place.

[orsty3001]

Is there a way to debug the software? I can't do anything to see where exactly it hangs because of the hard lockup that occurs.

[JamesP6000]

Hi Guys,

I'm suspecting that something recently changed in Jessie...

Can you see if running PiFmRds produces the same problem?
https://github.com/ChristopheJacquet/PiFmRds

Both codebases are using mailbox.c to configure the memory maps and the ioctl messages you're seeing are coming from mailbox.c.

JP

[orsty3001]

I'll try to run that program when I get off work but just to let you know WsprryPi worked when I downloaded a version of Jessie that is from December of 2016. So it's got to be something that's changed in the latest.

[JamesP6000]

I just upgraded to the latest Jessie (apt-get update/ apt-get dist-upgrade), rebooted, and it seems to be working fine on an old Raspberry Pi 1. No lockup. Perhaps they fixed the problem? Nothing was connected to any GPIO pins.

Could you send the actual command line you're using the launch the program?

James

[orsty3001]

sudo wspr -r -o -s My Callsign EM94ax 10 20m 0

[JamesP6000]

You seem to be missing your callsign. Can you try again and see if it still crashes? wspr [options] callsign locator tx_pwr_dBm f1 <f2> <f3> ... JP

…

On Mon, Apr 10, 2017 at 11:54 AM, orsty3001 ***@***.***> wrote: sudo wspr -r -o -s EM94ax 10 20m 0 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEiQH5OdOsQG4rcccqFLtkpjQboMSqAYks5runrZgaJpZM4M3NGd> .

[orsty3001]

I substituted "My Callsign" there so I wouldn't have to post my real callsign.

[orsty3001]

`Power: tx_pwr_dBm 10
Requested TX frequencies:
0.000010 MHz
14.097100 MHz
0.000000 MHz
Extra options:
NTP will be used to peridocially calibrate the transmission frequency
Transmissions will continue forever until stopped with CTRL-C
A small random frequency offset will be added to all transmisisons

ioctl_set_msg failed:-1
ioctl_set_msg failed:-1
Ready to transmit (setup complete)...
Desired center frequency for WSPR transmission: 0.000035 MHz
Waiting for next WSPR transmission window..`

Then it locks up. Also there is a typo in the program there. The words periodically and transmissions is spelled wrong.

Also was able to test PiFmRds and it works fine.

[JamesP6000]

It's interesting. In the email I received from github, there was no mention of "my callsign" but it's clearly shown on the webpage version.

Thanks for the spelling corrections :) Unfortunately the compiler does not flag spelling errors :)

From the program output you copied, it seems that your wspr is trying to transmit on the frequency 10 Hz (the first line after "Requested TX frequencies". Is that what you intend? I have never tried it at that low of a frequency.

If I use your command line and substitute my callsign, I get the following without crashing and without a transmission at 10Hz:

`pi@RPi1:~/WsprryPi $ sudo ./wspr -r -o -s AB0JP EM94ax 10 20m 0
Detected Raspberry Pi version 1
WSPR packet contents:
Callsign: AB0JP
Locator: EM94AX
Power: 10 dBm
Requested TX frequencies:
14.097100 MHz
0.000000 MHz
Extra options:
NTP will be used to periodically calibrate the transmission frequency
Transmissions will continue forever until stopped with CTRL-C
A small random frequency offset will be added to all transmissions

Ready to transmit (setup complete)...
Desired center frequency for WSPR transmission: 14.097098 MHz
Waiting for next WSPR transmission window...
Obtained new ppm value: -43.1177
TX started at: UTC 2017-04-10 22:10:01.004
TX ended at: UTC 2017-04-10 22:11:51.597 (110.592 s)
Desired center frequency for WSPR transmission: 0.000000 MHz
Waiting for next WSPR transmission window...
Skipping transmission
Desired center frequency for WSPR transmission: 14.097090 MHz
Waiting for next WSPR transmission window...
`

[orsty3001]

I just noticed it did the same thing in my email. Very strange.

I'm at a lost. I'm not sure how to diagnose this issue since it just hangs up and can't do anything until the power is unplugged and plugged back in. I'll just run it on the older version of the OS for now to have a play with wspr.

Thanks.