DATA/FETCH/TIME command is not accepted
Opened this issue · 6 comments
Hi,
The stream I try, doesn't get plotted and in verbose mode, I get errors like above:
...response: DATA/FETCH/TIME command is not accepted
...negotiation with remote SeedLink failed: u'no stations accepted'
...network socket closed
...primary loop pass 0, state 0
Is that already with verbose flag -v
? Full output?
Can you get data from that very same seedlink server with other means OK (e.g. with this)
command:
seedlink-plotter -s "HP_GBT1:BHZ" --x_position 200 --y_position 50 --x_size 800 --y_size 600 -b 1m --seedlink_server "150.140.182.6:18000" --update_time 2s -v -f --force --x_scale 1m --line_plot
output:
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:parsed 1 streams from stream list
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
INFO: obspy.clients.seedlink [150.140.182.6:18000]:network socket opened
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:sending: HELLO
INFO: obspy.clients.seedlink [150.140.182.6:18000]:connected to: 'SeedLink v3.0 (2006.104)'
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:sending: STATION GBT1 HP
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:response: station is OK (selected)
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:sending: SELECT BHZ
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:response: selector BHZ is OK
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:response: 1 selector(s) accepted
INFO: obspy.clients.seedlink [150.140.182.6:18000]:requesting specified time window
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:sending: TIME 2016,8,9,8,32,24
ERROR: obspy.clients.seedlink [150.140.182.6:18000]:response: DATA/FETCH/TIME command is not accepted
ERROR: obspy.clients.seedlink [150.140.182.6:18000]:negotiation with remote SeedLink failed: u'no stations accepted'
INFO: obspy.clients.seedlink [150.140.182.6:18000]:network socket closed
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
INFO:root:0 Trace(s) in Stream:
ERROR:root:Empty stream for plotting
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
DEBUG: obspy.clients.seedlink [150.140.182.6:18000]:primary loop pass 0, state 0
Please try to fetch a specific short time piece using above basic seedlink client. I doubt this is seedlink-plotter specific..
Hm, yes I believe it has to do with SeedLink itself. However, easyseedlink does bring data chunks.
However, easyseedlink does bring data chunks.
Hmm.. strange. I thought maybe the seedlink server was configured to not allow same commands. But this might not be the case if easyseedlink client works.. but I don't know much about it's implementation.. maybe @bmorg has something to say about this.. or you can check what easyseedlink is doing differently..
Again, does the basic seedlink client to fetch a discrete time window mentioned above work?
#!/usr/bin/env python
from obspy import UTCDateTime
import obspy.clients.seedlink.basic_client as sl
host='my_host'
net='my_net'
sta='my_sta'
cha='my_cha'
client = sl.Client(host, timeout=60, debug=True)
t = UTCDateTime() - 10 #sec
st = client.get_waveforms(net,sta, "",cha, t, t + 3)
st = st.sort(reverse=True)
print(st)
Doesn't work either.