04-15-2016 12:01 AM - edited 04-15-2016 12:10 AM
Hello, I'm facing a rather odd situation:
Setup
Observations
What could be causing this? (In case it's related, I also noticed that my NI MAX cannot auto-detect cRIOs that run Linux RT, but it can auto-detect cRIOs that run VxWorks)
			
    
	
		
		
		04-18-2016
	
		
		07:50 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 - last edited on 
    
	
		
		
		02-07-2025
	
		
		04:20 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 by 
				
		
		
			Content Cleaner
		
		
		
		
		
		
		
		
	
			
		
Hi JKSH, 
Have you tried all of the troubleshooting steps listed in the following KnowledgeBase Article titled "Why Does My Netowrked Device Not Show UP in Measurement & Automation Explorer (MAX)?"
			
    
	
		
		
		04-19-2016
	
		
		09:54 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 - last edited on 
    
	
		
		
		02-07-2025
	
		
		04:21 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 by 
				
		
		
			Content Cleaner
		
		
		
		
		
		
		
		
	
			
		
Are you using some kind of a corporate network?
Are you sure communication on all necessary ports is allowed?
			
    
	
		
		
		05-05-2016
	
		
		01:06 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 - last edited on 
    
	
		
		
		02-07-2025
	
		
		04:21 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 by 
				
		
		
			Content Cleaner
		
		
		
		
		
		
		
		
	
			
		
Thanks for your replies, Shalini and stockson.
@Shalini.M wrote:
Have you tried all of the troubleshooting steps listed in the following KnowledgeBase Article titled "Why Does My Netowrked Device Not Show UP in Measurement & Automation Explorer (MAX)?"
Unfortunately, those automated instructions are for CompactRIOs (under "Remote Systems"). They can't be used for my CompactDAQs (under "My System -> Devices and Interfaces -> Network Devices")
@stockson wrote:
Are you using some kind of a corporate network?
Are you sure communication on all necessary ports is allowed?
As I said in my original post, my firewall is completely disabled. There's no corporate network, and all ports are open.
05-05-2016 01:15 AM
So, I tried with another computer an noticed that the "undiscoverable" cDAQ shows a glitch in one of the module names:
Good cDAQ
Glitched cDAQ
(Remember: I was able to manually add the good cDAQ to NI MAX, but couldn't do that for the glitched cDAQ.
So, I removed the glitched module from Slot 3, rebooted the cDAQ, and voila I could add it without any issues. After that, I put the module back into Slot 3 and the glitch was gone and the system continued working just fine.
What could have caused that?