Troubleshooting

networking renderer is not receiving data assuming that the connection between the ncam server and the renderer is a network connection, attempt the following confirm that the required tracking data is being sent from ncam, this will be shown in either the "dashboard" of the webui or the "system status panel" of the full ui if the required tracking output is not turned on, proceed to the the "preferences > data stream" window in the full ui to configure which tracking streams are sent confirm that the network configuration between the two devices is correct, can the two devices ping each other? is the correct port number set on both devices? can't configure a manual ip address the eth0 interface of the ncam server is configured as part of the ncam setup and it is not recommended to change it however eth1 and any other additional network interfaces that are present are able to be modified via the ubuntu network manager, this is reached via the ubuntu system settings black sceen on remote connection use the hdmi dummy dongle that is provided with the mk2 system, without this the graphics driver will not initialize on boot of the system connection "cannot open the video stream" this is typically caused when the witness camera bar has not been connected properly attempt to re seat the usb c cable and try connecting again "unable to connect to lens encoder" this error message is displayed when a network connection can not be established to the connection box, try the following steps confirm the connection box is powered confirm the network between the connection box and server is configured correctly typically it should be connected directly to the eth0 of the ncam server ensure the correct hostname/ip address has been entered into the "devices > camera bar > open" dialog power cycle both the ncam server and connection box witness camera images are laggy this is caused by connection issues between the ncam server and connection box remote connection when working through a vnc client or remote connection, some lag is to be expected confirm that the connection between the server and connection box is gigabit, this can be done using the "ethtool" command in a terminal enter the following ethtool eth0 this will display connection info for the eth0 interface, the " speed " value should be " 1000 " if "10" or "100" is displayed, try disconnecting and reconnecting the network connection between the two devices if the connection is still not gigabit, powercycle both devices can't connect to connection box unless the connection box has had a hardware failure then this is nearly always related to a network configuration issue, try the following steps remove power and network connection to the connection box connect power and wait approx 30 seconds, led light on connection box should begin flashing amber connect network connection, led should turn green and stop flashing if the led does not turn green, check the following does the network cable go directly from the connection box to the eth0 port on the ncam server? has the network configuration script been run on the ncam server? try replacing the ethernet cable between the two devices once you have a green led displayed on the connection box, you should be able to connect to the box via the full ui select " devices>camera bar>open " from the drop down menu, enter the connection box hostname + " local" into the popup the hostname will be printed on the connection box and will be in the format " ncbxxxx " if you are unsure of the connection box hostname, the appendices has a section on how to find this again if no lights are displayed on the connection box at all check that the power is properly applied to the device, if possible try an alternative source of power be aware that it will take approximately 30 seconds for the led to light after power is applied, this is normal calibration liveupdate does not give good results this is typically the case when the lens calibration has not been done very accurately if the liveupdate solution places the witness camera in the right orientation, but ahead of or behind the main camera by an exaggerated amount then this is a result of the h and v focal values in the lens calibration being wrong tracking stuttering in tracking data from the perspective of the ncam system, this can be caused by the following circumstances if a connection box is being used, the connection between the two devices must be gigabit use the "ethtool" in a terminal window to confirm that the network link speed is "1000" issues with the automatic networking tool can sometimes cause it to throttle down to 10/100 speeds if the ncamsdk datastream is being used and the renderer is requesting the key channel then this can use up a considerable amount of network bandwidth if streaming large amounts of tracking data ensure that the network interface between the server and renderer is at full speed the ncam server is not in "on air" mode on air mode should always be switched on when consistent tracking data is required tracking parameters are set too high in the full ui having the "density" value set to high values (over 25) or the "key position" value set very low (0 3 and lower) can cause the performance of the ncam server to degrade from trying to track too many points at once having too many "tracking cores" enabled at once it is possible to enable all the tracking cores at once, this can cause performance issues, particularly on the mk2 server, and is not how the multiple tracking options were designed to be used ncam support can advise which tracking cores should be preferred for your usage scenario disable the "fiducial" tracking core the fiducial tracking option only needs to be enable when initially learning the fiducials once the fiducials have been learnt and saved as part of an alignment then there is no requirement to have the core activated for normal usage reflective makers not being detected make sure that the "circular features" tracking option is enabled in the "preferences > tracking" window reflective markers should not be deformed in how they are applied to a surface that is to say, do not stick them to curved surfaces such as pipes or tubes as this will impede how well they can be detected additionally make sure the ir emitter is attached to the camera bar and is powered the led light will emit a red glow to indicate it is powered finally ensure that the size of the markers are large enough to be detected at the distance that the camera bar is observing them at the marker calculator can be used to help determine the correct marker size for your setup increase the gain on the camera bar to make the reflective markers much more distinct, using the optional ir filters will also assist with this