John Lokanis Posted June 30, 2009 Report Share Posted June 30, 2009 Name: Ping dotNET Submitter: John Lokanis Submitted: 07 Jul 2009 File Updated: 03 Jan 2011 Category: Remote Control, Monitoring and the Internet LabVIEW Version: 8.6 License Type: Creative Commons Attribution 3.0 Ping dotNET v1.0.1 Copyright © 2009, John Lokanis All rights reserved. Author: John Lokanis LAVA Name: jlokanis Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 8.6.1 Dependencies: Requires .net 2.0 or higher Description: This VI performs a ping operation on the requested IP address or host name (requires DNS) the timeout for each ping as well as the delay between pings can be specified. The results are provided as arrays of each output type and in a text format designed to mimic the command line ping output. Instructions: Enter a valid IP address or host name and execute the VI. Known Issues: None. Acknowledgements: MSDN Change Log: v1.0.0: Initial release of the code. v1.0.1: Updates to the readme file and arrangement of the folder structure. (Mark Balla) License: Distributed under the Creative Commons Attribution 3.0 (http://creativecommo.../about/licenses) See link for a full description of the license. Support: If you have any problems with this code or want to suggest features: please go to www.lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the "[CR]Ping dotNET" support page. Distribution: This code was downloaded from the LAVA Code Repository found at www.lavag.org Click here to download this file 1 Quote Link to comment
TobyD Posted June 30, 2009 Report Share Posted June 30, 2009 Please give it a try and let me know if you find any bugs or have any suggestions for improvements. thanks, -John Nicely done John! I've thought about doing this for a while now, but I can almost always find something to do with my time that doesn't involve dealing with the "slog" of MSDN. Thanks for taking the time to share this! -Toby Quote Link to comment
John Lokanis Posted June 30, 2009 Author Report Share Posted June 30, 2009 Thanks! Unfortunately I already found a bug! But the fix was easy. On failed pings the options .net ref was null. I was trying to close this ref in all cases. Should have read that MSDN a little closer... Here is the new version. -John Click here to download this file Quote Link to comment
John Lokanis Posted July 6, 2009 Author Report Share Posted July 6, 2009 Added better error handling and cleaned up some of the BDs. I think this is read to be submitted to the CR. Can someone let me know what next steps to take or what might needed to get this code into the CR? thanks, -John Click here to download this file Quote Link to comment
Mark Balla Posted July 8, 2009 Report Share Posted July 8, 2009 Added better error handling and cleaned up some of the BDs. I think this is read to be submitted to the CR. Can someone let me know what next steps to take or what might needed to get this code into the CR? thanks, -John Hi John, We are in the process of updating the Code Repository submission process. Here is a rough draft of the requirements. LabVIEW Code (Moderators discretion) Appropriate level of Documentationincluding the use of the VI Documentation, Free text on the Front Panel and/or Block Diagram. You don't need to include a novel, but please consider the average level of knowledge of a LabVIEW programmer that has never seen your code before. [*]Appropriate Error handling[*]Follow basic style guidelines Minimize wire bends Use the 4-2-2-4 pattern for subvis Meaningful icons Code does not take-up multiple screens. Code conforms to stated function Code must be useful Zip File The .zip file must end with the LabVIEW version and the software version in the following format [filename_LV##_v###] example [Mysubmission_LV86_v100] Must contain Organized LabVIEW code Must contain Readme.txt file Recommended to contain the FP screen shot I am attaching a readme .txt template to fill in and an example readme for reference.README fillin.txtREADME example.txtHere are the steps to submit you codeCreate a Readme.txt file Create a screen shot of your application Place the Readme.txt , screenshot and the Organized LabVIEW code in the .zip file Name the .zip file as required. Go to the LAVA Code Repository Tab (http://lavag.org/ind...p?app=downloads) and click on the “Upload File” button. Select a category that best fits your submission and press “continue Fill in the file Information. Copy the contents of the readme file into the Description box Replace any email addresses with –see readme file for contact information. Attach zip file and screenshot found in the File Management area. Click on the “Add Submission” button to complete. A Moderator will then be assigned to review the code and if it passes it will then be placed in the Code Repository. Once approved a support topic will be generated in the CR Forum (http://lavag.org/for...tory-certified/) Edit MB: I left out an item in the templates added dependencies: 7-7-09 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.