CompactRIO configuration

[Ice__man]

Hi everybody

I have a heating/cooling chamber which I need to write a controller for and I was wondering, if I buy the configuration attached Configuration ID  CR2775920, do I have everything to program and run my chamber controller or does the RIO controller also need a license or something (do not think about the I/O modules)?

The chamber runs typically for 3 months so I was thinking cRIO because I don´t see a PC running each test for 3 months sucessfully, is that a wrong assumption?

I need to log and query for a database and since cRIO does not support the database toolset I will have to program a solution around that.

I have no real timing demands so I think the FPGA Deployment Option is an overkill, is that a correct assumption?

All feedback is very appreciated

ps. If I do not go with the RIO then I will go with the CompactDAQ configuration also attached Configuration ID  CD2775595 and buy LabVIEW Developers Suite.

Thanks

[Rachel D]

Hi.

cRIO will be the best choice for your application. You will need a chassis, controller, and I/O coupled with LabVIEW development, LabVIEW RT, and LabVIEW FPGA which is included in the Developer Suite.

To ensure that you are choosing the best hardware and software for your application, I would advise you to contact a local National Instruments technical sales representative. You can find contact information for your region at the below link:

[Ice__man]

Thank you Rachel

Quick question though, what is the argument(s) that I should choose cRIO instead of cDAQ?

thanks for replying

[Ice__man]

Last question(s) Rachel, then I will leave you be;)

As before:

1. what is the argument(s) that I should choose cRIO instead of cDAQ?
2. You said "You will need a chassis, controller, and I/O coupled with LabVIEW development, LabVIEW RT, and LabVIEW FPGA which is included in the Developer Suite." It seems to me that neither LabVIEW RT nor LabVIEW FPGA is in cluded in the Developers Suite according to NI.com? And why do I need LabVIEW FPGA since I have no real time demands (everything happens in the temperature domain which is very slow)?
3. I could also use Compact Fieldpoint instead of cRIO, but it seems to me that cFieldpoint it is at least the same price as cRIO and the only big difference I notice is that cFieldpoint has a much lower sampling frequency?

I hope that you will find time to answer this

Thanks again for the help

[Rachel D]

It would really be best for you to talk to your sales representative to get the best answers to your questions. He/She will be able to discuss the specifics of your application and decide which software and hardware options would be the most appropriate for your needs.

You are correct in that LabVIEW RT and FPGA are not included in the Developer Suite. I apologize for giving you incorrect information.

Best,

[Ice__man]

Hi again Rachel

The country that I am in (not Denmark) has very little Labview activity, a fact that I would like to change.

Therefore I would really like you to answer the questions since you are already a bit familiar with the

system specification and we are in dialogue?

1. What is the argument(s) that I should choose cRIO instead of cDAQ?
2. Do I need LabVIEW FPGA since I have no real time demands (everything happens in the temperature domain which is very slow)?
3. I could also use Compact Fieldpoint instead of cRIO, but it seems to me that cFieldpoint it is at least the same price as cRIO and the only big difference I notice is that cFieldpoint has a much lower sampling frequency?

Thanks again

[taper]

You should use a cRIO only if you need the benefits of a Real-Time system.  You get a self-contained system with limited storage and display capabilities.  They will be more stable than a Windows system, but usually more complicated to get running.  If you can run all your modules in Scan Mode you won't need any FPGA development or license.  Scan Mode is much slower than reading with the FPGA though.  If you need a display or logging you'll have to setup a Host PC and shared variables.

cDAQ runs off a regular computer with DAQmx, just like a PCI(e) DAQ card.

I've run continuous tests for a few months at a time on Windows.  It usually works, just make sure your machine is clean of any dead weight that doesn't need to be running.  It sounds like your system will be dependent on a PC anyway for the database and logging, I'd use the cDAQ and put in some kind of notification if it's not running.