FieldPoint Family

cancel
Showing results for 
Search instead for 
Did you mean: 

FP 1601 doesnt work with P4

Hi!
Last week I wrote a message where I described troubles disconnecting a
FP1601 from LAN.
I make a brief summary:

When I disconnect a FP bank from LAN I don't receive any message or error
code (usually I receive 33163 code)
Even if the bank is connected again LabVIEW hangs up when I close the NI
example that I used to make this trials
I have this kind of problem only with Pentium 4 CPU (I tried various OS and
HW) but not with AMD Duron or Athlon
I make this trial with LabVIEW 7.0, Fieldpoint 4.0.1, MAX 3.0.1 and every
time I used a PC with installed OS only!!

Thanks and Best Regards
Alessio Colzi
0 Kudos
Message 1 of 4
(3,492 Views)
Alessio:

I have attached 3 files (see below).

You will only get the error code if you look at the actual code or set your General Error Handler to show warnings. The error you get is actually not an error, but a warning 33163. See my Warning.jpg and the BD.jpg for how I made my test VI show me this warning.

Now, after I unplugged my FP bank, I did start getting the error. When I plugged it back in, the error continued until I refreshed the FP I/O Name Constant by clicking on browse >> refresh...

This is all expected behavior.

Good luck!

Sincerely,

Brooks B
Applications Engineer
National Instruments
Download All
0 Kudos
Message 2 of 4
(3,492 Views)
I have the behavior you describe me only with certain kind of PC. I made several trials with different Pentium 4 PC using NI example and I doesnt work.
Which kind of PC you use for your trial??

Regards
Alessio Colzi
0 Kudos
Message 3 of 4
(3,492 Views)
I am using a Dell Dimmension 4500 P4. The problem is most likely related to the operating system, network card, or motherboard of your PC. Did you try it with just a crossover cable and not through a network? Again, this is not a National Instruments error code, but rather a generic winsock TCP error coming from the Windows TCP/IP driver. Unfortunately, this is not something we have much control over. If you find a PC that works, just use that PC or troubleshoot the error code on Microsoft's support page.

Thanks and Good Luck!

Sincerely,

Brooks B
0 Kudos
Message 4 of 4
(3,492 Views)