HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » other » visual3dserver » documentation » Visual3DServer Troubleshooting
other:visual3dserver:documentation:visual3dserver_troubleshooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
other:visual3dserver:documentation:visual3dserver_troubleshooting [2024/07/16 19:23] – created sgrangerother:visual3dserver:documentation:visual3dserver_troubleshooting [2024/07/17 15:44] (current) – created sgranger
Line 1: Line 1:
-====== Visual3DServer_Troubleshooting ======+====== Visual3DServer Troubleshooting ======
  
 This page is for Visual3DServer Troubleshooting. If you have a question or a trouble shooting issue that is not addressed on this page please contact support@c-motion.com with the issue. We value your input. This page is for Visual3DServer Troubleshooting. If you have a question or a trouble shooting issue that is not addressed on this page please contact support@c-motion.com with the issue. We value your input.
Line 9: Line 9:
 1. Open run, and type cmd in the "search programs and files" box 1. Open run, and type cmd in the "search programs and files" box
  
-{{RunButton.png}}+{{:RunButton.png}}
  
 Among the programs listed should be cmd.exe which will have the following icon. Among the programs listed should be cmd.exe which will have the following icon.
  
-{{cmd.png}}+{{:cmd.png}}
  
 2. Select it and type in the command ipconfig, as seen below: 2. Select it and type in the command ipconfig, as seen below:
  
-{{ipconfigCMDwindow.png}}+{{:ipconfigCMDwindow.png}}
  
 3. Press enter and several lines of writing should appear. You want to find the line that starts with IPv4. On that line is the IP address which in this example is 192.168.1.100 and circled in red. This is the number that should be entered into the IP Address box for V3D server. 3. Press enter and several lines of writing should appear. You want to find the line that starts with IPv4. On that line is the IP address which in this example is 192.168.1.100 and circled in red. This is the number that should be entered into the IP Address box for V3D server.
  
-{{IPv4circledCMDwindow.png}}+{{:IPv4circledCMDwindow.png}}
  
 ===== Data Quality ===== ===== Data Quality =====
Line 41: Line 41:
 5. If Visual3DServer reports no "ongoing" missed frames (in plugin tab, top left area), then pause Visual3DServer display and then connect TestClient with your script and model. 5. If Visual3DServer reports no "ongoing" missed frames (in plugin tab, top left area), then pause Visual3DServer display and then connect TestClient with your script and model.
  
-{{ServerMissedFrames.png}}+{{:ServerMissedFrames.png}}
  
 6. Allow your cameras, Visual3DServer and TestClient to run for 30 seconds. 6. Allow your cameras, Visual3DServer and TestClient to run for 30 seconds.
Line 47: Line 47:
 7. If TestClient reports no "ongoing" missed frames in status bar, then disconnect TestClient and Visual3DServer, increase the camera hardware rate and repeat steps 4 to 7. You can try doubling the camera rate each time or adding a constant increase. 7. If TestClient reports no "ongoing" missed frames in status bar, then disconnect TestClient and Visual3DServer, increase the camera hardware rate and repeat steps 4 to 7. You can try doubling the camera rate each time or adding a constant increase.
  
-{{ClientMissedFrames.png}}+{{:ClientMissedFrames.png}}
  
 Note: some frames are usually missed during the initial connection between client and server. This is normal. As a result the missed frames count will typically be bigger than 0. However, the value should not be increasing when everything is working properly. Note: some frames are usually missed during the initial connection between client and server. This is normal. As a result the missed frames count will typically be bigger than 0. However, the value should not be increasing when everything is working properly.
other/visual3dserver/documentation/visual3dserver_troubleshooting.1721157790.txt.gz · Last modified: 2024/07/16 19:23 by sgranger