12-14-2023 08:03 AM
Hello,
I try to connect to a Ni 9074. I am having a hard time doing this. I did try to do most of what's described in this link:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019R3TSAU&l=nl-NL
When I read the link above I get the impression I need to make or edit a config file. I did search for It but I could not find it. Could this be the reason I do get Error -314004 ?
Hope you can help, thanx
12-14-2023 09:26 AM - edited 12-14-2023 09:27 AM
Update:
I did check the CPU load with Ni distributed system manager and I can see the Normal priority is 97 or higher all the time.
I did close the debug connection with the cRIO and I did manage to connect one time. But then the shared vars were giving an error. I will try to find which loop is causing this behaviour.
Is there a kind of systemmonitor for the cRIO which can pinpoint more accurate ? like top in linux? This cRIO uses VxWorks btw
12-14-2023 11:23 AM
I think I might be doing something wrong with deploying the code to the cRIO.
I do a build, clicking the build file --> right mouse --> build
Then I click the build file to deploy. when I deploy I get a message telling me
the target is already running a real time application I can click okay then it deploys. The CPU load drops so I know the new build is running (I did put a wait in the loop receiving messages from the message stream of 50 ms it was 1ms). when I reboot the cRIO hitting the reset button the CPU load is high again. This makes me think a old build runs after I hit the reset button. There is also a switch on the cRIO telling me "No APP". As there are a lot of things that might go wrong can someone please tell me if I need to use the "No app switch" ? Or give a general direction how to fix the network issue. I think I need the lower CPU load to connect to the cRIO to start with.
12-14-2023 01:08 PM
Can you share your code? It's extremely hard to troubleshoot without code.
12-14-2023 03:25 PM - edited 12-14-2023 03:33 PM
Hello adekruif,
thanx for your reply. It is hard to share this code because is property of the company I work for.
I think I did find something though.
2023-12-14 11:07:24 DROP UDP XX.XX.XXX.XX 224.0.0.251 5353 5353 904 - - - - - - - RECEIVE
2023-12-14 11:07:24 DROP UDP XX.XX.XXX.XX 224.0.0.251 5353 5353 286 - - - - - - - RECEIVE
I think my setting for seeing the blocked packages with procmon was wrong I ended up with searching for the firewall log file the name of the file in windows is: pfirewall.log it is located at this location c:\Windows\System32\Logfiles. I did replace the lp number with X characters for security reasons. The IP is the IP from the cRIO
If anyone knows the correct filter for procesmonitor to view the dropped packages please let me know!
I am at home now, tomorrow I will have another try. I think I need to open these ports is this correct ?