Just to double check, are you sure that the CNC IP Address is set correctly on the switch? (Run the show tsn cnc) command and be sure that the output matches the IP address for your VM.
Below is the output of that command. The IP is the same as the CNC.
One other thing I'd like to try is changing the credentials that the CNC uses to authenticate with the switch. When attempting to setup the switch secret and password, there was an error on the switch saying that both password and secret for a user could not be set at the same time (although I was following the commands for setting up the switch elsewhere on this forum).
If you design the network topology manually and create the schedule, does that process work for you?
to follow up to what Miro stated, if the CNC discovery fails to find the CRIO devices but does find the IE4000's check one thing
- the hostname length of the crio. there could be an issue on teh CNC where the length of the hostname being discovered by the CNC exceeds some internal buffer length. this 'could' be the root cause of the issue.
i've seen discovery work where the devices connected to the IE4000 with short host names (<20 characters) are discovered and long host names are not. I don't have an exact length at this time.
if that doesn't resolve, then fallback plan is to create the CRIOs virtually in the CNC, and create the link between the virtual CRIO and the Ethernet interface on the IE4000. this will allow you to move forward with creating schedules. and as long as the IE4000's are discovered, you should be able to distribute computed schedules to them for TSN traffic flows.
if you are still having issues, to root cause the problem I will need you to capture a log on the CNC.
1) open a command line on Ubuntu on CNC
2) cd ~/de/cnc/logs
3) tail -f ncs-java-vm.log
note: you'll need to capture log output
4) in the CNC start a discovery process
5) keep capturing the log until it looks like it has ended.
append the log in a response on this thread.
Adding the cRIOs manually didn't seem to work. When trying to connect to the cRIO I created I received the error "Device [cRIO] is south bound locked". (See attached screenshot). Also attached is the log from the CNC during a discovery
The device section should only contain devices that the CNC is communicating to, which is a IE4K switch only. Just to recap, the CNC role is to simply compute a schedule for the ports on the IE4K and deploy a schedule to a IE4K switch. However, before this happens the CNC needs to know what devices are connected to what port. This seems to not work for you so what Albert suggested is to add devices manually (aka build network manually).
From home screen:
- Add a switch to the network and cRIOs. I believe you mention that the switch shows up already. Therefore continue with adding cRIO
- Continue adding all of your devices in similar fashion. In my case I added two cRIOs which look like this:
- Next add a link between each device. In other words, telling CNC how the devices are connected between each other. It only cares about the "TSN connection". In my case I added two links. First, between the volt1 port8 and cRIO1 port 1. Second, between volt1 port 5 and cRIO2 port1.
In the end my network looks like this:
Network is completed now, you can proceed adding flows between devices as shown in the video.
Thank you, I didn't realize that the "discover typology" step wasn't required. However, now that I've moved past this section and am attempting to push my new schedule to the switch, it shows as "no devices currently connected", even though my switch is connected and shows up under "Devices".
I can't see video on the page. Can you send video to my mailbox.