Pokemon Infinite Fusion The information you provided is very helpful! It sounds like you've made significant progress with your GPS receiver/simulator using BladeRF. Here are some insights on the issues you mentioned and potential solutions:
Packet Loss at 40 Msps:
Reduce Sampling Rate: While a higher sampling rate captures more detail, it also increases processing demands. Try reducing the sampling rate to a value closer to 8 Msps (like in your Tx example) and see if packet loss improves. You can find a balance between capturing necessary data and reducing packet loss.
Optimize Buffers: Review your code and optimize buffer sizes and data transfer between BladeRF and your processing unit. Ensure buffers aren't overflowing at high sampling rates.
Check USB 3.0 Connection: Double-check your USB 3.0 connection for any physical damage or loose connections. A stable and fast USB 3.0 connection is crucial for handling high data rates.
Large DC Bias:
Calibration: Perform proper BladeRF calibration using the bladeRF-cli calibration command. This can help reduce DC bias.
Hardware Considerations: In some cases, the DC bias could be hardware-related. If calibration doesn't resolve the issue, consult Nuand's documentation or support for troubleshooting steps specific to BladeRF hardware.
Tx Issues at 1.5 GHz:
Power Supply: Ensure your power supply can provide enough current for both Rx and Tx operations at 1.5 GHz. BladeRF might not have sufficient power for Tx at higher frequencies with a weak power supply.
Check BladeRF version: Consult Nuand's documentation to confirm if your specific BladeRF model supports Tx at 1.5 GHz effectively. Some models might have limitations in Tx capabilities at higher frequencies.
Software Conflicts: Check for any software conflicts that might interfere with BladeRF-cli.exe. Try running the commands from a different terminal or environment. Consider updating BladeRF firmware or software libraries to the latest versions.
