LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ping.vi

When I use the Ping.vi I get :
 
Error 7 occurred at Open File+.vi:Open File
Possible reason(s):
LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on UNIX.
---
NI-488:  Non-existent board.
 
It doesn't look like its creating the txt file.
 
 
What is the purpose of the
pingtemp.txt ??
 
Why do the error out clusters of the delete.vi ( lower left of ping.vi) go to a flatten sequence but really not connect to anything?
 
On the frt panel is:
Must run on Windows machine that has ping.exe executable.
What does this mean ?
0 Kudos
Message 1 of 6
(4,618 Views)
Hi Clint Eastwood,
can you upload your ping.vi? I can´t find it. To make a ping from LabView you can also use the "System Exec.vi".
 
You need the ping.exe on your system means, that the ping.exe has to be available on your pc, for instance in Windows\System32 folder.
 
Mike


Message Edited by MikeS81 on 04-10-2008 02:50 PM
0 Kudos
Message 2 of 6
(4,613 Views)

Sorry.  It was a shipping example w LV 7.1.

 

 

0 Kudos
Message 3 of 6
(4,589 Views)
I don't think that was a shipping example but an example on NI Developer Zone. I started using that with 6.0 or earlier I believe. A while ago, I started having the same problem you are seeing but for the life of me, I can't remember the exact fix and since I used it at a previous job, I no longer have access to the code. It was related to an OS upgrade and was either a permission problem to the temp directory or the need to change command.com to cmd. You can try changing the permissions to the temp folder, change the Temp Driectory to Current VI's Path with a Strip Path to get the folder, or use cmd.
0 Kudos
Message 4 of 6
(4,582 Views)
The command to cmd was my 1st thought but decided to ask first.  I will try both suggestions.
 
Thanks !
0 Kudos
Message 5 of 6
(4,579 Views)
The problem has to do with the actual temp directory path. The way the VI is written it assumes the path doesn't contain spaces. I.e., it assumes the temp directory is something like C:\temp. Nowadays it's more likely to be C:\Documents & Settings\...

This means you have to enclose the paths with spaces. Attached is a corrected version.
Message 6 of 6
(4,574 Views)