LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

cannot read network published shared variables, lvlib on PC and VI on cRIO, error -1950679027

Solved!
Go to solution

Hi Aaron,

 

thanks again for the help. The wizard was able to find my cRIO and confirm no firewalls are blocking the wizard or MAX. I added the sequence structure with a 5 second wait to initialize the SVE and still receive error -1950679035. Attached screenshots have details.

 

best regards,

Ryan

Download All
0 Kudos
Message 11 of 27
(2,154 Views)

Can you run the code without error if you connect the cRIO directly to your computer over Ethernet?

 

It would also be helpful to get a Wireshark capture while you are deploying your executable. There might be some information in the capture that would point us to the reason your code is not running at startup. 

Aaron Douglass
Applications Engineer
National Instruments
0 Kudos
Message 12 of 27
(2,136 Views)

I installed the latest cRIO drivers (CompactRIO 16.0 and NI-RIO 16.0) but still receive the error. I used a crossover cable & receive the same error as when i use a router. I installed wireshark but cannot run the tutorial VIs in step 4 (TCP Communication between Host and Target using Labview) because I am missing 'Add Noise.vi' and because wireshark does not show a capture interface for my cRIO, only two USB ports. 

 

I noticed the 'getting started with wireshark' is from 2014, wireshark version 0.99, labview 8.5 while i have wireshark 2.2.3, labview 2015 so a good amount of differences exist. i've spent a few hours on it but will continue to try and capture packets and follow the TCP stream between my computer and the cRIO. do you think chasing this solution path is worth it considering the additional obstacles i've discovered?

0 Kudos
Message 13 of 27
(2,105 Views)

I resolved the wireshark issue using the below link.

https://ask.wireshark.org/questions/1281/npf-driver-problem-in-windows-7

 

I resolved the missing 'add noise.VI' subVI by revising a case structure in Server.VI to only do the generate random number case instead of a cosine or sin function with noise.

 

The Client and Server VIs run properly while the wireshark captures packets and follows TCP streams. I am unsure of how to interpret this data. Should i be looking for other colors than purple in the 'packet list pane' of wireshark?  When i saved a TCP stream it was 40 MB so i did not attach it. Where do we go from here? I have attached 4 screenshots of running the recommended LabVIEW project and wireshark.

 

0 Kudos
Message 14 of 27
(2,097 Views)

Thanks for going through the trouble to generate that Wireshark capture. I sent you a personal message with instructions about how you can get that to me since it is too large to post here. 

 

A few other suggestions:

Have you tried desabling firewalls since error -1950679035 became the primary error? Firewalls are a very common cause of this error. There is some more information here.

 

Do you still see the original error (-1950679027) or are we strictly dealing with error -1950679035 at this point? How often do you see each error?

 

If you ignore error -1950679035 does it go away after a while?

 

If you host lvlib on a different computer can you access it from the cRIO? Do you get the same errors?

 

Do you have multiple NICs on the PC you are hosting lvlib on?

 

Thanks,

 

Aaron Douglass
Applications Engineer
National Instruments
0 Kudos
Message 15 of 27
(2,057 Views)

Good Morning Aaron. Please see the below responses.

 

I have tried disabling my windows firewall & verified with MAX discovery wizard that no firewalls are blocking the cRIO.

 

I am currently receiving only -1950679027 for all configurations (configuration = possible solution that does not work. firewall on or off, crossover cable or router, bound control or control writing to NPSV, sequence structure used to write to NPSV then read or parallel loops with NPSV initialization). As i have tried different configurations, -1950679035 would sometimes result. I tried to duplicate it but cannot currently. 

 

The errors do not go away if ignored for a while. 

 

I only have 1 computer with labview. I do have LV2014SP1 with a different SN that i could install on a different computer to check. I'll do that today. 

 

I believe i have one Network Interface Card (does one card do wireless & ethernet?) on the PC i am hosting the lvlib on. i have attached a screenshot of control panel-device manager-network adapters. I always disable my wireless network connection when connecting to the cRIO via ethernet. 

 

i went ahead and attached the wireshark capture (pcapng file) since this is only 280 KB. if you'd like me to select a right click a specific packet and do follow TCP stream to generate a 40 MB file, please let me know. 

Download All
0 Kudos
Message 16 of 27
(2,040 Views)

Here is some additional information regarding the wireshark capture. My computer IP is 192.168.1.5 and the cRIO is 192.168.1.214. The wireshark capture was taken when running the lvproj that i originally uploaded, not the wireshark tutorial lvproj. 

0 Kudos
Message 17 of 27
(2,038 Views)

Thanks for sending in that wireshark capture and the additional information. I will need another day or so to look into the wireshark. I will post back here when I have some new information. 

Aaron Douglass
Applications Engineer
National Instruments
0 Kudos
Message 18 of 27
(2,027 Views)

Hi Aaron,

 

I received the same errors when running the lvproj on another computer. 

 

I tried running the VI and lvproj on a home computer that has LV2012. After installing the required 2012 drivers on the cRIO & activating modules on my computer, i was able to duplicate the 3 combos of VI and lvlib location that work and the 1 combo that doesnt work (lvlib on computer, VI on cRIO). i received the same 2 errors: -1950679027 and sometimes -1950679035. i also found that labview 2012 was not as robust when deploying lvlibs after you move lvlib location in the lvproj. i had to open the DSM to remove the library, close & open the lvproj, then re-deploy to see if a given configuration would work. 

0 Kudos
Message 19 of 27
(2,018 Views)

Are you sure this can be done? Sometimes when I move the lvlib to the computer from the cRIO or vice versa, the setup doesn't quite "register" the change and still uses the lvlib at the old location. This makes it look like it works when it really doesn't.

0 Kudos
Message 20 of 27
(2,017 Views)