What I've done goes a step further; write wrappers for all the low level
GPIB VIs you use. These wrappers read a global to determine if the GPIB
calls are to execute on the present machine or on a machine elsewhere on the
network (via VI server loading the wrapper VI on the remote machine). You
could also add a setting to make the wrappers simply return without doing
anything, but possibly more elegant would be to hook the instrument up to
one of your other machines and, without downtime on that other machine,
debug that one instrument from your desk PC across the network. As long as
you're not pushing the machine and the GPIB bus hard with either its "real"
work or your debugging everything should be fine.
Henry Coulter wrote in messa
ge
news:3A7898C7.590CC2DA@loxinfo.co.th...
> I do by installing the drivers needed to the PC without the GPIB card. You
> obviously can't run any commands that would make request to the bus, but
you
> can work with the VI. If you need to run the VI and do some thing that
might
> make a GPIB call, I usually take the lowest level VI can work with and
make a
> dummy VI that returns some value that will not stop the program from
executing
> (i.e. none error value), then you can still check the running code. BUT
beware,
> you must remember to replace the temp VI with the actual one on your GPIB
card
> installed setup.
>
> Henry
>
