I have been developing a control application using an old PC (200MHz Pentium MMX) under NT4 with LabVIEW 6.0.2 and a FP1600 with a variety of modules (DI330, RLY420, RTD122, AO200 and TC120). FP firmware is at 4.11 and FP Explorer at 3.0.1. The application runs ok on this system.
I have recently got funding for new systems and am trying to port the app onto a system (2GHz Pentium 4) running Win 2000 Pro but have hit some problems. The most obvious is the time stamp from the FPAdvise in my temperature read loop. With the new system I get garbage either immediately or within approx 30 mins (garbage = dates/times that bear no resemblance to reality, settling at 01/01/1904, 1:00:00 but occasionally jumping about to seemingly random d
ate/times). I have the time server set to the IP of the PC running the app.
Other quirky behaviour I have also seen on the new system is -
1) Control of the DO's can vary from instantaneous to very sluggish (5-10 secs)
2) Spurious signals from the DI module
3) Temperatures jumping around occasionally from the actual ambient to 0 or inf.
FP explorer appears to work ok on the new system (so probably not a noise issue). I am using the same iak file that worked with the old system and have also tried reloading FP firmware.
Currently I am trying various experiments to try to home in on what is going on, but not having much luck. I've tried stripping the code down to the temperature loop and running under various combinations/permutations of OS/Hardware
New system/W2K - doesn't work (saw 33162 error on 1 occassion)
Old system/NT4 - ok overnight
Old system/W2K - doesn't work (Intermittent 33162 errors - "unable to connect to the data item on the module AIAdvise", t
his might be occurring more often above and I haven't noticed it)
I'm intending to run some other experiments (New system/NT4) but haven't managed this yet. In the mean time, any suggestions would be appreciated.
Regards,
Niel.
