03-01-2011 01:03 PM
Hi Folks,
This is a first one for me - running 2009 v9.0f3 and am having trouble with the above vi (included as part of the "System Replication" example). I've used this VI for a while now and never had this trouble.
The local 10/100 NIC set to DHCP by default, but static if DHCP unavailable (172.16.1.1/255.255.0.0).
cFP-2010 is static at 172.16.1.2
link/ping find between target and host computer.
Target is running RT v8.5.1, FP VI Manager 6.0.1 / FP Drivers 6.0.0, and variable client support for LV RT.
Crashes when:
-host PC connection to cFP-2010 is OK
AND
-"Find Only Unconfigured" bool terminal is set to (False)
Won't crash if:
-host computer is connected to 'coorperate' network and has IP via DHCP (no targets to respond). Either bool value.
-host PC connection to cFP-2010 is OK
AND
-"Find Only Unconfigured" bool terminal is set to (True)
Crash is hard - no 'program has stopped responding', all LabVIEW windows just gone.
Recovery kicks in on next LV start, but no error reporting.
Any thoughts? Not sure where to start, other than *maybe* another cFP-2010.
Regards,
Jamie
Solved! Go to Solution.
03-07-2011 09:54 AM
Hi 8bitbanger,
Do you experience the same thing when connected with a crossover cable?
Also if you could test with another cFP-2010 that would be ideal so the problem could be pinpointed.
<Brian A | Applications Engineering | National Instruments>
03-07-2011 09:58 AM
Hi Brian -
I have always used straight-through cables, as all of the NICs I encounter these days are Auto-MDI/MDI-X.
I have yet to try another target, but that's on my list for today. 🙂
Thanks,
Jamie
03-07-2011 11:13 AM - edited 03-07-2011 11:15 AM
I have confirmed that swapping target controllers does not help;
I've tried both devices in Safe mode, no good. Devices show up in MAX as expected, nothing out of the ordinary there.
03-07-2011 11:24 AM - edited 03-07-2011 11:25 AM
As it turns out, a build from late last year seems to be running fine using this VI.
So I re-built a small test VI -> exe, and I get this crash dialog when attempting to run.
Beginning to think the NI VI has become corrupt - can you provide an MD5 hash, (or some other means of checking the file)?
V/R,
Jamie
03-07-2011 01:24 PM
After I realized this was indeed a DevZone toolkit, I re-downloaded, re-placed into \user.lib folder, and all is well.
Thanks,
Jamie