Control fieldpoint fp-do-400 through network ...

[Jimmy89]

Hi,

I've a problem :

         I've a vi who control a fieldpoint fp-do-400. If I connect directly the modules to a computer, the vi can control de fieldpoint,    BUT if I connect the modules to the network and the vi cannot control it ...   (my control is : when my shaft is more than 300rpm "whith AI-100", it allows fp-do-400 to turn ON the sourcing output)

Do somebody 've had the same problem ??  How can I do to be able to control through the network ? 😞       heeeelp

[Graziano]

Hi!
   CAn you clearify about your system? which ethernet controller have you connected to the FP-DO-400? Or you're using a serial module and bricging serial/ethernet?  Can you post your VI? This too can help understand the problem.

graziano

[Jimmy89]

Hi Graziano,

My ethernet controller is a FP-2000.

To cearify my problem, i've created an executable of my vi and when i launch it on the network, I use an other computer than the "programmer computer".

And I was thinking about one thing just before :

                my problem is from this morning, because I've just installed the Fp-do-400, so modify my *.iak file.    I think it doesn't work because i've not update this file on the computer connected to the network.

Do you think it could be that ?     Now i'll try it on Monday, not before :-(, one guy is missing to make me able too ...

[Graziano]

Hi!
   If I understand, you have created a VI on your developement computer, and tested it on FP-2000 module.  Are you programming it as a Real-Time target?

   The other PC, has the same LabView developement environment? I mean, did you used RT on your PC, and then try to run this VI on a PC without RT? Sometimes, this is an issue.

   I once developed an application, and connected to fieldPoint through different PCs, that didn't have the same iak file (but the same LV dev gear), and this didn't cause problems, but I can't grant that the problem you get is not due to iak file.... sorry!

   Taking a look at the code can help! Can you post it? Also a simplified version, or a picture of it...
  
   BTW, which LV are you using?

graziano

[Jimmy89]

Hi Graziano,   sorry for the late ....

Yeah, that is !

I'm going to ask you something silly ...   when I'm programming for example with LabView 7.1  , where is the difference between Real-time and normal ?? 

Hum, ok, i'll post the VI, i've got here.

So, I'm using Labview 7.1

Thx a lot

Jimmy

[Graziano]

Hi Jimmi!
   In general, Real-Time is absolutely not the same as non-Real-time! In real-time you have some useful functions, and a RT-OS running on your FieldPoint module.  An important issue, is that when you develop for a Real-Time target, you can embed your application into the target, for example, it's been a long time I'm developing aplications that resides on compact Field Point cFP-2020 and cFP-2120, that work as stand-alone CPUs (not connected to PCs), i.e. when you feed the system, cFP-2020 boots and start application.  You can't do this in non-real-time, to say it simply!

   Anyway, if you have Real-Time package, you can execute on your PCs almost the same code you develop for a real-time target (except those architecture-specific functions, of course!).  And on the other side, when you develop for a real-time target, you can't use al the functions of LabView.  When you target a cFP-2020 (similar to FP-2020), for example, you can't use LabView functions listed in chapter 4-1 of cFP-20xx user guide, namely:

  
    • ActiveX
    • Front panel datalogging
    • Dialog boxes
    • Printing
    • Programmatic menus
    • Front panel Web publishing
    • NI-DAQ

    And some other functions seems to have limited behavior, such as front-panel objects references, as I discussed in a former post.

  Hope this helps...

   Anyway, if you have some specific questions, post them, especially with your code, and problems you encountered.

graziano

[Jimmy89]

Graziano,

Thx for all !!   You've been very helfull !! really

Best regards
Jim

[Graziano]

Yuo're welcome!
   Anyway, most things you can find on the documentation, the only problem is that sometimes there's a plethora of User manuals, application notes, datasheets..

graziano