I'm using a 9045 cRIO that was being used in an older project with two C series modules into it. After keeping pressed the reset button for several seconds to reset IP settings and other old user config and setting my own one I added it to a LV project.
The problem was that I couldn't right click into the chassis label in the labview project tree because it throws an error saying "Unexpected Error" without elaborating further. Also, if I tried to add the series C modules into Real-Time Resources it said "An error has ocurred. Visit the..." Also without elaboratin further about the kind of error. But then I noticed that under NI MAX there was a VISA error in the cRIO, specifically under the "Devices and Interfaces". It was saying error "0xBFFF00A7" and it was mentioning "viFindRsrc", but I don't have the full error sentence, but these were the relevant bits.
I have find some relevant posts like this, this or this one, but nothing useful...
The point is that I was able to ping the cRIO and even I logged in through SSH to check if there was some visa proccess running on it, and "ps aux | grep -i visa | grep -v grep" returned "1907 lvuser 0:00 /usr/local/vxipnp/linux/NIvisa/nivisaserver" so it seems it was working properly.
So then I removed all the cRIO software and installed it again (including the NI-VISA). Now, there isn't the error under NI-MAX anymore but I still can't right click chassis label into LV project nor add the serie C modules into real-time resources... But I can read data through MAX test panels!
So to recapitulating and (maybe) adding some extra info...
I can:
- Ping the cRIO and login through SSH
- Use test panels trough NI MAX and acquire real data from the series C modules
- Check the connected series C modules through NI MAX & labview (but not add them to the LV project)
I have checked/done:
- NI-VISA use the same port (3537) and version (18.5) in host and cRIO
- NI-VISA is running in host and cRIO
- Reinstalled all cRIO software
I can't:
- Right click into chassis field in LV project ree
- Add series C modules into LV project
EDIT: I have found error logs like the attached one in the cRIO. I don't know if they have anything to do with the error.
