cRio Programming without the Real-Time module

[CharlesD3]

Does anyone know a way to access and program a cRio (model 9053, specifically) without using the Real-Time module?  It seems utterly ridiculous that NI sells a piece of equipment for ~$5000 or more, and then wants another $5000 for the software to use it.  And that's on top of the $8000 or so paid for the "PROFESSIONAL" version of Labview.  It may be that those things are all true, despite the ludicrousness of it all, but since I can control the equipment in MAX, and can create a front-panel 'RIO' device that recognizes it, then I should be able to program it somehow or other, right?  Has anyone figured this out?

Thanks,

[wiebe@CARYA]

---

@CharlesD3 wrote:

 and then wants another $5000 for the software to use it.  And that's on top of the $8000 or so paid for the "PROFESSIONAL" version of Labview. 

---

Are those Singapore or Canadian dollars or something?

We usually pay more euros that US dollars, and in euros it's no where near 5000\8000 (2745\5121 ATM).

Exaggerate too much, and you'll loose your audience. 😊

---

@CharlesD3 wrote:

Does anyone know a way to access and program a cRio (model 9053, specifically) without using the Real-Time module? 

---

I think you should be able to access it, like Distributed System Manager does.

Programming it is possible, I guess. Not with LabVIEW though.

[CharlesD3]

I stand by my statements.  It is ridiculous to sell a product that does not include the software necessary to use it.  I can understand only including some lesser functionality, which is why I want to believe that there is some way to access it; I just have not found it yet.  Labview recognizes it as a "RIO Device", but it does not connect to anything I am used to using.

[GerdW]

Hi Charles,

why do you expect you can connect a "RIO" reference to VISA/IVI/NI-DMM functions???

Another question: why did you bought that cRIO before discussing all these issues with sales support?

I know other hardware, where you also get just some very basic software with the hardware. As soon as you need an advanced feature you also need to buy the full-featured IDE. (Phoenix Contact PLCs...)

For cRIO it's the same: you can start with a trial version of LabVIEW with nearly all modules included!

[CharlesD3]

The sales people never bothered to mention the limitations of the cRio.  I had previously used a PXi, which was perfectly compatible with the "Professional" version.  NI was 'gracious' enough to give me a trial version of the real-time module, but that has now expired.  Again, I stand by my statements.  The system should include the software modules necessary to use it.  And again, I will re-iterate that I understand some lesser functionality, but the equipment should be usable as purchased.  Using it at all is not an advanced feature.

I have no particular reason to expect the "RIO device" to connect to those items in that image, those are just examples of it not connecting to some common measurement tools.  The attached image is a VI that would work if Labview recognized the cRio in the same manner that it is addressed in MAX.

[wiebe@CARYA]

---

@CharlesD3 wrote:

The sales people never bothered to mention the limitations of the cRio.  I had previously used a PXi, which was perfectly compatible with the "Professional" version.  NI was 'gracious' enough to give me a trial version of the real-time module, but that has now expired.  Again, I stand by my statements.  The system should include the software modules necessary to use it.  And again, I will re-iterate that I understand some lesser functionality, but the equipment should be usable as purchased.  Using it at all is not an advanced feature.

---

I'm not disagreeing... There's just nothing I can do about it.

EDIT: you could ask for someone to make a RT exe so it isn't just an expensive door stop.

[JensG69]

---

wiebe@CARYA wrote:

---

---

I'm not disagreeing... There's just nothing I can do about it.

EDIT: you could ask for someone to make a RT exe so it isn't just an expensive door stop.

---

Or you could try to get your cRIO exchanged to a cDAQ chassis. Judging from your last screenshots that is what you were looking for in the first place.

Regards, Jens

[GerdW]

Hi Charles,

---

@CharlesD3 wrote:

The attached image is a VI that would work if Labview recognized the cRio in the same manner that it is addressed in MAX.

---

That is DAQmx - an advanced feature in my opinion!

DAQmx on cRIO is only available to the most recent devices with recent LabVIEW versions…

(Until now I work with LV2017 and cRIO906x/907x, which both don't support DAQmx on cRIO…)

Btw. the nice thing about NI is they provide all manuals online. You could the GettingStartedGuide like this before buying expensive hardware - it contains a section on needed software!

[wiebe@CARYA]

---

@JensG69 wrote:

---

wiebe@CARYA wrote:

---

---

I'm not disagreeing... There's just nothing I can do about it.

EDIT: you could ask for someone to make a RT exe so it isn't just an expensive door stop.

---

Or you could try to get your cRIO exchanged to a cDAQ chassis. Judging from your last screenshots that is what you were looking for in the first place.

---

I would definitely try that.

In fact, I'd try that first.

[JensG69]

---

@GerdW wrote:

Hi Charles,

---

@CharlesD3 wrote:

The attached image is a VI that would work if Labview recognized the cRio in the same manner that it is addressed in MAX.

---

That is DAQmx - an advanced feature in my opinion!

DAQmx on cRIO is only available to the most recent devices with recent LabVIEW versions…

(Until now I work with LV2017 and cRIO906x/907x, which both don't support DAQmx on cRIO…)

---

A cRIO-9053 belongs to those devices where you can use DAQmx from an RT-part of the cRIO. Since the 905x line is the current startup line I would not call it an advanced feature anymore.

But still - you cannot use such a cRIO like a cDAQ directly from Windows.

Regards, Jens