Troubleshooting
Instructions for troubleshooting and sending the application logs
If you're facing issues with AMAS please contact our support team at support@extendrobotic.com.
Why is my robot control significantly delayed?
Typically, the round trip latency of the teleoperation system is about 100-200 ms + network round trip latency. The round trip latency is defined as the time delay from when the user moves the digital twin to when the user observes the movement of the corresponding robot arm as seen whilst using the VR headset.
If you observe significantly higher latency, you will likely have one of the following problems.
Exit your AMAS application and check for one of the two scenarios:
If the robot arm stops the movement immediately, then it is most likely your PC is not powerful enough. Check our recommended PC configuration on this page.
If the robot arm continues movement for a delayed period after closing AMAS. This means there is latency in the network and/or router. Network delays can be introduced when using a low-cost switch between the robot and the PC running AMAS. Check for latency between devices on the network.
It might also be the case of bandwidth limitation of your network. You can check our recommended network requirements on this page. The typical behaviour is that:
Your robot is moving with minimal latency (robot control command consumes small bandwidth)
The operator observes delayed visual rendering from cameras, or the render of the feed is dropping frames.
Gather logs from AMAS
We highly recommend sending the Player.log file with the email so that our experts can diagnose the application's problem and recommend the best possible solution.
Follow these instructions to gather the log file:
Close AMAS
Open 'Run' Window.
Please type in the following command,
"%Appdata%/../LocalLow/Extend Robotics/AMAS"and press enter.
Run will then open a file explorer window.
Copy the file named 'Player.log' and send the file.
Why my device cannot connect to the internet?
Some Linux-embedded computers have operating system bugs that limit support for certain Wi-Fi devices. To resolve the issue, try to SSH into the device to activate the Wi-Fi driver.
After reboot, open the command prompt on a PC on the same network as the RoboKit, then in terminal type:
ssh extend@<Robokit/Sensekit_IP>
Please ensure that your device and the client have SSH installed. You can use this command to install SSH on your Linux machine:
sudo apt-get install -y apt-transport-https openssh-server
Last updated