Hello. This for the old school users.
History: We're running LabView8.2 on an old Windows XP Pro PC. As the old PC seemed to be dying, we purchased an identical PC and tried to transfer everything over to the new hard drive. After getting a new license and several other problems were addressed, we still have complications. In the mean time, I fixed the old computer and decided to try and use that as we continued to work our way through bringing the new computer on line.
Problem: Though nothing was changed with the old computer, other than disconnecting the ethernet cable, the old computer and it's peripherals are not behaving as usual. Basically, when opening the initial vi (called control panel-which mostly opens and closes valves) the valves don't respond physically. Then when pushing the stop sign, nothing happens, and if you close the window with the X in the corner, a new box pops up with "resetting vi". Sometimes this times out and sometimes you need to close with task manager. The computer communicates with the Instruments (in this case a Agilent device) through an ethernet cable and a GPIB-enet/100.
We've swapped out the GPIB device and re-established connections. Also, in Meas and Act program, initially, the instrument IDs don't populate instead it reads "the device did not respond to a *IDN?. However, if you open specific instrument and re-send communication, it populates with instrument ID. Has anybody seen this before and does it have an easy solution as I am not the programmer responsible? Also, does this have anything to do with SCPI vs older instrument language and how is that addressed?
Thanks for your time.
