GUI not showing on pi 4

Technical Support
1

I got rsudp up and running on windows capturing screenshots at the thresholds I wanted. I wanted to move this over to a pi 4. All looks to be running correctly, but on the local display, and over RDP it does not show the GUI, nor does it save screenshots when the thresholds are passed. Below is the start up log. I’ve tried export DISPLAY=:0.0 but I’m now at a loss why the graphic is popping up.

Thanks for any help,
Mark

pi@raspberrypi:~/rsudp $ bash unix-start-rsudp.sh
Installing from the git directory...
Done.
Qt import failed. Trying Tk...
detail: No module named 'PyQt5'
2020-07-13 20:15:07 [Main] Logging initialized successfully.
2020-07-13 20:15:07 Using settings file: /home/pi/.config/rsudp/rsudp_settings.json
2020-07-13 20:15:07 Output directory is: /home/pi/rsudp
2020-07-13 20:15:07 [Init] Initializing.
2020-07-13 20:15:07 [openSOCK] Opening socket on localhost:8888 (HOST:PORT)
2020-07-13 20:15:07 [Init] Waiting for UDP data on port 8888...
2020-07-13 20:15:09 [Init] Available channels: ['EHZ', 'EHN', 'EHE']
2020-07-13 20:15:09 [get_inventory] Fetching inventory for station AM.RE3C4 from Raspberry Shake FDSN.
2020-07-13 20:15:10 [get_inventory] Inventory fetch successful. Station region is MISSOURI-KANSAS BORDER REGION
2020-07-13 20:15:10 [conn_stats] Initialization stats:
2020-07-13 20:15:10 [conn_stats]                 Port: 8888
2020-07-13 20:15:10 [conn_stats]   Sending IP address: 192.168.0.32
2020-07-13 20:15:10 [conn_stats]     Set station name: RE3C4
2020-07-13 20:15:10 [conn_stats]   Number of channels: 3
2020-07-13 20:15:10 [conn_stats]   Transmission freq.: 250 ms/packet
2020-07-13 20:15:10 [conn_stats]    Transmission rate: 4 packets/sec
2020-07-13 20:15:10 [conn_stats]   Samples per second: 100 sps
2020-07-13 20:15:10 [conn_stats]            Inventory: AM.RE3C4 (Raspberry Shake Citizen Science Station)
2020-07-13 20:15:10 [Plot] WARNING: Running on armv7l machine, using Tk instead of Qt
2020-07-13 20:15:10 [Plot] Plotting 3 channels: ['EHZ', 'EHN', 'EHE']
2020-07-13 20:15:10 [Plot] Signal deconvolution set to CHAN
2020-07-13 20:15:10 [Plot] Seismogram units are channel-specific
2020-07-13 20:15:10 [Plot] Starting.
2020-07-13 20:15:10 [Alert] Alert stream units are counts
2020-07-13 20:15:10 [Consumer] Starting.
2020-07-13 20:15:10 [Producer] Starting.
2020-07-13 20:15:10 [Producer] Receiving UDP data from 192.168.0.32
2020-07-13 20:15:10 [make_trace] ERROR: No matching response information found.
2020-07-13 20:15:10 [Alert] Starting Alert trigger with sta=6s, lta=30s, and threshold=1.588 on channel=EHZ
2020-07-13 20:15:10 [make_trace] ERROR: Could not attach inventory response.
2020-07-13 20:15:10 [Alert] Earthquake trigger warmup time of 30 seconds...
2020-07-13 20:15:10 [make_trace]        Are you sure you set the station name correctly?
2020-07-13 20:15:10 [make_trace]        This could indicate a mismatch in the number of data channels
2020-07-13 20:15:10 [make_trace]        between the inventory and the stream. For example,
2020-07-13 20:15:10 [make_trace]        if you are receiving RS4D data, please make sure
2020-07-13 20:15:10 [make_trace]        the inventory you download has 4 channels.
2020-07-13 20:15:40 [Alert] Earthquake trigger up and running normally.
2020-07-13 20:17:13 [Alert] Threshold: 1.588; Current max STA/LTA: 1.5710^C
2020-07-13 20:17:14 [Producer] Sending TERM signal to threads...
2020-07-13 20:17:14 [Consumer] Exiting.
2020-07-13 20:17:14 [Alert] Exiting.
2

Hi Mark, sorry to hear this. I think I have seen this problem before, but I haven’t been able to figure out why it manifests in this way. The issue is that when you give a station name that is not in our database, matplotlib crashes.

The way I’ve found to work around this problem is to turn data forwarding on and wait a few hours for the change to propagate through to our FDSN server, then try starting rsudp again. For some reason that allows the draw processes to work the way they should.

1 Like