Pci 7344 to compact field point

Is it a good idea to switch from using PCI 7344 motion controller card to compact PAC so that I can implement fuzzy motion algorithm to control three axis ac servo motors.
TQ.

If you need higher level control than PID for your motion application NI SoftMotion is highly recommandable. This software module will give you a trajectory generator, a spline engine and a complete motion API and it is independent from the hardware you use.
As a hardware option I would either recommend a cRIO-System with an embedded controller or a cRIO R Series Expansion system with a PXI-7811R in a PXI chassis with an embedded controller running LabVIEW RT. It's mandatory to run the supervisory application on a RealTime target like the PXI or cRIO embedded controllers as it needs to run in synch with the control application on the FPGA.
FieldPoint or Compact FieldPoint is only an option if your control algorithms are allowed to run extremely slow (more than 10 ms control loop rate). Typical motion applications require control loop rates of 1 kHz and above. The cRIO and PXI/RIO solutions support control loop rates up to 100 kHz and should be a much better choice.
The solutions that I have proposed are of course much more complex than using a PCI-7344 motion controller as all the software layers that are present in the firmware of the PCI-7344 need to be implemented in software. Additionally it incorporates LabVIEW RT and LabVIEW FPGA programming. SoftMotion is a great alleviation as you can concentrate on the control algorithm and the rest is done for you. Especially the shipping examples help a lot to get started.
In my opinion SoftMotion in combination with LV RT, LV FPGA and a corresponding target hardware is one of the best and simplest solutions in the market to create your own motion controller with your own control algorithm.
After the release of SoftMotion it took me only one working day to learn the API, setup the hardware and modify an existing example. After that I had a running motion control application.
Everything is done in LabVIEW, even the real-time and the FPGA programming but it's not a good idea to start such kind of a project as a LabVIEW novice.
Best regards,
Jochen Klier
National Instruments Germany

Similar Messages

Compact Field Point with Touch Panel

Hi.
Have anyone designed a NI Compact Field Point or Compact RIO with a connected Touch Panel Monitor?
I have an instrument with RS232 output (serial data). Since I am using LabVIEW 8,
the executed application should run in Embedded WinXP. But, I need a touch panel for control and monitoring.
I would appreciate any advise please.
Thanks in advance.
Bon

Hey Bon,
What kind of information are you looking for? NI sells a TPC 2006 device which is a touch panel and runs windows CE. This device can be programmed using LabVIEW PDA. This device has a Ethernet port so that you can also communicate to the cRIO or the cFP. Is this what you are looking to do? You can call in on (888) 280-7645 and a sales person would be able to understand your application much better and advise you accordingly.
Regards,
Chetan K
Application Engineering
NI

Gsm modem with compact field point

Hi,
I need to acquire and send data via ftp using a Compact Field Point (there no possibility to use a lan connection or a phone line). I think a possible solution is the use of a GSM modem. Is it possible to connect the CFP to a service provider and access it via ftp (or web server)?
thank you,
paolo.

Paolo Squillari wrote:
Hi,
I need to acquire and send data via ftp using a Compact Field Point (there no possibility to use a lan connection or a phone line). I think a possible solution is the use of a GSM modem. Is it possible to connect the CFP to a service provider and access it via ftp (or web server)?
thank you,
paolo.
Hello Paolo
I have recently been faced with a similar situation. We have a cFP that is in a remote location and being used to log data and control a vacuum system. We also considered the GSM tool box suggested above, but found that it would be too expensive for the actual functionality we required of it.
Insted we have written our own vi's to send GPRS email etc.
If you need help regarding the proceedure etc just ask
Jan

¿Como veo los VI del compact field point?

Hola aqui de nuevo bueno tengo otra duda... como veo los VI que estan alojados en el compact field point al menos los que algun usuario metio en el cFP...

bueno antes que nada gracias por tu paciencia y por responder mis dudas.... ahora me surge una duda:
.... ya pude entrar al ftp ya le puse el pwd y toda la onda ahora mi duda es que no encuentro los vi en el cfp jejeje me podrias indicar en que carpeta esta los programas (vi) que se estan ejecutando en el cfp... apenas ando "migrando" a este ambiente y si me surgen ese tipo de dudas que para muchos son obvias pero creo que para eso estamos aqui jejeje

PCMCIA connectivity to remote controller (compact Field point)

Hi,
I have an acoustic emissions data acquisition board (Micro DiSP from Physical Acoustics), which can be connected to a Laptop using a PCMCIA connection and the acoustic data can be retrieved by the laptop using labview vi's provided by Physical Acoustics.
However, our intention is to use an Compact Field point (cFP2220) to communicate to the Micro DiSP board and retrive the data. Does anyone know how can a PCMCIA interface be connected to cFP 2220? You ideas will be appreciated.
Thank you
Ravi

rpula,
depending on that Physical Acusitcs API you may be able to communicate with the Compact FieldPoint 2220 through the FieldPoint read and write
Sam S
Applications Engineer
National Instruments

Requesting more information about field pointer & compact field pointer?

requesting u to give more info regarding field pointer & compact field pointer?

It is called Fieldpoint and compactFieldpoint.
What information do you want? Look on the NI.com website for the systems and modules. Contact your local sales representative.

Error on compact field point cfp-1808

hello,
why compact field point cfp 1808 not comunicate with lookout field point driver?
i set ip adress yak file and lookout crash. i have on the fieldpoint 5.1 firmware.

What do you mean by "crash"? Any alarms or errors? If possible, please provide some screenshots.
Which version of lookout?
Is everything working with 1808 in MAX?
Please delete all 1808 related configuration in MAX, and let it find 1808 again. Find devices, and save the .iak file. Then try Lookout. Tell me if you can reproduce the "crash" each time you do this.
Ryan Shi
National Instruments

End of memory. Labview + Real time module + Compact Field Point 2120

My name is Michele Ciampichetti, I'm writing from Italy.
Frist of all, excuse for my english.
This is my first experience with Labview, and the application is not so easy. We use Labview 8.2.1
Our system is costituited by two different parts: there is a Compact Field Point 2120 as remote target whit some I/O card, and a PC used to releave data and memorize them (host).
The comunication between the two targets is performed by ethernet lan with Shared Variables not bufferized and not real-time fifo.
The problem is this: the sistem requires a big number of Vis and Variables (about 20 Vis per target and 50 variables localizated in 5 different librarys all in the remote target), and it should store data, acquisited by the FieldPoint, on a database (SQL Server 2005), one time per minute. This storage is made by Labview Database Connectivity Toolkit, and it work correctly. The problem is an excessive consumption of RAM on the PC.
The question is this: The use of many shared variables or vis, bring the memory to always grow? I try to explain myself. When we start our application, after the first minute and registration on the database, the memory grow of approximately 1,3 Megabytes. This is repeated every minute, and after approximately two ours, Labview break down and display "Not enought memory".
We look the on-line help for one solution, and we have found that the variables (local and shared), the concatenate funcion, the array and Vi indicators copy in memory their older value when updated. Is possible that this is the cause of our problem? There is a method to avoid it? How labview uses memory? It is possible set it up for not maintain older value in memory?
We need to run the application up to 4 days for complete its work, is a long test for a climatic room.
We're looking forward to hearing from you.
Best regards
Michele

centerbolt is correct, you can't load a .exe or even run a program on the fieldPoint controller unless you have the Real Time module. However, that does not mean you can't use your FieldPoint bank without the Real Time module.
From LabVIEW for windows you can make calls to the fieldpoint IO using the fieldpoint read/write functions.
This program runs on the PC not the FieldPoint controller. If you loose network connection to the fieldpoint, your program will loose connection to the IO. For many data logging applications this type of arrangement can work just fine. However, if this is the only type of application you are ever going to run, then you may as well not buy the Real Time controller for your fieldpoint but the network controller only.
If your application requires more reliability, and/or greater determinism than can be achieved by running a program on windows, then you should use the LabVIEW Real Time module and develop a program that can run down on the FieldPoint controller independent of windows.
Message Edited by StevenA on 07-22-2008 04:14 PM
SteveA
CLD
FPGA/RT/PDA/TP/DSC
Attachments:
fp pallet.PNG ‏6 KB

What size external Compact Flash does the Compact Field Point 2020 support

I am datalogging with the old Compact Field Point 2020. NI says that the largest Compact Flash card that it supplies and knows the unit supports is 512MB. However I would like to know if it would support larger cards, say up to 4GB. Has anyone tried this?
Pete

I assume that you are using a cFP-2020 and are talking about the removable compact flash available on this device.
National Instruments has only tested this with cards up to 512MB, but it is a standard compact flash interface so it should work with larger. Take a look at the following two documents, which explain this and the type of cards used.
http://digital.ni.com/public.nsf/websearch/C4CFE4A4475705F986256CED0009F993?OpenDocument
http://digital.ni.com/public.nsf/websearch/3FAFA0DB1B261A7886256D10005B021C?OpenDocument
I hope this helps, if you have any questions let me know
Hannah
NIUK & Ireland

Do compact Field Point devices need special drivers in Lookout?

We recently switched one of our processes from regular to compact Field Point. We use Lookout 6.0.1 and are having trouble accessing signals from the Field Point object created in Lookout. Do we need a compact Field Point driver, or does the regular driver support compact field point objects. Thanks for your help.

I am using Lookout 6.0.1, that we purchased about 2 and a half years ago. I do not beleive we have updated any drivers in that time. We are able to view, edit and controls signals with MAX, and have saved our edited informations to a new .iak file. We are using a cFP-1804 backplane with a cDO-400, a cAIO-600, and cTC-125 modules and cCB-1 and 3 bases. Our problem is that in Lookout we do not see any of the connected channels listed in the newly created Field Point object when trying to edit connections or modify existing objects like gauges and hypertrends. We entered the .iak file and checked the import alias information box when creating the FP object. I have been able to write to the DO module, by entering the address DO001.00 in the edit connetions menu, but hae not had the same luck with the AIO or TC channels.
<:AtomicElement>Thank your for your help.
<:AtomicElement>Matt

Compact field point compatability with Labview7

I want to puchase a Compact Field point but need to confirm that it is compatiable with Lab view 7.0

It depends:
1) Are you using LabVIEW RT? Or will your LabVIEW 7.0 application run on a PC?
If you are planning on using LabVIEW Real-Time 7.0, then you cannot use the cFP-21x0 controllers. cFP-21x0 controllers support LV RT 7.1 and higher. If you are using a [c]FP-20x0 controller, then you are OK because they are compatible with LabVIEW 7.0.
If you intend to run your application on the PC and use a cFP-180x network interface (or if you use a cFP-20x0, cFP-21x0 controller as a network interface), then you can use LabVIEW 7.0.
2) NOTE: You will need to download FieldPoint 5.0 drivers (or older) from ni.com to get
LabVIEW 7.0 support. The latest FieldPoint driver installer
(FieldPoint 5.0.1) that ships with the hardware installs support
for LabVIEW 7.1 and higher.
-Tommy

Compact Field Point freezing while executing code

While executing my application, the compact FieldPoint will freeze and break communication with the touch panel. I looked at the error logs for the cFP by right clicking on the target in MAX and selecting view error log and I found this
LabVIEW error log:
#Date: TUE, DEC 22, 2009 07:05:40 AM
#OSName:
#OSVers: 6.3
#OSBuild:
#AppName: /c/ni-rt/system/lvrt.out
#Version: 9.0
#AppKind: AppLib
12/22/09 09:27:32.948 AM
source/mgcore/MemoryManager.cpp(143) : DWarnInternal: Memory error 2 in DSSetHSzClr
$Id: //labview/branches/Orion/dev/source/mgcore/MemoryManager.cpp#27 $
12/22/09 09:27:32.952 AM
source/exec/CleanupProc.cpp(267) : DWarn: can't realloc cleanup tbl
I'm not sure what this message means. Anyone have any ideas what this message means and how to find the issue in the code?
Thanks.

It appears that I have a memory leak in my code. As I execute my code, I can see the memory usage climbing using the Distributed System Manager. Once the usage reaches 91% then the system "freezes". I did read that the memory allocated for subVIs is not deallocated until the top-level Vi finishes running or the entire application stops. So I added Request Deallocation function in each of the subVIs.
I'm attaching a zip of my code so hopefully someone can point out what might the issue or give me more guidance on how to find the memory leak. The code is intended to run a test stand that performs life cycling testing so I've set up a state machine for initializing the system, executing the testing, and then a wait state to see if the operator wants to perform more testing or stop. The testing state consists of 5 state machines that turn valves on or off for a certain amount of time.
I am using a cFP2200 with 2 cFP-DIO-550 and 2 cFP-AI-100.
Thank you in advance for any input.
Attachments:
Valve Test Stand.zip ‏561 KB

Data missing in datalog type files when logging on Compact field point

Hi,
I have a datalogging application running on CFP 2220 which logs data every 10sec to a *.dat file continuously for 2days. The logging method is as follows:
1. Open *.dat file connection once in the beginning of the application.
2. log data continuously to the file every 10 secs
3. Close connection when the application is stopped.
Data fields logged to the file are : Datetime, SensorName, Sensorvalue1, Sensorvalue2, SensorErrordetail.
The problem I am facing is that, when I try to read the data in Labview (on PC) from the *.dat file then it contains valid data only for approx. 1 day and the data for other days is not logged to the file but instead there are empty fields displayed. Also when I checked the file last update datetime I could see thats its latest and updated..
Can someone please help me to figure out the possibilty of the problem.
Thanks,
Alifiya

Matthew
I have tried doing all you mentioned a few times over the last couple of days.
I have somewhat isolated the problem. Here is what I have done. I set up a few systems and have been swapping controllers, back planes, and modules. The only difference between the setups that seems to matter is the software running on the controller. Slot 8 is not working when "FieldPoint 6.0.2 - July 2008" is installed. This is the case for both real-time 8.6 and 8.5. going back to FieldPoint 6.0.1 - January 2008 software results in slot 8 being recognized.
I am currently using the minimal install of FieldPoint 6.0.1 with Real-time upgraded to 8.6 (trying to avoid unistalling programs on computer). Hopefully I will find the mix of software that allows my application to run while still recognizing all slots.
We shall see
Thank you for your time / help.

How Do I accurately measure digital Polses using a compact field point

Hi All,
My Goal Is to measure the speed of an item by measuring the difference between operation of 2 switches.
Pulse can be between 100 msec and hours.
I require > 100 uSec Accuracy @ 100 msec, 1msec @ 1 Sec etc...
This architecture is fixed, What I am looking for is a method.
I am used to using M-Series NI-DAq's with their synchronus digital sampling or counter acquisition,
I have looked at a cFP-DI-304 but it looks like it is an asynchronus sample, dependent on CPU Loading.
The cFP-50x is promising but I can't find many code examples and there are a few "sorry for the missed pulse events" notes.
Does anyone have any suggestions or helpful hints for me?
Thanks in advance.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

As I said in my post, the architecture is fixed, I understand that there are many alternatives, most of them are an "Up-Sell",
Very few have extended temperature range, LV R/T, small form factor, fair price and industrial 24V operation.
We have an existing solution that uses custom hardware and I am looking to improve the accuracy, reduce size, improve reliability and reduce overall system cost,
Compact Rio is too expensive to achieve these goals.
I experimented with a cFP-DI-304 (on change method) yesterday an got reasonable results around the 1mSec mark.
I don't have a sig-gen capable of the 12V required to stimulate the inputs at a a precise rate, so I wasn't able to confirm it's accuracy.
What I want to find out is how accurate the on-change timestamps are? Do they go beyond the quoted 1kHz sampling mode? are they prone to event loss like other NI devices?, Does CPU load effect function.
How about cFP-500/502?
I would like to be able to help myself but I haven't been able to find much useful information on the inner architcture of the cFP backplane, or associated modules.
The most I could find was that the data is transferred a bit like a shared variable.and is subject to losing samples if cpu loading is too high.
In the case of event based acquisition, I am hoping that it capures the edges from a high accuracy timebase and places it in a shared variable /buffer for collection by the software.
Thanks
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

Why doesn't my compact field point file handle files as expected

Before I add this to my LV2011 Whinge Thread I thought I would give the forum a go at this one.
This is a 3 step challenge:
Challenge 1, Spot the difference in the 2 pieces of code
Challenge #2 Explain why this is happening
Challenge #3 Find me a workaround.
Challenge #4, Give me a good reason to continue to use Labview......
Background:
This code is tested and works on a PXI-8108
This code Does Not work on a cFP-2220
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
Attachments:
mytest.vi ‏12 KB

Timmar wrote:
Jarrod,
First let me thank you for the late night post, This way this "behaviour" will ony destroy a small ammount of my Sunday.
My Code is part of a much, Much bigger codebase that is used in multiple programs on multiple platforms (Windows included)
Based on your advice, I should make the change below:
*Yes I know the folder names are differernt, I have corrected this already.
I will check it out tomorrow morning (Sunday) and see if it works.
This code has migrated from 8.5, I am not sure if it supported Path data types in config files.
/* Start Rant
1. My included block diagrams show the "appended array" indicator with identical data for both metheds.
I consider myself to be an experienced programmer and logic would say that I should expect the same result with the same data. They both should either be bad or good, not one of each.
The config file contains the text c:\\meridian\\holding which should be cFP friendly.
2. Why are the 2 platforms different? I don't believe that I should have to change my config files as I move between platforms. (Looks like a Linux Base vs DOS Base) - Very confusing
1) Path differences between platforms is probably one of the single most reasons multiplatform libraries fail in one way or the other. A large part of cygwin and even larger part of MSYS are dedicated to trying to make those differences invisible for the tools that work inside their environment yet they all have the problem that they run sooner or later into contradicting requirements and can't make it fully seemless. LabVIEWs approach is one of the better approaches in that respect.
2) The Path control stores the paths in a platform independant format, but displays them in the format of the host system it runs on. Since your front panel is running on your Windows host, it shows the path as Windows path eventhough the code runs in fact on vxworks, which is for the most part to be considered Unix. The INI file functions store the path also in a platform indepenanden format but that still does not mean that path "/c/meridian/holding" is a valid path on the VxWork system, unless you have created this directory specifically. Because of this it is usually better to not work with absolute paths but instead use relative paths to a known location. Known starting path locations could be the various path constants that are available in the file palette.
And of course if you invent some path location you should also always make sure that the entire path to the directory containing your files does exist, so an execution of the Create Directory Recursively function is always a good idea before trying to create a file someplace.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Pci 7344 to compact field point

Similar Messages

Maybe you are looking for