Adding information to the LabVIEW_Debugging_Techniques.md

[cchidean]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

The Pull Request adds information about Custom Devices to the LabVIEW_Debugging_Techniques.md file

Why should this Pull Request be merged?

Because the information in the file is part of the Custom Devices Handbook documentation.

What testing has been done?

https://niveristand-custom-device-handbook--9.org.readthedocs.build/en/9/LabVIEW_Debugging_Techniques.html

[PaulDanH]

Hey Calin, please check my above suggestions and comments. Thanks!

[nidaring]

Overall, I'm not sure what purpose this document serves vs the table here: https://www.ni.com/documentation/en/veristand/latest/manual/custom-device-benchmark-debug/

I'm guessing that it is meant to be a 'companion document' that adds more color to the tech comms help? If so, then maybe we should have the same ordering of 'tools' and make sure the same tools show up in both places?

[WillCawley]

Hey @cchidean. Can you remove me from this review? I'll submit a separate pull-request with updates for clarity and concision when you all are done with making sure it is technically correct.

[PaulDanH]

Hey @cchidean. Can you remove me from this review? I'll submit a separate pull-request with updates for clarity and concision when you all are done with making sure it is technically correct.

Hey @WillCawley you can always use insert a suggestion button for small changes that can be incorporated in the same PR. This worked great for us on the first pass review.

[cchidean]

Overall, I'm not sure what purpose this document serves vs the table here: https://www.ni.com/documentation/en/veristand/latest/manual/custom-device-benchmark-debug/

I'm guessing that it is meant to be a 'companion document' that adds more color to the tech comms help? If so, then maybe we should have the same ordering of 'tools' and make sure the same tools show up in both places?

@cheloizaguirre what do you think about this question?

[cheloizaguirre]

Overall, I'm not sure what purpose this document serves vs the table here: https://www.ni.com/documentation/en/veristand/latest/manual/custom-device-benchmark-debug/
I'm guessing that it is meant to be a 'companion document' that adds more color to the tech comms help? If so, then maybe we should have the same ordering of 'tools' and make sure the same tools show up in both places?

@cheloizaguirre what do you think about this question?
This document seems slightly better than the one in the manual, which makes sense because this guide should be more detailed. We can tweak it later, it seems good enough to survive the first pass

[cheloizaguirre]

Overall it's good enough for me. Just do whatever Paul says for now and we can look into improving other content later.

[PaulDanH]

Small rendering changes for consistency. Please check and submit these, and this one is good to go. Thanks!

[PaulDanH]

Please delete "docs/images/Disable_ni_emb.jpg" as it is not used anymore.

And this is one is good to go.