search

jbrzusto / sensorgnome

master control process for a sensorgnome receiver
GNU General Public License v2.0
1 stars 2 forks source link

fix funcube frequency being displayed as 0 MHz on the web interface #37

Open jbrzusto opened 7 years ago

jbrzusto commented 7 years ago

this is likely due to the shell call to "fcd -g" timing out. I don't think the funcube is really set to 0 in these cases. A funcubedongle stuck in bootloader mode after a failed attempt at setting the 48 kHz sampling rate might also show a frequency of 0, but then no pulses will be detected.

adamdsmith commented 7 years ago

Seeing it here:

http://live.sensorgnome.org/SG-1814BBBK0461

jbrzusto commented 7 years ago

This unit seems to have stopped running correctly in late March. The last few files written were:

-rwxr-xr-x 1 bone bone 298284 Mar 31 22:34 MACKI-1814BBBK0461-000021-2017-03-31T21-38-18.6390P-all.txt.gz -rwxr-xr-x 1 bone bone 286736 Mar 31 22:39 MACKI-1814BBBK0461-000021-2017-03-31T22-34-52.9490P-all.txt.gz -rwxr-xr-x 1 bone bone 762325 Mar 31 23:21 MACKI-1814BBBK0461-000021-2017-03-31T22-39-40.5510P-all.txt -rwxr-xr-x 1 bone bone 193656 Mar 31 22:43 MACKI-1814BBBK0461-000021-2017-03-31T22-39-40.5510P-all.txt.gz

The funcubes are unresponsive and the master process is not running.

I don't know whether the unit is fried, but if not, its temperature sensor suggests it is running very hot:

cat /sys/devices/ocp.3/44e10448.bandgap/temp1_input

127000

That's a nominal core temp of 127 degrees C - way over spec, which maxes out at around 90 degrees C.

I'm going to reboot it now to see whether anything changes.

J.

On Mon, May 8, 2017, at 15:01, Adam Smith wrote:

Seeing it here:

http://live.sensorgnome.org/SG-1814BBBK0461

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/jbrzusto/sensorgnome/issues/37#issuecomment-299942655

--

-----------------------------------

John Brzustowski

Wolfville, NS Canada

adamdsmith commented 7 years ago

Nothing by trouble with this station. It was already killed by lightning once...

A

On Mon, May 8, 2017 at 2:16 PM, John Brzustowski notifications@github.com wrote:

This unit seems to have stopped running correctly in late March. The last few files written were:

-rwxr-xr-x 1 bone bone 298284 Mar 31 22:34 MACKI-1814BBBK0461-000021- 2017-03-31T21-38-18.6390P-all.txt.gz -rwxr-xr-x 1 bone bone 286736 Mar 31 22:39 MACKI-1814BBBK0461-000021- 2017-03-31T22-34-52.9490P-all.txt.gz -rwxr-xr-x 1 bone bone 762325 Mar 31 23:21 MACKI-1814BBBK0461-000021- 2017-03-31T22-39-40.5510P-all.txt -rwxr-xr-x 1 bone bone 193656 Mar 31 22:43 MACKI-1814BBBK0461-000021- 2017-03-31T22-39-40.5510P-all.txt.gz

The funcubes are unresponsive and the master process is not running.

I don't know whether the unit is fried, but if not, its temperature sensor suggests it is running very hot:

cat /sys/devices/ocp.3/44e10448.bandgap/temp1_input

127000

That's a nominal core temp of 127 degrees C - way over spec, which maxes out at around 90 degrees C.

I'm going to reboot it now to see whether anything changes.

J.

On Mon, May 8, 2017, at 15:01, Adam Smith wrote:

Seeing it here:

http://live.sensorgnome.org/SG-1814BBBK0461

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/jbrzusto/sensorgnome/issues/37#issuecomment-299942655

--

-----------------------------------

John Brzustowski

Wolfville, NS Canada

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jbrzusto/sensorgnome/issues/37#issuecomment-299947280, or mute the thread https://github.com/notifications/unsubscribe-auth/ADDDz3YUoMomyVYyrDIGK1qtBrrHK37aks5r31wEgaJpZM4NUBtR .

jbrzusto commented 7 years ago

After a reboot, this unit appears to be working. The web interface is back up; the funcubes are tuned correctly, the GPS is working, and the band_gap temperature is down to 64 degrees, which is fine.

I wonder if this sytem got a power jolt back in late March. Whatever happened didn't cause a restart, but seems to have scrambled the state of USB devices and left the kernel very confused about its own temperature - I doubt a simple reboot would drop the temperature 60+ degrees in the space of a couple of minutes.

Weird...

On Mon, May 8, 2017, at 15:01, Adam Smith wrote:

Seeing it here:

http://live.sensorgnome.org/SG-1814BBBK0461

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/jbrzusto/sensorgnome/issues/37#issuecomment-299942655

--

-----------------------------------

John Brzustowski

Wolfville, NS Canada

adamdsmith commented 7 years ago

Well, that's better than having to replace the whole unit again. Thanks for the reboot. I'll check it more frequently.

On Mon, May 8, 2017 at 2:30 PM, John Brzustowski notifications@github.com wrote:

After a reboot, this unit appears to be working. The web interface is back up; the funcubes are tuned correctly, the GPS is working, and the band_gap temperature is down to 64 degrees, which is fine.

I wonder if this sytem got a power jolt back in late March. Whatever happened didn't cause a restart, but seems to have scrambled the state of USB devices and left the kernel very confused about its own temperature - I doubt a simple reboot would drop the temperature 60+ degrees in the space of a couple of minutes.

Weird...

On Mon, May 8, 2017, at 15:01, Adam Smith wrote:

Seeing it here:

http://live.sensorgnome.org/SG-1814BBBK0461

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/jbrzusto/sensorgnome/issues/37#issuecomment-299942655

--

-----------------------------------

John Brzustowski

Wolfville, NS Canada

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jbrzusto/sensorgnome/issues/37#issuecomment-299951239, or mute the thread https://github.com/notifications/unsubscribe-auth/ADDDzyrk0aoR9J9T5aLbNqngK5hdpvJDks5r319IgaJpZM4NUBtR .