I'm trying to migrate some of the previous work I've done from an Epiq Matchstiq SDR platform to the ZC706/FMCOMMS3 combination that I recently purchased. Specifically, I want to be able to send out 802.11-compliant probe request packets and pick them up on another machine running Wireshark. I'm also evaluating the probe response packets that are coming out of an access point I have set up in the same room. The MATLAB code used to generate the probe request packet is the same for both implementations up to a point the difference being that for the Matchstiq, I add Matchstiq-specific header information to the data, write to a binary file, then copy it to the Matchstiq and run a custom program on the ARM that feeds the binary data to the FPGA and consequently the RF transmitter. WIRESHARK IP ADDRESSES NOT DISPLAYING CODE For the ZC706/FMCOMMS3 combination, I'm using libiio to interface with the RF board from MATLAB directly. This all sounds relatively straightforward in theory, but in practice, I'm running into a problem that I'm not entirely sure how to solve.
WIRESHARK IP ADDRESSES NOT DISPLAYING HOW TO Namely, when using the ZC706/FMCOMMS3, Wireshark is unable to resolve the probe request packets, but picks up the probe response packets coming from the access point just fine - in other words, the access point recognizes the packets, but Wireshark does not. Normally, I'd chalk this up to a Wireshark issue, but Wireshark has no problem resolving the probe requests when they're sent by the Matchstiq.
This leads me to believe that there's a fundamental difference in how the data is being packaged and sent to the transmitter.
Set up a system object and loop for each packet as follows: Here is a description of what I'm doing. The I component of the data ranges from -1 to 1 scale this by 1024 and round (Note: I thought the AD9361 had a 10 bit DAC, but the sine wave example I saw scales by 1024 so I went with it). The Q component of the data is all zeros because this is a BPSK signal. WIRESHARK IP ADDRESSES NOT DISPLAYING CODE.
0 kommentar(er)
