-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EnvironmentError: IOError: Block ctrl (CE_01_Port_40) packet parse error UHD 3.15.LTS and UHD 3.14 #484
Comments
This means a control packet was lost somewhere (on the wire maybe). |
Can you please share some info about your application? Is this reproducible with UHD examples? |
Sure, my application is collecting wifi packets, demodulating them whether they are ofdm or Dsss and producing pcap files or running to null. My application creates the flowgraph like so...USRP -> Burst Detector -> Eventstream -> Demod blocks -> null. I haven't run any UHD examples to try and reproduce. Are there any you suggest I use? |
|
Cannot reproduce in this state. |
Issue Description
X310 Failure after limited run. Full error below.
thread[thread-per-block[7]: <block gr uhd usrp source (3)>]: EnvironmentError: IOError: Block ctrl (CE_01_Port_40) packet parse error - EnvironmentError: IOError: Expected packet index: 3318 Received index: 3319
Setup Details
X310, two TwinRx daughterboards. Scanning between 2 frequencies every 11secs.
10Gig connection, two channel collect @100Msps, 80Mhz BW
UHD: 3.15.LTS, Also seen with UHD 3.14
OS: CentOS 7.9
Python 2.7.5
GNU: 3.7.14.0
Docker Environment
Server based system
Expected Behavior
Collection to continue and not error out
Actual Behaviour
Error message above seen and collection stops. I then must do a ctrl-C to fully exit out then restart my application again to retask the X310
Steps to reproduce the problem
Flowgraph includes UHD source block, with a number of demod blocks.
Additional Information
Numerous D's and O's seen leading up to the error. After performing a ctrl-C to completely exit the application, I get the error messages below.
The text was updated successfully, but these errors were encountered: