Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Software versions on fieldpoint controller

[TommyTestBoy]

What drivers do you currently have installed, and what drivers are you trying to install?  I know you are trying to upgrade to LV RT 8.2, but what other drivers do you currently have, and what drivers are you trying to upgrade?

You will definitely need FieldPoint 5.0.1, not 5.0, in order to use the newer version of LV RT.  If you do not have FieldPoint 5.0.1, you can download it from ni.com or get it from a NI Device Driver CD that came with LabVIEW 8.2.

-Tommy

[thieumat]

the fieldpoint driver installed is the 5.1.2 like you can see in my configuration here
the network is ok and I don't see any proble except one : when I have done the backup via the ftp client provided by NI I have also a timeout problem, so I use another client (filezilla) and I have done my backup without problem (probably because of the resume capacity of this client) but this problem may still exist ...

[TommyTestBoy]

Sorry - let me a bit more clear.  The versioning of FieldPoint RT driver components do not match up with the host driver version, and this is a bit confusing. 

If you want to use LVRT 8.2 with FieldPoint, then you should install FieldPoint Drivers to 5.2.0, and FieldPoint VI Manager to 4.1.0 to your FieldPoint controller.  These two FieldPoint driver components are installed with FieldPoint 5.0.1 (either from the Driver CD you received with LabVIEW 8.2, or from the latest FieldPoint CD that you can download from ni.com).  The FieldPoint Driver 5.1.2 and FieldPoint VI Manager 4.0.0  components come with FieldPoint 5.0, and are not compatible with LabVIEW 8.2.  You can see a chart of compatible RT driver versions for FieldPoint here.

Does this help?

[thieumat]

oki

sorry for being so late to answer
so
I follow your advises and I have successfully  updated my controller to LVRT 8.2 and all the software needed to fit this version (fp drivers 5.2.0, fp vi manager 4.1.0, ni visa 4.0, ni serial 3.1 ni watchlog 2.1.5 and ni irda 1.0.1). but I still have some problems :
I have build the code of my predecessor and tried to deploy it but, at the deploy, it said that I have 6 errors that appears to be a shared variable problem (error 1950678996) but it may not be really important or linked to my principal problem :
I access my controller with a web browser, until the update there is no problem but since the update I can't access my controls, the frame of the control panel is there but instead of my controls I have the following text : "remote panel protocol version incompatible"

thank you for your help

matthieu

Message Edité par thieumat le 02-01-2007 04:48 PM

Message Edité par thieumat le 02-01-2007 04:49 PM

[Ching_F.]

Hi matthieu,

The error you are receiving about "remote panel protocol version incompatible" refers to the fact that you probably generated your html code in a different version of LabVIEW than you are currently running on the target.  To resolve this issue, just run through the Web Publishing Tool again in the new version of LabVIEW, and ftp the new html file over to your target. 

As for the issue with the shared variables, can you please elaborate?  The error is due to an invalid variable configuration.  Please try to reconfigure your variables and see if the issue goes away.  If not, please expand on where the issue arises, how the variable causing the issue is configured, and any other information you think would be useful.

Best of luck on your application, and have a wonderful weekend!!!!

[thieumat]

hi
cphuong, I have run through the web publishing tool and deployed my compiled code but with the same error on the remote http acces.
in th FP2120 user manual (section 4-3) the web server configuration is accessible through "Tools>RT Target Options" but in my project, under tools there is no menu called RT Target Options, and I use the stardard web publishing tool, so not specificaly for RT, maybe I haven't installed the right feature ?

[Ching_F.]

Hi thieumat,

Did you ftp your new html file to your controller?  You will need to ftp your html file from  C:\Program Files\National Instruments\LabVIEW 8.0\www to /ni-rt/system/www/ on the controller in addition to deploying your program.

To ftp your html file, open up Measurement and Automation Explorer.  Find you device under Remote Systems.  Right-click on the device, and select the File Transfer option.  Click OK, then navigate to the /ni-rt/system/www/ directory on the remote system and the C:\Program Files\National Instruments\LabVIEW 8.0\www directory on the local host.  Find the html file you created through the Web Publishing Tool on the local host, and transfer this file to the remote system by selecting the file and then clicking on the To Remote button.  Please let me know if you have already tried this, or if you have any further questions.

Best of luck on your application, and have a wonderful day!!

[thieumat]

well well

I follow your instructions without problem, first I can see the frame of my front panel in my webpage but without the front panel and nothing interesting inside but I just have to upgrade the runtime of the navigator in the control computer and I can see the % bar a brief time before a message saying that the vi isn’t loaded into memory

I follow the instructions here http://digital.ni.com/public.nsf/allkb/7FEE6BCFD264175C8625723E000D928E and until the point 8 there is no problem
at this point they said that my vi should be running and I need to stop it, but, my vi isn’t running because it doesn’t ask me to stop it
anyway I follow the rest of the instructions without success, my remote panel isn’t there

I made a right click on my vi under the connected RT target and select run, an error message appears saying "vi using booleans with "latch until released" or "switch until released" mechanical action cannot be downloaded" and nothing else
the error is the same if I try to deploy this vi

I remember you that all the code were probably running fine before the departure of my predecessor so I don't really understand

this story is quite like a quest, I have some parts of the puzzle and I progress step by step, every day I understand new things but every day there is new difficulties ... but I can access the controller just a few minutes per day because this is on the production line,  the time is passing and my boss put more and more pressure on my back ... is there is a way that someone from NI can come on site and fix all my fieldpoint problems in one day to make everybody happy  ?!

[Ching_F.]

Hi thieumat,

The reason you are getting an error that states that the VI is not loaded in memory is because the VI is not running on the controller, so the first problem we must deal with is the issue of the VI not deploying.  To resolve the issue with the incorrect mechanical action, change the mechanical action of the Booleans on your front panel so they are not “latch until released” or “switch until released”.  For directions on how to change the mechanical action of the Booleans, please take a look at the LabVIEW Help on this topic.  (Help » Search the LabVIEW Help » Fundamentals » Building the Front Panel » How-To » Front Panel Controls & Indicators » Boolean Controls » Changing the Mechanical Action of a Boolean Object)  Once the VI is deployed, you can double click on the VI through the project and the front panel should open.  Once you do this, you should be able to view the VI through the web browser.

Please let me know if this doesn’t work.

As for your request to get someone from National Instruments to visit you, you may contact your local sales representative, and see if they are able to come help you.  Also, you may go to http://ni.com/ask, to create a service request and speak to an Applications Engineer on the phone.

Best of luck on your application, and have a great day!!

[thieumat]

all right
for the mechanical action of my buttons this is very strange, switch until release wasn’t supported, it was impossible to deploy with it, I flush it and replace it by a bit of code that do the same programmatically and then I could deploy 0_o ...
anyway it seems to work, my startup vi is accessible through a browser and I need just a last hint :
on my browser the vi is there but it's not running, I need to click on the arrow to start it and it execute only once for about 10s and then it stops
isn’t it supposed to run continuously ?, seems like it runs a loop and then it reinitializes
with the run continuously arrow it just restart every 10s ...
I think that instead of loosing my time by trying to reuse the (big and dirty) code of my predecessor I had code my own program from ground I may have now a good control on my process instead of being in the dark ...