Reset FP2000, now no software, and MAX cannot reload - solved!

[DanJ]

Setup: an older cFP-2000 system which came with real-time version 7.  We now want to create a new control program with LabView Real-Time versions 8.5.   System was working before upgrade.

I tried to connect with MAX.  As expected I had to upgrade the software on the FP2000.  Created my first test program - the standard 'Front Panel Communication' example created by project manager.  Then I modified this slightly for my hardware.  It worked OK.

I wanted to try my desired model - 'Network Communication' but the default example created by project manager would not deploy.  I read the comments about memory limitations on the FP2000 and moved the network global variables to the host.  I copied the optional network communication software modules to the FP2000 via MAX.  Then deploy got further (according the the progress indicator) but the procedure would display a message about 'lost connection' and stop the download.

So, I did what any Microsoft user would do... I did a hard reset of the fieldpoint system.  I tried a standard 'reset' (turned switch 8 'ON').  Naturally, after a reset, you have to change the IP address or the host system may not find it.  When a standard reset didn't help I thought I would also try a 'safe mode' restart so that I could clean out all software and reload fresh from MAX.

Now MAX can see the FP2000 module, but does not show any attached hardware.  It does not show anything under the 'software' option.  When I try to reload software it then complains that the FP2000 is not connected (it is, and the switches have been restored and the hardware power cycled (several times)) and therefore it cannot download the base software package.

Any idea what is wrong?  How to I restore software to this FP2000?  How do I get it to reestablish connection with the I/O hardware?

Thanks for any help!

[Devin_K]

Hi Dan,

First, make sure that you are using the latest version of FieldPoint (LabVIEW RT 8.5 requires that you use FieldPoint 6.0).  You can download the NI-FieldPoint driver as part of the latest Device Drivers Installation:
http://joule.ni.com/nidu/cds/view/p/id/961/lang/en

Try installing the software by booting the controller into safe mode, right-clicking on the Software section, and selecting Add/Remove Software.  If this doesn't work, follow the steps in the following KnowledgeBase article to get your controller set up properly: How to Network FieldPoint to a Host Computer with Ethernet.  Follow the steps for Configuration 1 if you are directly connected to the controller using a crossover cable or a network without DHCP, or the steps in Configuration 2 if you have it connected to a network with DHCP.  If you are still having problems after this, try a different method of connection if possible (if your controller is on a network, try directly connecting it to your computer with a crossover cable, or vice versa).

In order to have the FieldPoint modules show up, you will need to right-click the controller under Remote Systems and select "Find Devices".

Please let me know whether the above steps helped get the controller back online for you.  Regards,

[DanJ]

Thanks to Devin for reading the message and taking the time to reply.

Although this is my first post on the NI discussion forum, it is not my first posting (remember "News"?) or my first software problem.

I did verify all the versions of software and the sources as he suggested.  My searching had turned up the Developer Zone papers he mentions - and many more.  I was/am doing everything right - checked and double checked.

But you must always check and verify your assumptions!

I had reset the FP2000 many times.  Each time the IP address was reset to 0.0.0.0 and had to be changed to the one assigned by our IT staff.  Each time I checked and double checked that the IP address and mask were correct.  I should have also checked the IP address on my development host computer.

Sometime during this testing before Christmas, I had reset the FP2000 and also reset the development computer to static IP addresses assigned to me.  These both should have been "nnn.mmm.44.xxx".  Instead, on the development system it had been set to (somehow!) "nnn.mmm.40.xxx".  Since the host and the FP2000 were on a private network MAX could see the remote FP system. But, since the two addresses were on different 'sub nets' with mask values set to exclude the rest, MAX could not download software to the box, it could not get it to check for attached hardware, etc.

Fixed the address on the development host yesterday, and we are back in business.  I still have a problem trying to use network shared variables due to the low memory on the old FP2000, but that is a problem for another day.

Thanks again to those who read my post. 

Dan Johnston

National Research Council of Canada

[Devin_K]

Dan,

I'm glad that you were able to get your FieldPoint back up and running!  With so many things that could potentially be wrong, it's easy to make an oversight like that, especially since the problem was with your PC and not the controller.  Thank you very much for taking the time to tell us how you ended up solving your problem. Hopefully it can help any other members who are encountering a similar problem in the future!

Regards,