-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot find Setting/Connection page #3
Comments
I'm facing the same problem, also with the 1.72.38 version. I suspect that this driver uses a more up-to-date variant, so I'm currently updating TMFlow. I will update this thread once I know more. |
My suspicion was correct: I've updated to system version 1.80.53 and now the 'setting/connection' page is available. |
The instructions should also mention that the robot must be set to manual mode using the remote |
Robot interface warns you that you cannot access in auto mode. I think more importantly this readMe.md file should incorporate the compatible -or minimum- version of the TM Flow. |
@chicostate-mmem I mentioned this because it took me several minutes to figure it out, pretty much by chance, as I was not very familiar with this part, despite having worked with the robot for about a year. The previous software I used to control the robot did not have this requirement. Good point about the TMFlow version. |
@exwzd-kk I would agree with you in the case there is no explicit warning by the robotic system when it runs. If your comment is about the need of having different modes of the system such as auto, manual, remote auto, that is about the architecture of the software and the features which come with it. |
@chicostate-mmem Indeed, I just meant that the having the robot in manual mode, through the use of the I don't think asking for an explicit warning is realistic, unless I contributed to the effort. The mode approach is perfectly fine and it's none of my business to try and change it 😛 |
In our tm5_900 robot arm, we cannot find the Setting/Connection page in the step 3.
Our system version is 1.72.3800.
The text was updated successfully, but these errors were encountered: