update PCI 1330 firmware error on restart

[AZimmer]

I recently upgraded from 8.0.1 to 8.2.1.  Before I never had this problem.  Now I have had a number of new problems.
This one is that when I restart the computer it will usually not enable me to initialize a PCI 1330 motion board and prompts me to update the Firmware.  I have done this in the past, and the firmware was updated, but now it still prompts me to do this, although the firmware is upto date.  (Version 68331; 7.40.3000,   DSP 7;30.3000,  FPGA1 7.00.3001,   FPGA2; 7.00.3001).  I can't do anything about it so I restart. 
After a second restart the the error often does not occur the board works fine.  Sometimes I may have to restart the computer a number of times, but eventually the board loads fine and everything works.  Why is it being so sensitive to being restarted? 

Any thoughts?
Andre

[Jochen]

Andre,

according to your firmware versions you have already installed NI-Motion 7.5. I'm not aware of a problem in our driver/firmware that could cause such a behavior.
If possible, please move the PCI-7330 to another PCI slot. This will make Windows to redetect the board. If this doesn't solve the problem, your board is probably broken and you should contact your local NI branch.

Best regards,

Jochen Klier
National Instruments

[jslouie]

Hi Andre,

Thank you for using National Instruments Forums.  It is possible something happened to the board, but before we recommend sending the board in I have a few questions for you:

1.  Is LabVIEW 8.0 still on the system or did you uninstall it?
2.  Did you uninstall LV 8.0 before installing LV 8.2.1 or did you install 'on top'?
3.  Did you reinstall NI-Motion 7.5?

If you have not done 3, I would recommend trying that out first.  Having multiple copies of LV on the same system is not terrible, but there are some things to watch out for.

Let me know what you discover.

Justin Louie

[AZimmer]

I do have multiple copies of Labview on the system and never uninstalled Labview 8.0 or 7.1 (which i previously had).  I also have not reinstalled the motion driver.  In order to get my USB 6008 devices working I had to reinstall DAQmx after the upgrade to 8.2.1.  I am also have a problem with one of two firewire video cameras (see post on vision board (http://forums.ni.com/ni/board/message?board.id=200&message.id=14204) for more details) that are using the Legacy driver. 
When I upgraded to labview 8.2.1 (and the corresponding version of  MAX) all of my devices quit working, and through a series of reinstalls and restarts I eventually got them back on line.  This has been very frustrating as I am in the middle of experiments with a number of staff working on the project and don't have any room for down time.  The only reason I upgraded was to fix a bug whereby Labview would crash if a running VI was clicked onto quickly.  I had requested a fix to this bug so I could avoid upgrading (in case bugs like the ones I have encountered started), but was informed no stand alone bug fix existed (the upgrade notes did say that the bug I was having was fixed in 8.2.1, and this seems to be true).

I suppose I can try to reinstall the motion software, should I remove the board from the PCI slot after uninstalling the software and then put it back in after the software has been installed?  I do not have any spare PCI slots. 

Cheers,
Andre
 

[AZimmer]

This problem seems to have been solved by logging in as the original administrator account that was used to setup Labview, then turning off the computer with that account.  The starting it again and logging in with the same administrator account.  This way the settings were kept.  I have however not yet tried restarting with the second admin account that is used more regularly, but with which Labview was not originally installed with. 
Andre

[AZimmer]

I recently restarted with the second user account that was giving me problems originally, the IEEE drivers  and cameras loaded fine, but the motion board still gave me the same problem.  Once again, a second restart fixed the problem and the motion board loaded fine.  It seems that a second restart is required unless the computer is turned off and back on.  This was never a problem before the upgrade.  Anyone know what happened with the upgrade?

[jslouie]

Hi Andre,

On the first restart with the problem, this is happening with Initalization?  It is hard to tell where and why this is happening.  It could be related to the installs across multiple accounts, but then again, maybe not.  A repair on Motion may help if you're willing to try it.  Otherwise, you are definitely still able to keep working, which is the important thing.

Justin Louie

[AZimmer]

What seems to have finally 'solved' the problem is waiting after a restart until windows has finished loading all of the software and drivers (ie. HD light is not on any more and computer isn't 'thinking').  When I have waited for the computer to finish it's startup routines, and then launch MAX and LabView I haven't had any of the problems, when I try and Launch MAX as soon as I can click on the icon, I seem to have the problems.  This was never a problem with 8.0, but seems to be a problem with 8.2.  It is a problem I can live with, but did cause some weird behaviour for a while.
Andre

[AZimmer]

Ok, so this still seems to be a problem if I log into the user account before everything loads, and then wait till the hard drive quits working before launching the programs.  It seems I have to wait till the hard drive quits working (presumably this is when the devices are being loaded) before logging into the user account, and then wait again until the drive quits working before launching MAX or Labview.

[MacleanG]

Hi Andre,

When your computer starts, NI services are being loaded, for example the Device Loader, so you can't start communicating with the device before the loader service has started.  This is most likely why you have to wait until your computer is fully booted before using MAX or LabVIEW.  This is expected behavior, and I believe is regulated by the speed with which your OS loads the services, rather than the NI software. 

Regards,