Skip to content
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

questions for using the gui for measuring A-mode and B-mode data #13

Closed
TimChang1024 opened this issue Sep 4, 2024 · 2 comments
Closed
Assignees

Comments

@TimChang1024
Copy link

Solved:
• 3.2 Software Requirements
Unsolved:
• 2.4.2 Flashing the Device
Locate the .emProject file in the US_probe_nRF52_firmware folder as described and open it with Segger Embedded Studio.
Bottleneck: Unable to find the US_probe_nRF52_firmware folder.
• 2.5.1 Setting up the Toolchain
Install the Programmer application.
Bottleneck: The Programmer cannot be downloaded because the nRF Connect apps for Windows indicated in the manual are outdated.
Bottleneck of the Third Category:
• The user manual does not specify how to power up the transmitter part. As a result, we cannot ensure the probe is working, and the nRF52 dongle is not connected to the probe.
• If possible, we would appreciate a detailed, step-by-step procedure for the setup process, from start to successfully measuring the A-mode and B-mode graphs.

@Sergio5714 Sergio5714 self-assigned this Nov 11, 2024
@Sergio5714
Copy link
Collaborator

Sergio5714 commented Dec 17, 2024

Thank you for your feedback. Indeed, there were a couple of inaccuracies.
We updated the User Manual to address your comments. It will be available soon as a part of a new release.

Regarding the transmitter part, WULPUS actively power cycles HV domains to save power. The best way to validate that TX phase works as expected is to measure the excitation waveform at the output of the transducer connector. After TX is verified, you can connect the transducer and check the RX signal. This would be my suggestion.

@Sergio5714
Copy link
Collaborator

We fixed this issue and merged it into the dev branch. The changes will be a part of the release 1.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants