CRIO 9073 Question

[Fifty60_Hurts]

I am new to an old CRIO 9073 module.  I have studied for several days but there are still some basic gaps in my understanding. 

For example, is there an actual VI running on the CRIO 9073 module itself?  Or does the VI run on the host PC? 

If the VI runs on the module, is there any way to export the VI of the CRIO module if I do not already have a copy of the VI?

Thank you

[ZYOng]

It depends on the location of the VI. If it is placed under My Computer, it is running on the host PC. It runs on the cRIO if it is placed under Real-Time Controller and on the FPGA in the form of bitstream if it is under FPGA Target.

Understanding Communication Options Between the Windows HMI, RT Processor, and FPGA summarizes the options of communication between these targets.

cRIO-9073 is a controller. It interfaces with the module either via Scan Engine or FPGA. Only compiled binary is deployed to the cRIO. If there is an RTEXE that is configured to run on startup, it is not possible to retrieve the source code from the compiled binary.

[Fifty60_Hurts]

I believe I am using scan engine but I do not see NI-RIO in NI MAX.  Shouldn't I see NI RIO installed on the host PC?  Here are all the modules installed..

 

[GerdW]

Hi 5060,

---

@Fifty60_Hurts wrote:

Shouldn't I see NI RIO installed on the host PC?

---

When you want to program your cRIO then you need to install LabVIEW-Realtime module with "cRIO support".

I don't see those in your MAX screenshot…

Are you stuck on LV2009?

[Fifty60_Hurts]

I am migrating a 2009 LV and TestStand 4.2 to a windows 10 PC.  I know 4.2 and 2009 are not officially compatible, but NI said it "might" work.  All the VIs open up and run without crashing.

However, I am having trouble communicating with thr CRIO.  The last Max screenshot was from the old PC that is working.  I have the same packages installed on the new PC.

I believe I am using datasockets to communicate with the CRIO.  However the DS block in labview only has a pure URL fed to it for example \\\\192.167.50.9\\advint_hvac

\\ana_out?sync = true.   

It seems like I can see the CRIO but when I try to write to it I have problems.  I am trying to understand what I need set up on the new PC to make the datasocket comms possible.

When I look at distributed system manager I see this on the old PC, and the 2nd is what I see on the new PC.  I am missing items under local host a d I think this is a clue.  I appreciate any feedback you can provide 

 

 

[GerdW]

Hi 5060,

---

@Fifty60_Hurts wrote:

I am migrating a 2009 LV and TestStand 4.2 to a windows 10 PC.  I know 4.2 and 2009 are not officially compatible, but NI said it "might" work.  All the VIs open up and run without crashing.

However, I am having trouble communicating with thr CRIO.  The last Max screenshot was from the old PC that is working.  I have the same packages installed on the new PC.

I believe I am using datasockets to communicate with the CRIO.  However the DS block in labview only has a pure URL fed to it for example \\192.167.50.9\advint_hvac\ana_out?sync = true.   

It seems like I can see the CRIO but when I try to write to it I have problems.  I am trying to understand what I need set up on the new PC to make the datasocket comms possible.

When I look at distributed system manager I see this on the old PC, and the 2nd is what I see on the new PC.  I am missing items under local host a d I think this is a clue.  I appreciate any feedback you can provide 

---

It seems the old setup uses NSVs (network shared variables) to exchange data between cRIO and host computer.

I'm not a fan of those and did not gain much experience in using them. That being said:

• Can you access the shared variables on your cRIO using the DSM?
• Is your cRIO using the IP 192.168.50.101?
• Is the IP 192.168.50.9 hardwired (as constant) in your old VIs?
• When your cRIO hosts those NSVs then you don't need them additionally on your "localhost" IP. Background: only one system in the network should host the (same) NSVs…

[Fifty60_Hurts]

Below is what I see on DSM.  The CRIO is ip 101.  I do not see anything set up as ip 9, so not sure how to answer that question about it being hard coded.

For NSV, would I need ip 101 (the CRIO) to appear in the network or is it OK just appearing in My Systems?

 

---

[Fifty60_Hurts]

Below I think shows the issue.  IP 105 is the host PC and not the CRIO.  The command has ip 105 and the response is that ip 105 cannot find the label....

 

[JÞB]

Put the phone down! Your snapshots are very hard to see.

Your PC has a snipping tool that can capture screen areas.

[Fifty60]

Sorry about that, here is a better screenshot.It